Static IP address

Beynym, are you serious? What you're saying makes no sense on multiple levels. Static IP's hard to maintain? Like how? They need to be watered or fed? Or maybe groomed? Really?

So, you are happy to be restricted on how you could configure your device? I am not. I want to have options to do with it as much as I can. That makes ME happy. To see that the manufacturer took the time to implement good software,not asking me to change everything I have just because they want to protect me from making mistakes.

There is a quick cure against IP conflicts: it's called a list. It could be done the old fashion way,pen&paper, or on a tablet. Why do I even waste my time here? Because you made us stupid ( me and all the others above) for asking for something that SHOULD be there for a device commanding this amount of money. Read some replies from other " argumentative" people above. Maybe you'll educate yourself why we ask for this.

I have no skin in the game, i kept the Bose system. Same price and 5 minutes to configure.
I just love those guys who spend time at forums of products they don't own..

I just love the people who troll this forum arguing against an OPTION that they would never use because they can't handle consulting a list BEFORE assigning a static address and therefore always had conflicts in doing so.  You are why many devices warn that you must be a professional with knowledge of networks before enabling these features...  also probably why there is instructions on SHAMPOO...  I Have hundreds of networks online with static addressing for all permanent hardwired fixtures.  DHCP is for user level devices, iphones, laptops, tablets, etc.  Not for infrastructure, control, and automation.  I am not only a user but an integrator, it's what I do.  DHCP is why the "proper" reboot sequence is modem, router, then ALL your devices.  I don't EVER want to roll a truck to reboot all 100 devices on someone's network because they got lost in the land of auto-IP because their DHCP requests timed out.  My networks come back online as soon as the switch is back up.  The router just allows for outbound comms.  In other words, with static IP, when things fail you'd still see all your rooms up, you'd still have access to line in sources, when you go to online sources such as TuneIn or Pandora, it would say station list unavailable, Pointing the user to the fact that his/her internet is down.  He/She would then reboot their router and modem if my (statically assigned) PDU wasn't already doing so for them.  All they need to do to fix stupid is and stupid does is make an additional network reset procedure, like factory reset except maybe holding the volume down while applying power instead of mute.  That way when tweedle dee and tweedle dumb muck up their static addressing (again) tech support can walk them through performing a network reset instead of issuing an RMA for something that "doesn't work" because they disregarded the warnings that they should know what they are doing before changing these settings because the hundred devices they have bought and connected using defaults should have made them an expert...

Hi Putting manually static ip address into the device is dangerous because you have to keep a list of used ips somewhere to not use the same ip twice and have network problems. As Sonos advised is better to use a router dhcp mapping to set a mac address with a specific ip.

SONOS is standards driven and they use UPnP under the covers. UPnP requires DHCP.

I have some friends who are hard core network types and would never own SONOS simply because they can't assign static IP addresses. This is a shame because SONOS would become the most trouble free client on their network.

I recently mentored a networking guy who usually operates in the corporate network environment where one uses managed switches and routers. While SONOS usually "just works" when used with consumer level network gear, the corporate guy struggled with SONOS because, ... er ... he didn't quite get his corporate level network settings correct. In this particular case, static addresses would not have been any help.

For the audience that SONOS is targeting, DHCP is the way to go because these users do not have the technical skills or interest to fully manage a network.

@buzz,

So what do you think about reserving IPs on the router for each Sonos product?  

It would still default to DHCP and to the average user, they'd never even know there was an option.  Just like with home networking.  Everything defaults to DHCP and it takes experts like us to dig deeper and go static.  Why not have the choice?  UPnP does not require DHCP, I don't know where you heard that...  It's just plain wrong.

{taken from Wikipedia on UPnP protocol}
The UPnP architecture supports zero configuration networking. A UPnP compatible device from any vendor can dynamically join a network, obtain an IP address, announce its name, advertise or convey its capabilities upon request, and learn about the presence and capabilities of other devices. Dynamic Host Configuration Protocol (DHCP) andDomain Name System (DNS) servers are optional and are only used if they are available on the network. Devices can disconnect from the network automatically without leavingstate information.
{end Wiki}

Please refrain from saying you can't handle managing a static IP environment and therefore it shouldn't be an option.  For those of us who can and do, life is much easier.  To each his own, don't limit me because of your ineptitude.  Sonos already has massive amounts of hidden tools that the consumer knows nothing about.  This would be hidden along with them.

@buzz,

So what do you think about reserving IPs on the router for each Sonos product?  
It's a good idea to reserve all devices that are regular network clients.

If you are using any of the original SONOS controllers, they have an IP address too.

yep... and isn't it curious that wikipedia considers DHCP as optional... as in, it is a moot point...  There can be no network traffic UPnP or otherwise without a link.  DHCP or otherwise link is established then network traffic is started.  Yes, All UPnP devices must default to DHCP for true plug and play but as long as they can establish a link they do not care how that was done.  UPnP still functions under static so stop trolling.  You know nothing of networks.

By the way DCP does not in any way equal DHCP moron

For me, Infrastructure type equipment that lives on a shelf and does whatever it does, should be hard wired and set to a static IP.
They aren't going anywhere and this keeps quite a bit of (limited) throughput off the wifi band.
Done.
Phones, tablets, laptops (i.e. people) come and go on the network, only represent one user worth of throughput and typically prefer to be wireless.
And because the printer, scanner, NAS, SONOS or other device is hard wired, the bit stream goes to the access point antenna and then stays on hard wire to or from its destination instead of being broadcast back out to a wireless device...

Statit IP's 192.168.1.1 through 192.168.1.50 or 192.168.1.200 even for infrastructure, and let the DHCP assign IP addresses after that.
How many darn items can you actually have anyhow...? 50? 100?... 200...!?
Set it and forget it for the stuff that sits there and DHCP for the rest.

Why not add a little extra soho network security is to give your router an exclusive list of MAC addresses??

It is wicked annoying you cant assign a SONOS device its own IP address, though.
Just seems kinda silly to not have that interface.
My SOHO network days only go back to win 95 over BNC and even there they had this in the tcp ip settings....
Almost like you;d have to go out of your wat to not have this feature.