Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Router Charts

Click for Router Charts

Router Ranker

Click for Router Ranker

NAS Charts

Click for NAS Charts

NAS Ranker

Click for NAS Ranker

More Tools

Click for More Tools

Under The Covers

When I first received the Sonos package, I was only slightly familiar with its capabilities, and as I set it up, I was puzzled. It clearly had wireless capabilities, but there was no configuration necessary to get the three components - two of which were wireless - talking to each other. Digging deep into the menus I did find a setting for selecting which wireless channel would be used, but everything came up and worked fine on its own. I guess this is the way things should work.

The Sonos Website offered some answers. The Sonos system apparently uses "Sonosnet," which is an AES encrypted peer-to-peer mesh 802.11g-based networking system. You will not see any Sonos components show up on your list of available access points and the system automatically tries to find an open 2.4 GHz channel for itself so as not to interfere with other networks.

A scan of my network turned up three new IP addresses showing that each device was a little stand-alone computer in its own right. A port-scan of each of the devices turned up nothing interesting except what appeared to be an open UPnP port running on a Linux kernel. Sonos has a GPL download page that identifies specific GPL components as well as the Linux kernel version used.

I have a UPnP client on my network, so I was interested to see how it would react to the ZP80 servers. When I turned on my client, both servers showed up and I could navigate deep into their menus to see directory structure, artist name, album names, etc., but I couldn't get the actual music.

There must be something unusual about how Sonos is using UPnP. Since Sonos servers showed up was also a bit of an aggravation. The long server names " - Sonos ZonePlayer Media Server" cluttered up my device's source selection menu and served no purpose. I could not use them, and I could not remove their names from the menu.

At this point in the review, I normally pop off the cover of the device under review and take pictures of the main board. But with these expensive devices using smooth plastic cases and hidden screws, I was not willing to risk marring the case by prying them apart, so I had to rely on what I dug up on the Internet to tell me what was inside.

According to most of the info I saw, the CPU Sonos used for these devices is a Renesas SH-4 processor. I also found a group working on creating custom extensions to the Sonos device, but unfortunately they are doing most of their software in .NET, which will limit its audience.

Wi-Fi System Tools
Check out our Wi-Fi System Charts, Ranker and Finder!

Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Over In The Forums

Hi allIt seems that devices on 5G-1 and 5G-2 cannot "see" each other.On Wireshark it seems some packets can't traverse from one 5G band to the other. ...
Hello, I'm looking for advice for the build in the subject line. I'm a landscape architect starting my own small office. It will be two people at firs...
So I have a newer RT-AC3100 I've been running as my main router the past few months. I also had two older RT-N66 running as APs also. Everything was f...
Is this ok to do ? Also allow only specified ip address.I want to do this my for cousins so i don't have to go over there every time.I notice the 86u ...
About 2 years ago the WAN port on my R7000 died. About a year and a half ago I managed to get Tomato 1.28.0000 -140 K26ARM USB AIO-64K installed, with...

Don't Miss These

  • 1
  • 2
  • 3