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,