Project

General

Profile

Actions
Copy link

Regression #15899

open

LAGG LACP - adding a member stops DHCP from working

Added by Marcelo Cury 16 days ago. Updated 12 days ago.

Status:
Incomplete
Priority:
Low
Assignee:
-
Category:
LAGG Interfaces
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
24.11
Affected Architecture:
4100

Description

Noticed that if you add a member to the LACP lag0 group, DHCP will stop answering on the VLANs on this group.
A reboot fixes the problem.

Unfortunately I didn't have time to troubleshoot it further.

Actions taken:
Tried a restart the DHCP service, no joy (Using KEA, didn't try ISC-DHCP).
Captured packets on the VLAN, and found UDP 67 from 0.0.0.0 reaching pfSense, but no answer.
Reboot, this fixed the problem.

Actions
Copy link
 #1

Updated by Steve Wheeler 16 days ago

  • Tracker changed from Bug to Regression

Haven't been able to replicate this so far. Which interfaces were you using in the LAGG? How many?

Actions
Copy link
 #2

Updated by Marcelo Cury 15 days ago

Steve Wheeler wrote in #note-1:

Haven't been able to replicate this so far. Which interfaces were you using in the LAGG? How many?

Hello Steve,thanks for answering, igc0, igc1 and igc2.

Opened this ticket after removing igc2 from the LACP and the problem described above happened.

This happened a few times:

Firstly I didn't have any LACP setup here, so created one using interface assignments, created the VLANs and moved these VLANs to LAG0 group which initially only had igc0 and igc1 interfaces, the problem happened. Had to reboot to fix.

A few days later, I decided to include igc2 interface to the LAG, then the problem happened again. Had to reboot.

And lastly, just for the sake of testing if this would happen again, I removed igc2 interface from the LAG and was able to confirm this behavior.

If you need more details, feel free to ask and I'll test and provide the results after the working hours.

Actions
Copy link
 #3

Updated by Jordan G 13 days ago

Also unable to replicate so far with my 4100, adding/removing an interface to my existing LACP LAGG did not effect KEA/DHCP in terms of service status on dashboard or perceived functionality when trying to connect devices on the network.

Actions
Copy link
 #4

Updated by Marcelo Cury 13 days ago

Hello Jordan, thanks for testing.
It must be something particular to my setup then.

Since both of you couldn't replicate this issue, please go ahead and close this bug report.

Thanks for your efforts and time on this, both of you.

Actions
Copy link
 #5

Updated by Jim Pingle 12 days ago

  • Status changed from New to Incomplete

We can mark it incomplete for now. If you can figure out what contributing factor in your setup is triggering the behavior so we can replicate the problem, we can look into it again.

Actions
Copy link

Also available in: Atom PDF