<?sphp $this->text('pagetitle') ?>
Home of the Squeezebox™ & Transporter® network music players.

Network Design

From SqueezeboxWiki

(Redirected from NetworkDesign)
Jump to: navigation, search

This page needs editing. Great content, but dated. Needs to be brought into the modern world of networking.


Network Design for the Squeezebox

The Squeezebox is a device on a home network, just like a PC, laptop or networked printer .

For some new users, adding a Squeezebox may be your first step into multiple-device home networking.

If you've added a second PC to your home network, the process of adding a Squeezebox is identical.

A Basic Broadband Internet-Connected Network

Network diagram basic.jpg

This is the most basic home network of all. If you have broadband Internet service, you likely started out with something like this.

Adding a Squeezebox

Adding a Squeezebox is equivalent to adding a second computer to the network. If you didn't require Internet access, you could connect your primary computer's network interface card (NIC) directly to the SliMP3/Squeezebox/2/3 using a crossover cable. (The ethernet port in the Squeezebox Receiver is auto-sensing, so a crossover cable is optional here.)

However most people want Internet access, and the Squeezebox needs Internet access as well for SqueezeNetwork.

One way to do this is directly through the primary PC. Add a second NIC, wired or wireless, to the PC and enable "Internet Connection Sharing" (ICS). If the NIC is wireless you've created an "ad-hoc" network.

Network diagram adhoc.jpg

Though this is simple, it doesn't have the security advantages of a router (see below) and it may not be as reliable or as easy to troubleshoot if you have problems.


You could use something like the above if you're on dial-up. You can connect the PC's NIC directly to the Squeezebox. To access the Squeezebox and other devices wirelessly, you could either use a wireless NIC in the PC to create an ad-hoc network or connect the PC's NIC to a WAP (see below). To connect wired to multiple devices, connect the PC's NIC to a network switch.

Note you will not have the bandwidth necessary to use SqueezeNetwork, but if you enable ICS any other devices on the network will have Internet access.

The Optimal Arrangement

A much better arrangement is to use a router to "split up" the Internet connection.

Network diagram full.jpg

Here your Internet connection is shared among all the devices connected through patch cable or wirelessly to the router. Note most wireless routers also have 4 wired ports. All the devices can see each other as well, sharing files and printers. Note that SqueezeCenter transfers audio data to the Squeezebox much like file sharing. The router can handle networking requirements like DHCP and creates a private network isolated from the Internet yet still able to interact with it. Finally, the router adds a layer of security as most routers have firewalls.

Note in Europe, modem/routers are common, where the modem and router are combined in one device which is usually purchased by the user. In North America, the modem is usually separate and often owned by the ISP.

It's possible to use a network switch or a hub instead of a router. A switch will not have the security of a router and will not have a DHCP server either. You will be relying on your ISP to provide a series of IP addresses for all your internal devices. Each device will be directly connected to the Internet. (Please see discussion concerning the previous two sentences.) A hub adds another significant limitation - while a switch will direct packets to the appropriate device, a hub will echo all packets to all devices and it's up to each device to sort out what is addressed to it. This can lead to congestion. Hubs are effectively obsolete.

However, a switch is useful if you run out of wired ports on your router.

Note you can run the SqueezeCenter software on the desktop PC or the NAS (Network Attached Storage). Running SqueezeCenter on your NAS device means that you can access your own music library without having your computer turned on. You can run SqueezeCenter on a device with a wireless connection, but this creates two wireless hops between SqueezeCenter and the Squeezebox. This may be problematic for some. If you're experiencing problems caused by wireless bandwidth restrictions, always ensure your SqueezeCenter is wired first. This is usually easier anyway, because you'll probably want to keep your router and music library computer of NAS out of the living space anyway.

Wireless Access Points (WAPs)

A Wireless Access Point (WAP) is a device that connects to a wired network and creates a wireless network that can access the wired network. A wireless router will contain a WAP - think of a WAP as the radio portion of a wireless router broken out into a separate device.

You would use a WAP if you have a wired network and want to add one or more wireless clients. These wireless clients may be too far away from your existing cabling.

Network diagram WAP.jpg

WAPs are not as popular as they once were. Wireless routers have dropped in price so much that it can be more economical to replace a wired router with a wireless router and use the wireless router's wired ports to handle the wired portion of the network.


The Squeezebox2, Squeezebox Classic, Squeezebox Receiver and Transporter can act as wireless bridges. A wireless bridge is like a WAP operating in reverse.

A wireless bridge, as the name implies, acts as a "bridge" between the wireless network and a wired network. It accesses the wireless network and provides a wired ethernet port linked to the wireless network for a wired device.

As it is implemented in the Squeezebox, the bridge really functions like a wireless NIC, providing access to the wireless network for one wired device. However, if you were to attach a switch to this port, you could have more than one wired device linked to the wireless network. A switch would be perfect here if you already have a router upstream.

Network diagram bridging.jpg

The ethernet cable between the Squeezebox and the wired device should be a crossover cable for all models of Squeezebox except the Squeezebox Receiver (which has an auto-sensing ethernet port).

To enable bridging on a Squeezebox with a display, plug the ethernet cable in and go back to network setup by pressing and holding left on the remote for 5 seconds or by power-cycling the unit. Press up or down on the remote to enable wireless networking. When wireless networking is enabled but a cable is also connected, the SB will prompt to enable bridging.

For a Squeezebox Receiver, the procedure is slightly different. Robin Bowes' 'Net-UDAP' utility (described in this forum thread) should be used. 'Net-UDAP' allows the user to remotely configure the network settings for the Receiver, including the bridging feature. Users may find it easier to first configure the Receiver to connect to their wireless network in the normal way (using the Squeezebox Controller), and then use 'Net-UDAP' to simply enable bridging (the existing wireless settings should be retained).

Installing SqueezeCenter on the bridged device may at first seem a little circuitous and convoluted but Slim Devices' CEO and chief Squeezebox designer Sean Adams confirmed it should work well here. The Squeezebox is not merely a simple wireless bridge, it recognizes traffic destined for itself originating on the wired side and will process them. This is an interesting option: the Squeezebox can take advantage of the vast, reliable bandwidth between it and SqueezeCenter offered by the wired ethernet link, yet still have wireless remote access to SqueezeNetwork and the rest of your network.

Finally, note that wireless bridging and wireless access point technology are not identical. A Squeezebox functioning as a wireless bridge will not act as a WAP - a wireless client cannot see the Squeezebox as a wireless network access point.

Other Resources

/Linksys images used with permission of Cisco Systems, Inc./