>>>> L3 - route injection (got a routing protocol there already, use it) >>> >>> This sounds like it needs at least a coordination protocol between the APs? >> >> NO, just between the first-hop (homenet) routers. Should work with unchanged >> of the shelf crap-APs as long as they're attached to a homenet router.
> Could someone please explain to me how this is supposed to work? The client is running a stub implementation of the routing protocol. It's performing the normal routing protocol activities, such as sending periodic hellos and announcing routes or flooding LSPs. At any given time, the client has a default route through some neighbouring Homenet router. It sends its outgoing traffic through that router, which presumably knows how to deal with it. At any given time, the client is announcing a /128 route to itself to all neighbouring Homenet routers. This route gets propagated through the Homenet by the routing protocol, so that all Homenet routers know how to route to the client. This assumes that the Homenet is not doing uRPF internally. This approach has been extensively tested with Babel, with no link-layer support, and the outage after roaming has been measured as 2 to 4 Hello intervals, which is the time needed by the link quality estimator to yield meaningful data. (Which, just between the two of us, is pretty annoying, even if you're using Mosh.) -- Juliusz _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
