
If someone can help me understand more about the designated root, that would be helpful. My issue here is that we have been having ongoing intermittent network issues that I suspect is caused by broadcast storms and right now, I am focused on trying to accurately understand how the network is working as a first step. When I go to the designated root for all nodes shows as 8000.325e13xxxxxx - I have tried to identify the device on my network using arp tables and also using a MAC lookup to identify the manufacturer but I have been unable to find anything resembling even a distant match. It would seem that one way or another, based on the network matrix, all other units are adequately able to make wireless connections either directly to this node or to another, tertiary node.ģ. This Connect, (KITCHEN) is identified as a secondary node in the network matrix. There is only one Sonos device (Connect) with a wired connection into a TP Link Switch which in turn is plugged into an Arris wifi phone/cable modem gateway. All Sonos units are identified as either secondary or tertiary units which to me is fine but would indicate that another, non-Sonos device is acting as root. Your clients will still receive an address from the IP>DHCP-Server>address-pool.Just continuing to try to do some diagnostics on a buddy's Sonos setup and having difficulty identifying the designated root based on its mac address. You can disable this feature by setting IP>HotSpot>Server>address-pool=none.


The second will be from after the client has updated it's IP with your DHCP server.

There are two entries using the same MAC, the odd IP would be the Ip the client had from a previous connection.

Your first two examples in the screenshot show this. The hotspot sometimes detects old IPs a client might have had from a previous connection to another device before the client updated it's DHCP information for the current connection. When you set a address pool under IP>Hotspot>Server, the hotspot will use the pool to create a one to one NAT to allow clients with static IPs to be able to connect to the hotspot. Those are most likely clients that have static IPs set in their network adapter. Hello i have configured my Hotspot pool 172.16.0.0/16īut in Hosts i see some addresse and i don't know where they come from
