When stopping wpa_supplicant, the code is supposed to check if a file named $PIDFILE exists and kill the process listed inside. Instead it was checking if a directory named $PIDFILE exists and because this was never the case, killing of the wpa_supplicant process would always silently fail.
This would, after a few invocations of the ifup command, leave the system with large number of running wpa_supplicant processes, all trying to take control of the same interface.
This commit adds support for configuring static PTMP overlays with VXLAN by
allowing to specify multiple IPs for »vxlan-peer-ips«. If more than one IP
is given ifupdown-ng will set up additional FDB entries for all peer IPs and
the Linux Kernel will do ingres / head-end replication for BUM traffic.
For a cleaner naming schema and simliar names to commercial vendor CLIs the
options to specify unicast or multicast peers have been renamed and aliases
added for compatibility to previous versions of ifupdown-ng:
* »vxlan-remote-ip« now is named »vxlan-peer-ips«
* »vxlan-remote-group« now is called »vxlan-peer-group«
Signed-off-by: Maximilian Wilhelm <max@sdn.clinic>
The new "tunnel-local-dev <iface>" option allows to specify an interface
to read the IPv4/IPv6 address from which should be used as "tunnel-local"
address. The address family is determined based on the given "tunnel-mode".
Closes#118
Signed-off-by: Maximilian Wilhelm <max@sdn.clinic>
When having multiple addresses set from the same prefix they might/will(?)
be configured as 'secondary' and implicitly removed when removing the
non-secondary address. This leads ip complaining about not being able
to remove the secondaries as they are already gone. So we ignore errors
while deconfiguring addresses as they liked occur when removing a
vanish address anyway.
Signed-off-by: Maximilian Wilhelm <max@sdn.clinic>
* Add a bond executor
* Add mappings from ifupdown1/2
* Add a detailed man page
* Remove legacy compatiblity glue for setups with 'requires' only
The current implementation has to work around the fact that member interfaces
will be already up then the bond is created. This is simply done by downing
them, adding them to the bundle and upping them again. This can possible be
done in a nicer way after revisiting the ordering of plugin execution (#12).
Closes#91
Signed-off-by: Maximilian Wilhelm <max@sdn.clinic>
Hetzner uses link-local addressing for their default IPv6 route,
accordingly we should specify the device a route is associated with
so that it will use the correct interface.
Thanks to Devin Brown for reporting this issue.
