Skip to main content

I’ve seen a few other posts on this, but nothing very definitive.

I have a setup that includes two Amps; both are wired - one directly to my core switch, and one to a switch in my bedroom which is in turn connected to the core switch.  Both are using different cable types, and I’ve swapped them out to known working cables to help eliminate that (they tested fine and connected at 2.5GbE for other devices with no errors).  Right now, they are on my old switch but I’m moving from a MikroTik setup over to a Ubiquiti setup.  I don’t use STP on the MikroTik - but the Ubiquiti use STP to prevent loops in the logical topology (I know I can turn it off, I’d like to not do so).

The “Disable WiFi” option is greyed out for both of the Amps.  I can see link lights on the back of each Amp (flickering as data comes in/out); the switches report a 100 full-duplex connection.  Oddly, I don’t see DHCP via the wired interface for them at all - it’s strange, it’s as if they are connected physically, but the port isn’t being used. When they are wired in on my Ubiquiti setup, it seems to be causing loops in the network. 

I’d like to disable WiFi on all but one of my setup (I only have two Sonos units that aren’t wired via Ethernet) to eliminate loops.  I keep most things wired when possible, as it’s an RF unfriendly environment (dense city apartment, lots of WiFi going on around here).

 

I also have two Fives in a stereo pair, which are wired - and I was able to disable WiFi on those (although, it does seem to turn back on at some points… maybe when it upgrades?).


Does anyone have ideas/advice on what I’m doing wrong here?

 

Will that option be greyed out if they are serving the other wireless units?

For whatever reason the Amp wired ports are not seeing a network connection.

I don't have an Amp but on my other Sonos I see the same MAC for either the wired or wireless connection and DHCP assigns the same static/reserved IP to each wired or Wi-Fi. 

I use only dumb switches.


Ok, so I nmap’ed my network, and found one of the units.  Not sure why pfSense isn’t showing the DHCP lease.

Going to http://theaddress:1400/status/wireless shows:

 


Which is the same mode my Five’s show (seems to be disabled), yet the app shows it as enabled.  In fact all of them show this.  Is this not reflective of the actual enabled/disabled state?


One of the amps, in my kitchen, definitely seems like it’s wired - 0 bytes over the wireless:

 

 


For whatever reason the Amp wired ports are not seeing a network connection.

I don't have an Amp but on my other Sonos I see the same MAC for either the wired or wireless connection and DHCP assigns the same static/reserved IP to each wired or Wi-Fi. 

I use only dumb switches.

Huh, I wonder if this is a bug.  If so, it’s going to prevent me from using Sonos reliably on the new setup, unless I disable STP which is rather undesirable.


For whatever reason the Amp wired ports are not seeing a network connection.

I don't have an Amp but on my other Sonos I see the same MAC for either the wired or wireless connection and DHCP assigns the same static/reserved IP to each wired or Wi-Fi. 

I use only dumb switches.

Yeah it looks like they bridge it all (the br0 interface) and use the MAC of the bridge, which makes sense.  Sorry, I posted another response but it seems it’s gone to the moderators (no idea why) with some additional info.

Thanks for the info, ​@Stanley_4 - much appreciated.


Time to do a diagnostic and call Sonos support with the number (Don't post it) as they can see internal data we users can't. 


Time to do a diagnostic and call Sonos support with the number (Don't post it) as they can see internal data we users can't. 

Yeah, I’ll give it a few days here to see if there are any other suggestions before I go there.  But that seems the likely conclusion.


Well, STP issues abounded once I moved to the new networking setup, so as a result Sonos is now all wireless.  So far so good, but I’m uneasy about the inability to be flexible on networking configuration.  Maybe it’s just a bug.

I might raise a support ticket.  I might also just start to look at alternatives, after somewhere around 20 years with a Sonos setup.


Reply