[SOLVED] Netgear Wireless N150 Access Point WN604

tronayne · 01-19-2013, 09:14 AM

I'm having problems figuring out how to set up a WN604 for fixed IP Ethernet connections plus wireless.

My current router (a Linksys BEFSR41 Cable/DSL Router with 4-Port Switch) has worked "just fine" with servers and Ethernet printers using fixed IP addressing; i.e., my servers are 192.168.1.10, 192.168.1.20 and so on and an H-P Business Inkjet 2280tn also uses a fixed IP address (it's 192.168.1.15). Network settings for each are the address, the netmask and the gateway (which the Linksys is 192.168.1.1).

Now this WN604 has four Ethernet jacks plus the Wi-Fi antenna. It's default address is 192.168.0.X -- that conflicts with the addressing of my HugheszNet modem/router, 192.169.0.1 (I think it conflicts).

The initial setup for the WN604 is 192.168.0.210, subnet mask 255.255.255.0 (same mask as the Linksys); that allows you to get to the setup menu at 192.168.0.100. It also allows you to get network access via the wi-fi which assigns 192.168.0.3 when connected with WICD.

What I'd like to do is "retire" the Linksys and replace it with the Netgear but I can't seem to figure out how to set the WN604 so that my existing equipment with existing fixed IP addresses, netmask and, most importantly, gateway address (Linksys is 192.168.1.1) will work (so far, nope).

So I'm wondering if anyone can point me in the right direction as to what the WN604 settings should be?

Let's say that one server, pita, is set

Code:

IP Address: 192.168.1.30
Netmaks:    255.255.255.0
Gateway:    Uh, I dunno what it should be for WN604

The setting in the WN604 are only the IP address (192.168.0.210) and the netmask (255.255.255.0); the default gateway is blank, as are the two DNS server addresses (which I don't use in the Linksys, I use DNS server addresses in /etc/resolv.conf). Is 192.168.0.210 the gateway? Arrgghh!

I prefer not to use DHCP on my LAN. The only real reason I got the WN604 in the first place is so my wife can access wi-fi with her Kindle. One option I do have is to use a crossover cable from an unused Linksys Ethernet port to the WN604 to provide wi-fie (that actually works) but that's another piece of hardware cluttering up the place and, if possible, I'd like to just switch the Linksys for the WN604 without having to reinvent all my other stuff while still maintaining fix IP.

Hopeless?

Thanks.

michaelk · 01-19-2013, 09:48 AM

According to the online manual which could be a bit confusing since it mentions two different default IP address for the AP. It does say the access point is set, by default, with the IP address of 192.168.0.100 with DHCP disabled. To change the WN604 plug in a computer to a LAN port and change its IP to 192.168.0.210 and 255.255.255.0 as suggested in the manual.

Log in to the device via a web browser and change the IP to match your old network picking an unused IP address. Once the new IP address has been saved you should be able to reload the computers with its original IP address and reconnect to the access point. Once the device is recognized on your network you can configure the wireless settings as desired.

tronayne · 01-19-2013, 11:12 AM

Well, thanks, I've pretty much got part (I did read and follow the Installation Guide and read the 70-page manual while I was at it).

So far, everything I've tried just doens't want to work, from changing the subnet from 0 to 1 (192.168.0.100 to 192.168.1.100), reconfiguring the computer network (from 192.168.0.210 to 192.168.0.30) and trying to figure out what the gateway address has to be: if you change the IP address in the WN604 from 192.168.0.100 to 192.168.1.100 it demands a default gateway address (and I have no clue what that has to be. Too, reconfiguring the system address with netconfig (Slackware's network configuration utility), it wants system name, domain, IP address, netmask, (optional) gateway and an optional DNS address. Nothing I've tried seems to work.

Sigh.

michaelk · 01-19-2013, 12:11 PM

Is the access point connected to the HughesNet or Linksys router?

You need to change the HughesNet modem/router IP address to match your LAN i.e. 192.168.1.1 255.255.255.0. I would if possible set the dhcp address range to something that does not include your existing devices. The HughesNet router dhcp server might have the capability to configure the same IP address for a device based upon its MAC. This will keep from having to reconfigure the Kindle if its wifi is used outside the home.

The gateway will be the IP address of the HugesNet router. BTW configuring the access point for DHCP all of the settings will be automatically configured. BTW since your devices are using static IP address you might also have to update their DNS information when switching out router.

tronayne · 01-19-2013, 01:01 PM

Quote:

Originally Posted by michaelk

Is the access point connected to the HughesNet or Linksys router?

The access point is connected to the HughesNet box via Ethernet cable.

Quote:

You need to change the HughesNet modem/router IP address to match your LAN i.e. 192.168.1.1 255.255.255.0. I would if possible set the dhcp address range to something that does not include your existing devices. The HughesNet router dhcp server might have the capability to configure the same IP address for a device based upon its MAC. This will keep from having to reconfigure the Kindle if its wifi is used outside the home.

Actually, can't do that -- not allowed to edit that in the HughesNet modem/router setup. The Linksys is addresses at 192.168.1.1 (the gateway address methinks). The Kindle works fine when I've got the Netgear going and it also works fine at the library (you select whatever wi-fi network is available with the Kindle).

Quote:

The gateway will be the IP address of the HugesNet router. BTW configuring the access point for DHCP all of the settings will be automatically configured. BTW since your devices are using static IP address you might also have to update their DNS information when switching out router.

Ah! That might be a workable solution! Didn't even think of doing that (too stuck in my ways, I suspect). Don't know about the DNS stuff, though, I use ISPS provided servers for DNS (in /etc/resolv.conf) in those have been working fine for, well, years (but, then, with a Linksys, different than a Netgear!).

Thanks for the input, I'll give the above a try.

tronayne · 01-23-2013, 06:57 AM

Quote:

Originally Posted by michaelk

The gateway will be the IP address of the HugesNet router. BTW configuring the access point for DHCP all of the settings will be automatically configured. BTW since your devices are using static IP address you might also have to update their DNS information when switching out router.

OK, thank you, that did it (duh!).

The HugesNet thing insists on DHCP, like it or not, and the Linksys, of course, got automagically connected and, uh, "gatewayed(?)" to the HughesNet and I could configure it to gateway at 192.168.1.1 (in spire of the gateway actually being HughesNet's 192.168.0.1).

So, set the Netgear gateway to 192.168.0.1, plug 'er to the HughesNet, viola!, everybody mumbles nicely to everybody else (and, you know, change all my fixed-IP stuff to that gateway address).

Then, just for the heck of it, I put stuff back the way I had it -- Linksys to Netgear with a cross-over cable (had one laying around doing nothing). The wi-fi works just fine and I didn't have to change every piece of gear to different addresses. Hmm.

Madame is happy. Equipment is happy. I'm happy. Sort of a kludge but what the heck, it works -- maybe not "right," but it works and all is well that ends. I might get uppity and remove the Linksys completely but, for now, I think I'll leave it this way and see what happens.

Thanks for you input.