Question Wireless Repeater IP address ?

robburne

Distinguished
Jul 31, 2005
40
0
18,540
Just a curiousity regarding the configuration of my home network.

My main router is a Linksys MX4000 router, I also have a Tenda router which is configured for Wireless repeating in Client + AP mode. I've not set the IP address of the Tenda repeater but I'm wondering what determines its IP address of 192.168.0.219 - this never changes. It is not configured in the Linksys (my DHCP starts from 192.168.0.100). The IP is quite specific and can't be random, all works fine its just bugging the hell out of me.

Any ideas?

Thanks!
 
Hard to say for sure it is likely some value the tenda router itself is configured to use unless you change it. Tenda is a "value" router so there is not as much documentation on it. At least they made it smart enough to change the IP when you are not running it in router mode. Some routers leave it the standard 192.168.0.1 and it will conflict with other routers.

It is highly unlikely it is in anyway set by the linksys. There is no standards for "repeater" mode. They all use WDS to make it possible to bypass the mac/encryption restriction in wifi, it is basically a hack not a standard. This though has nothing to do with IP assignment.

Now some mesh systems can configure the remote clients but this also is all proprietary and does not function between different brands of routers.

My guess would be that is the IP tenda uses when you set it to repeater/ap mode. It likely would use the same IP even if your router used say 192.168.1.1 and therefore the tenda is not on a different subnet.
 

robburne

Distinguished
Jul 31, 2005
40
0
18,540
Ok yes I see there is a DHCP reservation table on the Linksys, looks like an IP address has been added already for the Tenda, but it is 192.168.0.100, not the 192.168.0.219 address. If I change the reserved address to be the one being used the Tenda is no longer available, so perhaps it needs the 192.168.0.100 and the 219 address for the WISP?

Either way it seems this is where it is configured and solves the mystery I think - thanks.