Routing or FW rule(??) 255.255.255.255 (Sonos) requests from WLAN to LAN
-
Hi everyone, I’ve been without my sonos system now for 3months+ as I never took the time to write this document and ask for help, just been too busy with work. I hope you can help me.
I have pfSense 2.3.2 with 4 interfaces : WAN, WLAN, LAN, DMZ (nothing plugged in so can be ignored). I also have a PIAVPN which I use only for my Synology NAS, so this can also be ignored.
The issue I have is that I cannot get my sonos app to connect to my sonos amp when I run the application on my laptop or on any other WLAN device (ipad etc.). The application and my sonos system works fine when I run the application on my desktop which is connected via LAN. My sonos amp is also connected on LAN.
I did a packet capture and I see the following :
192.168.1.156.1901 > 255.255.255.255.1900: [udp sum ok] UDP, length 230
07:05:20.017841 b4:ae:2b:e2:be:5a > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 272: (tos 0x0, ttl 4, id 24544, offset 0, flags [none], proto UDP (17), length 258)
192.168.1.156.1901 > 239.255.255.250.1900: [udp sum ok] UDP, length 230
07:05:20.114570 b4:ae:2b:e2:be:5a > 00:0e:c4:cf:50:ea, ethertype IPv4 (0x0800), length 60: (tos 0x0, ttl 128, id 26457, offset 0, flags [DF], proto TCP (6), length 41)From sonos help, I can see that these are:
1900 (UPnP events and device detection)
1901 (UPnP responses)So I think all I need to route any 1900 requests from WLAN to LAN. Would I also need to route 1901 responses from WLAN back to LAN? My sonos amp device IP is 192.168.0.180
I don't even know if this is a static route that I need to create or a forward in firewall..
thank you for your help in getting my sound system back!!
I am also attaching screenshots of my current configuration.
-
Those are UDP broadcasts that by definition can't be routed across routers. You'd need a specialized proxy in order to make the traffic cross a router and I doubt that anything like that is available on FreeBSD/pfSense for Sonos products.
-
I think people have used Avahi to get Sonos' device discovery to work across different subnets. I've not had to do this myself (I have a Sonos component wired to my network, rather than using their WiFi setup) so I can't provide much insight, but that might give you something else to search for that might turn up results.
-
kpa - thanks.
virgiliomi - my Sonos is on ethernet, my laptop is on Wifi - it seems you have your sonos & the app via ethernet?
re: avahi , i've just installed the package, trying to figure out the specific setup.
in the meantime if anyone has other thoughts - pls share.
thanks
-
virgiliomi - my Sonos is on ethernet, my laptop is on Wifi - it seems you have your sonos & the app via ethernet?
re: avahi , i've just installed the package, trying to figure out the specific setup.
in the meantime if anyone has other thoughts - pls share.
No, my WiFi just doesn't use a separate subnet from the rest of my LAN. I have a specific Guest VLAN/SSID that is separate, but my main WiFi SSID is on the same subnet as my wired network.
Re: Avahi… like I said, I've not used it myself, but maybe this thread might get you pointed in the right direction:
https://forum.pfsense.org/index.php?topic=96160.0
-
Avahi is only for mDNS discovery, not for generic broadcast protocols. If Sonos products use or can be made to use mDNS it should work with avahi.