Date: Fri, 28 Sep 2007 22:01:04 -1000 From: Randy Bush <randy@psg.com> To: Sam Leffler <sam@errno.com> Cc: FreeBSD Net <freebsd-net@freebsd.org>, Andrew Thompson <thompsa@freebsd.org> Subject: Re: bridging ath Message-ID: <46FE0640.3030102@psg.com> In-Reply-To: <46FC574B.1070507@errno.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>
index | next in thread | previous in thread | raw e-mail
> 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. randyhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46FE0640.3030102>