Date: Sun, 24 Mar 2002 21:54:08 -0700 From: "John Nielsen" <oniblerz@attbi.com> To: "Randy Bush" <randy@psg.com>, "Brooks Davis" <brooks@one-eyed-alien.net> Cc: "freebsd emulator list" <freebsd-emulation@FreeBSD.ORG> Subject: Re: vmware nat windoze services Message-ID: <01ae01c1d3b9$19739420$0900a8c0@max> References: <E16obOB-000HmW-00@rip.psg.com><02f701c1d23a$d4be6c30$0900a8c0@max><E16pGMV-000OPy-00@rip.psg.com><E16pIAk-0001iQ-00@rip.psg.com><003901c1d394$72e0f310$0900a8c0@max><E16pJf1-0004VG-00@rip.psg.com><20020324180238.A1318@Odin.AC.HMC.Edu> <E16pLAO-0007RQ-00@rip.psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Randy Bush" <randy@psg.com> To: "Brooks Davis" <brooks@one-eyed-alien.net> Cc: "John Nielsen" <oniblerz@attbi.com>; "freebsd emulator list" <freebsd-emulation@FreeBSD.ORG> Sent: Sunday, March 24, 2002 8:29 PM Subject: Re: vmware nat windoze services > >> have options BRIDGE in kernel > > vmware uses netgraph bridging so this is just going to cause problems. > > had tried the other way. ah well. > > >> choosing netgraph and wi0 (my physical external interface). > > You can't do this. It's not possiable to bridge to a wireless card > > supported by wi(4). Some people claim it works for an(4), but others > > have failed to get that to work. > > well, that explains many wasted hours. sigh. Sorry if I led you up the garden path earlier. FWIW, I always have bridging support in the kernel when I use VMware and I've never had a problem. (I don't enable the bridge manually, though.) > then, back to my original question .... > > running ipfw / divert, how do i make the client win98se visible, i.e. > browsable, sharable, ... to the other windows systems on the lan? The simplest way is probably to set up a second (alias) IP address on the real network on the FreeBSD host. Then send a redirect_address flag to natd to it passes all the traffic to that address to a natted address on the internal (virtual in this case) network. That should get you so sharing will work, but won't get you browsing. If you don't mind using UNC paths with IP addresses in them (i.e. \\real.IP.addr\sharename) then that's fine. If browsing is a must, then install Samba on the Host and set it up as a WINS server. Then tell your virtual machine to use the FreeBSD host's vmnet interface address as its WINS server. In this case you do want the vmnet address to be on the same subnet as the guest OS. JN 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?01ae01c1d3b9$19739420$0900a8c0>