The batctl binary is currently optional for batman-adv installations. But new configuration settings will only be exposed via generic netlink. The batctl tool will therefore be required to modify them. batctl must therefore no longer depend on batman-adv but batman-adv must depend on batctl. Some already implemented settings are already moved to batctl. Signed-off-by: Sven Eckelmann <sven@narfation.org>
37 lines
657 B
Bash
Executable file
37 lines
657 B
Bash
Executable file
#!/bin/sh
|
|
|
|
. /lib/functions.sh
|
|
. ../netifd-proto.sh
|
|
init_proto "$@"
|
|
|
|
proto_batadv_init_config() {
|
|
proto_config_add_string "mesh"
|
|
proto_config_add_string "routing_algo"
|
|
}
|
|
|
|
proto_batadv_setup() {
|
|
local config="$1"
|
|
local iface="$2"
|
|
|
|
local mesh routing_algo
|
|
json_get_vars mesh routing_algo
|
|
|
|
[ -n "$routing_algo" ] || routing_algo="BATMAN_IV"
|
|
batctl routing_algo "$routing_algo"
|
|
|
|
batctl -m "$mesh" interface add "$iface"
|
|
proto_init_update "$iface" 1
|
|
proto_send_update "$config"
|
|
}
|
|
|
|
proto_batadv_teardown() {
|
|
local config="$1"
|
|
local iface="$2"
|
|
|
|
local mesh
|
|
json_get_vars mesh
|
|
|
|
batctl -m "$mesh" interface del "$iface" || true
|
|
}
|
|
|
|
add_protocol batadv
|