Date: Mon, 11 Oct 2004 02:20:40 +0200 From: Christian Hiris <4711@chello.at> To: freebsd-questions@freebsd.org Subject: Re: route vmnet1 host server Message-ID: <200410110221.05289.4711@chello.at> In-Reply-To: <20041010160231.GA836@pooh.nagual.st> References: <20041010160231.GA836@pooh.nagual.st>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 10 October 2004 18:02, Dick Hoogendijk wrote:
> I installed vmware3 on my fbsd-4.1 box. This machine has one
> ethernetcard and is a part of my local network (192.168.11.22)
>
> The situation:
>
> Server -- internet (217.122.132.217) - eth0
> -- localnet (192.168.11.1) - eth1
> (gw, dnsserver)
>
> fbsdbox -- localnet (192.168.11.22) - rl0
> -- subnet2 (192.168.22.1) - vmnet1 (vmware3)
> -- windows on vmware3 (192.168.22.201)
>
> -does vmnet1 indeed have to be configured as a different subnet?
> -is vmnet1 the gateway for the vm win machines to be installed yet.
> -how do I get the diff subnets talking to each other?
In your case /dev/vmnet1 is used for bridging (line vmnet1.Bridged = "YES" in
your VMware config). It bridges the network traffic from the inside of your
virtual machine (win-guest) to your physical NIC and vice versa.
win-vm <--> bridge [vmnet1/rl0] <--> rl0 (phys) <--> localnet/gateway
The easiest solution is to assign a free ip-address of your localnet
(192.168.11.nnn) to your win-guest. Try to avoid a setup of two subnets on
one physical NIC.
As /dev/vmnet1 acts as bridge it's ip-address isn't relevant. There is only
the requirement that it's ip-address should not conflict with any already
'in-use' ip-address on your network. So I would leave it as is (in theory a
bridge doesn't need any ip-address - it operates on layer2).
> -did I get the ipnat rules correct?
If you decide to use a ip-address in your localnet ip-range, just duplicate
the host-specfic rules and change the host-ip(192.168.11.22) to your
win-guest-ip (192.168.11.nnn) in theese rules. You maybe want to do some
extra-blocking of unwanted win-specific traffic. I only use ipfw, so I'm not
the one that can answer your ipnat question in detail.
Cheers,
ch
- --
Christian Hiris <4711@chello.at> | OpenPGP KeyID 0x3BCA53BE
OpenPGP-Key at hkp://wwwkeys.eu.pgp.net and http://pgp.mit.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)
iD8DBQFBadHx09WjGjvKU74RAn1tAJ9YmLUTghPghwgd6K5ufw8A2O0mQACaA/Ms
yk+P4NGF86/rjgtPpTJYvng=
=kmCL
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410110221.05289.4711>