touch-packages team mailing list archive

[Vasily Makarov <1497936@xxxxxxxxxxxxxxxxxx>]

** Description changed:

  My first bug report on launchpad, sorry if I messed anything up
  
  ifupdown package contains /etc/init/netwok-interface.conf script, which uses ifconfig to setup loopback interface.
  ifupdown package depends on iproute2 (ip tool), not on net-tools (ifconfig).
  
- On machines w/o ifconfig installed this may lead to offling loopback
+ On machines w/o ifconfig installed this may lead to offline loopback
  interface after boot. I actually see this happening on one of my
  headless machines.
  
  My suggestion is:
  @@ -19,7 +19,8 @@
-  pre-start script
-      if [ "$INTERFACE" = lo ]; then
-  	# bring this up even if /etc/network/interfaces is broken
+  pre-start script
+      if [ "$INTERFACE" = lo ]; then
+   # bring this up even if /etc/network/interfaces is broken
  -	ifconfig lo 127.0.0.1 up || true
  +	ip link set lo up && ip addr add 127.0.0.1 dev lo || true
-  	initctl emit -n net-device-up \
-  	    IFACE=lo LOGICAL=lo ADDRFAM=inet METHOD=loopback || true
-      fi
+   initctl emit -n net-device-up \
+       IFACE=lo LOGICAL=lo ADDRFAM=inet METHOD=loopback || true
+      fi
  
  By the way, is it OK to hardcode loopback IP address?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ifupdown 0.7.47.2ubuntu4.1
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 21 12:45:16 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-26 (237 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  My first bug report on launchpad, sorry if I messed anything up
  
- ifupdown package contains /etc/init/netwok-interface.conf script, which uses ifconfig to setup loopback interface.
+ ifupdown package contains /etc/init/network-interface.conf script, which uses ifconfig to setup loopback interface.
  ifupdown package depends on iproute2 (ip tool), not on net-tools (ifconfig).
  
  On machines w/o ifconfig installed this may lead to offline loopback
  interface after boot. I actually see this happening on one of my
  headless machines.
  
  My suggestion is:
  @@ -19,7 +19,8 @@
   pre-start script
       if [ "$INTERFACE" = lo ]; then
    # bring this up even if /etc/network/interfaces is broken
  -	ifconfig lo 127.0.0.1 up || true
  +	ip link set lo up && ip addr add 127.0.0.1 dev lo || true
    initctl emit -n net-device-up \
        IFACE=lo LOGICAL=lo ADDRFAM=inet METHOD=loopback || true
       fi
  
  By the way, is it OK to hardcode loopback IP address?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ifupdown 0.7.47.2ubuntu4.1
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 21 12:45:16 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-26 (237 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
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/1497936

Title:
  Ifupdown package depends on iproute2 but uses ifconfig

Status in ifupdown package in Ubuntu:
  New

Bug description:
  My first bug report on launchpad, sorry if I messed anything up

  ifupdown package contains /etc/init/network-interface.conf script, which uses ifconfig to setup loopback interface.
  ifupdown package depends on iproute2 (ip tool), not on net-tools (ifconfig).

  On machines w/o ifconfig installed this may lead to offline loopback
  interface after boot. I actually see this happening on one of my
  headless machines.

  My suggestion is:
  @@ -19,7 +19,8 @@
   pre-start script
       if [ "$INTERFACE" = lo ]; then
    # bring this up even if /etc/network/interfaces is broken
  -	ifconfig lo 127.0.0.1 up || true
  +	ip link set lo up && ip addr add 127.0.0.1 dev lo || true
    initctl emit -n net-device-up \
        IFACE=lo LOGICAL=lo ADDRFAM=inet METHOD=loopback || true
       fi

  By the way, is it OK to hardcode loopback IP address?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ifupdown 0.7.47.2ubuntu4.1
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 21 12:45:16 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-26 (237 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1497936/+subscriptions