You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: