Date: Mon, 26 Mar 2001 23:41:04 -0500 From: The Babbler <bts@babbleon.org> To: scotty@klement.dstorm.net, The Babbler <bts@babbleon.org>, freebsd-emulation@freebsd.org Subject: Re: VMware networking (was: Slooow VMware on RELENG_4 SMP) Message-ID: <3AC019E0.F1CF1B1E@babbleon.org> References: <Pine.BSF.4.21.0103261836280.1691-100000@klement.dstorm.net> <3AC00B6A.54C2B0D7@babbleon.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for your help . . . I remembered why, in particular, I was trying to avoid having the guest be just another node on the network, but rather wanted to do NATD or whatever. It came to me when I was making my guest into a regular DHCP client (which I'm trying anyway just to see if I can get BRIDGE or NETGRAPH working that way). It's because I have a VPN tunnel into work under FreeBSD and I want for the guest packets to be able to hitch a ride there if they are going there, or to go out of eth0. In short, I really want for the vmware guest to somehow go through whatever routing I have set up by the host, automatically. Since the exact same addresses are sometimes served up to the host via DHCP and other times set up as a ppp over ethernet, it's confusing. However, I could solve this by making the VMware use DHCP all the time, I suppose, and let the host run a DHCP server just to serve the info to the guest. The static subnet approach seemed simpler. I did *not* have the VPN stuff working under Linux (I could never get it working there, in fact; it was a prime motivation to swtich to FreeBSD) even for the host, so I never got far enough to have an issue with VPN and the guest; the setup was anticipating this as a problem, though. With kernel BRIDGE support enabled and vmware set to DHCP, the vmware Win98se guest gets a DHCP address of 169.252.97.50. I have no idea where that comes from Having tried that without success, I've now deinstalled the old vmware2 port (vmware2-2.0.3.799) and reinstalled the new one (vmware2-2.0.3.799_1). There is still no "linprocfs.sh" in my /usr/local/etc/rc.d directory. However, a "df" shows that I do, in fact, have a linprocfs running, for whatever reason. I'm just guessing here, but I bet that rtc.sh is for the RTC device, which works ok but I've been regularly disabling when vmware came up anyway, to avoid pegging the CPU at 100%. Will it matter for networking? I'll build & install a kernel with the bridging removed so that I can have a clean trial for the vmware netgraph code. As I said, it worked for me once. Maybe I can repeat my good fortune consistently. I'll post with the results. > > > So . . . . > > > With the latest vmware2 port (2.0.3.799_1), which is supposed to "just > > > work" by using netgraph, I can't even communicate from the guest to the > > > host at all. Not even from ...242.1 to ...242.2 or vice versa. > > > Actually, it's a little weirder than that. The *first* time I tried > > > this after installing that port, it all worked beautifully. But after > > > the next time I rebooted my host, it didn't work at all, and it never > > > has since then either. > > > > Strange. The scripts that should be starting these things are in > > /usr/local/etc/rc.d/ called "rtc.sh" "linprocfs.sh" "vmware.sh". They > > should be running when you boot. Do you see them running? Are there > > any errors? > > Well, I've backed up to 2.0.03.799, so it's hard to say for sure without > re-switching ports (which I will do shortly, but you had so many > questions I wanted to try answering what I could at one fell swoop). > With the port I'm currenlty running I don't have a "linprocfs.sh" but I > do have the other two. But I'm not sure if I should have linprocfs.sh > with the port I have or not. I'll send followup mail when I have a > change to try re-installing that port. -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. 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?3AC019E0.F1CF1B1E>