Date: Sun, 10 Feb 2013 15:48:48 +0200 From: Nikos Vassiliadis <nvass@gmx.com> To: "Teske, Devin" <Devin.Teske@fisglobal.com> Cc: Fbsd8 <fbsd8@a1poweruser.com>, FreeBSD questions <questions@freebsd.org> Subject: Re: vnet without epair Message-ID: <5117A540.1060702@gmx.com> In-Reply-To: <13CA24D6AB415D428143D44749F57D7201EA6BAB@ltcfiswmsgmb21> References: <511671FA.3050801@a1poweruser.com> <511680AD.1040209@gmx.com>, <5116A452.6030104@a1poweruser.com> <13CA24D6AB415D428143D44749F57D7201EA6A3F@ltcfiswmsgmb21>, <511780DF.6010600@gmx.com> <13CA24D6AB415D428143D44749F57D7201EA6BAB@ltcfiswmsgmb21>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/10/2013 2:54 PM, Teske, Devin wrote:
> It's not in ports only because I first wanted to see where jail.conf would take us w/respect to vimages.
I see.
> However, this package not being in ports shouldn't prevented you from trying it -- it's extremely stable and as I mentioned, we've been using it heavily at $work for over 12 months now. When you download the package (*.tgz) and 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 make a vimage (what's missing is the built-in support for generating bridges as vimages are brought up/down dynamically).
>
> I feel that before I add this to ports I need to reprogram it to use jail.conf (not directly). That will simplify its code and [should] make it smaller. 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 me from adding this to ports, but in spite of that it's still very much real _and_ real stable.
>
Yes, of course.
I will try it and report back to you my findings.
What I - nikos - really need from a script like yours is the ability
to generate arbitrarily complex topologies with interconnected vnet
jails. Something like:
a----b----c---d
|
|
h----e----f---g
|
|
i
Like a cut-down version of imunes[1] without the need of a graphical
user interface.
I understand that is not common case and that is why I was always using
ad hoc scripts.
But one can always hope(or write one himself/herself of course!).
1.
http://web.archive.org/web/20120418053250/http://imunes.tel.fer.hr/imunes/
Thanks, Nikos
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5117A540.1060702>