Of course rp_filter should be reset to its old value, and not to the old
accept_redirects value.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>

When a route is retracted, we want to switch to an alternate route
straight away even if the smoothed metric hasn't converged yet.
Setting the smoothed metric to infinity in this case makes this happen.

Use the hostname instead of "alamakota" when announcing the router
on the local interface.  It would make it possible for visualisation
tools, such as babelweb, to display a meaningful name automatically.

Off-by-one in error checking.  Reported by Gioacchino Mazzurco.

This used to mean "parasitic", but has been removed a long time ago.

We're working with deltas, not with absolute values, so we need to
subtract 1.  Oh, and it's multiplication, not division.

This would cause the smoothed metric to instantaneously jump to
the true metric when route_smoothed_metric was called twice in the
same second.

This caused a minor loss of accuracy.

The netlink API doesn't natively support atomic route changes.  We used
to attempt to install the new route before removing the old route, but that
would fail in mysterious ways on non-multipath kernels, leading to "stuck"
routes.  Avoid the pain, just take the native approach.

This makes Babel work (to the extent possible) over BATMAN interfaces, which
apparently some people are doing.  Thanks to Gioacchino Mazzurco and Sven
Eckelmann.

This caused empty lines to cause parse failures.

Reported by Antoine Beaupré.

This is a systematic way of implementing hyseresis in route
selection, and should solve the issues we're seeing with ETX
jitter and feedback.  The default half-time is 4s, which might
be too small.

This fixes an issue where find_best_route could very occasionally
return a route that was not feasible.

This is needed for the stability aware code.

This is brittle, and prevents me from making route selection smarter.

This is the functionality described in Appendix C of RFC 6126.  Its
main purpose is to avoid keeping a full source table, which makes it
possible to implement a subset of Babel in just a few hundred lines of
code.  However, the code for maintaining the source table is already
there, and a parasitic implementation can be simulated using filtering
-- so it makes little sense to keep the functionality.

Thanks to Denis Ovsienko.