From owner-freebsd-virtualization@FreeBSD.ORG Fri Dec 4 17:55:49 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A2861065670 for ; Fri, 4 Dec 2009 17:55:49 +0000 (UTC) (envelope-from nvass9573@gmx.com) Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.42]) by mx1.freebsd.org (Postfix) with SMTP id 7EF788FC13 for ; Fri, 4 Dec 2009 17:55:48 +0000 (UTC) Received: (qmail invoked by alias); 04 Dec 2009 17:55:46 -0000 Received: from adsl-252.91.140.44.tellas.gr (EHLO [169.254.0.102]) [91.140.44.252] by mail.gmx.com (mp-eu004) with SMTP; 04 Dec 2009 18:55:46 +0100 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX18mniQZ6agm/vg2Tl0zZbiO3PGtVV62mrZJ72zTgp 8/3/1tS5KUsDNi Message-ID: <4B194D06.2010705@gmx.com> Date: Fri, 04 Dec 2009 19:55:18 +0200 From: Nikos Vassiliadis User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Julian Elischer References: <66313f8d0912020817x5839715ake916804d61dea730@mail.gmail.com> <20091202224841.O83957@maildrop.int.zabbadoz.net> <66313f8d0912030616h691b149ay64dac79214336c45@mail.gmail.com> <4B1803A0.6000403@elischer.org> <4B192D38.6020309@gmx.com> <4B193BC5.9040707@elischer.org> <4B19413B.9090902@gmx.com> <4B194B5C.6040603@elischer.org> In-Reply-To: <4B194B5C.6040603@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.67 Cc: FreeBSD virtualization mailing list Subject: Re: ppp in vimages? X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Dec 2009 17:55:49 -0000 Julian Elischer wrote: > Nikos Vassiliadis wrote: >> Julian Elischer wrote: >>> we would expect it to work the way you wish but it appears that we >>> have left that out in oversight. >>> >>> We'll see what we can do.. >>> >>> (remember in 8.0 vimage is just s technology review feature and you >>> should not be trying to use it in production.) >>> I'll look at what it will take to fix this by 8.1 :-) >> >> Thanks a lot! >> >> Completely irrelevant to this thread, but is there any >> in-kernel NAT mechanism that is known to work with vnets >> at this time? > > ipfw nat? (same library, different interface) > I've never used it though so I don't know how it's done. > Tried that, but unfortunately the ipfw nat module panics the kernel on loading... Nikos