Obtaining IP Address Issue

Obtaining IP Address Issue

Obtaining IP Address Issue
Obtaining IP Address Issue
2024-10-02 07:23:17
Model: ER8411  
Hardware Version: V1
Firmware Version: 1.1.0 Build 20230705 Rel.64091

We have been facing an "Obtaining IP Address" issue at one of our sites for the past four weeks. Due to this, clients are unable to connect to the internet. I have shared an attachment showing that the internet cannot connect and is displaying the "Obtaining IP Address" message.

After our team's observations, we identified some key points: this issue consistently occurs at specific times. I have also attached a PDF file that has been crucial in our efforts to find a solution. If there were something wrong with the controller or the VPN, we would expect the problem to arise at any time.

Our team decided to replace the VPN router, suspecting there might be an issue with the VPN's DHCP service, which could explain why it is not providing IP addresses to clients. However, even after replacing the VPN router, the problem persisted during the same time frame, specifically from 7:30 PM to 11:00 PM, when the VPN is unable to assign IP addresses to clients.

After three to four days of observation, our team decided to replace the OC-300 Controller as well, thinking there might be something wrong with it. However, on the same day, we continued to encounter the "Obtaining IP Address" issue with both the VPN and the controller.

Currently, we are unable to find a solution to this issue. My question is: why is the DHCP unable to assign IP addresses to clients specifically at certain times? If there were something wrong with the VPN, we would expect the problem to occur at any time.

As a temporary solution, we have been restarting the server, which refreshes the DHCP service.

Please look into this matter to help us find a solution, as we face this issue daily and our clients are unable to connect to internet services.


 

 

 

File:
0.1V TP.pdfDownload
  0      
  0      
#1
Options
9 Reply
Re:Obtaining IP Address Issue
2024-10-02 07:24:14

Find the Attachment

 

File:
logs_2024-10-02_09-36-54.zipDownload
  0  
  0  
#2
Options
Re:Obtaining IP Address Issue
2024-10-02 07:30:58

Find the Attachment

File:
LogList_2024-10-02-09-12.xlsxDownload
  0  
  0  
#3
Options
Re:Obtaining IP Address Issue
2024-10-02 10:27:41

  @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

 

 

  0  
  0  
#5
Options
Re:Obtaining IP Address Issue
2024-10-02 10:42:09

@MR.S 

 

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

  0  
  0  
#6
Options
Re:Obtaining IP Address Issue
2024-10-02 10:50:32

  @AnnusKhan 

 

120 Minutes on Omada.

 

  0  
  0  
#7
Options
Re:Obtaining IP Address Issue
2024-10-02 11:58:40

  @MR.S 

 

IP lease time has been set to 120 minutes

 

  0  
  0  
#8
Options
Re:Obtaining IP Address Issue
2024-10-02 21:09:17 - last edited 2024-10-02 21:16:14

  @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

  0  
  0  
#9
Options
Re:Obtaining IP Address Issue
2024-10-04 03:58:57

Hi  @AnnusKhan 

As everyone has pointed out, it overlaps the public IP ranges. It would become a problem for the LAN.

And under this situation, there is no better solution or troubleshooting for you before you address this major misconfig.

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.
  0  
  0  
#10
Options
Re:Obtaining IP Address Issue
2 weeks ago

  @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.

  0  
  0  
#11
Options