Date: Fri, 10 Dec 1999 22:07:17 -0500 From: "Vladimir N. Silyaev" <vsilyaev@mindspring.com> To: "Viren R.Shah" <viren@rstcorp.com> Cc: "Louis A. Mamakos" <louie@TransSys.COM>, freebsd-emulation@freebsd.org, "Vladimir N. Silyaev" <vsilyaev@mindspring.com> Subject: Re: ANNOUNCE: Update port VMware 1.1 for Linux, Networking Support Message-ID: <19991210220716.D2287@jupiter.delta.ny.us> In-Reply-To: <14417.47612.360839.161751@jabberwock.rstcorp.com>; from viren@rstcorp.com on Fri, Dec 10, 1999 at 09:42:04PM -0500 References: <199912110143.UAA54831@whizzo.transsys.com> <14417.47612.360839.161751@jabberwock.rstcorp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 10, 1999 at 09:42:04PM -0500, Viren R.Shah wrote: > Well, I sorta have it installed -- it installed from the win98 CD, but > I've not yet managed to get networking of any kind up. My CDROM drive > was easily recognized by vmware (I symlinked /compat/linux/dev/cdrom > to /dev/acd0c. > > > Are msgs of this kind normal: > > Dec 10 21:26:07 frabjous /kernel: linux: syscall setresuid is > obsoleted or not implemented (pid=35075) > Dec 10 21:26:04 frabjous last message repeated 17 times I think you are run vmware not from root? > > Also, are we manually suppossed to configure the vmnet[01] devices? No. After port installation you are have the file /usr/local/etc/rc.d/vmware.sh, this file summoned and configured vmnet1 interface. > > My ifconfig looks like: > > frabjous# ifconfig -a > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet 192.168.100.2 netmask 0xffffff00 broadcast > 192.168.100.255 > ether 00:10:4b:2b:0d:3d > media: autoselect (10baseT/UTP) status: active > supported media: autoselect 100baseTX <full-duplex> 100baseTX > 10baseT/UTP <full-duplex> 10baseT/UTP 100baseTX <hw-loopback> > vmnet0: flags=942<BROADCAST,RUNNING,PROMISC,SIMPLEX> mtu 1500 > inet 192.168.100.7 netmask 0xffffff00 broadcast > 192.168.100.255 > ether 00:50:56:ea:c1:a8 vmnet0 currently not used. And more you don't want to summon vmnet0 interface, due to the ethernet address operations. And more this is a very bad idea to have the three ethernet adapters on one computer in the one TCP/IP network. > vmnet1: flags=843<UP,BROADCAST,RUNNING,SIMPLEX> mtu 1500 > inet 192.168.100.7 netmask 0xffffff00 broadcast > 192.168.100.255 > ether 00:50:56:ea:c1:a9 Just a select for vmnet1, another, unused IP network. After chose the right ip address for example 192.168.101.1/24, try to reinstall port (or manually change numbers in the /usr/local/etc/vmware/config and /usr/local/etc/rc.d/vmware.sh files. > > I'm currently trying to get win98 going with host-only networking. > > > My real interface is on xl0 with IP 192.168.100.2 > When asked by the vmware install what I wanted the IP for vmware to > be, I answered 192.168.100.7. Oh now, you are need separated network for this 'ethernet' adapter. > > I've currently got win98 a static IP of 192.168.100.6 with the gateway > pointing to 192.168.100.2 (my real interface). Is this correct? Probably not. Select your IP 192.168.100.1, network mask 255.255.255.0, Windows guest 192.168.100.2, and gateway 192.168.100.1 (only needed when you want to link guest with the rest world). -- Vladimir Silyaev 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?19991210220716.D2287>