Setting base IP address of Airport Extreme?!

I don't totally understand what you are saying about when you change the IP address of your AE how your clients then get their IP addresses from the router which has no connection to your ISP.

An alternative is to go back to your old setup and just hook up your AirPort Extreme up to your router. You could run it in bridge mode and assign it an IP address of 192.168.249.10 and then still allow your Linksys router to handle the DHCP of your private network. Computers could still use and take advantage of the 802.11n connection on your AE but actual IP addresses for the computers would be handled by your old router.

Double post, sorry.

Ok, there are two different settings that involve DHCP, one being the public IP address that is assigned to the AirPort and the other being the IP addresses that are assigned to the computers on the private network.

Before doing the following, I would hard reset the AirPort Extreme by holding the reset button on the back for 5-10 seconds, just so we can get a default onfiguration.

If you run AirPort Utility, go to Manual Setup, and click on Internet your Connection Sharing at the bottom should be listed as Share a Public IP Address. This enables your AirPort to be the gateway and to receive a public IP address from your cable provider. This should really already be enabled since you did a hard reset.

Now test to make sure you have an internet connection. If not, then you need to reset your cable modem. If after resetting your cable modem you still can't get internet connection then you need to call your cable provider and have then do whatever they need to do to get you a new IP address.

Now that you have a working internet connection you need to setup your private network. Run AirPort Utility, click on Manual Setup, and go to the Internet tab again. Write down the DNS servers you see listed. For Configure IPv4, you need to change the setting from Using DHCP to Manually. Enter the IP address as 192.168.249.10, the subnet mask as 255.255.255.0, the router address as 192.168.249.10, and then use the DNS Servers you just wrote down.

Now click on the DHCP tab next to the Internet Connection tab and select 192.168.249.100 as your beginning DHCP address. Ending address could be something like 192.168.249.200. Update your AirPort and then see if things are working correctly.

did you ever fix this? I am stuck at finding an ending address it will accept (I don't know if this will fix my particular problem as it is to do with BTMM, but I need to get past this WAN IP conflict first).

I need help doing this as well. I get the same conflict. Anyone know how to fix this?

Same boat. I can get the airport to be happy with the starting DHCP range, but not the ending one. The end address given by my "Gateway" (tv/phone/DSL box) is .17, but that one does not make airport happy any more than does any other number I've put it. I have tried dozens by this point.

Use a DHCP address range with a different third digit.

For example, if the utility complains 192.168.0.1 - 192.168.0.20 conflicts, use 192.168.1.1 - 192.168.1.20.

Any group of addresses in the range 192.168. x. y, where "x" is between 0 and 255 and "y" is between 1 and 254 will work for DHCP as long as the addresses aren't already in use by the WAN side of the router.

Unfortunately, that is what you get with closed architecture. All modern routers use Linux as OS and tailoring it to your need is easy.

I got the AEBS working ONLY after giving up on trying to customize it = cannot reserve IPs which makes it useless in a multicomputer environment.

Tried this and it worked... Thanks