Bezüglich Ingeborg Hellemo's Nachricht vom 21.02.2017 11:23 (localtime): > trond.endres...@fagskolen.gjovik.no said: >> Why does lagg0 refer to bge2 and bge3 in the ifconfig output, and not to >> bxe2 and bxe3? > My bad! No cut and paste from the console of the host without net. Wrote most > of it by hand but ended up using cut and paste from another host and forgot > to > edit. > > Correct lines: > laggproto lacp lagghash l2,l3,l4 > laggport: bxe2 flags=0<> > laggport: bxe3 flags=0<> >
There are known problems with laggproto lacp and if_bxe(4) due to full-duplex detection I guess. Workarround seems to be putting if_bxe(4) into promisc mode. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606 Especially comment #8 and #13! Mabye you can add your report to that bug, to raise it's priority. Using if_lagg(4) with laggproto lacp and if_igb(4) doesn't show any problems here on 11(-stable). I also think there were LACPDU changes forcing the switch to be set to active mode, but a very quick look didn't reveal a matching commit, so maybe I'm wrong. Anyway, in your case it seems if_bxe(4) is the root cause, not a configuration mismatch. -harry _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
