On Tue, Jan 07, 2014 at 12:13:01PM +0530, Harshal Vora wrote: > Hi, > > Please help resolve my confusion. > > From what I understand, > Ad-hoc networks do not provide transitive connectivity > i.e. if A can see B, B can see C and A cannot see C directly, there will be > no automatic route from A to C via B.
That is correct. Ad-hoc is a specific mode of 802.11 (Wi-Fi), which operates at layer 2 and does not deal at all with routing. > But mesh networks provide this transitive routing capability. Sure, and you need some routing protocol to achieve this. There are several out there: Babel, 802.11s, BATMAN-adv, OLSR, ... > What is the role of babel? > Does it help provide transitive routing capabilities to ad-hoc networks or > does it help improve the routing within a mesh network. Babel is a routing protocol. In this use-case, it can use a Ad-hoc wireless network (which is used as the underlying infrastructure) to build a mesh network. The introduction of this wikipedia article may be useful: https://en.wikipedia.org/wiki/List_of_ad_hoc_routing_protocols Also note that Babel works on any kind of network infrastructure, not just 802.11 in ad-hoc mode: 802.11 in infrastructure mode (Access Points), wired, VPN tunnels...
pgpfF13wOb0jq.pgp
Description: PGP signature
_______________________________________________ Babel-users mailing list Babel-users@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
