Date: Sat, 1 Mar 2008 04:51:17 -0500 From: "Outback Dingo" <outbackdingo@gmail.com> To: "Julian Elischer" <julian@elischer.org> Cc: Jeremie Le Hen <jeremie@le-hen.org>, FreeBSD Current <current@freebsd.org> Subject: Re: why vimage? Message-ID: <5635aa0d0803010151sa6f3a6fy70f3793df5425b1b@mail.gmail.com> In-Reply-To: <47C8B448.7050005@elischer.org> References: <47C44420.6050009@elischer.org> <20080229152542.GD94339@obiwan.tataz.chchile.org> <47C8B448.7050005@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I think there needs to be some decent howto or documentation established though, i compiled and installed a kernel and the binary read the man page... searched google... but cant for the life of me conceptualize how to get network interfaces up inside the vimage i see the standard rl0 interface in the main i can dhcp and address but dont see how one clones or creates an interface inside the other vimages i found a doc that read Virtual images in a simple bridged environment, written in 2002 and the command ifconfig create ve0.... doesnt work so i think, i for one and many others might appreciate vimages power a bit more if there was a fast howto quick and dirty on how to accomplish a working configuration and discover the power of this code.... I could see a use for it.. thats if i can foigure out how to get networking and chrooted images..... just my thoughts so far.... On Fri, Feb 29, 2008 at 8:41 PM, Julian Elischer <julian@elischer.org> wrote: > Jeremie Le Hen wrote: > > Hi Julian, > > > > On Tue, Feb 26, 2008 at 08:53:52AM -0800, Julian Elischer wrote: > >> I can give a very simple example of something you can do trivially on > >> vimage: > >> > >> Make three virtual machines on yhour laptop: > >> The base machine and two others. > >> Have the first 'other' machine be assigned an IP address on > >> your HOME LAN. > >> have the second virtual machine have an IP adddress on > >> your WORK LAN. > >> use the base machine to run encrypted tunnels from where-ever > >> you happen to be to your work and home.. when you put the laptop to > sleep > >> (assuming the tcp sessions are quiescent (no keepalives)) > >> then when you wake it up say an hour later.. as soon as the base > machine has > >> an IP address.. viola, your session on the virtual > >> machines are still alive. > > > > On this post [1], Marko states: > > > > % Each NICs is logically attached to one and only one network stack > > % instance at a time, and it receives data from upper layers and feeds > > % the upper layers with mbufs in exactly the same manner as it does on > > % the standard kernel. It is the link layer that demultiplexes the > > % incoming traffic to the appropriate stack instance... > > > > As I understand it, there is only one vimage per interface. I'm surely > > wrong or the setup you described wouldn't be possible. > > > > physical interfaces can be forked out to several virtual interfaces > which can be in different virtual machines.. > Or the virtual interfaces could be connected to tunnels. > > > Any explanation will be welcome :). > > Thanks, > > > > [1] > http://lists.freebsd.org/pipermail/freebsd-current/2008-February/083908.html > > > > Regards, > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5635aa0d0803010151sa6f3a6fy70f3793df5425b1b>