Date: Thu, 1 Jul 2004 08:40:34 -0500 From: Sean Welch <Sean_Welch@alum.wofford.org> To: Per Hedeland <per@hedeland.org> Cc: freebsd-emulation@freebsd.org Subject: Re: Patches to allow running multiple vmware3 instances Message-ID: <20040701134034.GA1345@NitroPhys.welchsmnet.net> In-Reply-To: <200407011323.i61DNhZ6000679@pluto.hedeland.org> References: <20040701130406.GA1134@NitroPhys.welchsmnet.net> <200407011323.i61DNhZ6000679@pluto.hedeland.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Ah. Aparently I don't understand netmasks well enough. ;-) I missed that they were on different subnets. That resolves my issue! Now I can do some network programming. Sean On Thu, Jul 01, 2004 at 03:23:43PM +0200, Per Hedeland wrote: > Sean Welch wrote: > > > >I added in your patches and recompiled. I do indeed get multiple > >vmnet interfaces but I don't seem able to configure them as you show > >in your example. Specifically, I cannot configure the interfaces to > >be on the same subnet with the same netmask. > > That's right - FreeBSD doesn't allow this AFAIK (it doesn't "make sense" > from a routing perspective). So that's a limitation that follows from > the use of one vmnet interface per vmware instance: Each vmware instance > must be in its own subnet. Unless you use bridged mode, of course... > > > Your example file suggests you used this > >(snip): > > > >vmnet1.Bridged = "NO" > >vmnet1.BridgeInterface = "" > >vmnet1.HostOnlyAddress = "172.31.254.1" > >vmnet1.HostOnlyNetMask = "255.255.255.240" > >vmnet2.Bridged = "NO" > >vmnet2.BridgeInterface = "" > >vmnet2.HostOnlyAddress = "172.31.254.17" > >vmnet2.HostOnlyNetMask = "255.255.255.240" > > Yes - note that those are two different subnets, .1-.15 and .17-.31, > given the netmask. > > >My config file looks like this: > > > >vmware.fullpath = "/usr/local/lib/vmware/bin/vmware" > >wizard.fullpath = "/usr/local/lib/vmware/bin/vmware-wizard" > >dhcpd.fullpath = "/usr/local/lib/vmware/bin/vmnet-dhcpd" > >loop.fullpath = "/usr/local/lib/vmware/bin/vmware-loop" > >libdir = "/usr/local/lib/vmware" > >vmnet1.Bridged = "NO" > >vmnet1.BridgeInterface = "" > >vmnet1.HostOnlyAddress = "172.19.20.40" > >vmnet1.HostOnlyNetMask = "255.255.255.0" > >vmnet2.Bridged = "NO" > >vmnet2.BridgeInterface = "" > >vmnet2.HostOnlyAddress = "172.19.20.41" > >vmnet2.HostOnlyNetMask = "255.255.255.0" > > And that won't work. As to why, lets say that your vmware instance has > the IP address 172.19.20.42 - how can the FreeBSD stack know whether > packets for it should be sent via the vmnet1 or the vmnet2 interface? > So it's simply not allowed - the interface configs are considered > conflicting. > > --Per Hedeland > per@hedeland.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040701134034.GA1345>