From owner-freebsd-current@freebsd.org  Tue Jan 12 20:52:53 2016
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 <melifaro@freebsd.org>
Envelope-From: melifaro@ipfw.ru
To: =?utf-8?B?T2xpdmllciBDb2NoYXJkLUxhYmLDqQ==?= <olivier@cochard.me>,
 Adrian Chadd <adrian.chadd@gmail.com>
Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>,
 "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
In-Reply-To: <CA+q+TcoHXeAmOQ2_-7c0WHMHHB3SvPpGdUiOLteG8tQXxCsQqA@mail.gmail.com>
References: <CA+q+Tco3MKBvhCQXvVaDkRZQYzX6tye8opD3yKrtnnF3imGDCg@mail.gmail.com>
 <CA+q+Tcq-CkyBMxvmWEDu1Ejg_36CDHmhPBE1t7CiV37hDVTvNQ@mail.gmail.com>
 <CAJ-Vmo=FJGwuaw6y--e3U6GfmtdUo4gnZwvhjeZXGaEmvEj-OQ@mail.gmail.com>
 <CA+q+TcoHXeAmOQ2_-7c0WHMHHB3SvPpGdUiOLteG8tQXxCsQqA@mail.gmail.com>
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-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jan 2016 20:52:54 -0000

12.01.2016, 23:48, "Olivier Cochard-Labbé" <olivier@cochard.me>:
> On Tue, Jan 12, 2016 at 7:22 PM, Adrian Chadd <adrian.chadd@gmail.com>
> 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"