Find the Attachment

Find the Attachment

  @AnnusKhan 

What on earth are you doing here, you have 65534 Public ip addresses, it's no wonder you have problems. why 65534 addresses? most manage with 254 IP addresses

and why lease time in 5 minutes

@MR.S 

Regarding the IP addresses we will create in series, don't worry about the lease time. What is the default lease time?

  @AnnusKhan 

120 Minutes on Omada.

  @MR.S 

IP lease time has been set to 120 minutes

  @AnnusKhan 

First of all, why is your DHCP range so small compared to the MASSIVE LAN IP range?

Secondly, your LAN IP is set to 134.x.x.x which is a public IP range which appears to be assigned to a german telecoms company.  Id be willing to bet that this is whats causing your end devices to fail to get DHCP as they may be reaching out to that company and will never recieve an address

1) Set your LAN IP range to a private one - 192.168.x.x, 10.x.x.x, 172.x.x.x

2) Set your DHCP range to something more sensible

Also, plug in your ER8411s backup power connector and look at the temperature situation in your rack, its running quite hot

  @Clive_A 

Thank you for your recommendation. However, I would like to inform you that I have a total of 12 sites, each controlled by different Omada Controllers, so they are not connected to each other. I have also attached a picture showing that all of my 12 sites share the same network IP range of 134.1.X.X. I haven’t faced any issues for the past three years.

There may be a conflict with the public IP range, so our team decided that whenever we acquire a new site, we will create the network using a different IP address range, which is beneficial for us to avoid mis-config.

Regarding your recommendation to change the IP, our team decided to switch to a different IP range to resolve the obtaining IP issue. Unfortunately, the problem persisted after 3 to 4 days of observation, and we became frustrated trying to identify the mis-config of the IP addresses."

I then decided to downgrade the firmware of the VPN router because I updated it one month ago through the Omada Controller. Since that update, we have been experiencing these issues. I downgraded the firmware from 1.2.1 (Build Xxxx) to 1.1.0 (Build 20230705 Rel.64091). After the downgrade, we have not faced the IP obtaining issue, which indicates that there may be a problem with the VPN firmware.

I also noticed on the TP-Link website that there is an update for the VPN router to version 1.2.2 (Xxx). I am unsure if this update resolves the problem.