netflector available as plugin (mDNS, SSDP, DIAL, WSD, WoL reflector)

[UnicronHD]

I am also using igmp proxy between my iptv wan and vlan.

Do you think I could also configure this with Netflector?

Have a look at this : https://forum.opnsense.org/index.php?topic=51192.msg262139#msg262139

It keeps IPTV issues nicely away from your OPNsense :)

After setting things up and making sure IPTV works, I packed the TV box from KPN and started using an app. Much better experience and no need in IGMP proxy :)

[vicking]

I am also using igmp proxy between my iptv wan and vlan.

Do you think I could also configure this with Netflector?

Have a look at this : https://forum.opnsense.org/index.php?topic=51192.msg262139#msg262139

It keeps IPTV issues nicely away from your OPNsense :)

Nice, never thought of that! And let it be the case I have a rpi laying around doing nothing! I also run a truenas server so instead of plugging in another device I think I will run an extra Debian VM. I have my kpn iptv in a separate VLAN and everything (working) and configured in opnsense, so have to figure out what needs to be kept in opnsense and what I can delete! I feel a nice weekend project coming up! 😂

[vicking]

After using netflector for two days I notice that I regularly cant find my Sonos systeem in the Sonos app because it is on a different VLan. With the old udpbroadcastrelay plugin in combination with the mdns repeater I never had these problems. Am I missing something?

[nero355]

After setting things up and making sure IPTV works, I packed the TV box from KPN and started using an app.

Much better experience and no need in IGMP proxy :)

Even better if the picture quality is the same! :)

[UnicronHD]

After using netflector for two days I notice that I regularly cant find my Sonos systeem in the Sonos app because it is on a different VLan. With the old udpbroadcastrelay plugin in combination with the mdns repeater I never had these problems. Am I missing something?

Thanks for the report. First check the direction of your reflector. Unlike udpbroadcastrelay and mdns-repeater, netflector relays one way: Source is the VLAN the phone with the Sonos app is on, Target is the Sonos VLAN. If the app runs on more than one VLAN (say, two SSIDs), each one needs its own reflector. If yours is the other way round, swap it and see whether that alone fixes it.

If the direction is right, there is one real difference from your old setup. udpbroadcastrelay forwarded SSDP (UDP 1900) unchanged, so the Sonos app saw every speaker announcement and search reply coming from the speaker's own IP. netflector relays SSDP through the firewall instead: those packets reach the app from the firewall's address, and the speaker's address is only in the LOCATION header. Some Sonos software, the SoCo library for one, takes the speaker address from the packet source and ignores LOCATION. I haven't confirmed the Sonos app does the same, but it would explain what you see.

To test that:

• On your current reflector, untick SSDP and leave mDNS on.
• Add a second reflector with the same Source and Target, Bidirectional ticked, no protocol boxes, Relay ports 1900 and Multicast groups 239.255.255.250.

That relays SSDP unchanged, as udpbroadcastrelay did, so it relies on the firewall rules you had for it: the speakers answer the app directly, from the Sonos VLAN to the app's VLAN.

If the app still loses the system after that, please post the reflector settings (Source, Target, Bidirectional, the protocol boxes, mDNS services, Devices) and, with Counter interval set to 60, the counter lines from Services > Netflector > Log File around a failed attempt.

[vicking]

After using netflector for two days I notice that I regularly cant find my Sonos systeem in the Sonos app because it is on a different VLan. With the old udpbroadcastrelay plugin in combination with the mdns repeater I never had these problems. Am I missing something?

Thanks for the report. First check the direction of your reflector. Unlike udpbroadcastrelay and mdns-repeater, netflector relays one way: Source is the VLAN the phone with the Sonos app is on, Target is the Sonos VLAN. If the app runs on more than one VLAN (say, two SSIDs), each one needs its own reflector. If yours is the other way round, swap it and see whether that alone fixes it.

If the direction is right, there is one real difference from your old setup. udpbroadcastrelay forwarded SSDP (UDP 1900) unchanged, so the Sonos app saw every speaker announcement and search reply coming from the speaker's own IP. netflector relays SSDP through the firewall instead: those packets reach the app from the firewall's address, and the speaker's address is only in the LOCATION header. Some Sonos software, the SoCo library for one, takes the speaker address from the packet source and ignores LOCATION. I haven't confirmed the Sonos app does the same, but it would explain what you see.

To test that:

• On your current reflector, untick SSDP and leave mDNS on.
• Add a second reflector with the same Source and Target, Bidirectional ticked, no protocol boxes, Relay ports 1900 and Multicast groups 239.255.255.250.

That relays SSDP unchanged, as udpbroadcastrelay did, so it relies on the firewall rules you had for it: the speakers answer the app directly, from the Sonos VLAN to the app's VLAN.

If the app still loses the system after that, please post the reflector settings (Source, Target, Bidirectional, the protocol boxes, mDNS services, Devices) and, with Counter interval set to 60, the counter lines from Services > Netflector > Log File around a failed attempt.

Thanks for the detailed answer! The diretions are right, I have now made the changes you suggest and will report back after a while of testing. For now the Sonos app doesn't see the speakers, but I will give it a while before the changes become active.

To mention, I didnt make any specific firewall rules for it.

Edit: Aaaand bam, there are the speakers again in the app. Started to work after the change in Netflector! :D
One thing, do I also need to tick "Broadcasts"?

For now, thanks for this!