Re: route vmnet1 host server
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 11 October 2004 21:04, dick hoogendijk wrote: > On 11 Oct Christian Hiris wrote: > > In the Ethernet Adapters configuration dialog select > >Connection Type: --> Custom > >Vmnet:--> /dev/vmnet1 > > In your next message you explain about the support for ¨bridge¨ on > freebsd. However, I don´t have vmware3 setup like this. I chose HostOnly > and all is working perfectly now. Only needed to change the local IP of > the virtual machine. > > Is there an advantage on Connection Type --> Custom over the Connection > Type --> HostOnly ?? > > As said, the latter workt flawlessly. AFAIK the interface type hostonly is hardwired to /dev/vmnet1. As long as you connect only one virtual machine this should work fine, too. If you want connect multiple virt. machines to your network, bridged mode + Custom + /dev/vmnetN setup is the easier way to go. The doc MultipleInstances.FreeBSD decribes bridged/non-bridged vmware setups in detail. If you connect only one virtual machine, i see no advantage/disadvantage. I had some troubles w/ hostonly setup in the past. That's the reason why I prefer to advice use of the custom interface type. But - there was a large improvement on the vmnet code during the last months, so things might work fine for both interface types. - -- Christian Hiris <[EMAIL PROTECTED]> | 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) iD8DBQFBawRL09WjGjvKU74RAoglAJ4z9uICoYu1bcN7ik6xeqZXizGg2gCfbSQF J8A8DRGXfGXGcTpsbMnt0kA= =TKgi -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: route vmnet1 host server
On 11 Oct Christian Hiris wrote: > In the Ethernet Adapters configuration dialog select >Connection Type: --> Custom >Vmnet:--> /dev/vmnet1 In your next message you explain about the support for ¨bridge¨ on freebsd. However, I don´t have vmware3 setup like this. I chose HostOnly and all is working perfectly now. Only needed to change the local IP of the virtual machine. Is there an advantage on Connection Type --> Custom over the Connection Type --> HostOnly ?? As said, the latter workt flawlessly. -- dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.10 ++ Debian GNU/Linux (Woody) + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilya ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: route vmnet1 host server
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 11 October 2004 16:37, Christian Hiris wrote: > On Monday 11 October 2004 12:27, dick hoogendijk wrote: > > The above information says it all, I guess. I was confused, because the > > vmware3 ports speaks of no support for bridging. This must be some other > > kind of bridging ;-) As you tell me, this is a normal story and I don't > > expect to have difficulties with it. > > Yup, you don't need to set gateway_enable="YES" in your rc.conf same with > ipnat, you don't need it. There is one important thing when you start > vmware and set up your virtual machine: > > In the Ethernet Adapters configuration dialog select >Connection Type: --> Custom >Vmnet:--> /dev/vmnet1 What you read about unsupported bridging is related to this. The vmware3 port supports bridging, but you can't use the 'Connection Type Bridged' in the virtual machine setup. However, bridging is supported via 'Connection Type Custom' and 'Vmnet /dev/vmnet1'. This is maybe a little confusing, if you are new to VMware on FreeBSD. - -- Christian Hiris <[EMAIL PROTECTED]> | 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) iD8DBQFBaqCT09WjGjvKU74RAv5QAJ989h9mdPUS+Q7pm4JVyl9ZQrwVJACfejiu davJVxTq/1jv96agSHN4xxQ= =yOPP -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: route vmnet1 host server
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 11 October 2004 12:27, dick hoogendijk wrote: > > The above information says it all, I guess. I was confused, because the > vmware3 ports speaks of no support for bridging. This must be some other > kind of bridging ;-) As you tell me, this is a normal story and I don't > expect to have difficulties with it. There was a thread some days ago on the questions and emulation mailing-list about vmware3 setup. > My next question is irrelevant too, I guess. If I give my vm-winbox a > 'normal' local IP there is no need for the freebsd machine to act as > gateway (away with it from rc.conf) and I also don't need ipnat. The > normal firewall rules will do. Yup, you don't need to set gateway_enable="YES" in your rc.conf same with ipnat, you don't need it. There is one important thing when you start vmware and set up your virtual machine: In the Ethernet Adapters configuration dialog select Connection Type: --> Custom Vmnet:--> /dev/vmnet1 - -- Christian Hiris <[EMAIL PROTECTED]> | 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) iD8DBQFBapq409WjGjvKU74RAhQfAJ9JZ20tg77jyrugYIK0X6tMUHWx2wCeO0Xb sYoIXJW8wQNFwQZOvFDiAZA= =qwVi -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: route vmnet1 host server
On 11 Oct Christian Hiris wrote: > 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. The above information says it all, I guess. I was confused, because the vmware3 ports speaks of no support for bridging. This must be some other kind of bridging ;-) As you tell me, this is a normal story and I don't expect to have difficulties with it. My next question is irrelevant too, I guess. If I give my vm-winbox a 'normal' local IP there is no need for the freebsd machine to act as gateway (away with it from rc.conf) and I also don't need ipnat. The normal firewall rules will do. If I'm wrong I like to hear it. That's why I'll leave the quetion intact. > > -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. -- dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.10 ++ Debian GNU/Linux (Woody) + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilya ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: route vmnet1 host server
-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 <[EMAIL PROTECTED]> | 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- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
