In the last post, my home network was a single sub-net and supported wired and ABG wireless devices including a Wii, XBox 360, one wirelessly-connected Color/FAX printer, wired LaserJet printer, two wired desktops, two wireless desktops, and three laptops. In the last week, I’ve replaced this network piece-by-piece as follows:
First, I added a LinkSys 10/100/1000 switch upstairs with CAT6 cable as an adjunct to the existing 10/100 switch and put all the higher-speed networking devices on it verifying that they all negotiated into 1Gb mode.
The most complicated part was replacing the ABG Wireless AP and range extender downstairs with a new dual-band ABGN+ Wireless Router. The initial setup is easy enough, but it assumes optimistically that it would be the only router in the mix and that it would be connecting directly to the DSL modem. NAT was turned on. It defined for itself a new sub-net (192.168.0.0/24). This sorta works, but it wasn’t exactly what I wanted because it was protecting the wireless devices from any access the wired devices might initiate. I didn’t see a way to turn disable the router portion, or I would have done that.
Instead, I have two sub-nets which roughly cut between upstairs wired versus downstairs wireless. The setup is more complicated, but it also offers greater control over traffic. I disabled NAT on the Wireless Router so that it functions just as a Router and Wireless AP. Routing from the wireless side remains easy as all of the routing there depends on being on the same sub-net or having the packet sent to the default gateway (the ABGN+ Wireless Router).
Routing on the wired side is more complicated because some packets are delivered within the same sub-nets, some are sent to the wireless sub-net, and some are delivered to the Internet through the DSL modem. Every single machine on the wired network requires an additional route be added manually:
- Windows: route -p add 192.168.0.0 255.255.255.0 192.168.1.4
- Linux: route add -net 192.168.0.0. netmask 255.255.255.0 gw 192.168.1.4
- FreeBSD: route add -net 192.168.0.0 192.168.1.4 255.255.255.0
Even the 327W router/modem needs to be told (or told how to learn) how to route packets to the new sub-net. Under “Advanced WAN/Route”, I needed to add the above information. The final (and possibly unexpected) kicker to the routing problem is back at the 327W DSL router/modem. It needs to be told that the “Private LAN” is no longer 192.168.0.0/24 but 192.168.0.0/23 (or 192.168.0.0 netmask 255.255.254.0). The reason for this is that the routing decision is not made until the router asks itself whether the packet is even for this private LAN. If a packet falls outside the private LAN range, it drops it.
The HP TouchSmart continues to use its 802.11G wireless operating at 50Mb/s. The Wii sees 802.11B. The other desktop received a new ABGN+ dual-band PCI Wireless adapter and is running at over 100Mb/s wirelessly.
Finally, for the XBox 360, I bought the N dual-band bridge. The ABGN+ dual-band Wireless router uses both bands simultaneously, but the clients of it are assigned mostly to one or the other band. I disconnected the XBox 360 wireless adapter, connected the console to the bridge via Ethernet the way it really wants to be connected, and assigned the bridge to use the 5Ghz band exclusively. Now, the XBox 360 plays movies without a hitch, and it signs in instantly without the previous ten minute wait.
Everything is separated by switches , routers, and bands, and it all works very, very smoothly without any additional wiring required. Every device can ping and use every other device (well, I can’t exactly copy files off the Wii or XBox 360, but you get my drift).
That’s it about the network. If there is a next post, it would be about my unspeakably weird home computing setup.