On Thu, 23 Feb 2017 at 8:43 pm, Alexandre Snarskii wrote:
>
> Hi!
>
> Long story short: if you try to aggregate tap(4) devices into lacp-based
> lagg(4), aggregate will fail to negotiate lacp with remote end and will not
> be able to pass traffic.
>
> Root cause: lacp code requires underlying int
Hi!
Long story short: if you try to aggregate tap(4) devices into lacp-based
lagg(4), aggregate will fail to negotiate lacp with remote end and will not
be able to pass traffic.
Root cause: lacp code requires underlying interface to be full-duplex
(else it will not participate in lacp negotiat
thing it's plugged into, ie
the modem (I'm guessing here - I assume that's what it's plugged into). If
the modem doesn't go over 10mbits half-duplex, then neither will the card
it's plugged into.
Further information r
At 04:18 PM 9/4/2006, Sam Wun wrote:
Hi,
I am running a FreeBSD 5.4 stable as a network router.
I don't know any reason why one of the ethernet ports becomes half-duplex.
Here is its detail:
em1: flags=8843 mtu 1500
options=b
inet 60.1.2.3 netmask 0xfffc broa
On Tue, Sep 05, 2006 at 12:18 , after knocking over a stack of dishes on
the heat sink Sam Wun
wondered out loud about:
> Hi,
> I am running a FreeBSD 5.4 stable as a network router.
> I don't know any reason why one of the ethernet ports becomes half-duplex.
> Here is its deta
Hi,
I am running a FreeBSD 5.4 stable as a network router.
I don't know any reason why one of the ethernet ports becomes half-duplex.
Here is its detail:
em1: flags=8843 mtu 1500
options=b
inet 60.1.2.3 netmask 0xfffc broadcast 220.233.99.39
ether 00:04:23:bc:
Hello,
I'm currently trying to set my 3com 3C985-SX gigabit NIC to Half-Duplex.
I've recompiled FreeBSD to include the ti driver but have been unsuccessful
in setting it to Half-Duplex. I'm currently getting info from a fiber tap
which only sends and cannot recieve. When
