Date: Thu, 19 Apr 2007 20:26:07 +0200 (CEST) From: Juergen Lock <nox@jelal.kn-bremen.de> To: scottro@nyc.rr.com Cc: freebsd-emulation@freebsd.org Subject: Re: Bounty and timeline on vmware 5.x on FreeBSD 6.x Message-ID: <200704191826.l3JIQ7ap061788@saturn.kn-bremen.de> In-Reply-To: <20070416140454.GA79264@uws1.starlofashions.com> References: <200704050712.l357Ck5F000488@pluto.hedeland.org> <4614F65D.3010403@freebsd.org> <ygftzvuhk42.fsf@dominion.borderworlds.dk> <20070405215754.GA28008@saturn.kn-bremen.de> <461A6431.2030709@freebsd.org> <20070410123604.D35599@kozubik.com> <462379F1.3050008@freebsd.org> <20070416063519.L35599@kozubik.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20070416140454.GA79264@uws1.starlofashions.com> scottro@nyc.rr.com wrote: >... >My only problems with VirtualBox were in getting it to use bridged >networking with a wireless connection. I had no problem when it was >connected by cabled ethernet, but judging from a bit of googling, I'm >not the only one who couldn't get it working with wireless. > >Disclaimer number 2--I'm not at all experienced with bridging in Linux, >it seems to be a bit different than what I do with FreeBSD, and it could >easily be a PEBCAK problem. Afaik the problem is that bridging causes the source ethernet address of packets you send to change, and not all wireless nics/drivers support sending other source ethernet addresses than the nic's own. (This usually isn't a problem with wired nics...) HTH, Juergen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704191826.l3JIQ7ap061788>