Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 Sep 2015 13:01:11 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-net@FreeBSD.org
Subject:   [Bug 203031] LACP problem with FreeBSD 10.2-RELEASE
Message-ID:  <bug-203031-2472-PVtFGDNtvC@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-203031-2472@https.bugs.freebsd.org/bugzilla/>
References:  <bug-203031-2472@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=203031

--- Comment #3 from gondim@bsdinfo.com.br ---
Hi All,

I'm realizing another strange thing in all FreeBSD 10.2-RELEASE:

Look my ix0:

ix0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
       
options=8407bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO>
        ether 00:1b:21:89:25:28
        inet 192.168.255.1 netmask 0xffffff00 broadcast 192.168.255.255 
        inet6 fe80::21b:21ff:fe89:2528%ix0 prefixlen 64 scopeid 0x1 
        inet6 2804:1054:dead:faca::1 prefixlen 64 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (10Gbase-SR <full-duplex,rxpause,txpause>)
        status: active


<full-duplex,rxpause,txpause> ==> rxpause and txpause is correct?

All servers that are updated showing this message.

-- 
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-203031-2472-PVtFGDNtvC>