batman-adv: B.A.T.M.A.N V - make sure iface is reactivated upon NETDEV_UP event
authorAntonio Quartulli <a@unstable.cc>
Thu, 14 Apr 2016 01:37:05 +0000 (09:37 +0800)
committerAntonio Quartulli <a@unstable.cc>
Fri, 29 Apr 2016 11:46:11 +0000 (19:46 +0800)
commitb6cf5d499fddbfcffe751e81fb9f1a07d6348026
tree5fbbf99c9944eb5bc04eec29c7426ab3d0be719b
parent2871734e85e920503d49b3a8bc0afbe0773b6036
batman-adv: B.A.T.M.A.N V - make sure iface is reactivated upon NETDEV_UP event

At the moment there is no explicit reactivation of an hard-interface
upon NETDEV_UP event. In case of B.A.T.M.A.N. IV the interface is
reactivated as soon as the next OGM is scheduled for sending, but this
mechanism does not work with B.A.T.M.A.N. V. The latter does not rely
on the same scheduling mechanism as its predecessor and for this reason
the hard-interface remains deactivated forever after being brought down
once.

This patch fixes the reactivation mechanism by adding a new routing API
which explicitly allows each algorithm to perform any needed operation
upon interface re-activation.

Such API is optional and is implemented by B.A.T.M.A.N. V only and it
just takes care of setting the iface status to ACTIVE

Signed-off-by: Antonio Quartulli <a@unstable.cc>
Signed-off-by: Marek Lindner <mareklindner@neomailbox.ch>
net/batman-adv/bat_v.c
net/batman-adv/hard-interface.c
net/batman-adv/types.h
This page took 0.02537 seconds and 5 git commands to generate.