Proxmox/pve-common
5
0
Fork 0
mirror of git://git.proxmox.com/git/pve-common.git synced 2025-01-09 05:17:35 +03:00
Code Releases Activity
903d285751
pve-common/test/etc_network_interfaces/t.unknown_order.pl

98 lines
1.5 KiB
Perl
Raw Normal View History

don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
my $base = load('loopback');
sub wanted($) {
my ($ip) = @_;
return $base . <<"IFACES";
Inotify: write_network_interfaces : always autostart bond slaves interfaces Currently, bond slaves are mostly working without autostart, because bond slaves scripts from ifupdown1 && also ifupdown2 have some kind of hacks to start the slaves. But if users want to do some tuning on the ifaces, they are not applied. Also, with ifupdown2 + ovs, this kind of hack is not implemented (yet), so the slaves of the bond are still down. Debian/Ubuntu official docs always set "auto ethX" for bond slaves, it's really more clean like this. Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-06-07 14:39:47 +03:00
auto eth0
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
iface eth0 inet manual
Inotify: write_network_interfaces : always autostart bond slaves interfaces Currently, bond slaves are mostly working without autostart, because bond slaves scripts from ifupdown1 && also ifupdown2 have some kind of hacks to start the slaves. But if users want to do some tuning on the ifaces, they are not applied. Also, with ifupdown2 + ovs, this kind of hack is not implemented (yet), so the slaves of the bond are still down. Debian/Ubuntu official docs always set "auto ethX" for bond slaves, it's really more clean like this. Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-06-07 14:39:47 +03:00
auto eth1
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
iface eth1 inet manual
Inotify: write_network_interfaces : always autostart bond slaves interfaces Currently, bond slaves are mostly working without autostart, because bond slaves scripts from ifupdown1 && also ifupdown2 have some kind of hacks to start the slaves. But if users want to do some tuning on the ifaces, they are not applied. Also, with ifupdown2 + ovs, this kind of hack is not implemented (yet), so the slaves of the bond are still down. Debian/Ubuntu official docs always set "auto ethX" for bond slaves, it's really more clean like this. Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-06-07 14:39:47 +03:00
auto eth2
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
iface eth2 inet manual
Inotify: write_network_interfaces : always autostart bond slaves interfaces Currently, bond slaves are mostly working without autostart, because bond slaves scripts from ifupdown1 && also ifupdown2 have some kind of hacks to start the slaves. But if users want to do some tuning on the ifaces, they are not applied. Also, with ifupdown2 + ovs, this kind of hack is not implemented (yet), so the slaves of the bond are still down. Debian/Ubuntu official docs always set "auto ethX" for bond slaves, it's really more clean like this. Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-06-07 14:39:47 +03:00
auto eth3
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
iface eth3 inet manual
Inotify: write_network_interfaces : always autostart bond slaves interfaces Currently, bond slaves are mostly working without autostart, because bond slaves scripts from ifupdown1 && also ifupdown2 have some kind of hacks to start the slaves. But if users want to do some tuning on the ifaces, they are not applied. Also, with ifupdown2 + ovs, this kind of hack is not implemented (yet), so the slaves of the bond are still down. Debian/Ubuntu official docs always set "auto ethX" for bond slaves, it's really more clean like this. Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-06-07 14:39:47 +03:00
auto eth4
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
iface eth4 inet manual
Inotify: write_network_interfaces : always autostart bond slaves interfaces Currently, bond slaves are mostly working without autostart, because bond slaves scripts from ifupdown1 && also ifupdown2 have some kind of hacks to start the slaves. But if users want to do some tuning on the ifaces, they are not applied. Also, with ifupdown2 + ovs, this kind of hack is not implemented (yet), so the slaves of the bond are still down. Debian/Ubuntu official docs always set "auto ethX" for bond slaves, it's really more clean like this. Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-06-07 14:39:47 +03:00
auto eth5
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
iface eth5 inet manual
iface eth6 inet manual
iface eth7 inet manual
iface bond0 inet manual
Inotify : write network config : use modern syntax for options -replace options with '_' with '-' -use 'bond-slaves' instead 'slaves'
2018-06-20 08:36:55 +03:00
bond-slaves eth0 eth1
bond-miimon 100
bond-mode balance-alb
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
auto bond1
iface bond1 inet static
remove extra space after address && gateway options only 1 space like all others options Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-02-20 14:55:19 +03:00
address 10.10.10.$ip/24
Inotify : write network config : use modern syntax for options -replace options with '_' with '-' -use 'bond-slaves' instead 'slaves'
2018-06-20 08:36:55 +03:00
bond-slaves eth2 eth3
bond-miimon 100
bond-mode balance-alb
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
# pre-up ifconfig bond1 mtu 9000
auto bond2
iface bond2 inet manual
Inotify : write network config : use modern syntax for options -replace options with '_' with '-' -use 'bond-slaves' instead 'slaves'
2018-06-20 08:36:55 +03:00
bond-slaves eth4 eth5
bond-miimon 100
bond-mode balance-alb
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
# Private networking
tests: unknown interfaces order: rename vlan interfaces to unknown vlan(X) interfaces are not unknown anymore use generic name instead Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-01-25 12:27:04 +03:00
iface unknown3 inet static
remove extra space after address && gateway options only 1 space like all others options Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-02-20 14:55:19 +03:00
address 0.0.0.0
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
tests: unknown interfaces order: rename vlan interfaces to unknown vlan(X) interfaces are not unknown anymore use generic name instead Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-01-25 12:27:04 +03:00
iface unknown4 inet static
remove extra space after address && gateway options only 1 space like all others options Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-02-20 14:55:19 +03:00
address 0.0.0.0
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
tests: unknown interfaces order: rename vlan interfaces to unknown vlan(X) interfaces are not unknown anymore use generic name instead Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-01-25 12:27:04 +03:00
iface unknown5 inet static
remove extra space after address && gateway options only 1 space like all others options Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-02-20 14:55:19 +03:00
address 0.0.0.0
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
auto vmbr0
iface vmbr0 inet static
remove extra space after address && gateway options only 1 space like all others options Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-02-20 14:55:19 +03:00
address 192.168.100.13/24
gateway 192.168.100.1
Inotify : write network config : use modern syntax for options -replace options with '_' with '-' -use 'bond-slaves' instead 'slaves'
2018-06-20 08:36:55 +03:00
bridge-ports bond0
bridge-stp off
bridge-fd 0
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
tests: unknown interfaces order: rename vlan interfaces to unknown vlan(X) interfaces are not unknown anymore use generic name instead Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-01-25 12:27:04 +03:00
auto unknown6
iface unknown6 inet static
remove extra space after address && gateway options only 1 space like all others options Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-02-20 14:55:19 +03:00
address 10.10.11.13/24
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
pre-up ifconfig bond0 up
auto vmbr3
iface vmbr3 inet manual
tests: unknown interfaces order: rename vlan interfaces to unknown vlan(X) interfaces are not unknown anymore use generic name instead Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-01-25 12:27:04 +03:00
bridge-ports unknown3
Inotify : write network config : use modern syntax for options -replace options with '_' with '-' -use 'bond-slaves' instead 'slaves'
2018-06-20 08:36:55 +03:00
bridge-stp off
bridge-fd 0
tests: unknown interfaces order: rename vlan interfaces to unknown vlan(X) interfaces are not unknown anymore use generic name instead Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-01-25 12:27:04 +03:00
pre-up ifup unknown3
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
auto vmbr4
iface vmbr4 inet manual
tests: unknown interfaces order: rename vlan interfaces to unknown vlan(X) interfaces are not unknown anymore use generic name instead Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-01-25 12:27:04 +03:00
bridge-ports unknown4
Inotify : write network config : use modern syntax for options -replace options with '_' with '-' -use 'bond-slaves' instead 'slaves'
2018-06-20 08:36:55 +03:00
bridge-stp off
bridge-fd 0
tests: unknown interfaces order: rename vlan interfaces to unknown vlan(X) interfaces are not unknown anymore use generic name instead Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-01-25 12:27:04 +03:00
pre-up ifup unknown4
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
auto vmbr5
iface vmbr5 inet manual
tests: unknown interfaces order: rename vlan interfaces to unknown vlan(X) interfaces are not unknown anymore use generic name instead Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-01-25 12:27:04 +03:00
bridge-ports unknown5
Inotify : write network config : use modern syntax for options -replace options with '_' with '-' -use 'bond-slaves' instead 'slaves'
2018-06-20 08:36:55 +03:00
bridge-stp off
bridge-fd 0
tests: unknown interfaces order: rename vlan interfaces to unknown vlan(X) interfaces are not unknown anymore use generic name instead Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-01-25 12:27:04 +03:00
pre-up ifup unknown5
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
IFACES
}
r(wanted(13));
INotify: use cidr for address on config change netmask/broadcast options are deprecated since buster https://manpages.debian.org/buster/ifupdown/interfaces.5.en.html This still read both "old address/netmask" or "address cidr" format, but always convert it to cidr address format Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
2020-02-20 14:55:18 +03:00
update_iface('bond1', [ { family => 'inet', address => '10.10.10.11/24' } ]);
don't reorder unknown interface types Giving unknown interfaces an order-id of 0 caused them to always be on top of the interfaces file. This is often undesired. Instead we now only take type-ordering into account when both interfaces which are being compared have a known type, and otherwise only use the priority attribute. This should result in a more stable modification of interfaces. Fixes #747
2015-10-07 11:42:17 +03:00
expect wanted(11);
1;
Copy Permalink