DHCP lease does not show in multiple VLANs

jwoodard80 commented 4 years ago

Important notices Before you add a new report, we ask you kindly to acknowledge the following:

[-] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md

[-] I have searched the existing issues and I'm convinced that mine is new.

Describe the bug I'm not sure I described the problem correctly. However, I had a device that was static assigned in one VLAN (VLAN0 -> 10.20.30.x), however, was accidentally connected in another (VLAN 90 -> 10.20.90.x). The logs showed that the device was given a IP in VLAN90, however, it did not appear in the leases.

I spent several minutes trying to figure out what was going on and checking logs. I finally tested by deleting the static assigned and refreshing. After refreshing, my IP lease in the incorrect VLAN appeared.

I am unsure if this is by design, however, I don't believe it should be. When I click "Leases" I'm assuming that i'm going to be seeing ALL leases. I should be able to see that a MAC is appearing in both VLANs as this is what we display the online/offline for. If an address appears online in VLAN "X" it should (depending on lease times, etc) be offline VLAN "Y".

To Reproduce Steps to reproduce the behavior:

Create 2 VLANs
Create a static lease in VLAN 1 for device
Bring device up in VLAN 2
Device will not show in the "Leases" page in VLAN 2 but will continue to show offline in VLAN 1
However, the device can be looked up in the Logs

Expected behavior Leases should show ALL leases including duplicates. In the above example I would expect to see an offline static lease in the correct desired location but ALSO a DHCP lease in the incorrect VLAN.

Environment OPNsense 20.1.3-amd64 FreeBSD 11.2-RELEASE-p17-HBSD OpenSSL 1.1.1d 10 Sep 2019 CPU Type Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz (4 cores)

jwoodard80 commented 4 years ago

Can someone please let me know what I can do to change this from "incomplete"? Is this something I have left out?

jwoodard80 commented 4 years ago

I have edited the ticket to hopefully make it somehow complete.

klausagnoletti commented 4 years ago

Just wanted to chip in on this. I have the same problem (and has had it for quite a while with no idea what to do about it).. I have a 1-physical NIC (opnsense on a NUC) and a managed switch. VLAN30 is my LAN where I have all my clients. Here I experience that I can't see or edit all current DHCP leases. Some just aren't there. For instance, there is an expired lease for my laptop (flaplet) on 10.20.30.50 showing up in the GUI (which I can't edit or delete). This lease isn't effectuated - instead the client gets a random ip at 10.20.30.129. I have a few other examples. All leases are created a lot of releases ago on a fw that has been continually updated for at least 2-3 yrs. Maybe that is related somehow.

jwoodard80 commented 4 years ago

Can anyone let me know if any progress has been made on this? @AdSchellevis is there anything else I can do to help resolve this?

AdSchellevis commented 4 years ago

it's a community support ticket, by my knowledge dhcpd doesn't know which interface is involved, all leases are collected in /var/dhcpd/var/db/dhcpd.leases

AdSchellevis commented 3 years ago

This issue has been automatically timed-out (after 180 days of inactivity).

For more information about the policies for this repository, please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.

If someone wants to step up and work on this issue, just let us know, so we can reopen the issue and assign an owner to it.

dj0abr commented 3 years ago

Hi, just found this closed issue, I have the same problem with OpnSense 21.1.1 I have 3 VLANs. Services: DHCPv4: Leases only shows leases from the first VLAN. Anyway, the DHCP servers on the other VLANs are working fine, but the leases are not shown in the list.

marjohn56 commented 3 years ago

Can only say that they all show up find on mine - Static and dynamic `

`

dj0abr commented 3 years ago

a friend has no problem too, all is show. Another friend has the same problem I have, only one vlan is shown. So it looks to be a sporadic problem. How can we track it?

marjohn56 commented 3 years ago

Let's try and work out the commonalities, I am all static, running OPNsense 21.7.a_113-amd64. I also have static assigned leases on each VLAN as well as dynamics.

marjohn56 commented 3 years ago

Let's also check our ranges. My statics are always below 100 or above 199, dynamics are between 100 & 199 only. NOTE - Not true, I changed that, IOT is between 100 and 240!

pattisonmichael commented 3 years ago

I Have the same issue on OPNsense 21.1.5. If there is a static map it will not show a dynamic lease anymore. However it will show the static map online based on the MAC but that wrong. For example I had a device getting 192.168.70.10 from the dynamic range. Then I changed it to a static map at 192.168.70.4. Now I see the lease for 192.168.70.4 as online but actually the device is still on .10 reachable. This is very irritating as it's not a true reflection of the dhcp leases. The logs show correctly that the device is on .10 in the dynamic range. @AdSchellevis can you reopen this ticket please?

AdSchellevis commented 3 years ago

@pattisonmichael not without someone volunteering to work on it, no, please read our contributing guideline for details about our policy (https://github.com/opnsense/core/blob/master/CONTRIBUTING.md)

pattisonmichael commented 3 years ago

@AdSchellevis I read through this now but i'm not sure which part you refer too. Anyways this seems to me like a quiet serious bug, DHCP being a core function of a router and it seems like there are enough people affected to at least raise their voice in this ticket.

I'm not expecting instant results but feel that this should at least warrant further investigation by someone who knows the in and outs.

AdSchellevis commented 3 years ago

issues timeout after 180 days, if there's no one actively working on it. It was marked as support by the way, just remember that issues aren't always bugs. Looking at the comments, it looks like multiple people already have taken a look at it by the way..

RandMental commented 2 years ago

Still the same problem

NateroniPizza commented 1 year ago

Issue still present.

SMAW commented 1 year ago

Same Issue here, v23.1.11

opnsense / core

DHCP lease does not show in multiple VLANs #3962