DHCP IP Address Conflicts on Reboot

DHCP IP Address Conflicts on Reboot

16 Reply
Re:DHCP IP Address Conflicts on Reboot
a week ago - last edited a week ago

  @CoffeeAndTech 

 

 

 

 

  0  
  0  
#14
Options
Re:DHCP IP Address Conflicts on Reboot
a week ago

Hi @CoffeeAndTech 

Thanks for posting in our business forum.

CoffeeAndTech wrote

  @Clive_A 

 

These warnings are coming wireless devices. Here are two examples:

 

1) Conflict between a Macbook Air (connected to EAP_1) and an iPad (connected to EAP_2)

2) Conflict between an iPhone (connected to EAP_3) and an unknown MAC ID (suspect an iPhone) (connected to EAP_2).

 

What is interesting is that they are on different TP-Link EAPs (EAP650s). 

 

 

I tried setting my lease to 2 hours and then also to 7 days. Either option didn't seem to make an impact on the problem.

That does not make too much difference to me. These pictures are generic config. I don't find anything wrong with them.

 

I want to know if you simplify your network, will this error disappear? Remove other devices and keep the AP and the router, and monitor if this persists.

A diagram of your network is required.

A screenshot of your DHCP reservation page.

Does it only happen to certain devices? Or everything is randomly getting the same IP?

What's the network config like on affected devices? I want to learn about it.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  1  
  1  
#15
Options
Re:DHCP IP Address Conflicts on Reboot-Solution
a week ago - last edited Saturday

  @Clive_A 

 

After a lot of research, I determined this was a result of a few smart TVs that were holding on to their IP leases and not requesting a new IP from the server even after their lease was up. No problem with the router or setup. I forced an IP renewal on these TVs and it solved the problem. Thank you for all your help!

Recommended Solution
  0  
  0  
#16
Options
Re:DHCP IP Address Conflicts on Reboot , and DHCP Reservations not assigned.
Saturday

  @CoffeeAndTech 
I got these errors after the latest firmware upgrade, and boot.

tp-link oc200 as controller and er7206 v2 gateway
dhcp reservations not working anymore.

OC200 firmware v5.15.8.12

ER7206 v2.0
Firmware 2.1.3 20241030 release 55760
-
Going mad I did a total reset and started all over.
Setting up the gateway :
ER7206 v2.0
and setup DHCP and reservations..

it all works.

Setup the OC200 and adopted equipment / wifi ap...
Still ok.
Adopted the ER7206 v2.0 into OC200
Now trouble begins after reboot ... and still if rebooting all other devices IOT etc.
All IP reservations are ignored and some assigned to multiple devices.
= = =
This configuration and same equipment workd until september 2024, then new firmware was installed - and after that IP conflicts could occure if some equipment were booted ... seems like the DHCP lease and dhcp assignment does no longer work on ip reservations.

This was also a bug back in 2.x.x firmware of ER7206.
Before using OC200 with another gw as dhcp this was NEVER a issue., so it must be a bug comming back into the ER7206 Gateway. 

  0  
  0  
#17
Options
Re:DHCP IP Address Conflicts on Reboot , and DHCP Reservations not assigned.
Saturday

  @ginoue Since I didn't notice any clients having connection issues, I suspect this was a change to logging in the OC200. I don't think it's an issue.

  0  
  0  
#18
Options
Re:DHCP IP Address Conflicts on Reboot , and DHCP Reservations not assigned.
Saturday
And I should add that I *did* have some clients on my network who weren't releasing their IPs even when I set a static IP and rebooted them. These were mainly smart TVs.
  0  
  0  
#19
Options