wireguard about go2tv

[alexballas]

Hello!

SSDP relies on multicast traffic. To what I've seen with a quick search, you need to explicitly configure your WG setup to handle this type of traffic. I found this guide https://an0n-r0.medium.com/making-dlna-through-site-to-site-vpn-work-f393629f4ce0 online but I haven't tested it personally. This article addresses a different issue where someone is trying to access a DLNA server (which also relies on SSDP) remotely through WG, but it should give you an idea where to further look at.

Let me know if you have any other question.

Regards,
Alex

[heptagons]

Thanks. I'll check the guide.

1. The error I got is displayed in console mode. It should be nice to notify the error also in GUI instead of an empty list.
2. Forgive my ignorance. Is TVs discovery only possible with SSDP? What about ZeroConf?

Regards

[alexballas]

For 1)
You're right. There should be an error message to indicate inability to pull the device list. I'll improve it in the next version.

For 2)
What go2tv does is use a subset of the DLNA/uPnP specification which is something that all smart TVs and some Audio speakers support. This is described here https://openconnectivity.org/upnp-specs/UPnP-arch-DeviceArchitecture-v1.1.pdf and
SSDP is part of that protocol. It's the actual devices (TV/Speakers) that use SSDP to publish their capabilities to the rest of the network. Go2TV just looks for those.

Zeroconf is an implementation of the Multicast DNS-SD protocol. There are other protocols in the wild like the castv2 that chromecast devices use. Castv2 uses mDNS-SD as per it's specification.
Unfortunately go2tv does not support chromecast devices as also mentioned in #38

[alexballas]

I'll resolve this one for now. I added an extra check in the GUI mode to properly reflect these "unwanted" errors, like we do in the CLI mode