search

tcatm / l3roamd

12 stars 4 forks source link

host-routes for clients are not placed in routing table #27

Closed christf closed 6 years ago

christf commented 7 years ago

having tested l3roamd in versions 14e87caa275be2432ae0fcc7242742946851d327 (april 14th) and beed337 (may 10th) in the same environment the l3roamd built from master does not create host-routes for connected clients rendering the network unusable. So it seems that something in l3roamd broke between those two commits.

christf commented 7 years ago

checking further revisions, commit 9d474a9329e307a5e71fd55d53491d93d34dda13 from may 6th is adding the host-route to the routing table thus working as expected.

since commit 47c45737b8171b1236d7edd7f6896371b1f26204 from may 7th l3roamd is not adding the host-route to the routing table thus introducing the misbehaviour.

Is there anything missing in the environment or is this a regression in l3roamd?

christf commented 7 years ago

today I looked again at this issue. when changing clientmgr_is_ipv4() in clientmanager.c to always return false then the issue is gone. Of course this is a bad hack I would not like to commit but this limits significantly where this issue occurs.

I did not initialize the ipv4-prefix via cli.

With the original l3roamd, as a workaround initializing the ipv4-prefix to some bogus value causes the whole thing to work as well.

christf commented 6 years ago

This is resolved in the New upstream repository on @freifunk-gluon