I forgot, here's my whole babeld.conf on roadkiller:
redistribute metric 128
in ip 0.0.0.0/0 le 0 deny
in ip 0.0.0.0/32 le 0 deny
The other nodes have just the first line:
redistribute metric 128
... but I do not want to assume I control the other nodes.
A.
--
The problem is not a lack of
in ip 0.0.0.0/0 le 0 deny
I've just checked again, and it works just fine -- it rejects the
default route.
Are you sure that the babeld.conf file is being read (it's in /etc/)?
And that the spurious route is not being installed by DHCP or something
else?
-- Juliusz
On 2012-08-02, Juliusz Chroboczek wrote:
in ip 0.0.0.0/0 le 0 deny
I've just checked again, and it works just fine -- it rejects the
default route.
Are you sure that the babeld.conf file is being read (it's in /etc/)?
I am not sure. It is in /etc.
And that the spurious route is not being
I noticed that the default route problem started to happen when I
reverted the RTF_PROTO2 patch. Running without the patch: no such
problem. Of course, reverting the patch brings me back to the point
where the FreeBSD node announces the mesh's routes as itself's again and
basically breaks the
4 matches
Mail list logo