Xpra: Ticket #1332: mdns discovery of sessions

Make mdns more useful.

It should be easier to see which sessions are available on the LAN. Tools like avahi-discover aren't very user friendly and don't know about our service type.. (#731)



Thu, 06 Oct 2016 08:01:28 GMT - Antoine Martin: owner changed

Notes:


Example:

$ xpra start --bind-tcp=0.0.0.0: --mdns=yes --session-name=hello
$ xpra list-mdns
Looking for xpra services via mdns
* user 'antoine' on 'desktop.local'
 session 'hello', uuid=bce14c3aeed34c7892aea576ea8d78a8
 + ssh endpoint on host 192.168.1.200, port 22, interface eth1
   "ssh/antoine@192.168.1.200:22/2"
 + tcp endpoint on host 192.168.1.200, port 14500, interface eth1
   "tcp/antoine@192.168.1.200:14500/2"
1 service found
$ xpra info | grep uuid
server.uuid=bce14c3aeed34c7892aea576ea8d78a8

(works equally well for ssl sockets and the quoted uri should be usable as-is)

@afarr: mostly a FYI.


Wed, 12 Oct 2016 06:18:29 GMT - Antoine Martin:

Pull request for avahi: add Xpra service type


Mon, 24 Oct 2016 19:25:15 GMT - J. Max Mena: status changed; resolution set

Neat. Closing.

Note: if a server is on the non-standard port, this will not find it. Makes sense(because one would be deviating from the standard, and it'd be unreasonable to try to check every single port), but just wanted to note it for future reference.


Sat, 23 Jan 2021 05:21:21 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1332