Date: Fri, 8 Jan 2010 20:15:58 +0100 (CET) From: Juergen Lock <nox@jelal.kn-bremen.de> To: patfbsd@davenulle.org Cc: freebsd-questions@freebsd.org Subject: Re: Virtualbox and bridged interface. Message-ID: <201001081915.o08JFwnX034602@triton8.kn-bremen.de> In-Reply-To: <20100102005808.12d46e63@baby-jane.lamaiziere.net> References: <20100102002243.54ba6716@baby-jane.lamaiziere.net> <6201873e1001011536p51c47d0fh93d700c6d96fb126@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20100102005808.12d46e63@baby-jane.lamaiziere.net> you write: >Le Fri, 1 Jan 2010 17:36:30 -0600, >Adam Vande More <amvandemore@gmail.com> a =E9crit : > >> > Is there someone able to make VirtualBox working with a bridged >> > interface? >> > >> > I've got : >> > My gateway/access point on 192.168.1.1/24 >> > The host on 192.168.1.20/24 via wifi (wlan0) >> > The guest on 192.168.1.25/24 bridged with wlan0 >... > >> Bridged networking doesn't work on wireless interfaces. > >Ah ok :( > >I would be happy to know why, briefly. Is it a limitation in the >wireless connection or a limitation in the operating system (FreeBSD)? > The problem is caused by the fact that hosts on wifi can usually only use a single mac address, and while the vbox code does contain a `shared mac' feature thats supposed to work around this problem this feature hasn't been ported for FreeBSD hosts yet. >I've used some bridged guests on Mac OS X and vmware fusion but I don't >remember if I used the ethernet or the wireless interface. > >To J.D.Bronson: no mac authentication here, thanks for the "shot in the >dark" anyway. > >So I will try to setup a vpn between the host and the guest. There is another workaround tho that you can try involving a tap interface, routing, proxy arp, and a patch to vbox to enable direct tap networking, http://people.freebsd.org/~nox/vbox/patch-tapdirect.txt more details including a config example in this post: http://lists.freebsd.org/pipermail/freebsd-emulation/2010-January/007260.html (I patched vbox 3.1.2 thats not commtted to ports yet, it's possible the patch doesn't apply to the older version in ports. The latest vbox 3.1.2 Call for testing is here: http://lists.freebsd.org/pipermail/freebsd-emulation/2010-January/007241.html The patch can go in that port's files/ dir.) HTH, Juergen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201001081915.o08JFwnX034602>