Date: Fri, 28 Jul 2000 10:31:11 -0700 From: Nick Sayer <nsayer@sftw.com> To: freebsd-emulation@freebsd.org Subject: Bridged networking with vmware Message-ID: <3981C35F.85C5B821@sftw.com>
next in thread | raw e-mail | index | archive | help
Here's how to do it: 1. If /modules/if_tap.ko exists on your system, then you should use the next version of the port that Vladimir is going to release. :-) if_tap has a couple of small hacks in it that make vmware able to use it. I suspect (but won't speak for Vladimir) that vmnet gets rolled into vmmon since it consists only of some linux ioctl conversions with this step being taken. 2. After loading the module (either vmnet_bridge.ko or if_tap.ko) and making the /dev nodes, you must open the /dev node for the interface to be created. 'echo >/dev/vmnet1' is good enough. You will see ifconfig vmnet1 report the interface at that point. 3. After vmnet1 shows up, you must 'sysctl -w net.link.ether.bridge_refresh=1'. This informs the bridging code that there is a new interface. **WARNING** If you kldunload vmnet or if_tap, you must also IMMEDIATELY refresh the bridge to make sure that you don't panic your kernel (I suspect it won't be long before the bridge code is tied into ether_ifattach() and ether_ifdetach() to automate this). 4. ifconfig vmnet1 with the correct IP address (it doesn't actually matter in the grand scheme of things, but vmware checks, so it has to be right even if it is irrelevent). 5. Set up vmware to use host-only networking. It will be bridged anyway, but what it doesn't know won't hurt it. 6. Set up your vmware guest to use an IP address on the same network as your host, or have it be a DHCP client if that's appropriate. It will see the same LAN as the host. Note that if you tell your guest to be a DHCP client, you should set up a static MAC address in your vmware configuration. ethernet0.address = 00:50:56:1e:ad:bf will do it (make sure the number is unique and starts with 0:50:56:1_:). 7. sysctl -w net.link.ether.bridge=1. sysctl -a | grep bridge and make sure that bridge_cfg lists both your real Ethernet interface and vmnet1 in the same group. That should do it. Steps 2-4 are probably done automatically for you by the port's rc script, but if you're having trouble, it's best to make sure it's happening right. 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?3981C35F.85C5B821>