![]() There is a section about configuration settings that can be changed with registry keys. I found the documentation of Windows UPnP APIs. But these devices are not displayed in Windows Explorer. The IPv6 address ff02::c is a link-local multicast address and is not routed to the other network, but the request sent to 239.255.255.250 does reach the other network and answers from devices there reach the local network. When hitting Ctrl+F5 in the Network view in Windows Explorer, I can see SSDP M-SEARCH requests being sent to the multicast addresses 239.255.255.250 and ff02::c. I completely disabled Windows firefall for testing (no other firewall products installed).Network discovery and file and printer sharing are both turned on for the active network profile (Private) in advanced sharing settings.The Function Discovery Provider Host service (fdPHost) is enabled and running (although to my understanding this is not necessary for service discovery). ![]() The Function Discovery Resource Publication service (FDResPub) is enabled and running.I checked and tried the following things already: However, the Windows Explorer only shows devices from the local network in its Network view. In VLC on Windows, multimedia devices from both networks are found with mDNS as well as UPnP (SSDP) and can be accessed. local Domains works well across both networks, thanks to avahi-daemon reflection. On Windows 10 (21H2), mDNS name resolution of. This works well, both MDNS and SSDP packets travel from one network to the other, I checked it with Wireshark. On both VPN gateways, avahi-daemon works as mDNS repeater ( enable-reflector=yes) between the local network and the wireguard tunnel, and smcroute is set up to forward routable SSDP multicast packets (sent to 239.255.255.250, ff05::c, ff08::c) from the local network to the wireguard tunnel and vice versa. IP traffic (v4 and v6) travels fine between the networks. Routes to the other sites are configured in the default gateways and also distributed to the clients over DHCP. I have the following scenario: Two sites, each with their own network (non-overlapping private subnet), connected with a site-to-site VPN (layer 3, Wireguard).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |