From owner-freebsd-emulation@FreeBSD.ORG Thu Jul 1 13:41:48 2004 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1B6116A4CF for ; Thu, 1 Jul 2004 13:41:48 +0000 (GMT) Received: from starling.mail.pas.earthlink.net (starling.mail.pas.earthlink.net [207.217.120.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id D87D243D49 for ; Thu, 1 Jul 2004 13:41:48 +0000 (GMT) (envelope-from welchsm@earthlink.net) Received: from c-24-118-150-243.mn.client2.attbi.com ([24.118.150.243] helo=NitroPhys.welchsmnet.net) by starling.mail.pas.earthlink.net with asmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1Bg1nx-00082R-H2; Thu, 01 Jul 2004 06:40:45 -0700 Received: from NitroPhys.welchsmnet.net (localhost [127.0.0.1]) i61DeYe0001366; Thu, 1 Jul 2004 08:40:34 -0500 (CDT) (envelope-from welchsm@localhost.welchsmnet.net) Received: (from welchsm@localhost)i61DeYOn001365; Thu, 1 Jul 2004 08:40:34 -0500 (CDT) (envelope-from welchsm) Date: Thu, 1 Jul 2004 08:40:34 -0500 From: Sean Welch To: Per Hedeland Message-ID: <20040701134034.GA1345@NitroPhys.welchsmnet.net> References: <20040701130406.GA1134@NitroPhys.welchsmnet.net> <200407011323.i61DNhZ6000679@pluto.hedeland.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200407011323.i61DNhZ6000679@pluto.hedeland.org> User-Agent: Mutt/1.5.6i X-ELNK-Trace: 15d86f98c8ef8acad780f4a490ca69564776905774d2ac4bab97113d3346e939659a536a415b49f2350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 24.118.150.243 cc: freebsd-emulation@freebsd.org Subject: Re: Patches to allow running multiple vmware3 instances X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Sean_Welch@alum.wofford.org List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2004 13:41:49 -0000 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