On Tue, Aug 25, 2015 at 7:38 PM, Alia Atlas <[email protected]> wrote: >> There is also the point that multipath choices tend not to be >> isometric... just because the two paths from your local point of view >> seem to be good they are not necessarily good from the point of view >> of the next hop. > > > In a way that can't be captured by link metrics? I haven't really looked at > the unique characteristics for wireless. I'm happy to do a bit of > self-education.
Imagine a network with three wireless routers (A,B,C)... A is the uplink, you are C, but both A and C can only see B. All routers are dualband routers (all have both a 2.4 GHz and a 5 GHz radio). >From your (C) point of view the multipath-solution is "easy", one path use 2.4 GHz (C to B to A), the other one uses 5 GHz (C to B to A). But when your IP packet arrives at B, B doesn't know it is part of a multipath stream... so forcing both streams to stay on their frequency is not trivial if you don't want to do source routing. There is a solution for this easy example (as Juliusz will certainly be able to tell you), but there are more complicated setups which are even more difficult. Multipath on wireless links is easy to mess up, so I would suggest NOT including it into the feature-set required by Homenet. Henning Rogge _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
