|
Re: strange nonservice behind repeater / switch
Connected to the WAN port of that router, you have the NAT layer in the way, that's the root of the issue. Here's the correct way to use that secondary router as a wireless switch/AP.
Connecting two (or more) SOHO broadband routers together.
Note: The "primary" router can be an actual router, a software gateway like Microsoft Internet Connection Sharing, or a server connection that has the capability to supply more than one IP address using DHCP server capability. No changes are made to the primary "router" configuration.
Configure the IP address of the secondary router(s) to be in the same subnet as the primary router, but out of the range of the DHCP server in the primary router. For instance DHCP server addresses 192.168.0.2 through 192.168.0.100, I'd assign the secondary router 192.168.0.254 as it's IP address, 192.168.0.253 for another router, etc.
Note: Do this first, as you will have to reboot the computer to connect to the router again for the remaining changes.
Disable the DHCP server in the secondary router.
Setup the wireless section just the way you would if it was the primary router, channels, encryption, etc.
Connect from the primary router's LAN port to one of the LAN ports on the secondary router. If there is no uplink port and neither of the routers have auto-sensing ports, use a cross-over cable. Leave the WAN port unconnected!
This procedure bypasses the routing function (NAT layer) and configures the router as a switch (or wireless access point for wireless routers).
|