You have given the AE an IP address for a network,
not a device on that network based on a standard
subnet mask. Each network has two unassignable
numbers, the IP address of the network, and
broadcast. Try 10.1.0.1 for your AE.
I was just giving an example of the network configuration, the ip address of the AE is not actually 10.1.0.0 but 10.1.0.4.
If you want
devices on different subnets to have access, they
need to at least be on the same network, and then
alter the subnet mask for them so both subnets appear
on the same network.
They are on the same network, in the sense that I can talk to a 10.1.0.x address from one of my public ip addresses and vice versa. The only difference is 10.1.0.x cannot talk to anything wan side where machines/devices with a public address can.
Devices assigned with the
public network IPs will be difficult to configure, so
they see the private non-routable network, but I
think it can be done???? I would try another
scheme.... give the AE one of the static IPs and then
NAT with it. Then it would be a Gateway to the
computers behind it for the others in your public
range.... but that's just me . Hope that helps.
I am not looking to setting up NAT. I already have a gateway, the cisco 837 router. I already have a wireless access point which I recently mounted. Thus, I'm not needing any of the wifi capabilities of the AE, but just the airtunes facilities to local machines running on my lan.
Just to reclarify, I have an ip range in the 217.155.6.x block, and to keep myself from using all of the ips in that block, I'm using 10.1.x.x addresses (non-traversable) for the remaining bits that don't require wan side communication.
Michael