Date: Fri, 15 Sep 2000 15:15:52 -0700 From: Nick Sayer <nsayer@sftw.com> To: freebsd-emulation@freebsd.org Cc: archie@freebsd.org Subject: vmnet, bridging and netgraph Message-ID: <39C29F98.F3A0FF53@sftw.com>
next in thread | raw e-mail | index | archive | help
Holy crap! It works!
For those of you who have an up-to-date install, you can hose out all of
the bridge stuff in your vmware.sh file and just change the exec line at
the bottom of /usr/local/bin/vmware into this:
ETHER= your ethernet interface (e.g. xl0)
ngctl mkpeer vmnet1: bridge lower link0
ngctl name vmnet1:lower vmnet_bridge
ngctl connect vmnet_bridge: ${ETHER}: link1 lower
ngctl connect vmnet_bridge: ${ETHER}: link1 upper
/usr/local/lib/vmware/bin/vmware "$@"
ngctl shutdown vmnet_bridge:
No more having to change the kernel, no more worries about having the
bridge turned on when vmware isn't running. It's all gravy.
Note that this will probably NOT work if your primary Ethernet interface
is a wi0 card. That's because those cards can't transmit Ethernet frames
with source addresses different than their own. Sorry. Blame Lucent.
They don't want you to avoid buying an access point to do
wireless-to-LAN bridges.
THREE CHEERS FOR ARCHIE!!!! HUZZAH! HUZZAH! HUZZAH!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39C29F98.F3A0FF53>