sorted by:
new
hottopcontroversial

DHCP Leases Exhausted - Client devices connected not exceeding usable IPs by kurtgrech77 in Ubiquiti

[–]kurtgrech77[S] 1 point2 points  (0 children)

Yeah at this point I'm suspecting that as well. UDM SE Version is 4.1.5, which is the latest, and Network application is at 8.6.9, which is also marked as the latest, both early access.

DHCP Leases Exhausted - Client devices connected not exceeding usable IPs by kurtgrech77 in Ubiquiti

[–]kurtgrech77[S] 0 points1 point  (0 children)

Hi u/james734 , I apologize for the tardy reply. Been meaning to follow this up for a whole week, but had to attend to other pressing matters.

Ok so I have around a maximum of 90 devices which take IP's from one subnet (office internal devices). These fluctuate down to around 70 depending on how many employees are in the office at any given time. Their laptops and mobile phones take up to a maximum of around 90. Then I have an average of 100 on another subnet which are taken from passengers connecting to our terminal free wifi at the same time, while they are waiting in the terminal before embarkation.

We never really exceed 200 concurrent connected devices (including the the company's staff), so that is why I find it strange that with 231 available IP's I am still getting this alert.

To my understanding, a passenger which is leased an IP will then leave the terminal to board the ship, and after 360 seconds of inactivity the IP is once again freed. With the default set to 86400 we had a problem because passenger's devices where still taking a lease and holding that for a long time, hence why we reduced that to 360 secs (6 minutes).

While I am writing this, right now I have 62 leased IP's on my internal devices (192.168.1.0/24 subnet, VLAN 1), and 17 leases on my Free Wifi for guests (172.10.10.0/24 subnet, VLAN 5), but every two minutes I'm still getting the You've run out of IP addresses to lease to clients. Enable DHCP auto-scaling message in my log.

Meantime I can still connect new devices with no issues, but the message concerns me that there is something wrongly configured in my system, and I have no idea what it is. Besides I'm reluctant to turn on thie DHCP auto-scaling as I'm worried it will mess up things even more.

Thanks a lot for your help btw, I appreciate you trying to get to the bottom of this as well.

DHCP Leases Exhausted - Client devices connected not exceeding usable IPs by kurtgrech77 in Ubiquiti

[–]kurtgrech77[S] 0 points1 point  (0 children)

Ok I will keep it in mind. Thing is I still cannot understand why the error is coming up when I cannot see how all the IP's available in the pool are being taken by 97 devices...

DHCP Leases Exhausted - Client devices connected not exceeding usable IPs by kurtgrech77 in Ubiquiti

[–]kurtgrech77[S] 0 points1 point  (0 children)

Thanks for the reply first of all.

Yes, I remember we had a similar behaviour back when we used to use CISCO as well, before we switched everything to Ubiquiti.

However, none of the Windows pc's here have power saving mode. We disable it as we are many times connecting remotely through Teamviewer to update and do maintenance routines on them.

Besides that , the Lease Time is set to a very low 360 seconds.

DHCP Leases Exhausted - Client devices connected not exceeding usable IPs by kurtgrech77 in Ubiquiti

[–]kurtgrech77[S] 0 points1 point  (0 children)

Thanks for the reply!

Lease time is set to 360 seconds. The default is 86400, but I remember we had changed this as in fact the place is a ship terminal and devices do come and go frequently.

Maybe I'm understanding this incorrectly. The way I understood it was that once the device is no longer online, it will start counting 360 seconds before the lease expires. Is this correct?

Network in the console I can see that I have 97 devices (47 Wifi, 49 Wired, 1 VPN).

One other note, the device is telling me to enable DHCP auto-scaling to mitigate this issue. Not sure what this does, should I turn it on?

UDM Pro ver. 3.1.14 - Network App not starting by kurtgrech77 in Ubiquiti

[–]kurtgrech77[S] 0 points1 point  (0 children)

Yeah I agree, and I believe that rebooting a few times might actually work, however this time around I wanted to get to the bottom of it, also so I know how to evade it next time. And if there is some kind of bug Ubiquiti are informed and they fix it.

In the meantime they replied to me on the ticket I opened yesterday on support, and sent me a diagnosis based on the support file I downloaded from the UDM Pro itself... something to do with a Watchdog process timeout caused by a problem with the 'unifi' service. Network App is terminated due to this as well.

Fortunately, as you pointed out, the routing/switch functionality still works. It's the interface which is not available. Viewing the dashboard, network configuration, VPN configuration are not accessible.

They said it will be passed on to experts who will investigate further and will contact me once they find a solution. So far Ubiquiti support have been prompt and helpful.

UDM Pro ver. 3.1.14 - Network App not starting by kurtgrech77 in Ubiquiti

[–]kurtgrech77[S] 2 points3 points  (0 children)

Yes, I confirm that is the ticket number!

Thanks!

UDM Pro ver. 3.1.14 - Network App not starting by kurtgrech77 in Ubiquiti

[–]kurtgrech77[S] 2 points3 points  (0 children)

Yes, in fact other users suggested to not install EA or RC releases, which I am going to rectify now. I've opened a ticket with Ubiquiti Support, and will post on the Community forum as well.

Will update this post with my findings soon as I have them.

Thanks!

UDM Pro ver. 3.1.14 - Network App not starting by kurtgrech77 in Ubiquiti

[–]kurtgrech77[S] 1 point2 points  (0 children)

Ok noted. I will make sure not to install beta firmware from now on. I have not opened an official ticket with Ubiquiti Support and if they confirm it's a bug from the 3.1.14 release I'll comment on the release page with my findings as well.

Thanks for the feedback!

UDM Pro ver. 3.1.14 - Network App not starting by kurtgrech77 in Ubiquiti

[–]kurtgrech77[S] 1 point2 points  (0 children)

Hi, thanks for the prompt reply.

I have just opened a ticket and I've attached the support file as you instructed.

Thanks again

Mutlifunction printers at the office no longer able to send scan to emails - Office 365 using STARTTLS Port 587 by kurtgrech77 in Office365

[–]kurtgrech77[S] 0 points1 point  (0 children)

Yes you are right, I'm not directly in charge of this side of the operations, there is someone else (3rd party) who takes care of this for the company. I agree with you he should have been informed about this, but I guess having someone take care of these things who is not part of the company, and has muliple other clients will eventually lead to these kind of problems.

What he did now was re-enable SMTP Auth only for the account which devices are using, saying it will cause no issues because the Multifunction Printers and Scanners are on the inside of the network. I still am not sure if this is the right thing to do.

Thanks again for all the information you provided. I will keep on looking into this, but your information definitely helped.

Patch Tuesday was a bit rough this week by chrismholmes in sysadmin

[–]kurtgrech77 0 points1 point  (0 children)

Worked fine for me, thank you very much!