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é wrote:
> After weeks of troubleshooting, at last I found how to reproduce this
On Tue, Jan 12, 2016 at 9:52 PM, Alexander V. Chernikov <
melif...@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.
>
>
Sure,
here
Ah, okay.
Can you ping out the routed interface whilst this occurs?
-a
On 12 January 2016 at 12:48, Olivier Cochard-Labbé wrote:
> On Tue, Jan 12, 2016 at 7:22 PM, Adrian Chadd
> wrote:
>>
>> This is actually the intended behaviour, right? The
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
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.
>
On Dec 23, 2015 2:32 AM, "Olivier Cochard-Labbé" 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]