Subject: Re: NetBSD and Xen 2.0
To: Thor Lancelot Simon <>
From: Daniel Carosone <>
List: port-xen
Date: 12/13/2004 07:24:20
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Dec 12, 2004 at 02:12:39PM -0500, Thor Lancelot Simon wrote:
> On Sun, Dec 12, 2004 at 06:17:48PM +0100, Manuel Bouyer wrote:
> >=20
> > I'm *very* interested in this, and have time to work on it.
> > After reading the Xen interface manual here is a summary of what I thin=
k needs
> > to be done (but I didn't look at any code yet):
> > - get a pseudo ethernet device in tree (maybe cube's ethfoo device, mod=
> >   so that it can be compiled in a static kernel), similar to tun(4) but=
> >   ethernet semantics. This is interesting for other reasons, for exampl=
e to
> >   build a virtual lan across an internet link, in a ssh, ipsec or other
> >   kind of securised transport tool. It would also be good for softwares
> >   such as simh: simh currently use /dev/bpf to talk to network, but thi=
s has
> >   some limitation, and one annoying bug (simh can't talk to his host th=
> >   network). Using such a device instead would allow to build a vitual e=
> >   network between simh and its host, and then bridge, NAT, or route it =
> >   the real network device. I guess vmware could use it too.
> Isn't one of the vmware compat modules that Frank did such an interface?
> Maybe it would be possible to reuse it.

yes, vmnet is such a thing, at least in general.  I've used it for the
purpose previously, even with no vmware running.

bridge(4) wants something with ethernet semantics, i've several times
wished it would also work with tun or gre, but something like the
above is another way to achieve it.

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.6 (NetBSD)