What's new

Manually Assigned IP Address Not Respected for Repeater

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

dwp

Regular Contributor
Hello. My main router is an Asus GS-AX3000. I have recently added an old Asus RT-N10+ configured as a repeater for the 2.4Ghz signal. I try to keep statically assigned IP for all the devices on my LAN and when I added the repeater, I specified the RT-N10+'s 2 interfaces as shown on the GS-AX3000's DHCP page. In the attached DHCP.JPG image, you can see this:
DHCP.JPG


However, after the main router reboots, I am seeing strange behavior in it's client list:

1. In the attached images WTF.JPG and WTF2.JPG main router, you can see that the 1st IP appears to be assigned correctly but the second is not.
WTF2.JPG
WTF.JPG


In addition, the odd, black "label" in the cell for the repeater's IP (which shows a balloon text of "undefined") is shown and I don't get that at all.

2. Since I did this, I have seen times where even the first IP was NOT the one I manually assigned (192.168.1.5). But in this specific case, I can see the expected assignment in the repeater's configuration page.
Repeater.JPG


3. I have also noted other odd behaviors, post reboot of the main router, where devices I know are connected to the main router are NOT shown in the main router's client list.

Also, any idea what the difference is in the labels shown in the client list "Manual" vs "Static"? I always thought of those I specifically assign on the DHCP page as being static IP's. But those all show as "Manual". Only the oddball, rouge one on 192.168.1.50 shows as "Static".

Can anyone explain what is going on here? Thanks
 
Last edited:
Manually assigned IP addresses can be a problem. Best to actually assign a static IP address at the client. Leave a pool of addresses free from DHCP and use those for static. For example, I start my DHCP pool at 192.168.50.20 which leaves me 18 free addresses. If you need more addresses it is easy to bump the starting address up. The benefit is when you have to reset the router the static addresses are already set.
 
After all this mystery, I spent a bunch of time yesterday trying to "fix" this.

I decided to try to migrate from the stock Asus RT-N10+ B1 firmware to DD-WRT. This went fine at first but somewhere along the line in trying to configure as either a station-bridge or client-bridge, things went off the rails and I thought I had bricked the router. I am not quite sure what I did - as I tried everything I could find, including opening the thing up, connecting serially, and trying to tfpt the stock firmware... But at some point, the DD-WRT came up in default configuration and I was "saved".

I then proceeded to try to configure as a repeater-bridge - even though I really did not want the repeater aspect, only the bridge. I followed the instructions precisely and still was not quite getting there. I did something at some point, cannot recall what, and then I had a working bridge to my main Asus router via wifi. I also had a repeater...

In this configuration, I see only the single entry in the client list on the expected IP of 192.168.1.5 and all else seems the same/fine.

Certainly, the stock RT-N10+ firmware makes this far easier. But the DD-WRT offers much more function - including periodic reboot, which I like.

Best!
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top