From owner-freebsd-wireless@freebsd.org Wed Dec 23 19:39:33 2015 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 61FFAA509CB; Wed, 23 Dec 2015 19:39:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::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 3472217CF; Wed, 23 Dec 2015 19:39:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x22a.google.com with SMTP id 186so227857647iow.0; Wed, 23 Dec 2015 11:39:33 -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=GHPnGC866XFjnjK9+292WZlKfoq+KaLCVdaJCcF6KI0=; b=YfDKfuRkH900vrNoF6ADvW/yYki1L7U6CWfMXJegx9FAcWpYGS6MbIvy0ZSPio4kWH GJb41iQBWGqzeGp/T4YdrbNSZ10cubXAuVDI+CeJG9EjQv8OaVdBNKyHwtFsadWiQGwO 3m/290T20NYIE4h0uMLjMxQ07ToVn/4ajvsj0Xx2WsNH09L7p7aOw42jTJx25o0mOh3o D7Flet98NP4mN6A01yeQKdcXMOscw2wbXofG5ImuQiy/imHwwavByEMMsiBal8lrUMlr DTi0ckHYmV437riD8O8Est60qq0R2rw4mcKvIkkS2/rPajTgGF/NsQKNnfSfNwkR4Afr BCng== MIME-Version: 1.0 X-Received: by 10.107.162.21 with SMTP id l21mr31043143ioe.123.1450899572620; Wed, 23 Dec 2015 11:39:32 -0800 (PST) Received: by 10.36.121.202 with HTTP; Wed, 23 Dec 2015 11:39:32 -0800 (PST) In-Reply-To: References: Date: Wed, 23 Dec 2015 11:39:32 -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: Wed, 23 Dec 2015 19:39:33 -0000 Hi, inet 10.239.142.126 netmask 0xffffffe0 broadcast 10.239.142.127 This looks like a problem with your addressing. That netmask !=3D that broa= dcast. Please recheck your networking setup! -a On 23 December 2015 at 02:31, 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-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= "