Hi,
Thanks a lot.
I tested babeld with a few moving wifi hosts all connected to each other
via an ad-hoc network.
Most of the times the routing table seems to be set up correctly along
with default gateway being propagated to all the hosts, even those which
are not in direct connection with the gateway.
But on few occasions, it inserts negative routes with Flag set to !H and
metric set to -1 for hosts which are in direct range of each other.
For ex. consider host A and host B.
Host A will have correct routing table for Host B, but host B will have
routing table entry with flag !H.
Both the hosts are not able to ping each other although there might be
host C which has correct routing table entry for both A and B in both
directions and will be able to communicate with A and B.
These negative routes remain persistent until i restart babeld and
sometimes until i reboot the host.
Shouldn't it be auto-corrected? Is there any way to fix this?
Also, is it possible to redistribute routes added with proto kernel or
boot?
This is required mainly to distribute routes for internet gateway that
are assigned by dhcp on ethernet port.
Generally in a plug and play environment for sensors I don't want to
explicitly specify the gateway of the router and the route for default
access with proto static.
Regards,
On Tuesday 07 January 2014 06:12 PM, Baptiste Jonglez wrote:
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...
_______________________________________________
Babel-users mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
_______________________________________________
Babel-users mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
