Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Apr 2007 20:49:50 +0200
From:      Sten Daniel Soersdal <netslists@gmail.com>
To:        Juergen Lock <nox@jelal.kn-bremen.de>
Cc:        freebsd-emulation@freebsd.org
Subject:   Re: Bounty and timeline on vmware 5.x on FreeBSD 6.x
Message-ID:  <463245CE.7060104@gmail.com>
In-Reply-To: <200704191826.l3JIQ7ap061788@saturn.kn-bremen.de>
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> <200704191826.l3JIQ7ap061788@saturn.kn-bremen.de>

next in thread | previous in thread | raw e-mail | index | archive | help
Juergen Lock wrote:
> 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...)
>

In AP mode it should work but in station mode it can't because of 802.11 
restrictions. There is something called WDS but it's a poorly documented 
hack and is not, AFAIK, supported in FreeBSD.

-- 
Sten Daniel Soersdal



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?463245CE.7060104>