Summary: | After update to FreeBSD 13 Stable ( stable/13 aef4a2f5a ) lagg0 stop receiving traffic | ||
---|---|---|---|
Product: | Base System | Reporter: | Rumen Palov <rpalov> |
Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | New --- | ||
Severity: | Affects Many People | CC: | jeroen.pulles, rudolphfroger |
Priority: | --- | ||
Version: | 13.0-STABLE | ||
Hardware: | amd64 | ||
OS: | Any |
Description
Rumen Palov
2022-01-11 09:02:05 UTC
Hello again, I have tried new FreeBSD stable/13 compilation - today checkout, but the lagg interface is still not working. The workaround is to install older version, which is known to work. Hello all, the reason for not receiving traffic in FreeBSD 13.0 / 13.1 is the present vlan devices in cloned_interfaces pragma in /etc/rc.conf. When we remove the vlans from cloned_interfaces they are working properly. To be more clear, when we have configuration like this, after update from FreeBSD 12 to FreeBSD 13, vlans stop working: cloned_interfaces="lagg0 vlan100" vlans_lagg0="vlan100" .......... create_args_vlan100="vlan 100 vlandev lagg0" ifconfig_vlan100="inet 192.168.0.1/24" When we remove the vlan100 from cloned_interfaces, vlans start working. Until FreeBSD 13 they are working even present in cloned_interfaces. What change is affecting that behavior ? I've got a very similar problem when updating from FreeBSD 12.3 to 13.1. With FreeBSD 12 our setup with lagg and vlans worked fine. Snippet from our /etc/rc.conf: ifconfig_bge0="up" ifconfig_em0="up" cloned_interfaces="lagg0" ifconfig_lagg0="laggproto lacp laggport bge0 laggport em0" vlans_lagg0="33" ifconfig_lagg0_33="inet 192.168.0.10/24" defaultrouter="192.168.0.1" When I add -vlanmtu to both bge0 and em0 then it seems to works just fine: ifconfig_bge0="-vlanmtu up" ifconfig_em0="-vlanmtu up" Another way we got this to work (without -vlanmtu) is manually issuing "ifconfig em0 up" and "ifconfig bge0 up" after the machine has booted. Unfortunately my previous message is incorrect. The "-vlanmtu" doesn't reliably make the combination of lagg and vlan work. Sometimes the combination of lagg with vlans works after a reboot and sometimes it doens't. After a boot bringing the hardware interfaces down and back up again seems to always solve the issue. Also see bug #240825 which may or may not be related. |