[Babel-users] able to ping to neighbor but no entry in routing table

[Harshal Vora]

Hi Gabriel,

If I understood correctly, we should use addresses with netmask 
255.255.255.255
But with this netmask, each device will think that it is the only IP in 
the adhoc network and it will not be able to ping or ssh into any other 
device that we expect to take part in the adhoc network (even if they 
have the same SSID). Basically there will be no adhoc network.

How does babeld work in this case?

------------------------------
We use the following commands to start babeld

Command to start babeld on master:
start-stop-daemon --start --pidfile /var/run/babeld.pid --exec 
/usr/local/bin/babeld -- -C 'redistribute metric 128' -C 'redistribute 
proto 3 allow' -d 3 -L /var/log/babeld.log -D -I /var/run/babeld.pid -r 
-g 33123 wlan0

'redistribute proto 3 allow' is used to distribute routes generated for 
the ethernet interface.

Command to start babeld on slaves

start-stop-daemon --start --pidfile /var/run/babeld.pid --exec 
/usr/local/bin/babeld -- -d 3 -L /var/log/babeld.log -D -I 
/var/run/babeld.pid -r -g 33123 wlan0
---------------------------

Does this mean that any device that now wants to be a part of this 
network will have to compulsorily run babeld?
Also since we are redistributing routes only on the master, other slaves 
will get only routes distributed by the master?

For ex.
If we have master A and slave B and C such that B is in proximity of A 
and C is in proximity of B but not A
A --- B --- C
|                |
-------x------


Will C get routes from A ?

Regards,


On 03/22/2014 10:54 PM, Gabriel Kerneis wrote:
> On Sat, Mar 22, 2014 at 08:18:14PM +0530, Harshal Vora wrote:
>> We checked that we are able to ping from the master to the slave
>> (because of the proximity and because they are on the same adhoc
>> network)
>> 10.0.0.0/24 metric 128 (exported)
>> 192.168.1.0/24 metric 128 (exported)
> I have no idea where your problem comes from, but it is common in mesh
> networks to set your addresses with a /32 prefix (or /128 for IPv6). The
> reason is precisely to avoid those hard-to-debug behaviours where you do
> not know whether you can reach another host thanks to a correctly
> installed route, or thanks to the default route for your prefix and
> random proximity.
>
> Best,