From owner-freebsd-net@freebsd.org Thu Mar 22 13:58:27 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6BBE6F69AEA for ; Thu, 22 Mar 2018 13:58:27 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: from mx1.101011010.xyz (mx1.101011010.xyz [94.130.97.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.101011010.xyz", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DBFD475D3A for ; Thu, 22 Mar 2018 13:58:26 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: by mx1.101011010.xyz with ESMTPS id w2MDwI0o063422 for on Thu, 22 Mar 2018 15:58:18 +0200 (EET) X-Authentication-Warning: mx1.101011010.xyz: Host lan.relay.xx [192.168.210.25] claimed to be relay.xx Received: on behalf of honored client by relay.xx with ESMTPS id w2MDvLQG096620 for on Thu, 22 Mar 2018 15:57:22 +0200 (EET) From: "Zeus Panchenko" To: Subject: ether <-> wlan failover still is broken (was: is lagg (re+wlan) working on 11.0-RELEASE?) In-reply-to: Your message of Tue, 18 Oct 2016 14:43:13 +0300 <20161018144313.45827@relay.ibs.dn.ua> References: <20161018144313.45827@relay.ibs.dn.ua> Organization: I.B.S. LLC Reply-To: "Zeus Panchenko" X-Attribution: zeus Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw 15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5 lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M 1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6 7tXQAAAAASUVORK5CYII= X-Mailer: MH-E 8.6; nil; GNU Emacs 25.3.1 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Date: Thu, 22 Mar 2018 15:57:21 +0200 Message-ID: <20180322155721.96618@relay.xx> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 13:58:27 -0000 =2D----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-la= gg-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=3D0x028000 card=3D0x1785103c chip=3D0x0032168= c rev=3D0x01 hdr=3D0x00 vendor =3D 'Qualcomm Atheros' device =3D 'AR9485 Wireless Network Adapter' class =3D network re0@pci0:7:0:0: class=3D0x020000 card=3D0x3387103c chip=3D0x816810ec rev=3D= 0x06 hdr=3D0x00 vendor =3D 'Realtek Semiconductor Co., Ltd.' device =3D 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controll= er' class =3D network subclass =3D ethernet does anybody else face same trouble, please? =2D --=20 Zeus V. Panchenko jid:zeus@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) =2D----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQYIXL6FUmD7SUfqoOveOk+D/ejKgUCWrO2QQAKCRCveOk+D/ej KrUjAJoCx6H9QgcJH97lMklyQZfOy0PrnQCggDki8cJvqdQl+mgWCLkNGePC1Fc=3D =3DvSkJ =2D----END PGP SIGNATURE-----