[Cerowrt-devel] Recording RF management info _and_ associated traffic?

[Dave Taht]

On Sun, Jan 25, 2015 at 6:43 PM, David Lang <david at lang.hm> 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.

> As far as layer 2 vs layer 3 goes. If you try to operate at layer 3, you are
> going to have quite a bit of smarts in the endpoint. Even if it's only
> connected vi a single link. If you think about it, even if your network
> routing tables list every machine in our environment individually, you still
> have a problem of what gateway the endpoint uses. It would have to change
> every time it moved. Since DHCP doesn't update frequently enough to be
> transparent, you would need to have each endpoint running a routing
> protocol.

Hmm? I don't ever use a dhcp-supplied default gateway, I depend on the routing
protocol to supply that. In terms of each vm running a routing protocol,
well, no, I would rely on the underlying bare metal OS to be doing
that, supplying
the FIB tables to the overlying vms, if they need it, but otherwise the vms
just see a "default" route and don't bother with it. They do need to inform the
bare metal OS (better term for this please? hypervisor?) of what IPs they own.

static default gateways are evil. and easily disabled. in linux you
merely comment
out the "routers" in /etc/dhcp/dhclient.conf, in openwrt, set
"defaultroute 0" for the
interface fetching dhcp.

When a box migrates, it tells the hypervisor it's addresses, and then that box
propagates out the route change to elsewhere.

>
> This can work for individual hobbiests, but not when you need to support
> random devices (how would you configure an iPhone to support this?)

Carefully. :)

I do note that this stuff does (or at least did) work on some of the open
source variants of android. I would rather like it if android added ipv6
tethering soon, and made it possible to mesh together multiple phones.

>
>
> Letting the layer 2 equipment deal with the traffic within the building and
> invoking layer 3 to go outside the building (or to a different security
> domain) makes a lot of sense. Even if that means that layer 2 within a
> building looks very similar to what layer 3 used to look like around a city.

Be careful what you wish for.

>
>
> back to the topic of wifi, I'm not aware of any APs that participate in the
> switch protocols at this level. I also don't know of any reasonably priced
> switches that can do anything smarter than plain spanning tree when
> connected through multiple paths (I'd love to learn otherwise)
>
> David Lang



-- 
Dave Täht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks