Date: Sat, 29 Sep 2007 23:42:44 +1200 From: Andrew Thompson <thompsa@FreeBSD.org> To: Randy Bush <randy@psg.com> Cc: FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: bridging ath Message-ID: <20070929114244.GC44719@heff.fud.org.nz> In-Reply-To: <46FE0640.3030102@psg.com> References: <46FB1044.7020000@psg.com> <20070927214100.GB20718@heff.fud.org.nz> <46FC25C3.8030703@psg.com> <46FC4036.3040604@errno.com> <46FC4C5F.8000004@psg.com> <46FC560E.1070301@errno.com> <46FC574B.1070507@errno.com> <46FE0640.3030102@psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 28, 2007 at 10:01:04PM -1000, Randy Bush wrote: > > I don't know what you're trying to do > > no surprise. i rarely do. :) > > > When you attach your wired nic to a bridge and and turn the bridge on > > the nic gets set in promiscuous mode. This is likely why you can > > ping the other wireless station through the wired nic. To ping the > > wireless station through your AP then AP must either fwd the packet > > directly or bridge it using some mechanism. You cannot bridge a > > wireless interface unless it's operating as an ap. Either way it's > > an issue at the AP. > > sokeris running current > application is a remote (via wireless) ether switch > wireless client, bridged to the ethers > a few devices on the ethers such as desktop, printer, ... > it is also a local samba etc, and ipsecs to the AP's net > > so it does not want to be an AP but it does want to bridge. At the bottom of if_bridge(4): "Only wireless interfaces in hostap mode can be bridged due to the 802.11 framing format, bridging a wireless client is not supported yet."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070929114244.GC44719>