From owner-freebsd-emulation@FreeBSD.ORG  Thu Jul  1 13:37:01 2004
Return-Path: <owner-freebsd-emulation@FreeBSD.ORG>
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 CF21416A4CE
	for <freebsd-emulation@freebsd.org>;
	Thu,  1 Jul 2004 13:37:01 +0000 (GMT)
Received: from pluto.hedeland.org (c0172a.mael.bostream.se [194.236.4.19])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2D12F43D58
	for <freebsd-emulation@freebsd.org>;
	Thu,  1 Jul 2004 13:37:01 +0000 (GMT)
	(envelope-from per@hedeland.org)
Received: from pluto.hedeland.org (localhost [127.0.0.1])
	i61DZmVx000894
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 1 Jul 2004 15:35:48 +0200 (CEST)
Received: (from per@localhost)i61DZmh6000893;
	Thu, 1 Jul 2004 15:35:48 +0200 (CEST)
Date: Thu, 1 Jul 2004 15:35:48 +0200 (CEST)
From: Per Hedeland <per@hedeland.org>
Message-Id: <200407011335.i61DZmh6000893@pluto.hedeland.org>
To: killing@multiplay.co.uk, Sean_Welch@alum.wofford.org
In-Reply-To: <01ea01c45f6d$dc2961b0$7b07000a@int.mediasurface.com>
X-Scanned-By: MIMEDefang 2.39
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
List-Id: Development of Emulators of other operating systems
	<freebsd-emulation.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-emulation>,
	<mailto:freebsd-emulation-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-emulation>
List-Post: <mailto:freebsd-emulation@freebsd.org>
List-Help: <mailto:freebsd-emulation-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-emulation>,
	<mailto:freebsd-emulation-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2004 13:37:01 -0000

"Steven Hartland" wrote:
>
>The second interface will most likely need a 255.255.255.255
>subnet mask just like a normal interface alias.

No, that won't work - each vmnet interface is (from the host
perspective) conceptually connected to a "real" network (this is
independant of my patches), which needs to have the IP address of the
host (the one configured on the interface), the address(es) of the
vmware guest(s) (can be multiple with different IP addresses, only you
cannot run them simultaneously), and broadcast address. I.e. the longest
netmask you can use is 255.255.255.252, for four-address subnets. And
the vmnet interfaces are all "equal".

--Per Hedeland
per@hedeland.org