From owner-freebsd-wireless@freebsd.org Tue Jan 12 22:01:06 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8ACB7A803E2; Tue, 12 Jan 2016 22:01:06 +0000 (UTC) (envelope-from cochard@gmail.com) Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E884C1DAA; Tue, 12 Jan 2016 22:01:05 +0000 (UTC) (envelope-from cochard@gmail.com) Received: by mail-lb0-x235.google.com with SMTP id x4so23660033lbm.0; Tue, 12 Jan 2016 14:01:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=zDwbh3qAi+dCt9Jr66r/egTUH4SEiFlnK/GeTYX2xkw=; b=Gh1/auH4im7O/DqHx/mVtx5buqbcWbrHYFgEoEJeTSxN7JASOyqHhH/FkRVEGnsQ+m 19Ras2I0Gf4tLtbRDBMUXgzmNPRj3wKY1cVFHzbxydeO/6xhX47zDHBK7vmfp4jn36bm Nwkg925wmGu0qwDIovnU+S5aKkrPRvNVOE7aaiDB0xQseDvAVk14t5El+WF+nzasPbBe EhDH0lT3Fp2uqAiHsHNRUtmJ2bZm+H3UPzl6RaCi1D/w5myImKQ/Gi8DZ+MngP7nhSE/ XnpeBcou5tG/xwoTl/vkWaUonzOe82SaB3KTqxHDjeDw6lguSqT5o/rbpiml+YqExAjo FbZA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cochard-me.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=zDwbh3qAi+dCt9Jr66r/egTUH4SEiFlnK/GeTYX2xkw=; b=rlw3/9oqoR3paRSJRq6f9RyclYmIETIURPZrH7vyc/gfdNaJyGCPymc8CJJt6qdpqe o7QaXi8pGfGYT3jqNkqaPwjoO4cDGTK9H4Ly9q4dRXL5BaG2921dmgLRFNEtOkxnry/y jBz5LBtGQwXRlB0trV9RONk0qEaFdd4Vj5T+flLmAv0OhLHvifiZdx6rObJV+Vj+y1K9 BJqI6CotjhxB4kDz6EmQYqGwzWo6dr4x4HybE3rl8O3dWRtSnCJ+mta8nZ6iWEJDlsT1 bsdDsKkCkG+ior1+DfmBmOVMVxBLGZ9lAvHdf9edr4gH208XdmMEywUeV07V/LY7lc/q VNAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=zDwbh3qAi+dCt9Jr66r/egTUH4SEiFlnK/GeTYX2xkw=; b=eJJ/oXDPy0wGYYm1PvO6XQXHxBQJQSb0a10zc08TQN4SYqfjrWipV+TmbotEGv7mLk QwWkisqAuxxLShwj3S/bjvdFIRwN+l2OsAKFSYqThs1/wofDVYBZNma63EeDP6ukZWjx igr+MxYgok7Zvgkps0tZNlDBtnXcY7J6jEuZ9tSwBOMkT8Rcmb19YMUMz8+Ub52xtBMt Own7FOZYyQbhurz9H9QFzYHbl1/BZiFyeGSymjgac3NwMvNIwcnHxvOMOsVOR7d1OSnT /OAaab16+T72C0ZUz4GLf5KlgCtSwR65aBIqLRqNE9XDgPbMHWrbMpjyaQyQRlXaTQfQ Sraw== X-Gm-Message-State: ALoCoQmtCu/hnRucA77B7I/Hm1kVEGZzHl9gscBDNwGhX4cmn6s2iweXCuy6/N0TEnvBLv0f0HhT1vAIBRNcz9oY5a9cbdAmdw== X-Received: by 10.112.14.234 with SMTP id s10mr49638010lbc.136.1452636063482; Tue, 12 Jan 2016 14:01:03 -0800 (PST) MIME-Version: 1.0 Sender: cochard@gmail.com Received: by 10.25.136.11 with HTTP; Tue, 12 Jan 2016 14:00:43 -0800 (PST) In-Reply-To: <1223091452631961@web14j.yandex.ru> References: <1223091452631961@web14j.yandex.ru> From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Tue, 12 Jan 2016 23:00:43 +0100 X-Google-Sender-Auth: tfSHIlK62wJg4ZUPsgk0WS8sgLc Message-ID: Subject: Re: forwarding didn't work if wlan0 is member of a bridge To: "Alexander V. Chernikov" Cc: Adrian Chadd , "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jan 2016 22:01:06 -0000 On Tue, Jan 12, 2016 at 9:52 PM, Alexander V. Chernikov < melifaro@freebsd.org> wrote: > > Could you show 'netstat -rn' output when one of bridge members is down? > Btw, I tried to reproduce it today (but, with ix0 instead of wlan0) and I > wasn't able to trigger the problem. > > =E2=80=8BSure, here some output with the re1 (member of bridge) unplugged: root@ =E2=80=8Bfbsd-router :~ # ifconfig bridge0 bridge0: flags=3D8843 metric 0 mtu 1500 ether 02:6b:c0:de:b8:00 inet 1.1.1.1 netmask 0xffffff00 broadcast 1.1.1.255 nd6 options=3D9 groups: bridge id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: wlan0 flags=3D143 ifmaxaddr 0 port 5 priority 128 path cost 33333 member: re1 flags=3D143 ifmaxaddr 0 port 2 priority 128 path cost 55 root@ =E2=80=8Bfbsd-router :~ # ifconfig re1 re1: flags=3D8943 metric 0 mtu 1500 options=3D82099 ether 00:0d:b9:3c:ae:25 nd6 options=3D29 media: Ethernet autoselect (none) status: no carrier root@ =E2=80=8Bfbsd-router=E2=80=8B :~ # netstat -r =E2=80=8B4=E2=80=8B n Routing tables Internet: Destination Gateway Flags Netif Expire 1.0.0.0/24 link#1 U re0 1.0.0.1 link#1 UHS lo0 1.1.1.0/24 link#6 U bridge0 1.1.1.1 link#6 UHS lo0 127.0.0.1 link#4 UH lo0 During this "one-member-unplugged", the freebsd-router can still ping each hosts on different connected interface, it just "refuse" to forward between its interfaces: root@fbsd-router:~ # ping 1.1.1.2 (the wireless client connected to wlan0, member of the bridge0 interface) PING 1.1.1.2 (1.1.1.2): 56 data bytes 64 bytes from 1.1.1.2: icmp_seq=3D0 ttl=3D64 time=3D4.600 ms 64 bytes from 1.1.1.2: icmp_seq=3D1 ttl=3D64 time=3D5.878 ms ^C --- 1.1.1.2 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev =3D 4.600/5.239/5.878/0.639 ms root@fbsd-router:~ # ping 1.0.0.2 (an host on the LAN0) PING 1.0.0.2 (1.0.0.2): 56 data bytes 64 bytes from 1.0.0.2: icmp_seq=3D0 ttl=3D64 time=3D0.282 ms 64 bytes from 1.0.0.2: icmp_seq=3D1 ttl=3D64 time=3D0.280 ms ^C --- 1.0.0.2 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev =3D 0.280/0.281/0.282/0.001 ms root@fbsd-router:~ # arp -na ? (1.1.1.1) at 02:6b:c0:de:b8:00 on bridge0 permanent [bridge] ? (1.1.1.2) at 00:c0:ca:7e:8b:fe on bridge0 expires in 1055 seconds [bridge= ] ? (1.0.0.1) at 00:0d:b9:3c:ae:24 on re0 permanent [ethernet] ? (1.0.0.2) at 0c:c4:7a:6b:a6:d3 on re0 expires in 1106 seconds [ethernet] =E2=80=8BAnd the wireless client (1.1.1.2) can still ping the fbsd-router b= ridge interface (1.1.1.1) too (for answering to the Adrian question).=E2=80=8B Now I replug re1: root@fbsd-router:~ # ifconfig re1 re1: flags=3D8943 metric 0 mtu 1500 options=3D82099 ether 00:0d:b9:3c:ae:25 nd6 options=3D29 media: Ethernet autoselect (1000baseT ) status: active and here are netstat output (no changes with previous): root@fbsd-router:~ # netstat -r4n Routing tables Internet: Destination Gateway Flags Netif Expire 1.0.0.0/24 link#1 U re0 1.0.0.1 link#1 UHS lo0 1.1.1.0/24 link#6 U bridge0 1.1.1.1 link#6 UHS lo0 127.0.0.1 link#4 UH lo0 Because you didn't reach to reproduce with ix0 in place of wlan0, I've did some modification to my bridge setup: 1. In place of using re1+wlan0, I've put re1+re2 in the bridge0. And I've connected an host on re2: I didn't reach to reproduce the problem too, then= I confirm we didn't have this bug with 2 Ethernet Interfaces. 2. In place of using PCI ath(4) (Atheros 9280), I've plugged an USB rum(4) (old Ralink) and configured it as wlan0 like was the ath0: the bridge0 was reverted to re1+wlan0. And I reach to reproduce the problem with a different wireless card: This thread seems correctly belong to the "wireless" mailing-list :-)