On Fri, Nov 9, 2012 at 4:05 PM, Teco Boot <[email protected]> wrote: > Yes, it is More Adhoc NETwork and called Homenet. You could be surprised how > well MANET protocols work in homenets. This is not my point. > > Wireless links need per neighbor link costs, a requirement for the Homenet > routing protocol: > The inclusion of the PHY layer > characteristics including bandwidth, loss, and latency in path > computation should be considered for optimising communication in the > homenet. > Can be done with OSPFv3, so use it. Please suggest how to deal with it.
Can be done with olsr, babel, 802.11s, batman, and BMX. There is a large amount of operational data in the field regarding doing routing well on wireless networks, and a regular conference dedicated to exploring how well they actually work in the real world. http://guifi.net/en/node/17714/view/map please pack up your favorite ospfv3 and manet extensions and wifi hardware and go to one. http://battlemesh.org/ None of the metrics work particularly well, and are functioning badly in our increasingly bufferbloated universe. > > Teco > > Op 9 nov. 2012, om 15:10 heeft Acee Lindem het volgende geschreven: > >> Home Wireless Routing != MANET >> >> Acee >> >> On Nov 9, 2012, at 8:49 AM, Teco Boot wrote: >> >>> So this disqualifies OSPFv3 with DR? Support for wireless is >>> a main reason to route in the homenet. This brings us to P2MP >>> or in the MANET arena. >>> >>> There is a lot of code out there gathering link metrics for >>> dynamic links. MANET wg is working on a std track protocol for >>> it, called DLEP. This is for transfer of data between radio >>> and router devices. >>> >>> MANET protocols support link metrics quite well now. OLSRv2 is >>> near to std track RFC. >>> >>> Teco >>> >>> Op 8 nov. 2012, om 20:26 heeft Acee Lindem het volgende geschreven: >>> >>>> You'd have to do this through manual configuration. >>>> Thanks, >>>> Acee >>>> On Nov 8, 2012, at 2:08 PM, Teco Boot wrote: >>>> >>>>> >>>>> Op 8 nov. 2012, om 14:03 heeft Acee Lindem het volgende geschreven: >>>>>> >>>>>> I'd expect homenet ethernet and WiFi interfaces to default to the >>>>>> broadcast type. >>>>> >>>>> Then, we cannot have costs per neighbor, correct? >>>>> By experience I've became aware this is a bad idea on wireless networks, >>>>> like WiFi. >>>>> What options do we have to fix this? >>>>> >>>>> Teco >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> homenet mailing list >>> [email protected] >>> https://www.ietf.org/mailman/listinfo/homenet >> > > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet -- Dave Täht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
