The Raging Battle Over 192.168.1.1
Not sure if this is the fault of the ISPs or the manufacturers of wireless routers, but it seems like more often than not, adding wireless to your network is NOT simply plug-and-play.
Our recent battle pitted Verizon with the ever-popular Linksys WRT54G. The initial setup was quick and making secure connections to the Linksys didn’t even require a glance at the instruction manual. Once connected, though, there was no internet.
A quick comparison of Network Settings in the System prefs when connected directly to the Westell DSL Modem and when connected to the Linksys revealed that BOTH devices thought they lived at the same address: 192.168.1.1
The fix for this wasn’t immediately obvious: changing the IP address of the router to 192.168.1.XX didn’t do anything. Pressing Linksys’ “one-touch config” didn’t do anything, either.
A call to Linksys technical support connected me with a very friendly Indian (it was late at night here in the States) who informed me the address the Linksys should use is 192.168.2.1. Worked like a charm, but not until after an hour was lost to tweaking a dizzying number of config options, restarting devices, swapping plugs and more.
Of course this begs the question: if all of these routers are being sold to consumers who already have cable or DSL (provided by companies who want to charge extra for letting you have a wireless network or lie and tell you that their service isn’t compatible with 3rd-party wireless services), why don’t they ship with the correct IP address to begin with???
For the record: Apple does; their routers use the other local subnet 10.0.1.XX 🙂