Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error allocating DHCP Addresses #908

Open
rednus opened this issue Apr 22, 2024 · 4 comments
Open

Error allocating DHCP Addresses #908

rednus opened this issue Apr 22, 2024 · 4 comments

Comments

@rednus
Copy link

rednus commented Apr 22, 2024

I have couple of devices that restart every night, and the next morning they are not on the network (ping fails) with below error repeating on the logs. Not sure if this is an issue with the device, router (I use Nest Wifi Pro) or Technitium. Help please.

[2024-04-22 11:45:59 Local] [0.0.0.0:68] DHCP Server offered IP address [192.168.1.33] to CAMERA [XX-XX-XX-XX-XX-XX] for scope: Default
[2024-04-22 11:46:00 Local] DHCP Server cannot allocate reserved lease [192.168.1.33] to XX-XX-XX-XX-XX-XX for scope 'Default': The IP address is already allocated.
[2024-04-22 11:46:00 Local] DHCP Server cannot allocate reserved lease [192.168.1.33] to XX-XX-XX-XX-XX-XX for scope 'Default': The IP address is already allocated.
[2024-04-22 11:46:00 Local] DHCP Server cannot allocate reserved lease [192.168.1.33] to XX-XX-XX-XX-XX-XX for scope 'Default': The IP address is already allocated.

Additional info:

  • I have a lot of my devices with fixed leases setup in the scope
  • Most devices like mobiles & cars are not on network continuously
  • Some devices are setup to reboot at each night
  • Some devices can not be restarted easily to get new IP (like home power gateway or solar inverter)
  • I have 3 nest wifi pro devices spread around the house (they use .252, .253 and .254)
  • When the above error occurs the only way to resolve is to restart the network/router
@ShreyasZare
Copy link
Member

Thanks for the post. I am assuming that the MAC addresses in these log entries are all same. Do you have the "Ignore Client Identifier (Option 61)" option enabled in your Default scope? Usually this issue comes up since some devices generate a new client identifier when they reboot and thus making it not possible to assign same IP address to them. Enabling the "Ignore Client Identifier (Option 61)" option fixes these kind of issues.

@rednus
Copy link
Author

rednus commented Apr 23, 2024

Hi Shreyas,

I have enabled this option now. Will let you know if this has been resolved.

Thanks

@ShreyasZare
Copy link
Member

I have enabled this option now. Will let you know if this has been resolved.

Since it was not enabled earlier, the existing reserved leases will need to be deleted manually otherwise existing clients wont receive these lease until they expire and would get a dynamic lease assigned till then.

@rednus
Copy link
Author

rednus commented Apr 23, 2024

Thanks. I only have 1 or 2 dynamic leases in the network all others are Reserved leases.

I will restart the network when I get a chance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants