Date: Tue, 16 Sep 2003 21:34:49 +0200 From: John Hay <jhay@icomtek.csir.co.za> To: Julian Elischer <julian@elischer.org> Cc: freebsd-current@freebsd.org Subject: Re: atheros (ath) driver bridging Message-ID: <20030916193449.GA76069@zibbi.icomtek.csir.co.za> In-Reply-To: <Pine.BSF.4.21.0309161114590.52605-100000@InterJet.elischer.org> References: <329513875.1063710581@melange.errno.com> <Pine.BSF.4.21.0309161114590.52605-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 16, 2003 at 11:16:54AM -0700, Julian Elischer wrote: > I'm not sure what I typed there but what I meant to say was.... > "At one stage the wi driver could not be put in promiscuous mode and > the bridging code required that. Most people still think this is true." I think it is still true. What you can do is bridging between ethernet and wireless if you use host-ap mode. What you can't do is bridging ethernet-wireless --- wireless-ethernet. For that you will need WDS or something similar. > On Tue, 16 Sep 2003, Sam Leffler wrote: > > > > I think what he meant was that at on state was known (I don't know the > > > current state) that as the wi could not be but in promiscuous mode it > > > could not be used for bridging.. Bridging requires promiscuous mode > > > (or some very tricky proxy-arp stuff). > > > > You can put wi (and ath) in promiscuous mode. The bridge manual page is > > wrong and I will fix it. John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030916193449.GA76069>