From owner-freebsd-wireless@freebsd.org Sun Jan 10 14:12:36 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 BF2CDA6A35E for ; Sun, 10 Jan 2016 14:12:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AFC3A1BBC for ; Sun, 10 Jan 2016 14:12:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0AECaib031675 for ; Sun, 10 Jan 2016 14:12:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203105] [new driver] Port openbsd rtwn, new rtl8188ce driver Date: Sun, 10 Jan 2016 14:12:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: evil.lombo@gmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sun, 10 Jan 2016 14:12:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203105 --- Comment #15 from Simone Mario Lombardo --- Hi, tried the module and the card was detected fine and it's working. So far I get three issues with it: - WPA2 authentication seems to work only the first time to me. If I stop wpa_supplicant or put down the wifi card via ifconfig, the further authenticaitona fails for expired timeout. -Speed seems limited to 16Mbps rate (around 120 kbps on downstream),even th= ough the ifconfig summary show 802.11g/56mbps. - After heavy usage, it stops working and dmesg shows a "rtwn0: can't map to rbuf (error: 12)" (12 =3D ENOMEM) and after some mins of this error, the ke= rnel panics. I can't restore the wifi status via ifconfig and I have to reboot t= he laptop. Which kind of info do you need for troubleshooting? Thanks, Simone --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Sun Jan 10 15:18:10 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 7435FA6B9CE for ; Sun, 10 Jan 2016 15:18:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 64F641309 for ; Sun, 10 Jan 2016 15:18:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0AFI9WJ029059 for ; Sun, 10 Jan 2016 15:18:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203105] [new driver] Port openbsd rtwn, new rtl8188ce driver Date: Sun, 10 Jan 2016 15:18:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: s3erios@gmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sun, 10 Jan 2016 15:18:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203105 Andriy Voskoboinyk changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |s3erios@gmail.com --- Comment #16 from Andriy Voskoboinyk --- (In reply to Simone Mario Lombardo from comment #15) Hi, > - WPA2 authentication seems to work only the first time to me. If I stop= =20 > wpa_supplicant or put down the wifi card via ifconfig, the further=20 > authenticaitona fails for expired timeout. Can you test the patch from https://reviews.freebsd.org/D4820 ? It should f= ix this issue. Also, > or put down the wifi card via ifconfig If I understand this correctly (ifconfig wlan0 down; ifconfig wlan0 up), th= en you will need to restart wpa_supplicant too (wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf) (+ 'dhclient wlan0' for DHCP); or just recreate t= he interface (ifconfig wlan0 down && ifconfig wlan0 destroy && ifconfig wlan0 create wlandev rtwn0) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Sun Jan 10 16:25:36 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 27993A69F9C for ; Sun, 10 Jan 2016 16:25:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1864510EA for ; Sun, 10 Jan 2016 16:25:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0AGPZsx092283 for ; Sun, 10 Jan 2016 16:25:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203105] [new driver] Port openbsd rtwn, new rtl8188ce driver Date: Sun, 10 Jan 2016 16:25:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sun, 10 Jan 2016 16:25:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203105 Adrian Chadd changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|In Progress |Closed --- Comment #17 from Adrian Chadd --- Please open a new problem report for bugs. :-) This one was just for "port driver!" Thanks! -a --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Sun Jan 10 19:06:49 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 29CD7A6B2BB for ; Sun, 10 Jan 2016 19:06:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 00E5E1FF0 for ; Sun, 10 Jan 2016 19:06:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0AJ6mDR060081 for ; Sun, 10 Jan 2016 19:06:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 206112] [rtwn] Under heavy load, "can't map mbuf (error 12)" arises Date: Sun, 10 Jan 2016 19:06:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: evil.lombo@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sun, 10 Jan 2016 19:06:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206112 Bug ID: 206112 Summary: [rtwn] Under heavy load, "can't map mbuf (error 12)" arises Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: evil.lombo@gmail.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Hi, I'm testing the rtwn module and under heavy usage (e.g. video streaming) or= a high number of active connections (e.g. multiple browser tabs or P2P), the interface stops responding in a few minutes and the following message spams multiple times on the system message buffer. rtwn0: can't map mbuf (error: 12)=20 where 12 I assume it's the error number of ENOMEM. ifconfig wlan0 down and ifconfig wlan0 up does not reset the interface and = the card still not respond. A full reboot of the machine fixes it. When those messages appear, trying to resume the stream from the application issues a kernel panic while trying to unload the module results in a machine freeze. I'll take the crash dump, if it's necessary. With light usage, I can't get the issue. (I don't know if this relates to the performance issue I have with the modu= le. The speed seems capped to around 1/3 rather than the full 54mbps rate I got using the ndis wrapper. I'm opening a separate bug report for that.) Which information are needed? Thanks, Simone --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Sun Jan 10 21:00:31 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 DA671A6BC44 for ; Sun, 10 Jan 2016 21:00:31 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D1B1E1B3B for ; Sun, 10 Jan 2016 21:00:31 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0AL01Ws004728 for ; Sun, 10 Jan 2016 21:00:31 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201601102100.u0AL01Ws004728@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-wireless@FreeBSD.org Subject: Problem reports for freebsd-wireless@FreeBSD.org that need special attention Date: Sun, 10 Jan 2016 21:00:31 +0000 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: Sun, 10 Jan 2016 21:00:31 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 154598 | [ath] Atheros 5424/2424 can't connect to WPA netw Open | 163312 | [panic] [ath] kernel panic: page fault with ath0 Open | 166190 | [ath] TX hangs and frames stuck in TX queue Open | 166357 | [ath] 802.11n TX stall when the first frame in th Open | 169362 | [ath] AR5416: radar pulse PHY errors sometimes in Open | 169433 | [iwn] iwn(4) doesn't support 6235 chip. 6 problems total for which you should take action. From owner-freebsd-wireless@freebsd.org Mon Jan 11 22:53:10 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 DEF0FA6BE42; Mon, 11 Jan 2016 22:53:10 +0000 (UTC) (envelope-from cochard@gmail.com) Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) (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 4D1C81749; Mon, 11 Jan 2016 22:53:10 +0000 (UTC) (envelope-from cochard@gmail.com) Received: by mail-lb0-x22c.google.com with SMTP id x4so5757250lbm.0; Mon, 11 Jan 2016 14:53:10 -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:content-type; bh=8NNcFGvRUIAq3R0zzBqZGD+X6dVaygaZxOOfzZjWvP4=; b=GJACdDnwnw3s2mHBFe8GcJZ2q/zzwcu0X7kONPZAMpPtEpS406ZNwbcohLpmvryfhH 86CtGEVierEY17NuRAXLXmIP5lsHZDOaB1kzvyusd+TccaICb6mLIrkevwBqjPSQUW5/ VXQjc3nuPlZn5Sm4JtImBCYYdo8gBsXy0+eDHVmfXcRRhFSpcEfOk4o7/4otEdvTdPjc hN0TUWuO8Und1X4xyM7xUNkcOWNQS3Mt+TSlgsF1URn6WIz4ECrfD/9l3yczO0VFzAP7 hIh0tmLYKnjPDBcGAkGHF2oADMYH6AagHneKWl7u26ruAr/LsMPgmql/CPQOravPkgSv Hggw== 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:content-type; bh=8NNcFGvRUIAq3R0zzBqZGD+X6dVaygaZxOOfzZjWvP4=; b=QgOjfpE0Ce+8wBSVXt/+lri1DvBLeKFzamPig1jCjvHlw/H66KcTKhELk4c/tB4yQC q7WoBPP1WPlTLneQz41j5Fd9d6SbOVcDdlYQGygH0esaiRQziFZrWtplVADjXd0DPnVS MLgz46AAIZaTauFC4Z2QTV96HsqoUNMIRpACKJpGMcvB4UHvYeJJ+BLVJwSv+vv1LAEq qk2C56pvYu4UvEFixsm5ML5h//5M1/jS4xU62iFYpeWkLost38J/nH/+rff4G1sIRkL3 4LEdgt6vtVerbhg+x1ucKZqO9LXUNsfNv682e4vK63/u4yO/d+wCuGCbQ7R3ZkCezgqg atRw== X-Received: by 10.112.149.202 with SMTP id uc10mr3531738lbb.57.1452552787888; Mon, 11 Jan 2016 14:53:07 -0800 (PST) MIME-Version: 1.0 Sender: cochard@gmail.com Received: by 10.25.200.10 with HTTP; Mon, 11 Jan 2016 14:52:47 -0800 (PST) In-Reply-To: References: From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Mon, 11 Jan 2016 23:52:47 +0100 X-Google-Sender-Auth: PYVoYtNDXFwb28Lna_YzgIcmtjQ Message-ID: Subject: Re: forwarding didn't work if wlan0 is member of a bridge To: "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 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: Mon, 11 Jan 2016 22:53:11 -0000 After weeks of troubleshooting, at last I found how to reproduce this problem ;-) Here is the setup: LAN0 <--> [(re0) fbsd router (bridge0 addm re1 addm wlan0)] <--> Wireless LAN If interface re1 (bridge0 member with wlan0) is in "active" status (=ethernet cable plugged to something): I don't have any problem, all is working great for my wireless clients connected to wlan0: They can ping devices in LAN0. But once I've unplug the ethernet cable connected to re1 (bridge member with wlan0) and re1 state switch to "no carrier", Wireless LAN clients are not able to reach LAN0. Here is my rc.conf with simple subnetting for Adrian ;-) wlans_ath0="wlan0" ifconfig_wlan0="hostap channel 6" create_args_wlan0="wlanmode hostap" cloned_interfaces="bridge0" ifconfig_re0="inet 1.0.0.1/24" ifconfig_re1="up" ifconfig_bridge0="inet 1.1.1.1/24 addm re1 addm wlan0 up" gateway_enable="YES" And an example with re1 in "no carrier" status: root@fbsd-router:~ # ifconfig bridge0 bridge0: flags=8843 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=9 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=143 ifmaxaddr 0 port 5 priority 128 path cost 33333 member: re1 flags=143 ifmaxaddr 0 port 2 priority 128 path cost 55 root@fbsd-router:~ # ifconfig re1 re1: flags=8943 metric 0 mtu 1500 options=82099 ether 00:0d:b9:3c:ae:25 nd6 options=29 media: Ethernet autoselect (none) status: no carrier => from a wireless LAN client (1.1.1.2) I'm trying to ping a host on LAN0 (1.0.0.2): root@fbsd-router:~ # tcpdump -pni re0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on re0, link-type EN10MB (Ethernet), capture size 262144 bytes 23:38:04.466866 ARP, Request who-has 1.0.0.2 tell 1.0.0.1, length 28 23:38:04.467052 ARP, Reply 1.0.0.2 is-at 00:08:a2:09:c4:a2, length 46 23:38:04.467090 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 72, seq 1, length 64 23:38:04.467226 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 72, seq 1, length 64 23:38:04.467300 IP 1.0.0.1 > 1.0.0.2: ICMP host 1.1.1.2 unreachable, length 36 23:38:05.483053 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 72, seq 2, length 64 23:38:05.483259 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 72, seq 2, length 64 23:38:05.483318 IP 1.0.0.1 > 1.0.0.2: ICMP host 1.1.1.2 unreachable, length 36 23:38:06.387304 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 72, seq 3, length 64 23:38:06.387466 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 72, seq 3, length 64 23:38:06.387514 IP 1.0.0.1 > 1.0.0.2: ICMP host 1.1.1.2 unreachable, length 36 ^C 11 packets captured 11 packets received by filter 0 packets dropped by kernel 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 fc:64:ba:97:c0:ff on bridge0 expires in 1168 seconds [bridge] ? (1.0.0.1) at 00:0d:b9:3c:ae:24 on re0 permanent [ethernet] => The FreeBSD router answers "unreacheable" to the host: My wireless LAN client never get the ICMP reply. => Now I plug eth1 to a dummy machine (just for changing its status): root@fbsd-router:~ # ifconfig re1 re1: flags=8943 metric 0 mtu 1500 options=82099 ether 00:0d:b9:3c:ae:25 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active => and I restart the same ping from the wireless LAN client: root@fbsd-router:~ # tcpdump -pni re0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on re0, link-type EN10MB (Ethernet), capture size 262144 bytes 23:44:08.597429 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 74, seq 1, length 64 23:44:08.597660 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 74, seq 1, length 64 23:44:09.604447 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 74, seq 2, length 64 23:44:09.604683 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 74, seq 2, length 64 23:44:10.609711 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 74, seq 3, length 64 23:44:10.609874 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 74, seq 3, length 64 => It's works :-) How the status of a member of the bridge can impact the routing behavior of other interfaces ? How to fix this problem ? Thanks From owner-freebsd-wireless@freebsd.org Tue Jan 12 06:40:50 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 B7877A6D756; Tue, 12 Jan 2016 06:40:50 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward9j.cmail.yandex.net (forward9j.cmail.yandex.net [IPv6:2a02:6b8:0:1630::184]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 584CE1B6C; Tue, 12 Jan 2016 06:40:49 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from web2j.yandex.ru (web2j.yandex.ru [5.45.198.43]) by forward9j.cmail.yandex.net (Yandex) with ESMTP id 8A3FC21E8D; Tue, 12 Jan 2016 09:26:30 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web2j.yandex.ru (Yandex) with ESMTP id B5F212CC05FC; Tue, 12 Jan 2016 09:26:29 +0300 (MSK) Received: by web2j.yandex.ru with HTTP; Tue, 12 Jan 2016 09:26:29 +0300 From: Alexander V. Chernikov Envelope-From: melifaro@ipfw.ru To: =?utf-8?B?T2xpdmllciBDb2NoYXJkLUxhYmLDqQ==?= , "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" In-Reply-To: References: Subject: Re: forwarding didn't work if wlan0 is member of a bridge MIME-Version: 1.0 Message-Id: <1981491452579989@web2j.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Tue, 12 Jan 2016 09:26:29 +0300 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 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 06:40:50 -0000 12.01.2016, 01:53, "Olivier Cochard-Labbé" : > After weeks of troubleshooting, at last I found how to reproduce this > problem ;-) Hi Olivier, > > Here is the setup: > > LAN0 <--> [(re0) fbsd router (bridge0 addm re1 addm wlan0)] <--> Wireless > LAN > > If interface re1 (bridge0 member with wlan0) is in "active" status > (=ethernet cable plugged to something): I don't have any problem, all is > working great for my wireless clients connected to wlan0: They can ping > devices in LAN0. > But once I've unplug the ethernet cable connected to re1 (bridge member > with wlan0) and re1 state switch to "no carrier", Wireless LAN clients are > not able to reach LAN0. It looks like ICMP unreach messages are generated by IP forwarding. Probably because (for some reason) bridge0 interface prefix was removed from route table. I'll try to reproduce that. > > Here is my rc.conf with simple subnetting for Adrian ;-) > > wlans_ath0="wlan0" > ifconfig_wlan0="hostap channel 6" > create_args_wlan0="wlanmode hostap" > cloned_interfaces="bridge0" > ifconfig_re0="inet 1.0.0.1/24" > ifconfig_re1="up" > ifconfig_bridge0="inet 1.1.1.1/24 addm re1 addm wlan0 up" > gateway_enable="YES" > > And an example with re1 in "no carrier" status: > > root@fbsd-router:~ # ifconfig bridge0 > bridge0: flags=8843 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=9 >         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=143 >                 ifmaxaddr 0 port 5 priority 128 path cost 33333 >         member: re1 flags=143 >                 ifmaxaddr 0 port 2 priority 128 path cost 55 > > root@fbsd-router:~ # ifconfig re1 > re1: flags=8943 metric 0 > mtu 1500 > > options=82099 >         ether 00:0d:b9:3c:ae:25 >         nd6 options=29 >         media: Ethernet autoselect (none) >         status: no carrier > > => from a wireless LAN client (1.1.1.2) I'm trying to ping a host on LAN0 > (1.0.0.2): > > root@fbsd-router:~ # tcpdump -pni re0 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on re0, link-type EN10MB (Ethernet), capture size 262144 bytes > 23:38:04.466866 ARP, Request who-has 1.0.0.2 tell 1.0.0.1, length 28 > 23:38:04.467052 ARP, Reply 1.0.0.2 is-at 00:08:a2:09:c4:a2, length 46 > 23:38:04.467090 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 72, seq 1, > length 64 > 23:38:04.467226 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 72, seq 1, length > 64 > 23:38:04.467300 IP 1.0.0.1 > 1.0.0.2: ICMP host 1.1.1.2 unreachable, length > 36 > 23:38:05.483053 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 72, seq 2, > length 64 > 23:38:05.483259 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 72, seq 2, length > 64 > 23:38:05.483318 IP 1.0.0.1 > 1.0.0.2: ICMP host 1.1.1.2 unreachable, length > 36 > 23:38:06.387304 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 72, seq 3, > length 64 > 23:38:06.387466 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 72, seq 3, length > 64 > 23:38:06.387514 IP 1.0.0.1 > 1.0.0.2: ICMP host 1.1.1.2 unreachable, length > 36 > ^C > 11 packets captured > 11 packets received by filter > 0 packets dropped by kernel > 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 fc:64:ba:97:c0:ff on bridge0 expires in 1168 seconds [bridge] > ? (1.0.0.1) at 00:0d:b9:3c:ae:24 on re0 permanent [ethernet] > > => The FreeBSD router answers "unreacheable" to the host: My wireless LAN > client never get the ICMP reply. > > => Now I plug eth1 to a dummy machine (just for changing its status): > > root@fbsd-router:~ # ifconfig re1 > re1: flags=8943 metric 0 > mtu 1500 > > options=82099 >         ether 00:0d:b9:3c:ae:25 >         nd6 options=29 >         media: Ethernet autoselect (1000baseT ) >         status: active > > => and I restart the same ping from the wireless LAN client: > > root@fbsd-router:~ # tcpdump -pni re0 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on re0, link-type EN10MB (Ethernet), capture size 262144 bytes > 23:44:08.597429 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 74, seq 1, > length 64 > 23:44:08.597660 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 74, seq 1, length > 64 > 23:44:09.604447 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 74, seq 2, > length 64 > 23:44:09.604683 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 74, seq 2, length > 64 > 23:44:10.609711 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 74, seq 3, > length 64 > 23:44:10.609874 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 74, seq 3, length > 64 > > => It's works :-) > > How the status of a member of the bridge can impact the routing behavior of > other interfaces ? > How to fix this problem ? > > Thanks > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-wireless@freebsd.org Tue Jan 12 18:00:17 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 4E8C0A6C674 for ; Tue, 12 Jan 2016 18:00:17 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from outbound1i.ore.mailhop.org (outbound1i.ore.mailhop.org [54.149.26.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3133C1CD7 for ; Tue, 12 Jan 2016 18:00:16 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from homobox.opal.com (unknown [71.255.169.131]) by outbound1.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Tue, 12 Jan 2016 17:59:43 +0000 (UTC) Received: from shibato (shibato.opal.com [IPv6:2001:470:8cb8:3:21e:33ff:fe5f:cb65]) (authenticated bits=0) by homobox.opal.com (8.15.2/8.15.2) with ESMTPSA id u0CHx1It014153 (version=TLSv1.2 cipher=AES128-GCM-SHA256 bits=128 verify=NO); Tue, 12 Jan 2016 12:59:02 -0500 (EST) (envelope-from fbsd@opal.com) Date: Tue, 12 Jan 2016 12:59:01 -0500 From: "J.R. Oldroyd" To: Olivier =?UTF-8?B?Q29jaGFyZC1MYWJiw6k=?= Cc: "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" Subject: Re: forwarding didn't work if wlan0 is member of a bridge Message-ID: <20160112125901.7e15404c@shibato> In-Reply-To: References: X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (homobox.opal.com [IPv6:2001:470:8cb8:2::1]); Tue, 12 Jan 2016 12:59:02 -0500 (EST) X-Spam-Status: No, score=-0.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_40, OPAL_URI_COUNT_5_9,T_RP_MATCHES_RCVD shortcircuit=no autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on homobox.opal.com 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 18:00:17 -0000 On Mon, 11 Jan 2016 23:52:47 +0100 Olivier Cochard-Labb=C3=A9 wrote: > > After weeks of troubleshooting, at last I found how to reproduce this > problem ;-) >=20 > Here is the setup: >=20 > LAN0 <--> [(re0) fbsd router (bridge0 addm re1 addm wlan0)] <--> Wireless > LAN >=20 > If interface re1 (bridge0 member with wlan0) is in "active" status > (=3Dethernet cable plugged to something): I don't have any problem, all is > working great for my wireless clients connected to wlan0: They can ping > devices in LAN0. > But once I've unplug the ethernet cable connected to re1 (bridge member > with wlan0) and re1 state switch to "no carrier", Wireless LAN clients are > not able to reach LAN0. >=20 > Here is my rc.conf with simple subnetting for Adrian ;-) >=20 > wlans_ath0=3D"wlan0" > ifconfig_wlan0=3D"hostap channel 6" > create_args_wlan0=3D"wlanmode hostap" > cloned_interfaces=3D"bridge0" > ifconfig_re0=3D"inet 1.0.0.1/24" > ifconfig_re1=3D"up" > ifconfig_bridge0=3D"inet 1.1.1.1/24 addm re1 addm wlan0 up" > gateway_enable=3D"YES" >=20 > And an example with re1 in "no carrier" status: >=20 > root@fbsd-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 >=20 >=20 > root@fbsd-router:~ # ifconfig re1 > re1: flags=3D8943 metric 0 > mtu 1500 >=20 > options=3D82099 > ether 00:0d:b9:3c:ae:25 > nd6 options=3D29 > media: Ethernet autoselect (none) > status: no carrier >=20 > =3D> from a wireless LAN client (1.1.1.2) I'm trying to ping a host on LA= N0 > (1.0.0.2): >=20 > root@fbsd-router:~ # tcpdump -pni re0 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on re0, link-type EN10MB (Ethernet), capture size 262144 bytes > 23:38:04.466866 ARP, Request who-has 1.0.0.2 tell 1.0.0.1, length 28 > 23:38:04.467052 ARP, Reply 1.0.0.2 is-at 00:08:a2:09:c4:a2, length 46 > 23:38:04.467090 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 72, seq 1, > length 64 > 23:38:04.467226 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 72, seq 1, leng= th > 64 > 23:38:04.467300 IP 1.0.0.1 > 1.0.0.2: ICMP host 1.1.1.2 unreachable, leng= th > 36 > 23:38:05.483053 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 72, seq 2, > length 64 > 23:38:05.483259 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 72, seq 2, leng= th > 64 > 23:38:05.483318 IP 1.0.0.1 > 1.0.0.2: ICMP host 1.1.1.2 unreachable, leng= th > 36 > 23:38:06.387304 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 72, seq 3, > length 64 > 23:38:06.387466 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 72, seq 3, leng= th > 64 > 23:38:06.387514 IP 1.0.0.1 > 1.0.0.2: ICMP host 1.1.1.2 unreachable, leng= th > 36 > ^C > 11 packets captured > 11 packets received by filter > 0 packets dropped by kernel > 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 fc:64:ba:97:c0:ff on bridge0 expires in 1168 seconds [brid= ge] > ? (1.0.0.1) at 00:0d:b9:3c:ae:24 on re0 permanent [ethernet] >=20 > =3D> The FreeBSD router answers "unreacheable" to the host: My wireless L= AN > client never get the ICMP reply. >=20 > =3D> Now I plug eth1 to a dummy machine (just for changing its status): >=20 > root@fbsd-router:~ # ifconfig re1 > re1: flags=3D8943 metric 0 > mtu 1500 >=20 > options=3D82099 > ether 00:0d:b9:3c:ae:25 > nd6 options=3D29 > media: Ethernet autoselect (1000baseT ) > status: active >=20 > =3D> and I restart the same ping from the wireless LAN client: >=20 > root@fbsd-router:~ # tcpdump -pni re0 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on re0, link-type EN10MB (Ethernet), capture size 262144 bytes > 23:44:08.597429 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 74, seq 1, > length 64 > 23:44:08.597660 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 74, seq 1, leng= th > 64 > 23:44:09.604447 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 74, seq 2, > length 64 > 23:44:09.604683 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 74, seq 2, leng= th > 64 > 23:44:10.609711 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 74, seq 3, > length 64 > 23:44:10.609874 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 74, seq 3, leng= th > 64 >=20 > =3D> It's works :-) >=20 > How the status of a member of the bridge can impact the routing behavior = of > other interfaces ? > How to fix this problem ? >=20 > Thanks > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" You have different mac addresses on each interface. So, when an interface goes down, hosts with that interface's mac in their cache will stop working until the cache entry expires. Use the same mac address for the wired, wireless and bridge interfaces, something like this: cloned_interfaces=3D"wlan0 bridge0" ifconfig_ath0=3D"`ifconfig re1 ether`" ifconfig_ath0=3D"ether ${ifconfig_ath0##*ether }" wlans_ath0=3D"wlan0" create_args_wlan0=3D"wlandev ath0 wlanmode hostap" ifconfig_wlan0=3D"channel 6 ssid xxxx" ifconfig_re1=3D"up" create_args_bridge0=3D"addm re1 addm wlan0 stp re1 stp wlan0" ifconfig_bridge0=3D"ether ${ifconfig_ath0##*ether } inet 1.1.1.1/24" -jr From owner-freebsd-wireless@freebsd.org Tue Jan 12 18:22:49 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 7957CA8035C; Tue, 12 Jan 2016 18:22:49 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (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 55681109A; Tue, 12 Jan 2016 18:22:49 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-ig0-x22a.google.com with SMTP id mw1so135464941igb.1; Tue, 12 Jan 2016 10:22:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=uFf25AHchebOfjrJQ1UbJCcqHjJW+/LWDPczSGlcBpg=; b=Anoxk0eIvAlW/lGRTX8+5kJ8eCMVf/emBJPLIIUG1Lt6eVqsY9snDjpvin6i2NHaAP 2bmKBOc03S2gQcgPQCn1yqGRJ1PtUhbVPS/moJidkXgfFFJGF3zJqLD8cOZ84p5RDPTA 7aVRcZGIxX3AR5oKn/M4qxRomYCEecINK+yEfYNWN7E1vP9J35B9C3gH6O/1f6J1O4u8 VJcLIyYfpejfEvC4hAxBgj6fPD5ecZSezCAxyNCpOaza0ONsE6WtOS6FLQbLzIontplm 4xh4RJd3pbB/KgsRpF5h9i5ad5gXHAy81qTh1Pl7OfDyFsQrdZycb3oK58J40Zn+98H/ r1xg== MIME-Version: 1.0 X-Received: by 10.50.137.41 with SMTP id qf9mr17904253igb.22.1452622968406; Tue, 12 Jan 2016 10:22:48 -0800 (PST) Received: by 10.36.121.202 with HTTP; Tue, 12 Jan 2016 10:22:48 -0800 (PST) In-Reply-To: References: Date: Tue, 12 Jan 2016 10:22:48 -0800 Message-ID: Subject: Re: forwarding didn't work if wlan0 is member of a bridge From: Adrian Chadd To: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Cc: "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 18:22:49 -0000 This is actually the intended behaviour, right? The routed interface is down, so the IP address on it and connected to it are unreachable. -a On 11 January 2016 at 14:52, Olivier Cochard-Labb=C3=A9 wrote: > After weeks of troubleshooting, at last I found how to reproduce this > problem ;-) > > Here is the setup: > > LAN0 <--> [(re0) fbsd router (bridge0 addm re1 addm wlan0)] <--> Wireless > LAN > > If interface re1 (bridge0 member with wlan0) is in "active" status > (=3Dethernet cable plugged to something): I don't have any problem, all i= s > working great for my wireless clients connected to wlan0: They can ping > devices in LAN0. > But once I've unplug the ethernet cable connected to re1 (bridge member > with wlan0) and re1 state switch to "no carrier", Wireless LAN clients ar= e > not able to reach LAN0. > > Here is my rc.conf with simple subnetting for Adrian ;-) > > wlans_ath0=3D"wlan0" > ifconfig_wlan0=3D"hostap channel 6" > create_args_wlan0=3D"wlanmode hostap" > cloned_interfaces=3D"bridge0" > ifconfig_re0=3D"inet 1.0.0.1/24" > ifconfig_re1=3D"up" > ifconfig_bridge0=3D"inet 1.1.1.1/24 addm re1 addm wlan0 up" > gateway_enable=3D"YES" > > And an example with re1 in "no carrier" status: > > root@fbsd-router:~ # ifconfig bridge0 > bridge0: flags=3D8843 metric 0 mt= u > 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@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 (none) > status: no carrier > > =3D> from a wireless LAN client (1.1.1.2) I'm trying to ping a host on LA= N0 > (1.0.0.2): > > root@fbsd-router:~ # tcpdump -pni re0 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decod= e > listening on re0, link-type EN10MB (Ethernet), capture size 262144 bytes > 23:38:04.466866 ARP, Request who-has 1.0.0.2 tell 1.0.0.1, length 28 > 23:38:04.467052 ARP, Reply 1.0.0.2 is-at 00:08:a2:09:c4:a2, length 46 > 23:38:04.467090 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 72, seq 1, > length 64 > 23:38:04.467226 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 72, seq 1, leng= th > 64 > 23:38:04.467300 IP 1.0.0.1 > 1.0.0.2: ICMP host 1.1.1.2 unreachable, leng= th > 36 > 23:38:05.483053 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 72, seq 2, > length 64 > 23:38:05.483259 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 72, seq 2, leng= th > 64 > 23:38:05.483318 IP 1.0.0.1 > 1.0.0.2: ICMP host 1.1.1.2 unreachable, leng= th > 36 > 23:38:06.387304 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 72, seq 3, > length 64 > 23:38:06.387466 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 72, seq 3, leng= th > 64 > 23:38:06.387514 IP 1.0.0.1 > 1.0.0.2: ICMP host 1.1.1.2 unreachable, leng= th > 36 > ^C > 11 packets captured > 11 packets received by filter > 0 packets dropped by kernel > 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 fc:64:ba:97:c0:ff on bridge0 expires in 1168 seconds [brid= ge] > ? (1.0.0.1) at 00:0d:b9:3c:ae:24 on re0 permanent [ethernet] > > =3D> The FreeBSD router answers "unreacheable" to the host: My wireless L= AN > client never get the ICMP reply. > > =3D> Now I plug eth1 to a dummy machine (just for changing its status): > > 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 > > =3D> and I restart the same ping from the wireless LAN client: > > root@fbsd-router:~ # tcpdump -pni re0 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decod= e > listening on re0, link-type EN10MB (Ethernet), capture size 262144 bytes > 23:44:08.597429 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 74, seq 1, > length 64 > 23:44:08.597660 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 74, seq 1, leng= th > 64 > 23:44:09.604447 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 74, seq 2, > length 64 > 23:44:09.604683 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 74, seq 2, leng= th > 64 > 23:44:10.609711 IP 1.1.1.2 > 1.0.0.2: ICMP echo request, id 74, seq 3, > length 64 > 23:44:10.609874 IP 1.0.0.2 > 1.1.1.2: ICMP echo reply, id 74, seq 3, leng= th > 64 > > =3D> It's works :-) > > How the status of a member of the bridge can impact the routing behavior = of > other interfaces ? > How to fix this problem ? > > Thanks > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " From owner-freebsd-wireless@freebsd.org Tue Jan 12 20:48:29 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 90C2DA6DC0D; Tue, 12 Jan 2016 20:48:29 +0000 (UTC) (envelope-from cochard@gmail.com) Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (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 2B5F31623; Tue, 12 Jan 2016 20:48:29 +0000 (UTC) (envelope-from cochard@gmail.com) Received: by mail-lf0-x233.google.com with SMTP id h129so47244767lfh.3; Tue, 12 Jan 2016 12:48:29 -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=zJY0aYW0SwR8q634rR+LUXgymGcmrO5oAKurTtzH41w=; b=VV5P4o37VNNSPS3sNuu3blPnITfzD8ej1/fB1CDRdnU8cHiqsdE6efamvppItA/fvi ae2CtmrT+ts8YxPzq3X8rGWZZZdMFpsRcQ4euyPxoYNXNTL4XYX3jHHQs2lpbuNu8gEm wyYsutqYfxJ7pnviDfQd0u3wGp1nhFwKW7fqvEeOGa8tzqeRbVOCYkTcNSR3EUjoZNBS NscO1c7M8CoOScRU82C8nFcD8zxjS6g/Co9/QX0zIodjpY6+VgSFwgzmRswJxRa7a62Q g+Na4U2GweKGfzpO/V2a+SVR6kwL2J62GD1qDhWb/35k+pKradUGl2jLRo4bqyAW3dfY mGAg== 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=zJY0aYW0SwR8q634rR+LUXgymGcmrO5oAKurTtzH41w=; b=KNq7SoXfrpVXoPa6XrXaajbdYiO+YtHhUHFNEa2NcEFO065HGJzh89Jmv+STmxkqeG 5GazycvqKtlIKT4dnpWsnQHUe0JaqO9mtMsqPUtg24NdVUHcBGrnSlSaO+EsjGSFCrKF wInWWnyxSVcZ4psisLcuYJ0JKvErkLwwCaSIJvQFgB6QYqoIIdplDjrJDhhw8RoqB6lV AQ24j7EtoYv1DA5AAxB1vPXuNY8zMen4ExwidvJR4pur+3eflmRgmOBPiQEvXno2gij8 xrEtfOEB+HW171AK8gSSzh4tRG9SW1m5x9liA61PltyLvaQOZkqMZzSOGVc6/LphSRK/ WsBg== 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=zJY0aYW0SwR8q634rR+LUXgymGcmrO5oAKurTtzH41w=; b=GLKjWdpYxpMhQHMC+/MkVB/4PvMi3uH3nzzrgddPyhTK3vEnioxnkoO6MlKcDAdv8z ReNjX5eEXkJrX/XyWneBLapVOue6igdvzslKPBOxtLdhLeXvrxcVlK9uKgSSOIco3CJf qyAM4DFZ4jfhoslzKdoK3aUv6BjHcH1tcyYZKV7+QR5eSjpU+njVEUt88RW5ag776bK/ 9ScOvcnulc470ZycHxW/BlESWSPsaG104ljTPIdk0vXSwLtmOqE55sWgUOmOAJqGataU hNeaO3Z7g3jAdlk4ntU1zho5uGi/gwhtThxRKslKjz0AIk/VWbhpLiu2DkCqxjbK+T9M qovA== X-Gm-Message-State: ALoCoQkDELYZIJWemrt7xwjMdMDQvCrL7/An4DqcRuQFUOZmruMk38JGfhDSQ7HLF2Ml+3yfRz5VTOB4WjT7tI2DzEkccvAPZA== X-Received: by 10.25.133.84 with SMTP id h81mr34581170lfd.126.1452631706974; Tue, 12 Jan 2016 12:48:26 -0800 (PST) MIME-Version: 1.0 Sender: cochard@gmail.com Received: by 10.25.136.11 with HTTP; Tue, 12 Jan 2016 12:48:07 -0800 (PST) In-Reply-To: References: From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Tue, 12 Jan 2016 21:48:07 +0100 X-Google-Sender-Auth: Sc6B9x47TMlwJUiJxFSOmGX9LF4 Message-ID: Subject: Re: forwarding didn't work if wlan0 is member of a bridge To: Adrian Chadd Cc: "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 20:48:29 -0000 On Tue, Jan 12, 2016 at 7:22 PM, Adrian Chadd wrote: > This is actually the intended behaviour, right? The routed interface > is down, so the IP address on it and connected to it are unreachable. > =E2=80=8BHi Adrian, the routed interface is a bridge interface, and this bridge interface had only one of its 2 members interface down. Then the routed interface is not down. From owner-freebsd-wireless@freebsd.org Tue Jan 12 20:52:53 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 EC4B9A6DFA1; Tue, 12 Jan 2016 20:52:53 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward17j.cmail.yandex.net (forward17j.cmail.yandex.net [5.255.227.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AA6FA1C60; Tue, 12 Jan 2016 20:52:53 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from web14j.yandex.ru (web14j.yandex.ru [5.45.198.55]) by forward17j.cmail.yandex.net (Yandex) with ESMTP id 1883620DA7; Tue, 12 Jan 2016 23:52:42 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web14j.yandex.ru (Yandex) with ESMTP id 0DBF728A01FA; Tue, 12 Jan 2016 23:52:41 +0300 (MSK) Received: by web14j.yandex.ru with HTTP; Tue, 12 Jan 2016 23:52:41 +0300 From: Alexander V. Chernikov Envelope-From: melifaro@ipfw.ru To: =?utf-8?B?T2xpdmllciBDb2NoYXJkLUxhYmLDqQ==?= , Adrian Chadd Cc: "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" In-Reply-To: References: Subject: Re: forwarding didn't work if wlan0 is member of a bridge MIME-Version: 1.0 Message-Id: <1223091452631961@web14j.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Tue, 12 Jan 2016 23:52:41 +0300 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 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 20:52:54 -0000 12.01.2016, 23:48, "Olivier Cochard-Labbé" : > On Tue, Jan 12, 2016 at 7:22 PM, Adrian Chadd > wrote: > >>  This is actually the intended behaviour, right? The routed interface >>  is down, so the IP address on it and connected to it are unreachable. > > ​Hi Adrian, > > the routed interface is a bridge interface, and this bridge interface had > only one of its 2 members interface down. > Then the routed interface is not down. 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. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-wireless@freebsd.org Tue Jan 12 20:58:25 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 5EB35A801BE; Tue, 12 Jan 2016 20:58:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (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 2AF0B1150; Tue, 12 Jan 2016 20:58:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-ig0-x231.google.com with SMTP id z14so135737313igp.1; Tue, 12 Jan 2016 12:58:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=/HXDF4z6ihWZ5D03ltEx4DZiUsIIiYV0OfAfkAbV09I=; b=Xi18edESH+FGJwm2JNvFNW7Wh3bbis5tDTbkJcQ7XquGHTo+NShcIMQ+Ag7Nrzx4O/ raFbu3rPlxY0FsDsiM9xyADwviJMVvr16H8X45xxbCycm5k/4Z6bzyx+MHnlXiE5HYYO DIqwesh8PIhRWJseLe1bcIxmrv+mRrk47r2HZ28cHPjst50yEWWw/ETbzLYWD4KtTbOA zriATAXO31DVVuKl7T9SdSlefuPZ7stzo0sextJ8CB0gMvb+vnVMtOtgM3cb8Z35dxGr uisEarj+X0d2xEGthQg4bTsXPzrwNHpf91xUkK2Y3JRIWpbmZWjLA9vHzkt1yigNFlUp 9maQ== MIME-Version: 1.0 X-Received: by 10.50.137.41 with SMTP id qf9mr18524308igb.22.1452632304458; Tue, 12 Jan 2016 12:58:24 -0800 (PST) Received: by 10.36.121.202 with HTTP; Tue, 12 Jan 2016 12:58:24 -0800 (PST) In-Reply-To: References: Date: Tue, 12 Jan 2016 12:58:24 -0800 Message-ID: Subject: Re: forwarding didn't work if wlan0 is member of a bridge From: Adrian Chadd To: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Cc: "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 20:58:25 -0000 Ah, okay. Can you ping out the routed interface whilst this occurs? -a On 12 January 2016 at 12:48, Olivier Cochard-Labb=C3=A9 wrote: > On Tue, Jan 12, 2016 at 7:22 PM, Adrian Chadd > wrote: >> >> This is actually the intended behaviour, right? The routed interface >> is down, so the IP address on it and connected to it are unreachable. > > > Hi Adrian, > > the routed interface is a bridge interface, and this bridge interface had > only one of its 2 members interface down. > Then the routed interface is not down. > 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 :-) From owner-freebsd-wireless@freebsd.org Wed Jan 13 02:07:19 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 C5089A80557; Wed, 13 Jan 2016 02:07:19 +0000 (UTC) (envelope-from wefourall@gmail.com) Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (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 8B49514B4; Wed, 13 Jan 2016 02:07:19 +0000 (UTC) (envelope-from wefourall@gmail.com) Received: by mail-oi0-x234.google.com with SMTP id o124so76251126oia.3; Tue, 12 Jan 2016 18:07:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VVly7mJkFH9V+YjCIlUE2Tuge+1trBFGnoysg+a5vKM=; b=AunB9b7qaXHW8fIeD/EH5uvEJrb9J1xFX5J5kDOZ00YIfPsAhFIF7S9f4kIZ4rSoOH IgJ3V7Jg17EM5vMMyWlwCgd22JFu78J/fHdMj8LoTEarz8N2uef5g70rpG70fxzXaHmD 9frDOabCvK9xgmSjcBy7JPwJ2gAn00p6P+pFGkFgiGic3It2Hi8NEMOmoxDCbuxTeDyT jcwYgdXXkyWNC3RcKRI5iU/gzTsUpEJk8ACwh6ZaYTeg4TFV9mU9wekTKugqOEG/eK4w zltsGmda4QXrcH2xEpsggYWrgrJz6NMxZlYMgHKdumnnKCikQUbRZJDQW0E7hgfUcWIo ugcg== MIME-Version: 1.0 X-Received: by 10.202.221.65 with SMTP id u62mr98422810oig.30.1452650838879; Tue, 12 Jan 2016 18:07:18 -0800 (PST) Received: by 10.202.210.18 with HTTP; Tue, 12 Jan 2016 18:07:18 -0800 (PST) Received: by 10.202.210.18 with HTTP; Tue, 12 Jan 2016 18:07:18 -0800 (PST) In-Reply-To: References: Date: Tue, 12 Jan 2016 18:07:18 -0800 Message-ID: Subject: Re: forwarding didn't work if wlan0 is member of a bridge From: "Omni$" To: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Cc: "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" , Misty McCloud 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: Wed, 13 Jan 2016 02:07:20 -0000 On Dec 23, 2015 2:32 AM, "Olivier Cochard-Labb=C3=A9" = wrote: > Hi, > > If wlan0 interface is member of a bridge, FreeBSD didn't reach to > forward-back packets to wireless client > > My setup is this one: > > internet gateway <--> [net0] fbsd router [net1 + wifi-hostap in bridge0] > <--> wireless client > > and the problem description: > - wireless clients didn't receive any packet back: the fbsd-router block= s > answers because it thinks wireless clients are "unreachable". > - But wireless clients can reach all IP of the fbsd-router hitself witho= ut > problem, and fbsd-router can ping them too. > - Ethernet clients connected to the same bridge0 didn't have problem > > A tcpdump on the outgoing interface shows the fbsd-router correctly > receiving/NATing/forwarding the wireless-client packet (10.239.142.104 > natted to 192.168.100.70) toward the Internet-gateway (192.168.100.254), > but once received the response from the internet-gateway it is not able t= o > reach the wireless-client (unreachable): > [fbsd-router]~> sudo tcpdump -pni net0 icmp > tcpdump: verbose output suppressed, use -v or -vv for full protocol decod= e > listening on net0, link-type EN10MB (Ethernet), capture size 262144 bytes > 07:35:24.869560 IP 192.168.100.70 > 192.168.100.254: ICMP echo request, i= d > 1, seq 375, length 40 > 07:35:24.869772 IP 192.168.100.254 > 192.168.100.70: ICMP echo reply, id > 1, > seq 375, length 40 > 07:35:24.870314 IP 192.168.100.70 > 192.168.100.254: ICMP host > 10.239.142.104 unreachable, length 36 > > But directly from the fbsd-router, there is no problem for reaching the > wireless-client: > [fbsd-router]~> ping wireless-client > PING 10.239.142.104 (10.239.142.104): 56 data bytes > 64 bytes from 10.239.142.104: icmp_seq=3D0 ttl=3D128 time=3D2.633 ms > 64 bytes from 10.239.142.104: icmp_seq=3D1 ttl=3D128 time=3D1.614 ms > > I'm using a bridge because I need to use only one subnet for all my clien= ts > (ethernet and wifi): > [fbsd-router]~> ifconfig bridge0 > bridge0: flags=3D8843 metric 0 mt= u > 1500 > ether 02:82:9f:45:81:00 > inet 10.239.142.126 netmask 0xffffffe0 broadcast 10.239.142.127 > nd6 options=3D49 > 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 6 priority 128 path cost 33333 > member: net1 flags=3D143 > ifmaxaddr 0 port 2 priority 128 path cost 55 > > And this "unreacheable" problem is related to the bridge, if I remove the > wlan0 from the bridge, there is no more problem. > > What problem can cause FreeBSD to answer back "unreachable" when wlan0 is > member of a bridge ? > > Head versions tested: r290522, r291362, r292613. > > Thanks, > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g > " > From owner-freebsd-wireless@freebsd.org Wed Jan 13 08:45:53 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 43E6CA81654; Wed, 13 Jan 2016 08:45:53 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward13h.cmail.yandex.net (forward13h.cmail.yandex.net [IPv6:2a02:6b8:0:f35::9e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D4BE41A78; Wed, 13 Jan 2016 08:45:52 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from web5h.yandex.ru (web5h.yandex.ru [IPv6:2a02:6b8:0:f05::15]) by forward13h.cmail.yandex.net (Yandex) with ESMTP id 2EE3A210FA; Wed, 13 Jan 2016 11:45:39 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web5h.yandex.ru (Yandex) with ESMTP id 1D8B43841F94; Wed, 13 Jan 2016 11:45:38 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfw.ru; s=mail; t=1452674738; bh=vxHhtdI9DkWzGxEE8v+uc4Rsb+qrVVrSZBMFiRjLzYc=; h=From:To:Cc:In-Reply-To:References:Subject:Date; b=tbqwGLpzidSs/orHCBMt7sxtVeU1FdKxvchq/KYf4+U3o44Gf8OQI+lCtndoeXHj6 A1VEJIK9pAdrEZUT69xGlHoIZiJYapEoVLaIbFL8vFEyrjRtKBpS2t3YRnbMSMDu+r ZIQWo55Tb3x7gQEnsINFfz61x92zjdBfGtRobnwA= Received: by web5h.yandex.ru with HTTP; Wed, 13 Jan 2016 11:45:37 +0300 From: Alexander V. Chernikov To: =?utf-8?B?T2xpdmllciBDb2NoYXJkLUxhYmLDqQ==?= Cc: Adrian Chadd , "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" In-Reply-To: References: <1223091452631961@web14j.yandex.ru> Subject: Re: forwarding didn't work if wlan0 is member of a bridge Message-Id: <2985841452674737@web5h.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Wed, 13 Jan 2016 11:45:37 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" 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: Wed, 13 Jan 2016 08:45:53 -0000 From owner-freebsd-wireless@freebsd.org Wed Jan 13 10:02:12 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 EE8E3A81BCC; Wed, 13 Jan 2016 10:02:12 +0000 (UTC) (envelope-from cochard@gmail.com) Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) (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 60D7A1233; Wed, 13 Jan 2016 10:02:12 +0000 (UTC) (envelope-from cochard@gmail.com) Received: by mail-lb0-x22c.google.com with SMTP id bc4so286806420lbc.2; Wed, 13 Jan 2016 02:02:12 -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=/AJGczwju7E3xqMIeOrtUSfz3Dz8VP4dIzBuyL1yX4U=; b=Sg/7lx+uaPddr9Rhh7VAF8UH2le/+mImi8DX0ykkWnv0E64eYEaZcLF7pdi7bmKZhy Dffj+vT4mRny6+IMzfGqsGUN3k8p1JwEUH5cxtR+rjcNnf5ZK+3xC4/cPV/RqV+iuWpI juyzmmURma0Pth81poR1wdQpCs5+hzXbec6J+REreX6PJ0Ivf9tSSvDgIZ66iPhrmp5Z sW7Iq2HjPlaw3/28IX2bBXZNvH1+U5J7XHT/+1FST2bos0MOg2YEnGGHguzIvzhrZOR7 uuoGTbJ5XYYhci+cA6oqwuAFmYNNNbxeyCyIV48nfiPBIR5nwNdvX1ktUEV7pS8MpobR OtVw== 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=/AJGczwju7E3xqMIeOrtUSfz3Dz8VP4dIzBuyL1yX4U=; b=p7FftWEqua97018syWVEY6Tb3pfWlWoGCSMxjiB2XHL/inm/QHxM65RKEk0o0Ln8Ps 8hlI5qJXpkSKH6ReFL9hQWGDswXaMKAaBHEezg0ShS+d6JxKB5AbmZXrec25TlIoQ0pC ++ZCjWnNaB8Ag4WH1oIetfrF3DTSJqGYvSQmrmh5hnUp6pTgb8Arf2O788kP6Plsk9aV 4WVsKReFf17whOGUom4a4+WIycrsDQZXN6MLgJVcreeADLIpuecUqTLyQNbtvtDeH++h 4MX+f5P/VxdKounEazo6ymSj/h2rBWVqYvX2rYfLZzdJQRVftdArkQY1kS46Tzdy6SJ4 JaSA== 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=/AJGczwju7E3xqMIeOrtUSfz3Dz8VP4dIzBuyL1yX4U=; b=gmaPfeyzRA+cEgdEUSN437QHnaw9C/kuL8HeW7ChdS7iYkW0KvchVtOnwR9IiXdxV/ SPiLlsdOonfgUVNHPsBdI4DelXCC3pYCMS2dcXwpT66u8RJFwgOb8Elrdvp0/IhCypUx POgBzLomjWZFGIXb0XAWfk6c2CHm7M73IvqrxdCkI1szdVLWJLD0yraprbY+j9H4mDOU VfdYEvYFaXwcnoCmt62Xf/P7mbfArJpUXt/l1KKUXmAcEyx+PxwKjq8EZslWUCspQg1H IZlyi/tV5E9i5g0wCgbUAYefb+qgn6f2vCQ2ckAjb15MZyhCJJ0DwwIAWKcint+lluRg FarA== X-Gm-Message-State: ALoCoQlsMSevtdxX2TqcBaj3s226AUKOsBbfEhjrigfkfus94/GsTb9i5v5ETmulEebWLHfVDQZk7BOqbV10XF5Yrgtda5BTMA== X-Received: by 10.112.133.42 with SMTP id oz10mr49478376lbb.92.1452679329596; Wed, 13 Jan 2016 02:02:09 -0800 (PST) MIME-Version: 1.0 Sender: cochard@gmail.com Received: by 10.25.136.11 with HTTP; Wed, 13 Jan 2016 02:01:49 -0800 (PST) In-Reply-To: <2985841452674737@web5h.yandex.ru> References: <1223091452631961@web14j.yandex.ru> <2985841452674737@web5h.yandex.ru> From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Wed, 13 Jan 2016 11:01:49 +0100 X-Google-Sender-Auth: sFG3PRU73RmOQ4IsJ0OkwHyaH7U 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: Wed, 13 Jan 2016 10:02:13 -0000 On Wed, Jan 13, 2016 at 9:45 AM, Alexander V. Chernikov wrote: > > I suspect the reason here is link state bridge handling. > ix0 does not seem to have IFCAP_LINKSTATE option but re(4) does. Probably > wlan0 doesn't have LINKSTATE option. > Code in bridge_linkcheck() doesn't handle the case with both "has link > state" and "no link state" interfaces well: > if reX is the only interface w/ IFCAP_LINKSTATE and it goes down, bridge > will also change its link state to down. > (However, bridge does not seem to have link state option itself, so > RT_LINK_IS_UP() macro should return true...) > > > > =E2=80=8BFor validating your "IFCAP_LINKSTATE" hypothesis, I've plug an USB ethernet adapter ue(4) that didn't support IFCAP_LINKSTATE. And I've setup the bridge0 with wlan0 and ue0 (in place of re1): same bug triggered. I need to =E2=80=8Bplug a cable for correct routing. =E2=80=8Broot@fbsd-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: ue0 flags=3D143 ifmaxaddr 0 port 7 priority 128 path cost 55 member: wlan0 flags=3D143 ifmaxaddr 0 port 5 priority 128 path cost 33333 root@fbsd-router:~ # ifconfig ue0 ue0: flags=3D8943 metric 0 mtu 1500 options=3D80008 ether 00:19:fd:4e:77:4d nd6 options=3D29 media: Ethernet autoselect (none) status: no carrier =E2=80=8B =E2=80=8BRegards, From owner-freebsd-wireless@freebsd.org Wed Jan 13 18:17:23 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 D9D14A81886; Wed, 13 Jan 2016 18:17:23 +0000 (UTC) (envelope-from hoomanfazaeli@gmail.com) Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (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 A7F791575; Wed, 13 Jan 2016 18:17:23 +0000 (UTC) (envelope-from hoomanfazaeli@gmail.com) Received: by mail-pa0-x22a.google.com with SMTP id ho8so101387660pac.2; Wed, 13 Jan 2016 10:17:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=XN4HFhDGroZ2PDHcmmacJkLs2Bjnv8mzltLdIffGnQU=; b=TivP3SVKkZHxiAqTXG6cN3VRxJ/pNNEeBfT56/EhwD9S3h69jDPNY6hRlidBZF0n/3 UzTF/AvwFM6vlQjDSpa4p6gZ7tQpc3w3chFZ9mFKYoWjgCxgO6JUA1/D4ZMXwwhjg83n nCdU5GVtA5l68M2Bchbd/WVEsUetvPAVNZk5+RGBFHesUl/jut5CECUJWap+Iq2JpDKP IergXkijsQyARVAm/k70oB2A8gM7FNeoelT2Vu2NwvdeF3dlFNxahKAfIEfrn6A3KUn2 O/ELkgxie36hwhwJM+oOMTbgRcPZnJGdXjqTFjY2Cx1tgQctgFeVEn4dHP16iV0A1Lcy YTQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XN4HFhDGroZ2PDHcmmacJkLs2Bjnv8mzltLdIffGnQU=; b=jJIuQBy2NuMvezuyhueZP1Nqk8rifmkVkVUYUhpE4eWGu5bRHZ09XjPUB6eVj5FTSr HOqXQLGs6+9UEk/4qeBUjfPmJeIIakWoypEzrhBDLFuLsShOpJeyXLuIHiANC7X/jUCs MfEuIj5BjBRb+QmvMKhPW0hL1UDXc1XExk3AEhFDowQFUyGN+KZh9JwhEWbZhlcorcS4 lNBNmzmKClwYPn1igXEyQsL06XLdwW+qj0QmkCI1bYFDjrEV7IYv6OQNXHt9lt/moE5X mLXX4t9NIS5qhsUIQhqGDW6EKwkHbNRUVSnrleLa63wOwO1qgTp9CGE0ZhBfXKGbO/t8 h7WQ== X-Gm-Message-State: ALoCoQn0zfUM47abOttgzOOq4TCkBqO2gwvwt9dAuQUB8CpJCrvbcCZglvgxKA4wjmXq9f6Jog1ABvDa42iJvO5pUPnS04B3Fw== X-Received: by 10.66.122.72 with SMTP id lq8mr198403253pab.1.1452709043298; Wed, 13 Jan 2016 10:17:23 -0800 (PST) Received: from [192.168.2.30] ([188.209.47.246]) by smtp.googlemail.com with ESMTPSA id w22sm4082440pfa.79.2016.01.13.10.17.17 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 13 Jan 2016 10:17:22 -0800 (PST) Message-ID: <569694A7.9030200@gmail.com> Date: Wed, 13 Jan 2016 21:47:11 +0330 From: Hooman Fazaeli User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: =?UTF-8?B?T2xpdmllciBDb2NoYXJkLUxhYmLDqQ==?= CC: "Alexander V. Chernikov" , "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" Subject: Re: forwarding didn't work if wlan0 is member of a bridge References: <1223091452631961@web14j.yandex.ru> <2985841452674737@web5h.yandex.ru> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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: Wed, 13 Jan 2016 18:17:23 -0000 On 1/13/2016 1:31 PM, Olivier Cochard-Labbé wrote: > On Wed, Jan 13, 2016 at 9:45 AM, Alexander V. Chernikov > wrote: > >> I suspect the reason here is link state bridge handling. >> ix0 does not seem to have IFCAP_LINKSTATE option but re(4) does. Probably >> wlan0 doesn't have LINKSTATE option. >> Code in bridge_linkcheck() doesn't handle the case with both "has link >> state" and "no link state" interfaces well: >> if reX is the only interface w/ IFCAP_LINKSTATE and it goes down, bridge >> will also change its link state to down. >> (However, bridge does not seem to have link state option itself, so >> RT_LINK_IS_UP() macro should return true...) >> >> >> >> > ​For validating your "IFCAP_LINKSTATE" hypothesis, I've plug an USB > ethernet adapter ue(4) that didn't support IFCAP_LINKSTATE. > And I've setup the bridge0 with wlan0 and ue0 (in place of re1): same bug > triggered. I need to ​plug a cable for correct routing. > > ​root@fbsd-router:~ # ifconfig bridge0 > bridge0: flags=8843 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=9 > 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: ue0 flags=143 > ifmaxaddr 0 port 7 priority 128 path cost 55 > member: wlan0 flags=143 > ifmaxaddr 0 port 5 priority 128 path cost 33333 > root@fbsd-router:~ # ifconfig ue0 > ue0: flags=8943 metric 0 > mtu 1500 > options=80008 > ether 00:19:fd:4e:77:4d > nd6 options=29 > media: Ethernet autoselect (none) > status: no carrier > ​ > ​Regards, > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" IMHO, this situation happens because if_bridge applies link state logic with the (wrong) assumption that it is _only_ responsible to forward packets between member interfaces. In this special setup, the packet comes from IP layer (not from another member interface) and should be forwarded on an up and active member interface w/o problem. It seems to me that the correct behavior for if_bridge it to check link state after it has determined outgoing interface and is about to forward the packet on that interface (however, I am not sure if returning unreachables, which is a good troubleshooting signal, is then possible or not). -- Best regards Hooman Fazaeli From owner-freebsd-wireless@freebsd.org Wed Jan 13 22:10:05 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 A34CCA812D0; Wed, 13 Jan 2016 22:10:05 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward17h.cmail.yandex.net (forward17h.cmail.yandex.net [IPv6:2a02:6b8:0:f35::a2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3DBD41578; Wed, 13 Jan 2016 22:10:04 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from web11h.yandex.ru (web11h.yandex.ru [84.201.186.40]) by forward17h.cmail.yandex.net (Yandex) with ESMTP id 375F82064C; Thu, 14 Jan 2016 01:10:00 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web11h.yandex.ru (Yandex) with ESMTP id 625B41226BF; Thu, 14 Jan 2016 01:09:59 +0300 (MSK) Received: by web11h.yandex.ru with HTTP; Thu, 14 Jan 2016 01:09:58 +0300 From: Alexander V. Chernikov Envelope-From: melifaro@ipfw.ru To: =?utf-8?B?T2xpdmllciBDb2NoYXJkLUxhYmLDqQ==?= Cc: Adrian Chadd , "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" In-Reply-To: References: <1223091452631961@web14j.yandex.ru> <2985841452674737@web5h.yandex.ru> Subject: Re: forwarding didn't work if wlan0 is member of a bridge MIME-Version: 1.0 Message-Id: <550651452722998@web11h.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Thu, 14 Jan 2016 01:09:58 +0300 Content-Type: multipart/mixed; boundary="----==--bound.55066.web11h.yandex.ru" 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: Wed, 13 Jan 2016 22:10:05 -0000 ------==--bound.55066.web11h.yandex.ru Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 13.01.2016, 13:02, "Olivier Cochard-Labbé" : > On Wed, Jan 13, 2016 at 9:45 AM, Alexander V. Chernikov > wrote: > >>  I suspect the reason here is link state bridge handling. >>  ix0 does not seem to have IFCAP_LINKSTATE option but re(4) does. Probably >>  wlan0 doesn't have LINKSTATE option. >>  Code in bridge_linkcheck() doesn't handle the case with both "has link >>  state" and "no link state" interfaces well: >>  if reX is the only interface w/ IFCAP_LINKSTATE and it goes down, bridge >>  will also change its link state to down. >>  (However, bridge does not seem to have link state option itself, so >>  RT_LINK_IS_UP() macro should return true...) > > ​For validating your "IFCAP_LINKSTATE" hypothesis, I've plug an USB > ethernet adapter ue(4) that didn't support IFCAP_LINKSTATE. > And I've setup the bridge0 with wlan0 and ue0 (in place of re1): same bug > triggered. I need to ​plug a cable for correct routing. We discussed/investigated this behaviour on IRC. To summarise: 1) ip_tryforward() does check interface linkstate regardless of linkstate capability 2) bridge linkcheck function does not seem to care about linkstate capability. What happened in original case: 802.11 does not provide linkstate cap and actual linkstate value is 0 (unknown). re0 does provide linkstate cap, so on link down, bridge_linkcheck() code decided to set own linkstate as DOWN as well (has non-zero linkstate interface, 0 up). On packet transmission. ip_tryforward() checked bridge0 state, found it to be DOWN so the icmp_error() was triggered. Attached patch fixes the problem, but I'm still thinking about better solution. > > ​root@fbsd-router:~ # ifconfig bridge0 > bridge0: flags=8843 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=9 >         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: ue0 flags=143 >                 ifmaxaddr 0 port 7 priority 128 path cost 55 >         member: wlan0 flags=143 >                 ifmaxaddr 0 port 5 priority 128 path cost 33333 > root@fbsd-router:~ # ifconfig ue0 > ue0: flags=8943 metric 0 > mtu 1500 >         options=80008 >         ether 00:19:fd:4e:77:4d >         nd6 options=29 >         media: Ethernet autoselect (none) >         status: no carrier > ​ > ​Regards, > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" ------==--bound.55066.web11h.yandex.ru Content-Disposition: attachment; filename="bridge_ls.diff" Content-Transfer-Encoding: base64 Content-Type: text/x-diff; name="bridge_ls.diff" SW5kZXg6IC91c3Ivc3JjL3N5cy9uZXQvaWZfYnJpZGdlLmMKPT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQotLS0gL3Vzci9z cmMvc3lzL25ldC9pZl9icmlkZ2UuYwkocmV2aXNpb24gMjkzNjU5KQorKysgL3Vzci9zcmMvc3lz L25ldC9pZl9icmlkZ2UuYwkod29ya2luZyBjb3B5KQpAQCAtMzU1MCwyMiArMzU1MCwyNSBAQCBz dGF0aWMgdm9pZAogYnJpZGdlX2xpbmtjaGVjayhzdHJ1Y3QgYnJpZGdlX3NvZnRjICpzYykKIHsK IAlzdHJ1Y3QgYnJpZGdlX2lmbGlzdCAqYmlmOwotCWludCBuZXdfbGluaywgaGFzbHM7CisJaW50 IG5ld19saW5rLCBub2xzOwogCiAJQlJJREdFX0xPQ0tfQVNTRVJUKHNjKTsKIAluZXdfbGluayA9 IExJTktfU1RBVEVfRE9XTjsKLQloYXNscyA9IDA7CisJbm9scyA9IDA7CiAJLyogT3VyIGxpbmsg aXMgY29uc2lkZXJlZCB1cCBpZiBhdCBsZWFzdCBvbmUgb2Ygb3VyIHBvcnRzIGlzIGFjdGl2ZSAq LwogCUxJU1RfRk9SRUFDSChiaWYsICZzYy0+c2NfaWZsaXN0LCBiaWZfbmV4dCkgewotCQlpZiAo YmlmLT5iaWZfaWZwLT5pZl9jYXBhYmlsaXRpZXMgJiBJRkNBUF9MSU5LU1RBVEUpCi0JCQloYXNs cysrOworCQlpZiAoKGJpZi0+YmlmX2lmcC0+aWZfY2FwYWJpbGl0aWVzICYgSUZDQVBfTElOS1NU QVRFKSA9PSAwKSB7CisJCQkvKiBYWFg6IEhhbmRsZSBhZG1pbiBkb3duPyAqLworCQkJbm9scysr OworCQkJY29udGludWU7CisJCX0KIAkJaWYgKGJpZi0+YmlmX2lmcC0+aWZfbGlua19zdGF0ZSA9 PSBMSU5LX1NUQVRFX1VQKSB7CiAJCQluZXdfbGluayA9IExJTktfU1RBVEVfVVA7CiAJCQlicmVh azsKIAkJfQogCX0KLQlpZiAoIUxJU1RfRU1QVFkoJnNjLT5zY19pZmxpc3QpICYmICFoYXNscykg ewotCQkvKiBJZiBubyBpbnRlcmZhY2VzIHN1cHBvcnQgbGluay1zdGF0ZSB0aGVuIHdlIGRlZmF1 bHQgdG8gdXAgKi8KKwlpZiAoIUxJU1RfRU1QVFkoJnNjLT5zY19pZmxpc3QpICYmIG5vbHMgIT0g MCkgeworCQkvKiBJZiBzb21lIGlmYWNlcyBkb24ndCBzdXBwb3J0IGxpbmstc3RhdGUgdGhlbiB3 ZSBkZWZhdWx0IHRvIHVwICovCiAJCW5ld19saW5rID0gTElOS19TVEFURV9VUDsKIAl9CiAJaWZf bGlua19zdGF0ZV9jaGFuZ2Uoc2MtPnNjX2lmcCwgbmV3X2xpbmspOwo= ------==--bound.55066.web11h.yandex.ru-- From owner-freebsd-wireless@freebsd.org Wed Jan 13 22:21:29 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 B3EBCA81807 for ; Wed, 13 Jan 2016 22:21:29 +0000 (UTC) (envelope-from petar@smokva.net) Received: from crane.smokva.net (crane.smokva.net [85.10.196.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 810C6118B for ; Wed, 13 Jan 2016 22:21:28 +0000 (UTC) (envelope-from petar@smokva.net) Received: from pintail.smokva.net (77-56-96-22.dclient.hispeed.ch [77.56.96.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by crane.smokva.net (Postfix) with ESMTPSA id 8598324F2D62 for ; Wed, 13 Jan 2016 23:16:10 +0100 (CET) Date: Wed, 13 Jan 2016 23:16:09 +0100 From: Petar Bogdanovic To: freebsd-wireless@freebsd.org Subject: AH_DIAGAPI Message-ID: <20160113221608.GA14807@pintail.smokva.net> Mail-Followup-To: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23+75 (1bd26d871d76) (2014-03-12) 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: Wed, 13 Jan 2016 22:21:29 -0000 Hi, should AH_DIAGAPI still exist somewhere? I was just grepping for it in /usr/src (10.2-REL) but there doesn't seem to be such a string. Cheers, Petar From owner-freebsd-wireless@freebsd.org Wed Jan 13 22:32:50 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 9D8B6A81CD8 for ; Wed, 13 Jan 2016 22:32:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (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 6B6E817F6 for ; Wed, 13 Jan 2016 22:32:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-ig0-x229.google.com with SMTP id ik10so183137488igb.1 for ; Wed, 13 Jan 2016 14:32:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=oSdxPzKfuWziK3S4OxqCx2S+woNwolCKO3CKjMPT6is=; b=F4UcBEyQq7xz19WPCAqH3rc2HDvaSOJ3K03E6Abos767c6XBPqeVDkntk9Ew3Nyc3Q YGQ1f25m815+9EEvxOljHiHpoJFQpACFIc9cN6DRuJEtbkuoIL5I6nIONYQWwbH5RtJA b3UJnoYgjCrmKlBzrI3wD+3d/AbjYEMV+l5RaCG9GVbIJM5JCwLR+KEBe43pl620AzDP vUuZnDGtvLFAKLqec6oORHomvqzbTY9pAryU/WFuhats/2XDRcvOdheeKNi0q1VVc9Pp T29viNopCujOm7dARmRG0PzwBDeb+E+lJfbvaSqEtgtGDTV+KQwEFt5ktu3Dxvr+dBks pOUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=oSdxPzKfuWziK3S4OxqCx2S+woNwolCKO3CKjMPT6is=; b=l9FvqKSSYDBnpe7gGP13EjloGIkJ1IaFdlUVjoVbK0J9EZP/gTuyIb/JZhwAlCirqV VZMPGgvffJryq03jlwQyPSB/9IxCKUJOcewdOv+sMFwlaf4/fF+iM2c/JjZM4SAONqn5 5ZEQPr174Fg7N6hClCLqERw2APZWBku58iORMcYqoDt9/SdogZkTDvXDppoC38iIDuIe jQUbSbi3Rq7GwBQRhhqfCS/zdzz+Is2qMt1743qZfkbYprzuHAEKOc0qrQXeenVk2iNr aUbi9vG52FmNdlLEMYREXhEMtJ6DzTuFdBsHRAUE6odTD2PnR0q4QwVHmjpwRWrVOisQ Prsg== X-Gm-Message-State: ALoCoQkrYJ4Vwqj8lrZ7guy9rmUcPJO68f3RcZQ5RyxtFPOqj53I1/IyHN/4VdqQiOMTK1A3zkKTJ/q/O8CxxT7eyVCUWQRCZw== MIME-Version: 1.0 X-Received: by 10.50.124.72 with SMTP id mg8mr24580666igb.22.1452724369841; Wed, 13 Jan 2016 14:32:49 -0800 (PST) Received: by 10.36.121.202 with HTTP; Wed, 13 Jan 2016 14:32:49 -0800 (PST) In-Reply-To: <20160113221608.GA14807@pintail.smokva.net> References: <20160113221608.GA14807@pintail.smokva.net> Date: Wed, 13 Jan 2016 14:32:49 -0800 Message-ID: Subject: Re: AH_DIAGAPI From: Adrian Chadd To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 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: Wed, 13 Jan 2016 22:32:50 -0000 Maybe it's ATH_DIAGAPI? -a On 13 January 2016 at 14:16, Petar Bogdanovic wrote: > Hi, > > should AH_DIAGAPI still exist somewhere? I was just grepping for it in > /usr/src (10.2-REL) but there doesn't seem to be such a string. > > Cheers, > > Petar > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@freebsd.org Wed Jan 13 22:35:57 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 9A660A81E11 for ; Wed, 13 Jan 2016 22:35:57 +0000 (UTC) (envelope-from petar@smokva.net) Received: from crane.smokva.net (crane.smokva.net [85.10.196.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 65BE61A62 for ; Wed, 13 Jan 2016 22:35:57 +0000 (UTC) (envelope-from petar@smokva.net) Received: from pintail.smokva.net (77-56-96-22.dclient.hispeed.ch [77.56.96.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by crane.smokva.net (Postfix) with ESMTPSA id 45EC024F2D62 for ; Wed, 13 Jan 2016 23:35:55 +0100 (CET) Date: Wed, 13 Jan 2016 23:35:54 +0100 From: Petar Bogdanovic To: freebsd-wireless@freebsd.org Subject: Re: AH_DIAGAPI Message-ID: <20160113223553.GA15108@pintail.smokva.net> Mail-Followup-To: freebsd-wireless@freebsd.org References: <20160113221608.GA14807@pintail.smokva.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23+75 (1bd26d871d76) (2014-03-12) 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: Wed, 13 Jan 2016 22:35:57 -0000 On Wed, Jan 13, 2016 at 02:32:49PM -0800, Adrian Chadd wrote: > Maybe it's ATH_DIAGAPI? It is, thanks! :) Maybe fix-worthy: This requires "AH_DIAGAPI" to be enabled in order for all the.. ^^^ https://wiki.freebsd.org/dev/ath%284%29/Debugging From owner-freebsd-wireless@freebsd.org Wed Jan 13 22:39:59 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 28A61A81EB9 for ; Wed, 13 Jan 2016 22:39:59 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (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 E98B81AE4 for ; Wed, 13 Jan 2016 22:39:58 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-ig0-x22a.google.com with SMTP id ik10so183251454igb.1 for ; Wed, 13 Jan 2016 14:39:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=eQGOBf6+dPifiIzhNLvNUj1VojrIJ3oZTXPOHjHVjEU=; b=QsLXAc7FdqZEBJVNL2wtV4J9vkI1V3dQMJrSQ/g4pGXhysOFdPerW3A3+Tzi3Xo/mx jd46n+62kH+TyYjNF1Kf1978IVRnzd2tKtrteAYv1KN0veTl3DyMSk8fDi5ivAiE3K9B jycrJQupMnujvtQZqP7ZH0/jgms3U5AFHBff+EygFCgL8Uy3nj0CYaz0izBAEvS+J+JZ 7yrE5ZOwSVJDwTCYc40fLKOXquG4FFHOGcjkumNHqGhZSt+1w1ZwoRizeM4vhMwRM3J0 ol3rqoxFSdNcp+X6dNgh5aULbZzlSd/v4gYFmjUdiOGk4oUPWXjeTgT2ITg9ktQlRo17 ui3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=eQGOBf6+dPifiIzhNLvNUj1VojrIJ3oZTXPOHjHVjEU=; b=cgcYAAZ75sCp53b+yzdoDoL0Bwn4bkYeVAtmYq5+w8/rVldqWuG89Be0QrkY8Ar2hc zzg43FfgIB3wddb7ik1DVPi2Mp8HfoFM2W6Hc6XSe//5Y2mddYC9FNdrZblK5zz4CJlD G1rvoVcLiKMonZ56xKHiPYhAM1HcWmNhUKL8sOavMbJgzjv6+1cbvB+cLAMR6XRjUtyG 9VeuLRnOaHvYlp59bBcZiqzazK3RaQmfSM+zsVaQS6y/ZooMAsaBrf2rBU8p56Vmr6pb jUb0iSA/f0KcYy7y/PTFy4Lzps5QtfDw8U/fUFEcxqCxLElcBFZF5y8QH4GVQyVcRrfa MMLw== X-Gm-Message-State: ALoCoQnRBLCzAG0CLgljGYZZEpemSd7qiW+3JuElngagnIRqCgnr33MKamN3rNjocOBUgIbc2yWYtagPmVi3hYZWz6OBZOuhRQ== MIME-Version: 1.0 X-Received: by 10.50.124.72 with SMTP id mg8mr24608094igb.22.1452724798493; Wed, 13 Jan 2016 14:39:58 -0800 (PST) Received: by 10.36.121.202 with HTTP; Wed, 13 Jan 2016 14:39:58 -0800 (PST) In-Reply-To: <20160113223553.GA15108@pintail.smokva.net> References: <20160113221608.GA14807@pintail.smokva.net> <20160113223553.GA15108@pintail.smokva.net> Date: Wed, 13 Jan 2016 14:39:58 -0800 Message-ID: Subject: Re: AH_DIAGAPI From: Adrian Chadd To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 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: Wed, 13 Jan 2016 22:39:59 -0000 Fixed! Thanks! -a On 13 January 2016 at 14:35, Petar Bogdanovic wrote: > On Wed, Jan 13, 2016 at 02:32:49PM -0800, Adrian Chadd wrote: >> Maybe it's ATH_DIAGAPI? > > It is, thanks! :) > > > Maybe fix-worthy: > > This requires "AH_DIAGAPI" to be enabled in order for all the.. > ^^^ > https://wiki.freebsd.org/dev/ath%284%29/Debugging > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@freebsd.org Wed Jan 13 22:48:20 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 1B1E5A81198 for ; Wed, 13 Jan 2016 22:48:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0BA881E99 for ; Wed, 13 Jan 2016 22:48:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0DMmJji033165 for ; Wed, 13 Jan 2016 22:48:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 206199] [patch] dev/bwn suppressing "bwn0: unsupported rate 0" messages Date: Wed, 13 Jan 2016 22:48:20 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Wed, 13 Jan 2016 22:48:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206199 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-wireless@FreeBSD.or | |g --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Sat Jan 16 21:50:13 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 5773FA8539D for ; Sat, 16 Jan 2016 21:50:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 492DF1E10 for ; Sat, 16 Jan 2016 21:50:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0GLoD5V021808 for ; Sat, 16 Jan 2016 21:50:13 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192641] [iwn] panic in AMPDU tx code "ni: no node" Date: Sat, 16 Jan 2016 21:50:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marinintim+freebsd@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sat, 16 Jan 2016 21:50:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192641 Tim Marinin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marinintim+freebsd@gmail.co | |m --- Comment #1 from Tim Marinin --- It seems like I'm having the same problem with N-2230 on CURRENT, it causes panics once in a while (I have 9 core dumps since New Year). Not sure how to debug it. --=20 You are receiving this mail because: You are the assignee for the bug.=