From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bifrost.lang.hm (mail.lang.hm [64.81.33.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id C9E3B21F200 for ; Sun, 25 Jan 2015 19:19:38 -0800 (PST) Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id t0Q3JZsn010874; Sun, 25 Jan 2015 19:19:35 -0800 Date: Sun, 25 Jan 2015 19:19:35 -0800 (PST) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: Dave Taht In-Reply-To: Message-ID: References: <54B5D28A.3010906@gmail.com> <7B1EA8F0-FCB6-4A37-950F-2558FC751DE8@gmail.com> <54C038D0.1000305@gmail.com> <54C0BD22.3000608@gmail.com> <54C13F47.1010203@gmail.com> <1422111577.328132080@apps.rackspace.com> <1422217048.025611275@apps.rackspace.com> <1422237076.005718796@apps.rackspace.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] Recording RF management info _and_ associated traffic? X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2015 03:20:07 -0000 On Sun, 25 Jan 2015, Dave Taht wrote: > On Sun, Jan 25, 2015 at 6:43 PM, David Lang wrote: >> On Sun, 25 Jan 2015, Dave Taht wrote: >> >>> To your roaming point, yes this is certainly one place where migrating >>> bridged vms across machines breaks down, and yet more and more vm >>> layers are doing it. I would certainly prefer routing in this case. >> >> >> What's the difference between "roaming" and moving a VM from one place in >> the network to another? > > I think most people think of "roaming" as moving fairly rapidly from one > piece of edge connectivity to another, and moving a vm is a great deal more > permanent operation. There are two different types of roaming. You have the case like I deal with at SCaLE where you are moving within one network (within one site) Then you have the case where you are moving between sites. within one site, roaming and migrating VMs are pretty much the same problem and handling it at layer2 makes a lot of sense (how frequently the migrations happen, and how permanent they are varies, both for wifi nodes and VMs) David Lang