routed network

Sigh.

If such a company's USP was operation over routed networks they'd have to hope for substantial B2B sales. Most homes have a simple flat subnet, off the ISP-supplied gateway box. The occupants have better things to do with their lives than worry about the niceties of routing.

If such a company's USP was operation over routed networks they'd have to hope for substantial B2B sales. Most homes have a simple flat subnet, off the ISP-supplied gateway box. The occupants have better things to do with their lives than worry about the niceties of routing.

We can ignore the Guest network setting on just about every consumer grade wifi router on the market. We can also ignore the security benefits of using it. However, doing so does not make them go away, not true, or not worth using / implementing.

And yes, there are better things to do than to have to worry about the routing, which is exactly why we need the vendors of our luxury appliances and devices (yup, $200 to $700 per speaker is a luxury item in my book) to make those issues go away.

I've been here a long time, and this is the very first time I've seen the request that Sonos be accessible from a Guest network. Matter of fact, we usually recommend Guest networks for people who want to limit access from guests. So while ignoring the Guest network may not make it go away, I highly doubt Sonos is missing significant sales if they continue ignoring this request. Nor is it any evidence that Sonos no longer innovates.

This seems to be a strange request. I would rather my networked speaker stay within a designated broadcast domain and minimize potential vulnerabilities (in both directions). With that said, it would seem someone diving into the application of multiple subnets in their home network could tackle the associated topics of multicast, bridging, relaying or various other methods of custom configurations. I find it hard to believe there are many users out there in this situation. There are several Linux based routers, firewalls, proxy servers and NMSs out there. I would be interested in hearing more about the home configurations requiring actual L3 traversal and not having the ability to keeps their Sonos on the same network.

In contrast to some posters above, I have a positive outlook on Sonos. This company does not charge for services, upgrades, licensing or support. You simply buy their product and they support it. You get software updates, bug fixes, multiplatform apps and streaming services. All the devices are compatible and very few hardware revisions are made. The product is easy to use and can easily be setup by users with the most minimal of technical skill. I purchased my first Sonos speakers last year and had this realization of the underlying product support and true value provided. With all things considered, I quickly expanded my investment in their products.

I can't think of another (tech) company providing the same level of product quality and support.

The solution most have come up with is to use an IGMP Proxy service to pass the necessary multicast data between networks to allow Sonos to function between two (or more?) different subnets. If you refuse to accept this as a solution only because you want Sonos to figure it out for you, then it's only your loss because the likelihood that Sonos is going to implement something that less than 1% of their customers want is slim to none.

And I'm with jgatie... I've been around here for a few years and never once seen a request from someone that wants what you're doing. Others have wanted to use Sonos across subnets (though not necessarily for guest use), and have been more than happy to implement it themselves with an IGMP proxy.

Agree. This is a networking problem, not a device issue - and Sonos boxes seem to be well behaved network connected devices. Mike, can you save me the research and provide some pointers as to the parameters for such a proxy. I'm assuming my Ubuntu router can run such a server.

An IPv6 packet walks into a bar carrying a duck. The barman exclaims that pigs arn't allowed in his bar. The packet says "it isn't a pig, it's a duck!" to which the barman says - "I was talking to the duck".