From owner-freebsd-current@FreeBSD.ORG Fri Feb 29 17:44:30 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B67E91065670 for ; Fri, 29 Feb 2008 17:44:30 +0000 (UTC) (envelope-from schwabe@uni-paderborn.de) Received: from mail.blinkt.de (mail.blinkt.de [88.198.169.219]) by mx1.freebsd.org (Postfix) with ESMTP id 767D88FC12 for ; Fri, 29 Feb 2008 17:44:30 +0000 (UTC) (envelope-from schwabe@uni-paderborn.de) Received: from dslb-084-061-146-006.pools.arcor-ip.net ([84.61.146.6] helo=styx.local) by mail.blinkt.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1JV8lN-0001Aw-Sb; Fri, 29 Feb 2008 18:11:13 +0100 Message-ID: <47C83CB1.6000902@uni-paderborn.de> Date: Fri, 29 Feb 2008 18:11:13 +0100 From: Arne Schwabe User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; de; rv:1.8.1.12) Gecko/20080213 Thunderbird/2.0.0.12 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: Jeremie Le Hen References: <47C44420.6050009@elischer.org> <20080229152542.GD94339@obiwan.tataz.chchile.org> In-Reply-To: <20080229152542.GD94339@obiwan.tataz.chchile.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Julian Elischer , FreeBSD Current Subject: Re: why vimage? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Feb 2008 17:44:30 -0000 Jeremie Le Hen schrieb: > 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. > > Any explanation will be welcome :). > Thanks, > I am sure you can use the bridge interface for this. Arne