[Bug 240825] Vlan interfaces does not work on lagg from em0, em1

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240825

Eugene Grosbein <eugen at freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Open
                 CC|                            |eugen at freebsd.org,
                   |                            |gallatin at FreeBSD.org,
                   |                            |jhb at FreeBSD.org,
                   |                            |mav at FreeBSD.org

--- Comment #2 from Eugene Grosbein <eugen at freebsd.org> ---
>From console.log at boot time:

lagg0.11: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1496
        options=403<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=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>

mtu=1496 for lagg0.11 (while mtu=1500 for lagg0) means that vlan was created
while lagg0 had no registered members with hardware vlan support. This is very
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.

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