Date: Thu, 26 Sep 2019 04:20:49 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 240825] Vlan interfaces does not work on lagg from em0, em1 Message-ID: <bug-240825-7501-gmFcRLHJlu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-240825-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-240825-7501@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=3D240825 Eugene Grosbein <eugen@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open CC| |eugen@freebsd.org, | |gallatin@FreeBSD.org, | |jhb@FreeBSD.org, | |mav@FreeBSD.org --- Comment #2 from Eugene Grosbein <eugen@freebsd.org> --- >From console.log at boot time: lagg0.11: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu= 1496 options=3D403<RXCSUM,TXCSUM,LRO> ether 00:e0:81:ba:ad:90 inet xx.xx.170.82 netmask 0xfffffff0 broadcast xx.xx.170.95 groups: vlan vlan: 11 vlanpcp: 0 parent interface: lagg0 media: Ethernet autoselect status: active nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> mtu=3D1496 for lagg0.11 (while mtu=3D1500 for lagg0) means that vlan was cr= eated while lagg0 had no registered members with hardware vlan support. This is v= ery strange. It looks like some race condition at boot time between internal lagg configuration and another ifconfig process creating vlan over lagg. Adding CC: for some people that worked with lagg(4) code recently. --=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-240825-7501-gmFcRLHJlu>