> What I don't understand is why it is needed. How is it that the main
> router is cognizant of whether or not the wireless router is even
> running DHCP? What evils could happen with cascading routers

Signature
Sander Tekelenburg, <http://www.euronet.nl/~tekelenb/>
Mac user: "Macs only have 40 viruses, tops!"
PC user: "SEE! Not even the virus writers support Macs!"
>> >to hang the wireless router off the main router:
>> >
[quoted text clipped - 19 lines]
>If you have multiple DHCP servers distributing addresses in the same
>range on the same subnet, you'll have some problems :)
That really wasn't the question. From a management perspective, I
completely agree -- it would be insane to use the same block. I have
no plans to do port forwarding; I'm not exactly sure what would nail
you even if you were to use the same block of IP addresses on both
servers -- as long as both were providing NAT services for their
clients.
The root of my question: what constitutes the "same subnet"? It would
seem that a router running DHCP and NAT services has essentially
created a distinct subnet.
The person I'm working with said that he was told he "couldn't have
routing" on his wireless; I don't understand why. But I couldn't
configure it; I'm going to turn off DHCP and NAT on the wireless. I
don't understand why that shouldn't work.
--phil
> If you make sure
>they don't, then it can work just fine, but I'd still only do that if
>you are very aware of what it is exactly that you're doing. If you're
>not, you'll get very confused when for instance you take your first stab
>at port forwarding without realising that for each instance you may well
>need to configure both routers.
Sander Tekelenburg - 28 Nov 2005 00:48 GMT
[...]
[...]
> >> >turn OFF dhcp on the wireless router (you do not want more than one
> >> >dhcp server on the same lan).
> >
> >[...]
> >
> >> What I don't understand is why it is needed.
[...]
> The root of my question: what constitutes the "same subnet"? It would
> seem that a router running DHCP and NAT services has essentially
> created a distinct subnet.
I think the issue is obscured by the fact that many boxes are both NAT
routers and DHCP servers (and firewalls, etc.). But they're still 2
different things, even though they live in the same box.
The NAT router defines the range of the subnet. A DHCP server on that
subnet hands out IP leases to devices on that subnet.
So if you'd have a second DHCP server active on that same subnet, you'll
get problems. Whether that second DHCP server lives by itself, or shares
a box with a NAT server is irrelevant *unless* that NAT server is active
and creates its own subnet on the DHCP server is active on *that*.
> The person I'm working with said that he was told he "couldn't have
> routing" on his wireless;
The problem with such statements is that all by themselves they are too
absolute. I would assume the statement refers to a specific context -
wanting to set up a network with specific capabilities. For instance,
like someone else says: Bonjour (aka,Rendez-Vous aka Zero-Conf) doesn't
work across subnets. So if you'd want to use Bonjour across wired and
wireless machines, indeed you'll have to set up the Airport box as a
bridge.
Someone else may *want* to create a different subnet and therefore
*need* to enable routing on the Airport.

Signature
Sander Tekelenburg, <http://www.euronet.nl/~tekelenb/>
Mac user: "Macs only have 40 viruses, tops!"
PC user: "SEE! Not even the virus writers support Macs!"