i want to test the nvenc proxy server functionality of xpra.
My proxy multi auth file looks like:
john|heimgeh|1000|1000|tcp:172.17.0.4:10000|EXAMPLE_ENV=VALUE|compression=0 john|heimgeh|1000|1000|tcp:172.17.0.5:10000|EXAMPLE_ENV=VALUE|compression=0 john|heimgeh|1000|1000|tcp:172.17.0.6:10000|EXAMPLE_ENV=VALUE|compression=0
how can i attach e.g. the session to the ip 172.17.0.5 from a client? Maybe its already possible in some way, but i dont know how to do?
Im searching for something like this:
john|heimgeh|1000|1000|tcp:172.17.0.4:10000|session-to-glxgears|EXAMPLE_ENV=VALUE|compression=0 john|heimgeh|1000|1000|tcp:172.17.0.5:10000|session-to-xterm|EXAMPLE_ENV=VALUE|compression=0 ...
and on the client:
xpra attach --username=john --password-file=/home/testing/password.txt tcp:i31forhlr4:443/session-to-glxgears --encoding=h264 xpra attach --username=john --password-file=/home/testing/password.txt tcp:i31forhlr4:443/session-to-xterm --encoding=h264
The "multifile" auth module can return multiple sessions to the proxy server using a CSV format, if you use a line similar to this one:
And the proxy server is able to take into account the "display" attribute of the connection string, so in theory the client could specify which actual session it wants to connect to. But I don't think we support long format display strings in the connection URI. (TBC)
Taking advantage of the two URL forms, you could try something like:
xpra attach tcp/john@i31forhlr4:443/tcp:172.17.0.5:10000
Run the proxy server with "-d auth" for more details.
If that doesn't work, maybe it can be fixed. Otherwise, we would need to support some form of "load balancing".
antoine gives some hints on how to solve it another way....
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1477