--WYTEVAkct0FjGQmd
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Sep 22 2007 - 18:43, Quentin Garnier wrote:
> > >=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
> >=20
> > OK... and would it make sense to have all qemu interfaces in bridge0 and
> > do some NAT between wpi0 and bridge0 ?
>=20
> Sure.  You affect an IP address to one of the tap interface and you make
> it the default route for the VMs.
>=20

I'll do that then.

> > The thing is, my laptop's wired NIC is not recognised (yet) by NetBSD so
> > wpi0 is my only way out to the Internet :-)
>=20
> What kind of device is it?  It's probably not to hard to add support for
> it.
>=20

Broadcom BCM5906M NetLink Fast Ethernet (ethernet network, revision 0x02) a=
t pci4 dev 0 function 0 not configured

Or maybe the device in just not in GENERIC ?
I'm using -rjmcneill-pm because it include support for my vga card (and
not GENERIC yet, AFAIK).

Regards,
	Jo


--WYTEVAkct0FjGQmd
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFG9VEE0/VH7L7F7Y4RAo8UAJ0ZZucvzAt8B8GwPVJUoYd8CiJ4ZgCcCgfN
aKViPNwYg2MOPZfX3YKWB90=
=c1nK
-----END PGP SIGNATURE-----

--WYTEVAkct0FjGQmd--