Problems setting up static ip

square_imp · 12 Jul 2008 at 16:52

Hey all,

I am having a few problems setting up a static ip at the moment. The hardware I am using is a Linksys AM200 ADSL modem, an apple airport express router and a Dell XPS M1330 laptop with vista 32bit. I have tried to find my static ip by running a command window and typing "ipconfig /all" which does then list the wireless information as follows:

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix :
Description : Intel<R> Wireless WiFi Link 4965AGN
Physical Address : 00-1D-E0-46-7A-4B
DHCP Enabled : Yes
Autoconfiguration Enabled : Yes
Link-local IPv6 Address :... (normal IPv6 format address)
IPv4 Address : 10.0.1.197
Subnet Mask : 255.255.255.0
Default Gateway : 10.0.1.1
DHCP Server : 10.0.1.1
DNS Servers : 10.0.1.1

Basically I thought I need an ip address in the form of 192.168.0.1 or similar, the other computer in the house that receives wireless internet lists its ip address as 10.0.1.199.

Any help with this would be great, I am clearly missing something obvious.

Defiance_co · 12 Jul 2008 at 17:13

Just looked at my o2 letter that came earlier

It's Subnet Mask is 255.255.254.0 Does mean anything to you ??

Only had cable n dialup so all this funky stuff is new to me lol

tolien · 12 Jul 2008 at 17:21

Ignore the O2 letter - it's what they do on the internet side, versus what you're trying to do with the LAN...

The machines need to be in the same subnet (i.e. the first three octets have to be the same), so a 192.168.0etc IP would be as much use as breasts on a fish.

Rabtech · 12 Jul 2008 at 20:02

Basically you have 2 x DHCP servers running, one in the AM200 and one in the Airport Express, the AM200 will most likely use 192.168.1.x before it hits the airport express and then the airport express uses 10.0.1.x.

You'll need to disable the airports DHCP and set it to obtain its ip addresses (for itself and to pass to the wireless machines) from the Linksys. Then you will have solely 192.168.1.x addresses on your network and can assign static local ip addresses on the router (Im assuming you want to do some port forwarding).

I dont have any step by step instructions (unless some other forum user has one), but I should be able to do a few tests at work and get back to you asap.

square_imp · 13 Jul 2008 at 09:43

I see, for the settings on the AM200 there is a checkbox for local DHCP server enabled with the following extra information:

192.168.1.2 with addresses going to 192.168.1.254

Of course as expected the modem ip is 192.168.1.1

subnet mask is 255.255.255.0

There are also port forwarding options within the modem settings. So essentially is the best bet to use the modem's functionality when it comes to setup and port-forwarding and use the airport express only for making the whole shebang wireless?

I will check through available options in the airport express in a minute. Thanks for your help thus far.

Rainmaker · 13 Jul 2008 at 12:08

Maybe I've missed something, but why don't you just use the AM200 in half bridge mode? That way the AM200 effectively has no public IP at all, but will pass on a public IP to the Airport Express. Half-bridge will also auto-disable NAT etc. I set my network up this way (using an AM200 and WRT54GL) in about three minutes flat.

Rabtech · 13 Jul 2008 at 12:16

In all honesty, the Airport Express isn't quite upto routing as well as the AM200, I get a bit fed up of power cycling the Airport Express as it locks up and wont allocate ip addresses. It probably would work, just not the ideal solution.

I use a BEBox in bridge mode to a WRT54GL too which rocks as the WRT (w/Tomato firmware) is a far better router than the BEBox.