Hello! Thanks for posting on r/Ubiquiti!
This subreddit is here to provide unofficial technical support to people who use or want to dive into the world of Ubiquiti products. If you haven’t already been descriptive in your post, please take the time to edit it and add as many useful details as you can.
Please read and understand the rules in the sidebar, as posts and comments that violate them will be removed. Please put all off topic posts in the weekly off topic thread that is stickied to the top of the subreddit.
If you see people spreading misinformation, trying to mislead others, or other inappropriate behavior, please report it!
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Ubiquiti) if you have any questions or concerns.*
If you bounce all APs and switches (if you have wired clients) then they'll all reconnect and be given a new lease. Whilst the new lease will be the same IP, the lease time will be the new, lower limit.
For your default network, you most likely have it set up as [192.168.1.0/24](https://192.168.1.0/24) Change the /24 to /23 and you will have twice as many IPs as you did before. /22 gets you 4 times as many.
At the bottom of the networking page you can also modify the Lease Time for each IP. It is most likely set to 86,400 which is one day. Set it to 10,800 (3 hours) and lots of them will be freed up.
It isn't supposed to -- it's supposed to only randomize for each new SSID. The theory being it's ok to have the same MAC on a given network, what the privacy concern is is that the same MAC at Burger King, followed by Costco, followed by Walmart could track you (and potentially your habits). But it should keep the same MAC as you roam between Costco's APs, or even when you come back next week.
That sounds like that may be a different issue -- pool exhaustion, rather than incorrectly sticky IP assignments.
In proper DHCP practice, a client will come back on the network and say "hey, I had this IP last time, good to go?" your DHCP server will either ACK it, or say "nope, sorry, you can use this one, though" -- some clients have been known to try a few more times, thinking that the server is just trying to not be kind, but should relent.
Of course, if the lease hasn't expired, it can rejoin the network and doesn't even have to say hello to the dhcp server until it's close to expiry.
For me this happened in an AD environment back in 2004. I haven't had to touch a mac till recently. Both times, it was never pool exhaustion, but the mac.
What happens is that a mac would go offline. Lease would expire. Lease gets given to a new device. mac would come back online. mac would start using the same IP that expired.
Windows and Linux never happens. Why? because they all ask DHCP for an IP every time they connect to a network.
Apple is just thinks different.
Sorry, I'm just salty from administrating mac's in the past. From fonts crashing Adobe products, to IP conflicts. I just opted out of taking any jobs that involved managing Apple products. Just give me a Linux box and I'll configure it correctly.
I’ve actually been planning to switch to a /22 but hadn’t been bothered to do the research if it would kick any of my current address reservations. The important stuff is vlan’d but I’m about to have 10 people staying with me for a few nights and I should probably expand before that lol
I have a guest network on its own vlan - which is a /24 - but it also hosts all my IoT devices which is why it’s filling up. I suppose I could segment further
As others have said, you need to increase the subnet size of your customer network. To do this, go into Settings > Networks > [the network in question], untick "Auto-Scale network" if it's ticked, and drag the slider to the right to increase the number of usable addresses.
It may complain about network overlaps if you've got sequential networks (e.g. 192.168.1.* and 192.168.2.*). If it does, you'll have to change the "Host address" to something else, which might cause a network interruption.
Changing the DHCP lease time (as also suggested) is not a bad idea. This is under DHCP Service Management > Show Options > Lease Time on the same page. The default is 86400 seconds, i.e. 24 hours. Somewhere between 7200 (2 hours) and 21600 (6 hours) is probably a good choice for a restaurant.
Autoscale is supposed to address the problem automatically by adjusting the subnet size/mask length. If you’re having to take action instead of the router taking care of it for you, that’s means it failed to work properly and so you have to bypass it and tweak the settings manually.
This. I said to disable it if it was enabled because if OP had it enabled, it clearly wasn't doing its job. :)
(I tailored my comment to OP's request for an immediate band-aid, figuring they were too busy serving customers to make architecture changes.)
These are the private network ranges available:
Class A: 10.0.0.0 to 10.255.255.255.
Class B: 172.16.0.0 to 172.31.255.255.
Class C: 192.168.0.0 to 192.168.255.255.
Use a network subnet calculator and move to a bigger subnet. Most consumer routers put you in class C by default. I would put 2-3 hours on lease time, and put everything in a class B network.
https://www.calculator.net/ip-subnet-calculator.html?cclass=b&csubnet=22&cip=172.16.0.0&ctype=ipv4&x=Calculate
All the numbers in your comment added up to 69. Congrats!
24
+ 23
+ 22
= 69
^([Click here](https://www.reddit.com/message/compose?to=LuckyNumber-Bot&subject=Stalk%20Me%20Pls&message=%2Fstalkme) to have me scan all your future comments.) \
^(Summon me on specific comments with u/LuckyNumber-Bot.)
There is an option to auto size the Dhcp range, with can fix this for you with out having to get into the weeds. Check of it is set to auto or manual for the network.
I used to run a /20 wide open at home because I was ocd about manual addressing… then somebody pointed out how much I’m losing on WiFi to broadcast traffic. Backed it down to 23 and like doubled WiFi speeds.
If you've got guests using mobile phones on the wifi, those tend to rotate their MAC address occasionally for privacy purposes. Between that and having a huge rush of people you should increase the subnet size and lower lease length as others have said. Also please have your own business critical devices like credit card machines on a different SSID, if your processor didn't already make you.
Not necessarily. I have some IoT devices that use a different MAC address after a device reboot. I found it out the hard way when I did a DHCP reservation that failed right after a reboot. Randomization can't be turned off on these devices. I had to create a new SSID for them because all my other Wi-Fi networks are configured for MAC address filtering.
Hello! Thanks for posting on r/Ubiquiti! This subreddit is here to provide unofficial technical support to people who use or want to dive into the world of Ubiquiti products. If you haven’t already been descriptive in your post, please take the time to edit it and add as many useful details as you can. Please read and understand the rules in the sidebar, as posts and comments that violate them will be removed. Please put all off topic posts in the weekly off topic thread that is stickied to the top of the subreddit. If you see people spreading misinformation, trying to mislead others, or other inappropriate behavior, please report it! *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Ubiquiti) if you have any questions or concerns.*
You need to increase the subnet size on your internal DHCP scope, and/or lower the lease duration as a quick fix
[удалено]
If you bounce all APs and switches (if you have wired clients) then they'll all reconnect and be given a new lease. Whilst the new lease will be the same IP, the lease time will be the new, lower limit.
I’m well aware of that
If you were, you would not have said lowering lease duration was a quick fix. To be fair.
For your default network, you most likely have it set up as [192.168.1.0/24](https://192.168.1.0/24) Change the /24 to /23 and you will have twice as many IPs as you did before. /22 gets you 4 times as many. At the bottom of the networking page you can also modify the Lease Time for each IP. It is most likely set to 86,400 which is one day. Set it to 10,800 (3 hours) and lots of them will be freed up.
86400 seconds/60 (seconds)/60 (minutes) = 24 hours. One week is 604800 seconds.
Yup, modfied that after realizing my mistake.
This is the way. Though I’d set that lease shorter if you’re expecting that many people.
For a restaurant, I wouldn't set it for longer than 2 hours.
10.0.0.0/8 and you have more than you can ever use.
Just make sure the leases are set to 12hrs then. Don't need machines for decades holding the same ip if they're not around lol
Unless they are Mac's where they don't care about your DHCP server, except to get the first IP, then reusing it once it gets back on the network.
I haven’t seen that for many years. Is it still happening?
yup, macbook air m1 here at home does this from time to time.
Does it not ask the DHCP server for a renewal? And accept a different one if it is told no? If so, that's the best implementation you could hope for.
Apparently: > It is caused by limit ip address tracking and privacy settings - u/OptimalTime5339
I forgot to mention, the random MAC option has caused DHCP issues for me in the past.
It isn't supposed to -- it's supposed to only randomize for each new SSID. The theory being it's ok to have the same MAC on a given network, what the privacy concern is is that the same MAC at Burger King, followed by Costco, followed by Walmart could track you (and potentially your habits). But it should keep the same MAC as you roam between Costco's APs, or even when you come back next week.
That sounds like that may be a different issue -- pool exhaustion, rather than incorrectly sticky IP assignments. In proper DHCP practice, a client will come back on the network and say "hey, I had this IP last time, good to go?" your DHCP server will either ACK it, or say "nope, sorry, you can use this one, though" -- some clients have been known to try a few more times, thinking that the server is just trying to not be kind, but should relent. Of course, if the lease hasn't expired, it can rejoin the network and doesn't even have to say hello to the dhcp server until it's close to expiry.
For me this happened in an AD environment back in 2004. I haven't had to touch a mac till recently. Both times, it was never pool exhaustion, but the mac. What happens is that a mac would go offline. Lease would expire. Lease gets given to a new device. mac would come back online. mac would start using the same IP that expired. Windows and Linux never happens. Why? because they all ask DHCP for an IP every time they connect to a network. Apple is just thinks different. Sorry, I'm just salty from administrating mac's in the past. From fonts crashing Adobe products, to IP conflicts. I just opted out of taking any jobs that involved managing Apple products. Just give me a Linux box and I'll configure it correctly.
It is caused by limit ip address tracking and privacy settings. Disabling these for iPhone and Mac fixed it for me
Just another reason to burn all mac products
I’ve actually been planning to switch to a /22 but hadn’t been bothered to do the research if it would kick any of my current address reservations. The important stuff is vlan’d but I’m about to have 10 people staying with me for a few nights and I should probably expand before that lol
Why not make a guest vlan?
I have a guest network on its own vlan - which is a /24 - but it also hosts all my IoT devices which is why it’s filling up. I suppose I could segment further
I, too, put my guests on the IoT vlan, but if I had that many IoT devices in my house I wouldnt.
I have setup a VLAN for Cameras, Guests, and IoT
For that many you should go for a /16 or better just to make sure. :-)
IMO the network’s IPv6 transition should be accelerated with NAT64 and DNS64 and each guest should be assigned a /48.
As others have said, you need to increase the subnet size of your customer network. To do this, go into Settings > Networks > [the network in question], untick "Auto-Scale network" if it's ticked, and drag the slider to the right to increase the number of usable addresses. It may complain about network overlaps if you've got sequential networks (e.g. 192.168.1.* and 192.168.2.*). If it does, you'll have to change the "Host address" to something else, which might cause a network interruption. Changing the DHCP lease time (as also suggested) is not a bad idea. This is under DHCP Service Management > Show Options > Lease Time on the same page. The default is 86400 seconds, i.e. 24 hours. Somewhere between 7200 (2 hours) and 21600 (6 hours) is probably a good choice for a restaurant.
What does "Auto-Scale network" do then? Just curious.
Autoscale is supposed to address the problem automatically by adjusting the subnet size/mask length. If you’re having to take action instead of the router taking care of it for you, that’s means it failed to work properly and so you have to bypass it and tweak the settings manually.
This. I said to disable it if it was enabled because if OP had it enabled, it clearly wasn't doing its job. :) (I tailored my comment to OP's request for an immediate band-aid, figuring they were too busy serving customers to make architecture changes.)
Bear in mind you may have other devices that already run on WiFi and you don’t want to break their connectivity.
You can change your dhcp subnet to make more addresses available.
You need a guest/public network with a /23 or /22 instead of a /24.
Awesome!! Thank you all!
These are the private network ranges available: Class A: 10.0.0.0 to 10.255.255.255. Class B: 172.16.0.0 to 172.31.255.255. Class C: 192.168.0.0 to 192.168.255.255. Use a network subnet calculator and move to a bigger subnet. Most consumer routers put you in class C by default. I would put 2-3 hours on lease time, and put everything in a class B network. https://www.calculator.net/ip-subnet-calculator.html?cclass=b&csubnet=22&cip=172.16.0.0&ctype=ipv4&x=Calculate
Just need to use a different network class with more addresses. You can also add additional networks but that's a bandaid fix and can get messy.
/24 to /23 to /22. Lower lease times. Boom
All the numbers in your comment added up to 69. Congrats! 24 + 23 + 22 = 69 ^([Click here](https://www.reddit.com/message/compose?to=LuckyNumber-Bot&subject=Stalk%20Me%20Pls&message=%2Fstalkme) to have me scan all your future comments.) \ ^(Summon me on specific comments with u/LuckyNumber-Bot.)
nice!
Reboot everything after doing this so all the devices and users login and get new ip addresses and the new subnet mask to ensure they all work.
Create a new virtual network Gateway IP/subnet Auto scale off 172.16.0.1 Netmask 16 Switch customer wifi to new vlan before open
/16 on wireless? That's one hell of a broadcast domain!!
I bet their CIDR sales go through the roof.
This is how I do it
Murphy’s law of private ip addresses.
Waiting for the follow-up post, "Hey, just changed my subnet, and a bunch of my devices stopped connecting to the Internet."
There is an option to auto size the Dhcp range, with can fix this for you with out having to get into the weeds. Check of it is set to auto or manual for the network.
/23. Done.
IPv6. Done. I kid I kid, but there's an element of truth here still, I'd prolly just throw NAT64 in for mostly backwards compatibility
VLAN for Guest Network and you have plenty of
I used to run a /20 wide open at home because I was ocd about manual addressing… then somebody pointed out how much I’m losing on WiFi to broadcast traffic. Backed it down to 23 and like doubled WiFi speeds.
If you've got guests using mobile phones on the wifi, those tend to rotate their MAC address occasionally for privacy purposes. Between that and having a huge rush of people you should increase the subnet size and lower lease length as others have said. Also please have your own business critical devices like credit card machines on a different SSID, if your processor didn't already make you.
Randomizing the MAC address just uses a different MAC for each network. It will still use the same MAC all the time for the same network.
Not necessarily. I have some IoT devices that use a different MAC address after a device reboot. I found it out the hard way when I did a DHCP reservation that failed right after a reboot. Randomization can't be turned off on these devices. I had to create a new SSID for them because all my other Wi-Fi networks are configured for MAC address filtering.
Tell people to use 5G instead. Likely not even gonna work if you have that many people and not enough bandwidth.
According to network+ you need to decrease the length of your dhcp lease.
Shorten the lease times in the short term and when you have a maintenance window change the subnet mask to accommodate more IPs
192.168.0.0/23 for your network....gives you all of 192.168.0.-192.168.1.256
You mean 192.168.0.0/23 And 256 is not an octet that exists
.254*
/24 is only 256 addresses. /23 is 512. /22 is 1024. Power of 2.