Alan Baker wrote:
Some neighbors would like to have a wireless bridge to
their existing home network, so the chain of devices
is...
WAN - Router - WAP - Client Bridge - Client Router -
Client PC


1) Can the client router have its own subnet?

Each client router MUST have it's own subnet unless it is configured for NAT.

2) How do I tell my router (a Linksys BEFSR81) to
route packets via the client router?

I don't think the Linksys routers have the ability to define multiple static routes; which would be the best way to do it. They do, however, support RIP routing protocol. With the routers operaing in router mode (not NAT mode) and with RIP turned on, all of the routers will discover the various subnets.

3) Can the client router get its dynamic IP address
from my router's DHCP? (I think #2 above make this an
oxymoron.)

4) Can the WAP (a D-Link DWL-900AP+) and the client
router have only fixed IP addresses?

I recommend that you avoid the use of DHCP on the AP, the Bridges, and the WAN ports of the routers. Assign static addresses to all of the network devices and client router WAN ports that are on your main subnet.

The customers may then choose to run statics or let
their router do DHCP for their subnet.

The customer could choose to run their router in NAT
mode. In that case, their WAN port could DHCP from
your router. You wouldn't need to worry about routing.
And they would prevent you from accessing anything on
their subnet.

So I guess it depends on what your customers are trying
to achieve. Running NAT gives them privacy. Running
subnets lets everyone still connect to each other.

Michael

--
general wireless list, a bawug thing <http://www.bawug.org/>
[un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless

Reply via email to