ether <-> wlan failover still is broken (was: is lagg (re+wlan) working on 11.0-RELEASE?)

[Zeus Panchenko]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

hi,

while having no any problem with separate (lagg less) mode, when I use
ether or wlan without aggregating, I am still experiencing severe problem
with ether <-> wlan failover

after upgrade to 11.1 I decided to give another try to the handbook Example 
30.3.
https://www.freebsd.org/doc/handbook/network-aggregation.html#networking-lagg-wired-and-wireless

it still does *not* work for me

after wlan MAC address change (to the one of the ethernet as it's described in
the handbook), wpa_supplicant becomes unable to associate with AP

> uname -a
FreeBSD 11.1-RELEASE-p8 #0

> pciconf -lv
ath0@pci0:3:0:0:class=0x028000 card=0x1785103c chip=0x0032168c rev=0x01 
hdr=0x00
vendor = 'Qualcomm Atheros'
device = 'AR9485 Wireless Network Adapter'
class  = network
re0@pci0:7:0:0: class=0x02 card=0x3387103c chip=0x816810ec rev=0x06 hdr=0x00
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
class  = network
subclass   = ethernet


does anybody else face same trouble, please?

- -- 
Zeus V. Panchenko   jid:z...@im.ibs.dn.ua
IT Dpt., I.B.S. LLC   GMT+2 (EET)
-BEGIN PGP SIGNATURE-

iF0EARECAB0WIQQYIXL6FUmD7SUfqoOveOk+D/ejKgUCWrO2QQAKCRCveOk+D/ej
KrUjAJoCx6H9QgcJH97lMklyQZfOy0PrnQCggDki8cJvqdQl+mgWCLkNGePC1Fc=
=vSkJ
-END PGP SIGNATURE-
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: is lagg (re+wlan) working on 11.0-RELEASE?

[Kevin Oberman]

On Wed, Nov 16, 2016 at 1:34 AM, Zeus Panchenko  wrote:

> thanks for quick reply
>
> J.R. Oldroyd  wrote:
> > There is a work-around.  Configure the re interface with the MAC
> > address of the wlan instead of the other way around.
>
> I done it and here is what happens:
>
> 1. I boot notebook with wire *not* plugged in,
>wlan is up, associated and authed, network is OK
>
> 2. I plug wire and network becomes stale
>
> 3. I run `tcpdump -ni lagg0' to see what's going on and oh wonder,
>network comes back lo life!
>
>
> so ... either to not to use lagg or run tcpdump constantly ... it is
> rather weird :(
>
> --
> Zeus V. Panchenko   jid:z...@im.ibs.dn.ua
> IT Dpt., I.B.S. LLC   GMT+2 (EET)
>

A bit odd, but not weird. Running tcpdump turns on promiscuous mode. Try
"tcpdump -p"  and I'm pretty sure it will not make any difference.

The real question is where the fault lies. It looks like the problem may be
in the re(4) driver. It looks to me like the "new" MAC address is not
getting properly instantiated so that packets to that MAC address are being
ignored. It is also possible that the packets are being sent to the correct
IP address, but the wrong MAC. (Pretty unlikely, though.)

What does ipconfig re0 show? Is the MAC correct? Capture traffic (tcpdump
-pe dst host LAGG-IP-ADDRESS) and confirm that the MAC and IP addresses are
correct. If they are, the issue is either hardware or the driver.

Since re-writing the MAC is a fairly uncommon operation so it is possible
that the firmware has an issue and it may be specific to a less common re
variant. Of course, slight differences in hardware revisions can trigger
driver issues that don't break things on most variants. And, lest I knew,
RealTek did not provide documentation adequate to write a driver and this
makes drivers more likely to have subtle bugs.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: is lagg (re+wlan) working on 11.0-RELEASE?

[Zeus Panchenko]

thanks for quick reply

J.R. Oldroyd  wrote:
> There is a work-around.  Configure the re interface with the MAC
> address of the wlan instead of the other way around.

I done it and here is what happens:

1. I boot notebook with wire *not* plugged in,
   wlan is up, associated and authed, network is OK

2. I plug wire and network becomes stale

3. I run `tcpdump -ni lagg0' to see what's going on and oh wonder,
   network comes back lo life!


so ... either to not to use lagg or run tcpdump constantly ... it is
rather weird :(

-- 
Zeus V. Panchenko   jid:z...@im.ibs.dn.ua
IT Dpt., I.B.S. LLC   GMT+2 (EET)


pgpQC1881A51t.pgp
Description: PGP signature

Re: is lagg (re+wlan) working on 11.0-RELEASE?

[Zeus Panchenko]

thanks for quick reply

J.R. Oldroyd  wrote:
> There is a work-around.  Configure the re interface with the MAC
> address of the wlan instead of the other way around.

I done it and here is what happens:

1. I boot notebook with wire *not* plugged in
   wlan is up, associated and authed, network is OK

2. I plug wire and network becomes stale

3. I run `tcpdump -ni lagg0' to see what's going on and oh, wonder,
   network comes back lo life!


so ... either to not to use lagg or run tcpdump constantly ... it is
rather weird :(

-- 
Zeus V. Panchenko   jid:z...@im.ibs.dn.ua
IT Dpt., I.B.S. LLC   GMT+2 (EET)


pgpi3chBzMziI.pgp
Description: PGP signature

Re: is lagg (re+wlan) working on 11.0-RELEASE?

[J.R. Oldroyd]

On Tue, 18 Oct 2016 14:43:13 +0300 "Zeus Panchenko"  wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> I'm using lagg(4) in failover to set up roaming between wired and
> wireless networks, just as manual describes (last example) and all
> was working perfectly on 11-CURRENT
> 
> now on 11.0-RELEASE (with the same configuration) wlan interface is
> unable to associate and auth against AP, while wired link works as
> expected
> 

It does not work as you have it configured, see PR#213207.

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

There is a work-around.  Configure the re interface with the MAC
address of the wlan instead of the other way around.

-jr
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"