-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discovery of devices connected via VPN #79
Comments
Hello! Device discovery uses ZeroConf/mDNS, which requires multicast. I believe it would be doable to enable this over WireGuard, but I don't have experience with it. A cursory Google search seems to indicate it would be possible to enable multicast on the WireGuard interface? Whether you can get discovery working or not, you can set the |
Hello, thank you for your quick response. A first try to enable multicast on the VPN server side did not work, so I have to look further into it, and maybe change the config on the CC, too. I'll post here if I am any wiser! Edit: Adding the external IP ( |
Hello everyone,
I have a CCwGTV that I use for traveling, and it would be great if I could also use CastSponsorSkip (CSS) with it.
My Setup is like this:
NAS with OpenMediaVault, running Docker and CSS (LAN IP: 192.168.0.100)
PiHole on a OrangePi Zero, with a Wireguard server (LAN IP: 192.168.0.3)
The IPs of the Wireguard clients are in the 10.100.0.x range.
I hoped that connecting the CCwGTV via Wireguard would do the trick, but unfortunately the device is not found by CSS, neither with limited IP ranges for the traffic, nor with all traffic routed through Wireguard.
Is there something I can do to make this work, or is there a different solution for CSS to discover a remote CCwGTV?
The text was updated successfully, but these errors were encountered: