IP address reservation still not working reliably
IP address reservation still not working reliably
I still cannot get DHCP reservation working reliably.
Per the screenshot below you can see I have an IP address reservation of 192.168.50.10 (outside my DHCP range which start is 192.168.50.75 - 192.168.50.254 and shown in the last image below) :
But looking at the current IP address of this device you can see below it has the IP address of 192.168.50.178 :
If I reconnect the device it will quickly revert to it's reserved IP address but it will eventually revert back.
This has been an ongoing issue for months now and I wish it could be resolved.
Lastly, here are my DHCP setting for the interface in question :
LASTLY I would add that all the devices I'm having problems with not reliably keeping their reserved IP addresses are also TPLINK devices IOT switches (HS200, HS220, HS110, etc.,)
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @TandS,
TandS wrote
LASTLY I would add that all the devices I'm having problems with not reliably keeping their reserved IP addresses are also TPLINK devices IOT switches (HS200, HS220, HS110, etc.,)
In case there are other community users looking for a solution for this address reservation issue, I'd like to update the solution here.
The R&D team has made a Beta firmware trying to fix the issue above.
Welcome to install the Beta firmware and comment with your feedback from the solution post below:
Solution ER605 ER7206 - “Use Fixed IP Address” (DHCP Reservation) Doesn't Take Effect
- Copy Link
- Report Inappropriate Content
Do you need the IP reservation address to be outside of your DHCP range? My IP reservations for the TP-link HS devices are all within the vlans DHCP range and always work.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Also... firmware?
- Copy Link
- Report Inappropriate Content
I don't have any other DHCP servers running, exclusively using TPLINK. Here is my equipment and version #'s :
I don't have anything configured in the port profile :
- Copy Link
- Report Inappropriate Content
I wonder why doesn't TPLINK respond or at least acknowledge an issue with static IP addressing not working.
There are plenty of threads on this forum with people reporting issues yet nothing is ever mentioned by a TPLINK representative.
Such a basic feature that is required in certain circumstances (in my case I require static IP's for my IOT devices in my home automation solution) and very disappointing from a consumer perspective.
At this time, I definitely wouldn't recommend this solution for BUSINESS USE.
- Copy Link
- Report Inappropriate Content
TP Link please fix this issue
- Copy Link
- Report Inappropriate Content
I would suggest opeing a ticke twith them directly.
they take a while... but so far have solved my issues
- Copy Link
- Report Inappropriate Content
TandS wrote
I still cannot get DHCP reservation working reliably.
Per the screenshot below you can see I have an IP address reservation of 192.168.50.10 (outside my DHCP range which start is 192.168.50.75 - 192.168.50.254 and shown in the last image below) :
But looking at the current IP address of this device you can see below it has the IP address of 192.168.50.178 :
If I reconnect the device it will quickly revert to it's reserved IP address but it will eventually revert back.
This has been an ongoing issue for months now and I wish it could be resolved.
Lastly, here are my DHCP setting for the interface in question :
LASTLY I would add that all the devices I'm having problems with not reliably keeping their reserved IP addresses are also TPLINK devices IOT switches (HS200, HS220, HS110, etc.,)
Given the amount of cacheing that can go on within these systems a power cycle is never a bad thing to clear old data.
I will normally set up address reservation manually tying MAC address to allocated IP BEFORE connecting the device onto the system, and I have never had a problem following this route. Also address reservation is designed to work on IP numbers contained WITHIN a DHCP range, outwith that it is nothing more than a fixed IP set within the device.
Hope that helps !!
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 3350
Replies: 14
Voters 0
No one has voted for it yet.