host-routes for clients are not placed in routing table

[christf]

having tested l3roamd in versions 14e87ca (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]

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

since commit 47c4573 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]

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]

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