MR600 - Address reservation doesn't work properly
MR600 - Address reservation doesn't work properly
Basically, address reservation for specific MAC addresses doesn't seem to work properly (it does whatever the hell it wants at any given time).
I have around 24 devices with reserved IP addresses. For a few of them, seemingly random, the router offers an IP from the DHCP pool instead of the one I reserved.
For example, you can clearly see the reserved address for this MAC:
And this is what happens when the client requests a new IP address, as seen in the log:
2020-10-03 16:10:36 [5] DHCPD: Recv DISCOVER from 08:00:27:73:01:64
2020-10-03 16:10:36 [5] DHCPD: Send OFFER with ip 192.168.1.105
2020-10-03 16:10:36 [5] DHCPD: Recv REQUEST from 08:00:27:73:01:64
2020-10-03 16:10:37 [5] DHCPD: Send ACK to 192.168.1.105
This happens with other three or 4 hosts with reserved addresses. I've done multiple restarts of the router and clients, removed and re-added the configurations, nothing seems to work. I even removed ALL reserved IP addresses and re-added them all, to no avail. This seriously messes up my IOT stuff setup...
Anyone facing a similar issue?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi,thank you very much for the feedback. Based on the screenshots, actual address didn't add 100 compared with reserved address for all devices, for example, reserved address for 70:AF:24:11:82:7F is 192.168.0.7, actual address is 192.168.0.106.
Besides, there is a RE305 in the client list of the router, may I know the hardware and firmware version of the RE305? V3 or higher version of RE305 supports OneMesh, please check if the RE305 and Archer MR600 are in OneMesh network or not.
If the problem still happens with OneMesh network used, please also try to unplug the RE305, then connect all devices to the MR600 to see if address reservation still have the problem.
By the way, what is the DHCP address pool configured on your MR600? you could also try to make sure all the reserved IP address are within the DHCP address pool to see if problem still exists.
- Copy Link
- Report Inappropriate Content
Thank you for the reply.
RE305 works correctly as a OneMesh. Also did a test without RE305 and it works still the problem occurs.
What is worth to mention that device
ComfoConnect_LAN_C | 14-4F-D7-1E-15-AE |
that is reserved to 192.168.0.5 is always bound to proper address.
I changed DHCP IP Address Pool: to .2 - .199 (previously was .100 - .199) but still some devices are not bound correctly. (
NAS417FA4 | 24-5E-BE-41-7F-A4 | 192.168.0.12 |
and it should be bound to 192.168.0.8
some other advice? its pretty annoying when I have everytime different IP addresess to particular devices.
screens below:
- Copy Link
- Report Inappropriate Content
Hi, sorry for that the problem still exists, please send an email to support.forum@tp-link.com with the following information, our engineer will continue to follow up the issue:
1. what kind of devices are able to get reserved IP address? are they connected to the MR600 via WiFi or Ethernet cable?
2. what kind of devices are unable to get reserved IP address, and what are their model no.? are they connected to the MR600 via WiFi or Ethernet cable?
3. after configuring the address reservation and saving the settings, did you try to disconnect from MR600 first and reboot the client device, then reconnect it to regain IP address?
4. what is the operation mode of your MR600? 3G/4G Router mode or wireless router mode?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 3035
Replies: 13
Voters 0
No one has voted for it yet.