From owner-freebsd-virtualization@FreeBSD.ORG Fri Dec 4 17:55:48 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 D034F106566C for ; Fri, 4 Dec 2009 17:55:48 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outA.internet-mail-service.net (outa.internet-mail-service.net [216.240.47.224]) by mx1.freebsd.org (Postfix) with ESMTP id B57A18FC14 for ; Fri, 4 Dec 2009 17:55:48 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 3E16B2DA6E; Fri, 4 Dec 2009 09:55:48 -0800 (PST) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id AB7B52D6018; Fri, 4 Dec 2009 09:55:47 -0800 (PST) Message-ID: <4B194D28.4040205@elischer.org> Date: Fri, 04 Dec 2009 09:55:52 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Nikos Vassiliadis 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> In-Reply-To: <4B19413B.9090902@gmx.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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:48 -0000 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? > > I was trying to use ng_nat, but it seems that it fails for > probably similar reasons. I don't think ng_nat would fail in that way. It's not the same. You create it in the vnet in which you want to use it. it may have some DIFFERENT reason to fail, but that wouldn't be it.. Just to be sure, you should examine the output of 'ngctl list' and check the connections as well (ngctl show [ID]:) in each jail when it is 'failing' to see what is connected to what. > > Nikos