babeld/routing: losing default route in table 42 - Githubissues

freifunkh / ansible-configs

Here we store all of our actual ansible hosts in freifunk hanover

2 stars 1 forks source link

babeld/routing: losing default route in table 42 #38

Closed 1977er closed 6 years ago

1977er commented 6 years ago

Irgendwelche unbekannten Ereignisse lassen den Kernel die default Route in der freifunk Tabelle (42) vergessen. Ein Abstubsen des Babel Dienstes löst das Problem.

[ ] Herausfinden, was das verursacht

Aktueller Workaround auf sn02: babeld alle 5min neustarten.

lemoer commented 6 years ago

What does the status socket of babeld say to this issue? (echo dump | nc ::1 33123)
Is only the default route affected?

1977er commented 6 years ago

Turns out: ferm was not enabled on boot.
Turns out: babeld is deaf when the firewall is up, altough -A INPUT -s fe80::/64 -p udp -m udp --dport 6696 -j ACCEPT is set.

And now?

May MARKing interfere?

lemoer commented 6 years ago

-A INPUT -s fe80::/64 -p udp -m udp --dport 6696 -j ACCEPT seems to work on sn08 (no ferm).

What happens if babeld gets restarted?

lemoer commented 6 years ago

You missed to add rules to allow the gre traffic from aegiedientor. Not babeld related.

1977er commented 6 years ago

Marvelous. How did you spot that?

lemoer commented 6 years ago

Ping over the gre interface also did not work.

1977er commented 6 years ago

It still does not.

lemoer commented 6 years ago

*is not working until gre packets are allowed from aegidientor