l3roamd should make sure it knows about every connected client when it is starting. At the moment, clients that are connected are never found until they time out on the client bridge interface.
ip neigh flush after starting to listen on netlink events mitigates this issue.
christf
commented
7 years ago
l3roamd should make sure it knows about every connected client when it is starting. At the moment, clients that are connected are never found until they time out on the client bridge interface. ip neigh flush after starting to listen on netlink events mitigates this issue.