--KNAbaO+RG+KCl9Km
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Sep 22, 2007 at 08:57:20AM -0400, Greg Troxel wrote:
> Quentin Garnier <cube@cubidou.net> writes:
>=20
> > You can't bridge a wpi.  I don't think you can bridge with any of
> > NetBSD's wireless drivers:  not only you need a card that supports
> > having as many associations to the AP as required, but of course you
> > need the software support.
>=20
> I had never thought of that, but I see your point.  Thoughts arising:
>=20
> 1) If it doesn't work brconfig should fail.

Well, it works if the interface is in AP mode...  Maybe add an ethercap
flag?

> 2) I wonder if another encapsulation would enable this to work.  My
> 802.11 spec memory is very fuzzy at this point, but I recall a way to
> carry 802.3 frames in 802.11, rather than the encapsulation that puts
> only the data and puts the 802.3 addresses in the 802.11 header.

But would you expect the AP to support that?

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"You could have made it, spitting out benchmarks
Owe it to yourself not to fail"
Amplifico, Spitting Out Benchmarks, Hometakes Vol. 2, 2005.

--KNAbaO+RG+KCl9Km
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (NetBSD)

iQEVAwUBRvUTrNgoQloHrPnoAQKL4Qf/TC8C9hX1+D/QODi527aRSrhHmzTEwQxJ
yXrF+HlkRNL9cyUZJKUU6RfiP8cjqsj2UFd1nPHd5VLMVrpQCLjzWvCO8Enl2ra6
m0Qhw5vBfk5tRVdFCfn92WhWfiJAhm2PmK4ru/4zQl76V9ttBUV1UDjs1ROQr1ar
ENVQ7G3MF8FiTW2F7IQyZfyGJmXoZsa/cV7fJsOFjShcQWlEpIaNBFoepFr+SH/H
caf+rqXrE2f7nKlNsPYEkOXNSOr0odqwjmhK46+pq4hqKHeyrxu6tH+zZhGpDv4p
YLh4/hN0HZlnY5xmImmvBh5JJTjLyQnUaUvJRdHp/yGgUzcDc4TD+Q==
=RJMz
-----END PGP SIGNATURE-----

--KNAbaO+RG+KCl9Km--