Obtaining IP address unable to connect WiFi
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi Guys,
I have setup with
Huawei modem with interface IP 172.16.1.x
Omada controller OC 200 172.16.1.x
Cisco POE Switch 270W 48 port (no VLAN)
Access point EAP115 IP 172.16.1.2 ……
Access point IP RAP225 IP 172.16.1.47 (total 45 AP’s)
Total number of users/ devices 170 including AP’s
Omada Controller OC-200 Version: 5.13.30.20
Build:1.29.4 Build 20240304 Rel.54362
Initially when we start the devices (oc-200. Cisco 48 port POE switch, EAP225 and EAP115) all AP’s getting IP address, and the users are getting access to the internet.
After 8 to 10 hours network start getting freezing any new device cannot connect to any WiFi devices its says “obtaining IP address” at the same time if I connect my laptop directly to modem not getting IP.
If I restart modem everything become normal. last 4 weeks I'm facing this issue
Can anyone help me to resolve this issue.
Thank You
Hi, @Al-Mashriq
It appears that the DHCP server hangs after a short while, is that correct? Which device is functional for that?
You commented, "If I connect my laptop directly to modem not getting IP." Is this a possible answer point to the router modem?
Are you using the L2+ switch, or is there another type of switch that has static routing and DHCP server functionality?
If so, assign the switch devices full control over all DHCP functions. Then, in order to access the internet, just a small static routing configure.
Additionally, I suggest you buy a new TP-Link l2+ switch to work as a core switch if you don't have one, then create a network of 2 VLANs, one for the management VLAN or internal purpose and the other for guests, then use ACL to isolate them out to secure internal. That would be wonderful, and it should be good for long term service.
TP-Link L2+ Page:
https://www.tp-link.com/en/business-networking/omada-switch-l3-l2-managed/?filterby=6386
How to configure switch as DHCP server on Standalone mode:
https://www.tp-link.com/th/support/faq/3656/
The network schema should be like this.
Thank you for your reply.
i have attached the site schematic network diagram and Omada cloud controller screen shot, there you can see number of Sites, AP's and devices connected.
DHCP Pool: 172.16.1.1 to 172.16.1.254
Mask: 255.255.0.0
DHCP relay time: 9 days
Maximum number of IP usage in this network is 45-APs plus 95-clients total 139-IP is used. still i have 115 IP address available for new devices to connect.
is this right way of connecting devices ? please suggest.
Thank you.
Thank you for your reply.
i have attached the site schematic network diagram and Omada cloud controller screen shot, there you can see number of Sites, AP's and devices connected.
DHCP Pool: 172.16.1.1 to 172.16.1.254
Mask: 255.255.0.0
DHCP relay time: 9 days
Maximum number of IP usage in this network is 45-APs plus 95-clients total 139-IP is used. still i have 115 IP address available for new devices to connect.
is this right way of connecting devices ? please suggest.
Thank you.
It looks so weird, why are you designing the site too much? I just wonder. It doesn't matter why as long as it meets your needs. .. 
..
By your network schematic, I think the modem router may be overloading because of the large dhcp pool and the extended lease duration, It uses up ram quite a bit. I only guessed at it because I don't exactly know the modem specification. I apologize if I'm incorrect.
Have you ever tried to shorten the lease period? by no more than 12 hours, share the result here. However, you really have no choice but to take my previous suggestions into consideration if the issue still exists.
// ===edit ===//
I also agree to minimize the subnet. /24 = 254 in total ip should be enough.
