[Bug 211436] Link aggregation setting wlan mac changed in 11

[bugzilla-noreply at freebsd.org]

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

Erik Nordstrøm <erik at nordstroem.no> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |erik at nordstroem.no

--- Comment #4 from Erik Nordstrøm <erik at nordstroem.no> ---
(In reply to Jason Bacon from comment #3)

Jason, was this in a fresh install or one with prior configurations?

I have a ThinkPad T520 running FreeBSD 11.0-RELEASE-p2.

Today I decided I wanted to set up failover link aggregation between the wired
and wireless interfaces and I struggled a lot. It was first when I realized
that I had previous configuration for one of the interfaces in
/etc/rc.conf.local in addition to the configuration I had for the other
interface in /etc/rc.conf.

I suggest you

grep -R re0 /etc/

and

grep -R urtwn0 /etc/

and perhaps even

grep -R wlan0 /etc/

on your computer to make sure that you don't have any other network
configuration that interferes with the lagg0.

My working configuration is this:

- Given wired em0 real MAC aa:aa:aa:aa:aa:aa, and
- given wireless iwn0 real MAC bb:bb:bb:bb:bb:bb

I put the following in /etc/rc.conf:

ifconfig_em0="ether bb:bb:bb:bb:bb:bb up"
wlans_iwn0="wlan0"
ifconfig_wlan0="WPA country NO"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 DHCP"

I live in Norway, so obviously use your country code in place of mine.

No other interface config should be present, or it might interfere.

In addition to this, I have my standard /etc/wpa_supplicant.conf from before
unmodified.

I still have to manually

service netif restart lagg0

in order for the routing tables to update, and I might also have to

service dhclient restart lagg0

both of these because the networks I usually are separate for wired and
wireless.

I wish to find a solution for that also but this bug is not the right place for
me to talk about that, I just wanted to mention it for completeness.

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