Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 03 Jun 2022 06:54:50 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 261100] After update to FreeBSD 13 Stable ( stable/13 aef4a2f5a ) lagg0 stop receiving traffic
Message-ID:  <bug-261100-227-Xiz2mDsTgl@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-261100-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-261100-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261100

Rudolph <rudolphfroger@dreamsolution.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rudolphfroger@dreamsolution
                   |                            |.nl

--- Comment #3 from Rudolph <rudolphfroger@dreamsolution.nl> ---
I've got a very similar problem when updating from FreeBSD 12.3 to 13.1. Wi=
th
FreeBSD 12 our setup with lagg and vlans worked fine.

Snippet from our /etc/rc.conf:

ifconfig_bge0=3D"up"
ifconfig_em0=3D"up"
cloned_interfaces=3D"lagg0"
ifconfig_lagg0=3D"laggproto lacp laggport bge0 laggport em0"
vlans_lagg0=3D"33"
ifconfig_lagg0_33=3D"inet 192.168.0.10/24"
defaultrouter=3D"192.168.0.1"

When I add -vlanmtu to both bge0 and em0 then it seems to works just fine:

ifconfig_bge0=3D"-vlanmtu up"
ifconfig_em0=3D"-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.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261100-227-Xiz2mDsTgl>