[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
I created a PPA with fixed vlan packages: https://launchpad.net/~ddstreet/+archive/ubuntu/lp1573272 ** Tags removed: bot-comment patch xenial ** Tags added: sts-sponsor ** Tags added: patch ** Also affects: vlan (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859127 Importance: Unknown Status: Unknown ** No longer affects: ifupdown (Ubuntu) ** Changed in: vlan (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in vlan package in Ubuntu: In Progress Status in vlan package in Debian: Unknown Bug description: [Impact] Systems using vlans, especially those using vlans on top of bond interfaces, in addition to default or other routes on the vlans, may find their vlan routes are not present at boot. The attached debdiff patches fix the vlan package's /etc/network/if- pre-up.d/vlan script. Currently, the script will bring up a vlan's raw device if needed; but the problem is if the vlan's ifup processing happens before the raw device's ifup processing, the raw device may be taken down and back up (especially for bonds), and when the raw device is taken down, the vlan is as well, and thus loses all its routing configuration. Instead of only bringing the raw device up using ip link up, the patch changes the vlan script to do a full ifup on the raw device, so it will remain up after the vlan is configured. [Test Case] Set up a system using two interfaces configured into a bond interface, with a vlan on top of that bond. Add a default route and/or specific routes to the vlan interface. Then edit the system as described in comment 8, and reboot. The vlan's routes will not be present in the system. [Regression Potential] Any modifications to ifupdown or the scripts it uses may cause wider problems with network configuration. Specifically, this could cause problems when using vlan interfaces, as it forces every vlan's raw device interface to be fully ifup'ed before the vlan interface can finish its ifup. [Other Info] original description below: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
** Description changed: - Expectation: After reboot, route for default gateway specified on - bonded interface is installed according to "gateway x.x.x.x" (where - x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or - files sourced per /etc/network/interfaces + [Impact] + + Systems using vlans, especially those using vlans on top of bond + interfaces, in addition to default or other routes on the vlans, may + find their vlan routes are not present at boot. + + The attached debdiff patches fix the vlan package's /etc/network/if-pre- + up.d/vlan script. Currently, the script will bring up a vlan's raw + device if needed; but the problem is if the vlan's ifup processing + happens before the raw device's ifup processing, the raw device may be + taken down and back up (especially for bonds), and when the raw device + is taken down, the vlan is as well, and thus loses all its routing + configuration. Instead of only bringing the raw device up using ip link + up, the patch changes the vlan script to do a full ifup on the raw + device, so it will remain up after the vlan is configured. + + [Test Case] + + Set up a system using two interfaces configured into a bond interface, + with a vlan on top of that bond. Add a default route and/or specific + routes to the vlan interface. Then edit the system as described in + comment 8, and reboot. The vlan's routes will not be present in the + system. + + [Regression Potential] + + Any modifications to ifupdown or the scripts it uses may cause wider + problems with network configuration. Specifically, this could cause + problems when using vlan interfaces, as it forces every vlan's raw + device interface to be fully ifup'ed before the vlan interface can + finish its ifup. + + [Other Info] + + original description below: + + + Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: - Installed: 2.7ubuntu1 - Candidate: 2.7ubuntu1 - Version table: - *** 2.7ubuntu1 100 - 100 /var/lib/dpkg/status + Installed: 2.7ubuntu1 + Candidate: 2.7ubuntu1 + Version table: + *** 2.7ubuntu1 100 + 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: - Installed: 0.8.10ubuntu1 - Candidate: 0.8.10ubuntu1 - Version table: - *** 0.8.10ubuntu1 100 - 100 /var/lib/dpkg/status - - - + Installed: 0.8.10ubuntu1 + Candidate: 0.8.10ubuntu1 + Version table: + *** 0.8.10ubuntu1 100 + 100 /var/lib/dpkg/status - - - - /etc/network/interfaces + /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static - address 10.96.96.2 - netmask 255.255.255.0 - network 10.96.96.0 - broadcast 10.96.96.255 - # dns-* options are implemented by the resolvconf package, if installed - dns-search *snip* - bond-mode balance-alb - bond-slaves none - bond-miimon 100 - auto bond0.3000 + address 10.96.96.2 + netmask 255.255.255.0 + network 10.96.96.0 + broadcast 10.96.96.255 + # dns-* options are implemented by the resolvconf package, if installed + dns-search *snip* + bond-mode balance-alb + bond-slaves none + bond-miimon 100 + auto bond0.3000 iface bond0.3000 inet static - address 172.21.33.29 - netmask 255.255.255.0 - network 172.21.33.0 - broadcast 172.21.33.255 - gateway 172.21.33.1 - dns-search *snip* - vlan-raw-device bond0 - dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - + address 172.21.33.29 + netmask 255.255.255.0 + network 172.21.33.0 +
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
The attachment "lp1573272-trusty.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in vlan package in Ubuntu: In Progress Status in vlan package in Debian: Unknown Bug description: [Impact] Systems using vlans, especially those using vlans on top of bond interfaces, in addition to default or other routes on the vlans, may find their vlan routes are not present at boot. The attached debdiff patches fix the vlan package's /etc/network/if- pre-up.d/vlan script. Currently, the script will bring up a vlan's raw device if needed; but the problem is if the vlan's ifup processing happens before the raw device's ifup processing, the raw device may be taken down and back up (especially for bonds), and when the raw device is taken down, the vlan is as well, and thus loses all its routing configuration. Instead of only bringing the raw device up using ip link up, the patch changes the vlan script to do a full ifup on the raw device, so it will remain up after the vlan is configured. [Test Case] Set up a system using two interfaces configured into a bond interface, with a vlan on top of that bond. Add a default route and/or specific routes to the vlan interface. Then edit the system as described in comment 8, and reboot. The vlan's routes will not be present in the system. [Regression Potential] Any modifications to ifupdown or the scripts it uses may cause wider problems with network configuration. Specifically, this could cause problems when using vlan interfaces, as it forces every vlan's raw device interface to be fully ifup'ed before the vlan interface can finish its ifup. [Other Info] original description below: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859127 ** Bug watch added: Debian Bug tracker #859127 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859127 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Invalid Status in vlan package in Ubuntu: In Progress Bug description: [Impact] Systems using vlans, especially those using vlans on top of bond interfaces, in addition to default or other routes on the vlans, may find their vlan routes are not present at boot. The attached debdiff patches fix the vlan package's /etc/network/if- pre-up.d/vlan script. Currently, the script will bring up a vlan's raw device if needed; but the problem is if the vlan's ifup processing happens before the raw device's ifup processing, the raw device may be taken down and back up (especially for bonds), and when the raw device is taken down, the vlan is as well, and thus loses all its routing configuration. Instead of only bringing the raw device up using ip link up, the patch changes the vlan script to do a full ifup on the raw device, so it will remain up after the vlan is configured. [Test Case] Set up a system using two interfaces configured into a bond interface, with a vlan on top of that bond. Add a default route and/or specific routes to the vlan interface. Then edit the system as described in comment 8, and reboot. The vlan's routes will not be present in the system. [Regression Potential] Any modifications to ifupdown or the scripts it uses may cause wider problems with network configuration. Specifically, this could cause problems when using vlan interfaces, as it forces every vlan's raw device interface to be fully ifup'ed before the vlan interface can finish its ifup. [Other Info] original description below: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
** Patch added: "lp1573272-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850618/+files/lp1573272-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Invalid Status in vlan package in Ubuntu: In Progress Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
** Patch added: "lp1573272-yakkety.debdiff" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850619/+files/lp1573272-yakkety.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Invalid Status in vlan package in Ubuntu: In Progress Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
** Patch added: "lp1573272-zesty.debdiff" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850620/+files/lp1573272-zesty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Invalid Status in vlan package in Ubuntu: In Progress Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
** Patch added: "lp1573272-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850617/+files/lp1573272-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Invalid Status in vlan package in Ubuntu: In Progress Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
Marking this as 'invalid' for ifupdown, as the problem is in the vlan package's script. ** Also affects: vlan (Ubuntu) Importance: Undecided Status: New ** Changed in: vlan (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: vlan (Ubuntu) Importance: Undecided => High ** Changed in: vlan (Ubuntu) Status: New => In Progress ** Changed in: ifupdown (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Invalid Status in vlan package in Ubuntu: In Progress Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
Thanks everyone, I'll work on getting the patch upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
The patch fixes the issue for me as well. Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
The patch fixes the issue for me as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
confirm, the patch is working for me as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
Seems OK for me -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
This patch to the vlan pre-up script should fix this bug, can someone who can easily reproduce it please update your system and retest to verify it fixes the bug? You can just hand-edit your vlan script as shown, to replace the call to ip to instead do a full ifup on the raw device. --- /etc/network/if-pre-up.d/vlan.orig 2017-03-16 16:50:37.97200 + +++ /etc/network/if-pre-up.d/vlan 2017-03-16 16:50:45.05600 + @@ -60,7 +60,7 @@ exit 1 fi if [ ! -e "/sys/class/net/$IFACE" ]; then -ip link set up dev $IF_VLAN_RAW_DEVICE +ifup $IF_VLAN_RAW_DEVICE vconfig add $IF_VLAN_RAW_DEVICE $VLANID fi fi ** Changed in: ifupdown (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
Ok I've reproduced this by introducing a delay by changing /lib/systemd/system/ifup@.service -ExecStart=/bin/sh -ec 'ifup --allow=hotplug %I; ifup --allow=auto %I; \ +ExecStart=/bin/sh -ec '/usr/bin/test %I == bond0 && echo found bond0 && sleep 3 ; ifup --allow=hotplug %I; ifup --allow=auto %I; \ that reproduces this by allowing bond0.3000 to complete ifup before bond0 is processed, and when bond0 is ifup'ed it clears bond0.3000's gateway due to bond0 going down and back up. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
I set up a default xenial vm with 2 extra interfaces, and configured them with exactly the config you listed in the description, and left it in a reboot loop checking for the default gateway each time, and it hasn't seen the problem at all, after hours of rebooting. Is there a something else specific needed to be able to reproduce this problem? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
Any idea if an upstream fix will be applied on Xenial ? It's a very annoying issue :/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
As a workaround, you can do the following (using the original report's config as an example): # systemctl edit ifup@bond0.3000 Add the following and save the file: [Unit] After=ifup@bond0.service Then, let's add Type=oneshot to the ifup@ template so that the above After= actually has some effect: # systemctl edit ifup@ Add the following and save the file: [Service] Type=oneshot Then reboot. The problem seems to be a race condition introduced with systemd integration. For me, the missing default route triggered around 80% of the time, but not always. On Ubuntu 16, systemd executes the ifup@ template units in parallel in a way that is not adequately controlled. For instance, ifup@bond0.3000 and ifup@bond0 will execute in parallel. The ifup for bond0 will involve "ip link ... down", then "up" from ifenslave hooks. I believe that if the link down comes after default route from bond0.3000, the default route will be deleted. My journalctl observations support this. Debugging tip: use systemctl edit ifup@, and add --verbose to the ifup invocations (note, there are 2 of them!). Adding the verbose option to /etc/default/networking does not work, except for lo interface. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
Able to replicate this very reliably with any bonded interface on Xenial Default Gateway (configured in e/n/i) is never set on boot, but always set with any interface raise thereafter. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
i think this affects more than just "bond" interfaces, and more than just the gateway setting from /etc/network/interfaces. i think dns- settings are also affected as experienced on 4 of my systems. note bug #1628552 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
** Changed in: ifupdown (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ifupdown (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
** Tags added: xenial ** Package changed: ubuntu => ifupdown (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: New Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp