[Battlemesh] WBMv7 test data processing (was: battlemesh v6 test data postprocessing)
neumann at cgws.de
Wed May 21 09:50:48 CEST 2014
On 05/20/2014 07:54 PM, Henning Rogge wrote:
> On Tue, May 20, 2014 at 7:33 PM, Juliusz Chroboczek <jch at pps.jussieu.fr> wrote:
>>> "Operation not permitted" is what you get if you trigger a REJECT rule
>>> in the local firewall.
>> Just to clarify -- this is probably an honest mistake. If Babel
>> failed to install a host route, the kernel could have attempted to
>> follow a default route installed by some other protocol, which would
>> have been shot down by the firewall.
>> Unfortunately, if the first SYN triggers a REJECT, then connect will
>> give up immediately -- so we never get a second chance to connect.
>> I'd really need to see the firewall setup to be sure.
> I don't think we had any firewall... but there was a VLAN for each of
> the protocols with its own ULA prefix. I am sure the ping for babel
> was unable to follow any routes of the other protocols.
> Also, we had no default routes because no protocol announced one.
> I think this was the script used for testing:
>From what I've seen babeld only setup routes to some of the nodes.
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
And it shows no default route (at least not in this table).
> Battlemesh mailing list
> Battlemesh at ml.ninux.org
More information about the Battlemesh