>>>>> "Mike" == Mike C <[email protected]> writes:
Mike> Ideally, the way I would configure this is have both wireless Mike> devices use DHCP but have separate pools so there's no Mike> conflicts. So in your case this might look something like: Mike> Belkin N900: 192.168.2.1 Upstream Router: 192.168.2.103 Belkin Mike> N900 DHCP pool: 192.168.2.2 - 192.168.2.102 Upstream Route DHCP Mike> pool: 192.168.2.104 - 192.168.2.204 Netmask for all of this is: Mike> 255.255.255.0 Not such a good idea, IMHO. The "access point" dhcp server is going to be giving itself out as the default route, unless you can tell it otherwise. Also, some embedded dhcp servers listen for other dhcp servers on the network before starting. If they hear one, they'll disable themselves. Others, stomp right ahead blindly. If you are doing this wan-port-trick at all, better to positively turn off the unneeded DHCP server, I think, to avoid the ambiguity. Too many cooks in the kitchen, etc. There are 500-umpteen ways of configuring networks that can (be made to) work. Some are more sane and less astonishing than others. -- Russell Senior, President [email protected] _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
