No subject

Tue May 20 19:58:52 CEST 2014

And the effect was that when launching a ping6 to an unknown destination
you observed this error.

You can check from the "ip -6 route" dump that was also logged at the
beginning and end of each wbm-test script execution, eg here:

babeld was in charge of the fdba:14::/32 routes for which you typically
find less entries in the main routing table than for the other protocols.

the mentioned dump also shows one:
unreachable fd14:42f:eaf0::/48 dev lo  proto static  metric 2147483647
error -128

And it shows no default route (at least not in this table).


> Henning
> _______________________________________________
> Battlemesh mailing list
> Battlemesh at

More information about the Battlemesh mailing list