Testing Done: Tested with vlan device with vlan-raw-device in interfaces
file
also reported here: https://github.com/CumulusNetworks/ifupdown2/issues/10
is_keyword was matching iface attribute 'vlan-raw-device' to the vlan
keyword and dropping it from ifaceobj config.
Signed-off-by: Roopa Prabhu <[email protected]>
Signed-off-by: Julien Fortin <[email protected]>
Testing Done: Tested with a config with vlan-raw-device
'ip -o -d link show' introduced a new attribute between
'vlan and id'. This makes the move to json or netlink
even more necessary.
The fixes were done for the following format:
61: vlan100@swp1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue state UP mode DEFAULT group default \ link/ether
00:e0:ec:27:4e:b7 brd ff:ff:ff:ff:ff:ff promiscuity 0 \ vlan protocol
802.1Q id 100 <REORDER_HDR> addrgenmode eui64
Signed-off-by: Roopa Prabhu <[email protected]>
Signed-off-by: Julien Fortin <[email protected]>
Ticket:
Reviewed By: Julien
Testing Done: Changed the /lib/systemd/system/networking.service then reboot
Following Sam solution posted on the bug report :
Adding "RemainAfterExit=yes" in the [Services] section of /lib/systemd/system/networking.service
E: ifupdown2: systemd-no-service-for-init-rcS-script networking
N:
N: The rcS init.d script has no systemd equivalent.
N:
N: Systemd has a SysV init.d script compatibility mode. It provides access
N: to each SysV init.d script as long as there is no native service file
N: with the same name (e.g. /lib/systemd/system/rsyslog.service corresponds
N: to /etc/init.d/rsyslog).
N:
N: Services in rcS.d are particularly problematic, because they often cause
N: dependency loops, as they are ordered very early in the boot sequence.
N:
N: Refer to https://wiki.debian.org/Teams/pkg-systemd/rcSMigration for
N: details.
N:
N: Severity: serious, Certainty: certain
N:
N: Check: systemd, Type: binary
ifupdown2 can invoke scripts under /etc/network/if-*.d/*
in the required order with the required environment variables.
This patch includes fixes to execute these scripts.
The following attributes in /etc/network/ifupdown2/ifupdown.conf
can influence the execution behaviour of python-addon modules
and /etc/network/if-*.d/*
<ifupdown.conf>
addon_syntax_check=0
addon_scripts_support=1
addon_python_modules_support=1
</ifupdown.conf>
Signed-off-by: Roopa Prabhu <[email protected]>
ifupdown2 code was one level deeper because ifupdown2 initially
had ifupdown2 and ifupdown2-addons as two separate packages.
Since they were combined into one package, it makes sense to
move all combined code under the top level directory
Signed-off-by: Roopa Prabhu <[email protected]>
Julien Fortin
Roopa Prabhu