Hi @larrezz 

Thanks for posting in our business forum.

larrezz wrote

  @MR.S 

 

Well, having the same issue again and I may identified what is happening...

 

On November 16th, I executed the full factory reset on the VPN router.

On November 26th I turned of one EAP, as I needed to replace the power plug. 

After this, a couple of devices (which were connected with this EAP), switched to another AP (the VPN Router). 

At that moment it switched the IP to a completely different IP (192.168.2.37) in stead of the fixed IP address (192.168.2.8). 

 

Then I just rejoined the device on the network and it is getting another new IP address (192.168.2.43) in stead of the fixed IP address. Looks like a kind of bug within the roaming functionality between the EAP and the VPN router. (see below image)

 

Could you please try out if you having the same issue in your lab environment? If so, I can reach out to TP-link support desk and hopefully they can fix this issue. 

 

 

 

 

See below my site settings related to roaming.

 

 

Delete the Fixed IP.

Go to the Service create a DHCP reservation and input the IP and MAC address manually. Save it.

Reboot the cam and see if it can request a new IP address.

Hi @larrezz 

Thanks for posting in our business forum.

larrezz wrote

  @Clive_A 

 

Thanks for the reply, but it doesn't fix the issue. It is rebooting again to the last IP address known. 

Thereby, if I need to do this again and again, it's simply a workaround for a bug in the software/controller.

First, there is a thing called DHCP lease time.
If your lease is not over, you will be using the same IP address.

That's not a bug. Read the RFC of DHCP.

Does this problem only happen to this device or all the network devices are affected?

Do not configure the fixed IP. Delete related reservations. Just create the DHCP reservation and reboot the router as well. It assigned the last known IP, which could be the DHCP lease time is not over so it reassign that known IP.

Hi @larrezz 

Thanks for posting in our business forum.

larrezz wrote

  @Clive_A 

 

Hi Clive, I understand how DHCP lease is working. The problem is that the gateway doesn't use the fixed IP in the right way. What is the cause that it doesn't use the fixed IP set in the router? Why are devices switching their ip address when they are roaming to another AP? Especially when they are changing from an EAP to the wifi of the router. Normally this behaviour can happen when someone is using standalone access points / a non-roaming/ mesh network. 

 

A fixed IP should prevent that an IP adress is switching right? Or am I missing something here. 

 

I simply never had this issue with my previous wifi set (TP link M4 (AP mode) with a Fritzbox as main router). 

No. This is not expected behavior if you switch between the AP and its IP changes regardless of what mesh/roaming it may involve.

Do you have another DHCP server in the LAN?

AP is AP and it does not serve the DHCP the router should not reassign a new IP address as you are still in the same network and the MAC address did not change.

Unless all of the preconditions are violated. New MAC and a different router/DHCP server.

Try what I recommend as this should fix the problem. I use various routers and this is the proper way to get the reserved IP addresses.

Try as I recommended, if it does not fix it, I am gonna escalate this and arrange a remote session with you. There is no need to waste time on the troubleshooting and we will review your system directly with a remote session.

Do you have AP mesh with the router? The mesh I am talking about is the EAP mesh which requires you to pick the root AP WIFI.

Do you have Seamless Roaming? Eanble 802.11 k/v/r in the controller settings?

Does it change WIFI between the same SSID and VLAN?

Prepare a backup for later discussion.