SONOS Sound System breaks RT-N66U

[rickms80]

I need help. As soon as I connect my Sonos Bridge to the router I can't view the routers online GUI correctly. It's corrupted. I also have firmware .102

Attached an image of the GUI.

Everything else seems to be working correctly to knowledge.

 

[harvad]

Sonos Bridge breaks the GUI

I have exactly the same issue.

Im running .108 but also had the issue with .102

I have raised a ticket with ASUS support.

I wondering if this is a general "Bridge" issue.

I have ordered a TEW-680M bridge and will check if that one breaks the GUI too

Br,

 

[RogerSC]

I have a Netgear WNCE-2001 bridge, and it works fine with the rt-n66u GUI. In fact, the router makes the bridge's IP into a link in the client list, and I can go to the bridge configuration by clicking on that link in the client list.

So it's working well, at least for that bridge.

 

[rickms80]

I will say that after leaving things in place, no rebooting or resetting, that the gui eventually started working again after about 5 days or so with .102. After upgrading to .108, it was of course broken again.

Not sure about getting a wireless bridge to connect to a speaker. Seems like that defeats a feature that sold me on the SONOS system anyways. Creates it's own wireless mesh keeping it off my wireless.

 

[harvad]

@rickms80
Fully agree with you on the intended functionality of SONOS - but I'm referring to the SONOS bridge, i need the bridge to reach my most distant players and i happen to have a switch in the same closet ;o) so that is why i'm using a "bridge"
Yesterday i tried to skip the bridge and just connected one of the players via ethernet and experienced the same behaviour with the GUI - so i think it's the way that SONOS does the bridging in general.
Some bridges changes the MAC addy of the device with it's own and pass through the IP addy of the device (Cloning) and other Bridges can pass through both the MAC and IP of the client so that there is a propper 1:1 mapping - i have a suspecion that is where things go wrong - as it seems the n66u GUI is stuck trying to resolve the MAC and IP of the players.
I will get a sniffer hooked up one of the next days - that should give me some more meat on the bone.
- Its good info that you have seen it settle down eventually, Thanks.

 

[rickms80]

ohhh ok. I thought you meant you were buying a Wireless to Ethernet bridge connecting the Ethernet to one of the speakers. I also have the SONOS bridge with it connected directly to my router. I'd love to know where this goes and why.

 

[rickms80]

Just fyi mine started working again. I rebooted router and quickly clicked the clients Icon on the network map section and so far the GUI hasn't broken.

 

[harvad]

Mine is still FUBAR - I have to disconnect my SONOS - and reboot the system when i want to make changes to the config.

A little cumbersome - but works for now - normally i don't mess with the config that much. So I guess i will live with it until ASUS gets time to fix it.

Apart from the broken GUI i don't see any "misbehaving" due to this.

I got my 3 stream bridge yesterday - the TEW-680MB from Trendnet
That one works like a charm and does not give the issues the SONOS bridging implementation does.

The TEW-680MB bridge comes with 4x 10/100/1000 ports and is dualband WiFi@450Mbps - and so far im very impressed with it. It's taking care of my PS3-ATV-Boxee Box and TV connection and I see a massive performance improvement when ie. streaming BD material to the TV from my Synology NAS.

 

[alterbridge86]

just tossing my name in as one of those affected by broken web-gui rendering with SONOS connected Just got the router today and it is friggin awesome...was going crazy trying to figure out why the GUI kept glitching every couple minutes, looks like now I found my answer though

A reboot does clear the glitch, but it returns fairly quickly Hope Asus can get this fixed up soon!

 

[frimp]

Hi all,

I have the same problem with the GUI, also with Sonos systems in the network.
So I switched to Tomato by shibby.

Well, what can be the reason? The Sonos uses multicast and upnp broadcasts, also it uses Spanning Tree on all interfaces. I think this is a good starting point to look at.
I have a separate Cisco switch where all LAN-devices are connected, including the RT-N66U. There are no other devics attached directly to the Asus. I'm wondering if I can drop multicast and upnp directly on the switchport or on the Asus, but couldn't find a way.
This is crazy: no other device is failing in this setup, so I have to blame Asus.

 

[srinivasvaradaraj]

To drop multicast as a test, do the following,
1) Back up your configs so you can restore if things go horribly wrong.
2) Enable telnet on the device, administration > system > enable telnet.
3) telnet to your router from a command prompt.
3) To drop multicast on an interface pls type ,
ifconfig br0 -multicast
This will disable multicast on the internal bridge LAN interface. If you have multiple internal VLAN interfaces, you can do the same for each. Please note this settings won't survive a reboot.
-sri

 

[frimp]

Hi all,

has anyone opened a ticket at Asus for this fault?
I would do that, but I changed to Tomato, because I have to enter a lot of DHCP configs and try out a lot, while my wife uses the Sonos system.

 

[mnmr]

I realize that this thread is old, but I'm having the same problem and found the cause:

Sonos equipment announces itself on the network using names that contain newline characters. Asus web interface builds a single string of all client names, and doesn't remove the newline characters, which in turn breaks the web interface and pretty much everything else.

I've reported the issue two months ago but have now given up on them.. anyway, just thought I'd let people know what the cause is in case someone knows someone that might get it fixed for us normal mortals eventually.

 

[RMerlin]

I realize that this thread is old, but I'm having the same problem and found the cause:

Sonos equipment announces itself on the network using names that contain newline characters. Asus web interface builds a single string of all client names, and doesn't remove the newline characters, which in turn breaks the web interface and pretty much everything else.

I've reported the issue two months ago but have now given up on them.. anyway, just thought I'd let people know what the cause is in case someone knows someone that might get it fixed for us normal mortals eventually.

I discussed this issue with Asus a few weeks ago, and sent them some code that I use in my own firmware to fix the issue. I thought they had integrated it in 354. What my patch does is it simply replace any invalid character in a device name by a space, taking care of quotes, newlines, etc...

I would recommend contacting Sonos about this too, since having a newline in a hostname is clearly a violation in terms of allowed characters.