Business Community > Controllers > IP address reservation still not working reliably
< Controllers

IP address reservation still not working reliably

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
12

IP address reservation still not working reliably

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
IP address reservation still not working reliably
IP address reservation still not working reliably
2022-02-16 18:08:34 - last edited 2022-02-25 17:20:55
Model: Omada Software Controller (Linux)  
Hardware Version:
Firmware Version: V5.0.29

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.,)

OmadaLinux v5.13.10 R605 V1:1.3.0 - Build 20230511 R.51317 SG2008P V1:V1.0.8 Build 20230602 R.73473 SG2008P V3:V3.0.5 Build 20230602 R.73473 3 x EAP245 V3:V5.1.0-Build 20230104 R.79433
  1      
 
  1      
 
#1
Options
1 Accepted Solution
Re:IP address reservation still not working reliably-Solution
2022-04-01 11:25:23 - last edited 2022-04-01 11:27:08

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

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  2  
  2  
#12
Options
12 Reply
Re:IP address reservation still not working reliably
2022-02-17 02:42:46

  @TandS 

 

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. 

  0  
  0  
#2
Options
Re:IP address reservation still not working reliably
2022-02-17 03:16:35
That was the suggested workaround before IP reservation was introduced The issue persists even with the IP addresses being within the dhcp range.
OmadaLinux v5.13.10 R605 V1:1.3.0 - Build 20230511 R.51317 SG2008P V1:V1.0.8 Build 20230602 R.73473 SG2008P V3:V3.0.5 Build 20230602 R.73473 3 x EAP245 V3:V5.1.0-Build 20230104 R.79433
  1  
  1  
#3
Options
Re:IP address reservation still not working reliably
2022-02-17 23:07:22
You can make in in range or out of range. should not matter. Are you sure you dont have a DHCP server configured anywhere else? Unmanaged access point? can we see you r port profile for 192.168.50.0?
  0  
  0  
#4
Options
Re:IP address reservation still not working reliably
2022-02-17 23:09:15

Also... firmware?

  0  
  0  
#5
Options
Re:IP address reservation still not working reliably
2022-02-18 18:15:04

  @jwaltrip 

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 :

OmadaLinux v5.13.10 R605 V1:1.3.0 - Build 20230511 R.51317 SG2008P V1:V1.0.8 Build 20230602 R.73473 SG2008P V3:V3.0.5 Build 20230602 R.73473 3 x EAP245 V3:V5.1.0-Build 20230104 R.79433
  0  
  0  
#6
Options
Re:IP address reservation still not working reliably
2022-02-25 17:20:29 - last edited 2022-04-01 11:27:15

  @TandS 

 

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.

OmadaLinux v5.13.10 R605 V1:1.3.0 - Build 20230511 R.51317 SG2008P V1:V1.0.8 Build 20230602 R.73473 SG2008P V3:V3.0.5 Build 20230602 R.73473 3 x EAP245 V3:V5.1.0-Build 20230104 R.79433
  2  
  2  
#7
Options
Re:IP address reservation still not working reliably
2022-03-16 04:23:40

@TandS 

TP Link please fix this issue

  0  
  0  
#8
Options
Re:IP address reservation still not working reliably
2022-03-23 20:09:01

I would suggest opeing a ticke twith them directly.  

 

they take a while... but so far have solved my issues

 

  0  
  0  
#9
Options
Re:IP address reservation still not working reliably
2022-03-25 17:14:42

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.,)

  @TandS 

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 !!

  0  
  0  
#10
Options
Re:IP address reservation still not working reliably
2022-03-25 17:29:09
The IP address outside the DHCP range was a suggested work around which is now outdated as the DHCP reservation functionality is officially supported in the most recent versions of the controller. The problem still persists in V5.1.17 and my devices are scheduled to reboot on a monthly basis. It doesn't make a difference if I power cycle the devices or the clients. The reserved IP address will be assigned following either a reboot of the client or a disconnect from the controller BUT the address is not always retained.
OmadaLinux v5.13.10 R605 V1:1.3.0 - Build 20230511 R.51317 SG2008P V1:V1.0.8 Build 20230602 R.73473 SG2008P V3:V3.0.5 Build 20230602 R.73473 3 x EAP245 V3:V5.1.0-Build 20230104 R.79433
  0  
  0  
#11
Options
12

Information

Helpful: 1

Views: 3440

Replies: 14

Related Articles
Omada_Software Controller_v5.1.7_Linux - DHCP RESERVATION NOT WORKING RELIABLY
754 0
Fixed IP Address NOT working
14541 0
Use Fixed IP Address not working.
4536 0
Change IP address of Software Controller
944 0
Fixed ip address VLAN on omada
2322 0
Cannot assign a fixed IP address
677 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.