Messages

1

22.1 Legacy Series / Re: Duplicate Entries for Static DHCPv4 leases

« on: April 29, 2022, 08:33:36 pm »

note this fix: https://github.com/opnsense/core/commit/eb0eb519dbe79e81dfe55f735db5a8abff1c10e8

Forgive the ignorant question as I'm unsure of the scope of the link you sent.  If there is a fix identified, would I expect this incorporated in a future release?

2

22.1 Legacy Series / Re: Duplicate Entries for Static DHCPv4 leases

« on: April 29, 2022, 06:01:16 pm »

In my case, the IOT device pulled a DHCP address from the pool.  I clicked on the + sign next to that lease entry and made that same address static.

The system does allow this.  It was my understanding this essentially creates that static reservation.  This way that client will ALWAYS pull the same IP from the pool.

I see folks testing this by creating a new static IP outside of the pool.  In my case, I'm looking to create a DHCP static reservation by using the + side in the leases tab.

3

22.1 Legacy Series / Re: Duplicate Entries for Static DHCPv4 leases

« on: April 29, 2022, 04:51:51 pm »

Could there be multiple client UID's coming from those devices? Perhaps checking the "Ignore Client UIDs" may sort it?

Thanks for responding.  I was under the impression that the multiple UID would pull additional addresses in that case.  These all show the same IP address assigned.

Additionally, these devices did no show multiple leases until I converted them to static assignments.  Thats when the duplicates showed up.

I just tested this setting to be sure and saw no change.

4

22.1 Legacy Series / Duplicate Entries for Static DHCPv4 leases

« on: April 29, 2022, 02:47:50 pm »

Hey folks.

 Newbie to Opnsense and working on migrating some of my home+Lab network over.

 As I'm moving traffic, I'm assigning static DHCP entries for many of my IoT devices.  Everytime I go through the process of adding it as static, I get multiple entries for the same IP in my lease report.

  While this does not seem to affect functionality, It seems incorrect.   Anyone have any idea if this is something I'm doing or perhaps a bug?