pfSense KEA DHCP problems after reassigning interface
-
I have a lan type interface, let's call it 'lab.' I reassigned it from lagg0.13 to bge1 recently for some testing. The problems arose when I changed the interface back to lagg0.13 and then shutdown the switch port connected to bge1. DHCP stops working.
After going down a bunch of rabbit holes I can see when running tcpdump on lagg0.13 that DHCP requests are coming in but not being replied to.
As an experiment, I brought up the bge1 interface again (but left it unassigned) and DHCP started working again. I can see, when running tcpdump simultaneously on lagg0.13 and bge1 that DCHP offers only go out when bge1 is up.
I tried restarting the DHCP service to no avail. Rebooting pfSense did the trick, however.
Anyone ever see anything like this?
Thanks,
Matt
-
@whosmatt Yeap, https://redmine.pfsense.org/issues/15899#change-75340
I've been trying to understand this issue for a while now, to help Netgate team to be able to replicate it.
If you can help us updating that ticket, it would help us a lot.
Thanks. -
@mcury I'm not sure that's the same issue. I've actually added and removed members from my lagg many times without DHCP being affected. My issue arises when I assign an interface to a different NIC and then back to the original NIC, which just happens to be a tagged interface with a lagg as the parent. I'm not sure the lagg is relevant.
-
@whosmatt said in pfSense KEA DHCP problems after reassigning interface:
@mcury I'm not sure that's the same issue. I've actually added and removed members from my lagg many times without DHCP being affected. My issue arises when I assign an interface to a different NIC and then back to the original NIC, which just happens to be a tagged interface with a lagg as the parent. I'm not sure the lagg is relevant.
hmmmm
I think that the ticket issue is related to yours but I got it wrong, the problem was not adding or removing members from the LAG.
See, previously I had some VLANs, and the issue happened after I moved them to the LAG interface.
At the same time I added a member and that confused me.So, I really think we have the same issue and I got it wrong when I reported.
This explains why Netgate team couldn't replicate it..Edit: It happened three times, guess what ?
I have three VLANs..