From owner-freebsd-hackers Sat Dec 29 22:25: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from msslpop1.mssl.uswest.net (msslpop1.mssl.uswest.net [207.225.0.1]) by hub.freebsd.org (Postfix) with SMTP id E84DD37B417 for ; Sat, 29 Dec 2001 22:25:04 -0800 (PST) Received: (qmail 12404 invoked by alias); 30 Dec 2001 06:25:04 -0000 Delivered-To: fixup-freebsd-hackers@FreeBSD.ORG@fixme Received: (qmail 12393 invoked by uid 0); 30 Dec 2001 06:25:02 -0000 Received: from msslapanas13poolb231.mssl.uswest.net (HELO casey.ccmt.net) (63.227.173.231) by msslpop1.mssl.uswest.net with SMTP; 30 Dec 2001 06:25:02 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Casey T.Zednick Reply-To: casey@ccmt.net To: "Joe Parks" Subject: Re: vmware guest networking not working - details Date: Sun, 30 Dec 2001 00:23:44 -0700 X-Mailer: KMail [version 1.2] References: In-Reply-To: Cc: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Message-Id: <01123000234401.00739@casey.ccmt.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well Joe, I will try to give you some pointers as I have VMware(2.0.3) working fine on 4.3 stable, running W2K. Here is my setup - local private LAN i.e. 192.168.0.* - FreeBSD box has an ethernet address set to 192.168.0.254 - Other boxes/vmware hosts have addresses 192.168.0.5...n - All boxes/vmware hosts have a default gateway of 192.168.0.254 - I use user ppp with ppp nat(not reg NAT) to connect to the Internet - VMware is set to use "host-only" On Saturday 29 December 2001 09:58 pm, you wrote: > FreeBSD 4.4-RELEASE. Vmware is running correctly, and I have successfully > loaded windows98 into a virtual machine with no problems. > When I loaded vmware from the port, it asked me what kind of networking I > wanted, and I chose 'bridging'. I think. I use host-only, and there is no settings that needs to be set. However bridged should work, but I never tried in FreeBSD. Exerpt from http://www.mindspring.com/~vsilyaev/vmware/ "28 Jan 01 Version 0.99-1-0.22 Support for multiple vmware sessions             Thnx to Luigi Rizzo Support for bridged and host-only networking" > The win98 VM has the 'AMD PCNET Family Ethernet Adator' installed (is this > some generic adaptor that vmware passes to win98? I don't have any > hardware Yes, the AMD PCNET is the VMware Ethernet adaptor. > My /usr/local/etc/vmware/config file says: > > (lines pertaining to paths omitted) > vmnet1.HostOnlyAddress = "10.20.30.1" > vmnet1.HostOnlyNetmask = "255.255.255.0" My /usr/local/etc/vmware/config file says: vmware.fullpath = "/usr/local/lib/vmware/bin/vmware" wizard.fullpath = "/usr/local/lib/vmware/bin/vmware-wizard" dhcpd.fullpath = "/usr/local/lib/vmware/bin/vmnet-dhcpd" loop.fullpath = ""/usr/local/lib/vmware/bin/vmware-loop" libdir = "/usr/local/lib/vmware/lib" vmnet1.HostOnlyAddress = "192.168.0.1" vmnet1.HostOnlyNetMask = "255.255.255.0" BUT I don't know what this exactly does as my VMware/W2K host has an IP of 192.168.0.5 NOT 192.168.0.1. Maybe it has to do with DHCP??? > I added these lines to /etc/rc.conf: > > gateway_enable="YES" > firewall_enable="YES" > firewall_type="open" > natd_enable="YES" > natd_interface="ep0" Never had to mess with this, but looks good to me. However if you are using "bridged networking" you should not need to run NAT, unless you have other reasons to. Somebody correct me if I'm wrong. > The freeBSD machine can successfully ping the vmnet1 interface. Good. > The win98 machine _cannot_ ping the vmnet1 interface. Bad. First try to use "host-only" networking and see if that works then go from there, as this has been working longer than bridged networking. As for trouble shooting ideas does your "dmesg" command output have something similar in it: /dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 $ /dev/vmmon: Module vmmon: initialized dc0: promiscuous mode enabled vmnet1: promiscuous mode enabled Second what does your "ifconfig" command output? Does it have something similar to this: vmnet1: flags=8843 mtu 1500 inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::2bd:faff:fe07:1%vmnet1 prefixlen 64 scopeid 0xa ether 00:bd:fa:07:00:01 Opened by PID 753 Also _once_ you get it working here is some performance tips. 1. disconnect the RTC in VMware this will give back a lot of CPU. 2. if you get messages saying "/var/tmp" is full create a file with this name in you ".vmware" directory, "config" have line in it like this, "tmpDirectory = path to directory with more space" If you still have trouble, questions, flames, or I was not clear please drop me a line. Casey Z. casey@ccmt.net -- This E-mail message was created with Open Source Software. Using: FreeBSD, http://www.freebsd.org KDE's KMail, http://www.kde.org Vist these sites and support O.S.S. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message