From owner-freebsd-questions@FreeBSD.ORG Sun Feb 10 12:54:59 2013 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4CA58D4B for ; Sun, 10 Feb 2013 12:54:59 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 1EE94B22 for ; Sun, 10 Feb 2013 12:54:58 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id r1ACsveE032455 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 10 Feb 2013 06:54:57 -0600 Received: from LTCFISWMSGMB21.FNFIS.com ([10.132.99.23]) by LTCFISWMSGHT06.FNFIS.com ([10.132.206.17]) with mapi id 14.02.0309.002; Sun, 10 Feb 2013 06:54:56 -0600 From: "Teske, Devin" To: Nikos Vassiliadis Subject: RE: vnet without epair Thread-Topic: vnet without epair Thread-Index: AQHOBt464Fa8DUsL5kqOlKb89O3Sd5hyJMWAgAAqfgD//8hg54ABPouA//+wx9E= Date: Sun, 10 Feb 2013 12:54:55 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D7201EA6BAB@ltcfiswmsgmb21> References: <511671FA.3050801@a1poweruser.com> <511680AD.1040209@gmx.com>,<5116A452.6030104@a1poweruser.com> <13CA24D6AB415D428143D44749F57D7201EA6A3F@ltcfiswmsgmb21>, <511780DF.6010600@gmx.com> In-Reply-To: <511780DF.6010600@gmx.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.120] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8327, 1.0.431, 0.0.0000 definitions=2013-02-10_04:2013-02-08,2013-02-10,1970-01-01 signatures=0 Cc: Fbsd8 , FreeBSD questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Feb 2013 12:54:59 -0000 On Sun, 10 Feb 2013, Nikos Vassiliadis wrote: > On 2/10/2013 1:12 AM, Teske, Devin wrote: > > On Sat, 9 Feb 2013, Fbsd8 wrote: > >> I did google search and could only find 9.0 vnet jails using epair. > > > > I'm surprised you didn't find my own page on vnet jails using netgraph: > > > > http://druidbsd.sf.net/vimage.shtml >=20 > I have seen this but I got the idea that it is not in ports(?) and this > stopped me from trying. >=20 It's not in ports only because I first wanted to see where jail.conf would = take us w/respect to vimages. However, this package not being in ports shouldn't prevented you from tryin= g it -- it's extremely stable and as I mentioned, we've been using it heavi= ly at $work for over 12 months now. When you download the package (*.tgz) a= nd pkg_add it, it installs the following two files only: /etc/rc.d/vimage /etc/rc.conf.d/vimage NOTE: The rc.conf.d file is the "documentation" on usage If you haven't tried it, then I hope you will because I think the new jail.= conf stuff falls short. Don't get me wrong, jail.conf is a great start, but= simply adding the ability to manage the vnet aspect of a jail does not mak= e a vimage (what's missing is the built-in support for generating bridges a= s vimages are brought up/down dynamically). I feel that before I add this to ports I need to reprogram it to use jail.c= onf (not directly). That will simplify its code and [should] make it smalle= r. I was somewhat waiting on /etc/rc.d/jail to blaze the trail for me. In short, the landscape has been changing fast enough that it's prevented m= e from adding this to ports, but in spite of that it's still very much real= _and_ real stable. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.