General
Diagnostic page for bridge, STP, mesh network
https://support.sonos.com/en-us/article/check-if-sonos-is-in-a-wireless-or-wired-setup
http://<IP>:1400/support/review
https://<IP>:1443/support/review
running /sbin/ifconfig
br0 Link encap:Ethernet HWaddr 38:42:0B:16:9D:E2
inet addr:192.168.2.227 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fdea:de6:938:ee41:3a42:bff:fe16:9de2/64 Scope:Global
inet6 addr: fe80::3a42:bff:fe16:9de2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5610124 errors:0 dropped:167047 overruns:0 frame:0
TX packets:1725037 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1317857431 (1.2 GiB) TX bytes:770755563 (735.0 MiB)
eth0 Link encap:Ethernet HWaddr 38:42:0B:16:9D:E2
inet6 addr: fe80::3a42:bff:fe16:9de2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6822179 errors:0 dropped:0 overruns:0 frame:0
TX packets:1733483 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1510189803 (1.4 GiB) TX bytes:771264940 (735.5 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:11420 errors:0 dropped:0 overruns:0 frame:0
TX packets:11420 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:5050373 (4.8 MiB) TX bytes:5050373 (4.8 MiB)
ra0 Link encap:Ethernet HWaddr 00:0C:43:29:23:99
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:60
running /usr/sbin/brctl showstp br0
br0
bridge id 9000.38420b169de2
designated root 8000.0264bfef25eb
root port 1 path cost 34
max age 20.00 bridge max age 6.00
hello time 2.00 bridge hello time 1.00
forward delay 15.00 bridge forward delay 4.00
ageing time 60.00 gc interval 0.00
hello timer 0.00 tcn timer 0.00
topology change timer 0.00 gc timer 3.01
flags
eth0 (1)
port id 8001 state forwarding
designated root 8000.0264bfef25eb path cost 10
designated bridge 8000.2cc81b6c68ad message age timer 15.68
designated port 8003 forward delay timer 0.00
designated cost 24 hold timer 0.00
flags
Fix AirPlay on Mikrotik WiFi
AirPlay problems
Use multicast-enhance=enabled in WiFi configuration
IGMP
IGMP
Mikrotik
https://help.mikrotik.com/docs/display/ROS/Group+Management+Protocol
https://help.mikrotik.com/docs/pages/viewpage.action?pageId=59277403
I have a mixed setup of 4 wired speakers and 3 wireless speakers. I had a setup with two non specifically stp aware routers (aka dump routers without any configuration) in series. In this configuration I had issues and the speakers being furthest away from my wifi router (behind the two lan routers) could not be found by the sonos app. I replaced the non stp supporting routers by one stp supporting router and the sonos app can now see the speakers. I plan to add again a second stp supporting router in the future and I am now more confident that this setup will work, because I can configure stp and igmp snooping on the router and then see the effects on the stp matrix of the devices.
You can see the network matrix of your sonos devices via http://xxx.xxx.xxx.xxx:1400/support/review
https://old.reddit.com/r/sonos/comments/guj5hm/igmp_snooping_and_completely_wired_sonos_set_up/
In general I segregate all IoT things into its own vlan and block traffic via firewall for added security.
As I don’t consider sonos to be a computer or smartphone i considered to segregate it to its own vlan or put it in same vlan as other IoT stuff.
Ultimately I decided against it and am hosting sonos system on same vlan my computers and smartphone reside for few reasons.
- I consider sonos to be more secure than your average IoT stuff. It gets updates quite often and I didn’t see any reports of wide spread sonos targeted attacks or any attacks that were using sonos systems for their needs (botnets, cnc, ddos, data harvesting, etc). Ultimately this is my home network, not a bank and sonos is not accessible from the internet like a web server. It’s already protected by firewall and on some level by IDS.
- I consider sonos to honor my privacy more than your average IoT stuff. This is more of a trust thing. Of course they make their gear “phone home” and give them stats on my network and sonos system usage. I know that and I decided that still trust them enough to not segregate. Besides, they already are doing it from my phone no matter which vlan I’m putting sonos system in - whatever I do I have to provide connectivity in order to use the system.
- Their speakers really are meant to be in same network (broadcast domain) as your phones and computers. It’s doable to segregate in separate vlan and configure it for connectivity but I don’t see real benefits in going through the pain because of points above.
- Sonos speakers tend to generate quite a bit of broadcast traffic. Keeping it on same vlan makes it possible to keep that traffic in check through igmpv3 and igmp snooping and arp proxy on AP.
- To that end I hardwired only one of my sonos speakers, so the system is running on its own sonosnet, turned off stp on that one port and left rstp on all other switch ports. I am using igmp snooping and igmpv3 and arp proxy and my broadcast traffic overhead on wifi is minimal, wired devices get IP through dhcp almost instantly and sonos system is rock solid on sonosnet in my home (8 speakers, your mileage may vary, each home is different).
So yeah, had same dilemma. Decided I don’t want to deal with that. Not because I’m lazy but because I don’t see real reason why should I. For the sake of having “sterile” network? IMHO it’s more philosophical than anything for home usage. Would I do the same in the corporate network i manage? Hell no, but this is my home network we’re talking about. It doesn’t need to be enterprise grade for everything. Ease of use is also important.
https://old.reddit.com/r/Ubiquiti/comments/vjn39s/sonos_on_unifi_vlan_necessary/
If you’re only seeing one product at a time, it’s likely your router is having trouble with multicast. Multicast is a type of network traffic that involves sending data from one device to multiple others at the same time.
While multicast is basic network functionality and should be supported by every router, it’s not something that’s leveraged in most home network environments, and it’s pretty likely Sonos is the only thing you own that needs it. That’s why it might seem like “the network” is fine, but something is still actually wrong.
If that’s the symptom you’re seeing, check your router’s advanced settings menu for a toggle that says “IGMP Snooping”. If that’s off and you turn it on, there’s a solid chance that the problem will go away like magic.Â
It still could be something else going on, but if there is a “quick fix”, that would be it. Other problems could be wireless extenders getting in the way of communication, a second router in the wrong mode, or you’ve got too many Sonos products (a good problem to have, of course, but the maximum number of units on a single system is 32).
Hope this helps!
https://en.community.sonos.com/speakers-229128/disappearing-speakers-its-not-my-wifi-6880563?postid=16645446#post16645446