Date: Thu, 27 Sep 2007 16:43:50 -0700 From: Sam Leffler <sam@errno.com> To: Randy Bush <randy@psg.com> Cc: FreeBSD Net <freebsd-net@freebsd.org>, Andrew Thompson <thompsa@freebsd.org> Subject: Re: bridging ath Message-ID: <46FC4036.3040604@errno.com> In-Reply-To: <46FC25C3.8030703@psg.com> References: <46FB1044.7020000@psg.com> <20070927214100.GB20718@heff.fud.org.nz> <46FC25C3.8030703@psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Randy Bush wrote:
> Andrew Thompson wrote:
>
>> On Wed, Sep 26, 2007 at 04:07:00PM -1000, Randy Bush wrote:
>>
>>> current i386 thinkpad t41
>>>
>>> ifconfig_lo0="inet 127.0.0.1/8"
>>> cloned_interfaces="bridge0"
>>> ifconfig_bridge0="inet 192.168.0.3/24 addm em0 addm ath0 up"
>>> ifconfig_em0="up"
>>> ifconfig_ath0="ssid rgnet up"
>>> defaultrouter="192.168.0.1"
>>>
>>> with ether plugged in, i can ping it. unplug ether and no ping over
>>> ath0. other hosts are on same ssid and working.
>>>
>> I will try to reproduce this in the weekend. Just to make sure, you are
>> pinging 192.168.0.3 from a remote wireless node connected to ath0, and
>> unplugging em0 causes this to fail?
>>
>
> connect both wireless and ether. it is pingable. disconnect ether. no
> can ping.
>
> reduce to
> ifconfig_ath0="inet 192.168.0.3/24 ssid rgnet up"
> with no em0, bridge, ... and it is pingable.
>
Be sure apbridge is enabled so the 802.11 layer does intra-bss bridging;
otherwise traffic must be fwd'd by a bridge component (should be on by
default). Also you can use tcpdump to check traffic on each interface
to isolate the issue.
Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46FC4036.3040604>