Bug 208235

Summary:	Link Aggregation Lacp not working on 10.3-RC3
Product:	Base System	Reporter:	sk8harddiefast
Component:	kern	Assignee:	freebsd-net (Nobody) <net>
Status:	New ---
Severity:	Affects Many People	CC:	bugmeister, emaste, girgen
Priority:	---
Version:	10.3-BETA2
Hardware:	amd64
OS:	Any
See Also:	https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

Description sk8harddiefast 2016-03-23 10:53:36 UTC

This is the output of uname -a

FreeBSD FreeBSD 10.3-RC3 FreeBSD 10.3-RC3 #0 r296998: Fri Mar 18 01:08:19 UTC 2016     root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64


This is my /etc/rc.conf

hostname="FreeBSD"
#ifconfig_re0="inet 192.168.1.18 netmask 255.255.255.0"
ifconfig_msk0="up"
ifconfig_re0="up"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto lacp laggport msk0 laggport re0 192.168.1.18/24"
defaultrouter="192.168.1.1"

My /etc/hosts.allow

ALL : ALL : allow

My /etc/resolv.conf

nameserver 192.168.1.1
nameserver 78.87.0.162
nameserver 78.87.0.195
nameserver 78.87.0.122

Using failover everything works. Using lacp I get error on boot 

ifconfig_create: Bad value

Also lagg0 gets active but msk0 and re0 are completely down.

Comment 1 Palle Girgensohn freebsd_committer

2016-03-25 11:47:26 UTC

I see the same thing with 10.2-RELEASE using bxe.

Had to use loadbalance, the lacp just refused. On multiple machines running 10.2p12 or similar.



this works:

ifconfig_lagg0="laggproto loadbalance laggport bxe0 laggport bxe1 192.168.1.81/24"


this doesn't

ifconfig_lagg0="laggproto lacp laggport bxe0 laggport bxe1 192.168.1.81/24"


can't remember exactly how the error was described, but I couldn't get it working.

Comment 2 Palle Girgensohn freebsd_committer

2016-03-25 11:56:25 UTC

the original report rings a bit like it would be an rc-script bug.

What I saw was that ifconfig didn't work at all. don't remeber exact wording of error messages, and machines are in production now, so I can't really test it on them. It works fine for an older machine with 1gbit bce, but the 10gbit bxe failed.

Comment 3 Mark Linimon freebsd_committer

2024-09-30 12:10:37 UTC

^Triage: to submitter: is this still a problem on supported versions of FreeBSD?