[Bug 1312836] [NEW] Doesn't bring up interfaces from /etc/network/interfaces

Iain Lane iain at orangesquash.org.uk
Fri Apr 25 17:07:26 UTC 2014


Public bug reported:

I had no networking when I booted up with systemd just now.

laney at raleigh> cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

laney at raleigh> ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:572 errors:0 dropped:0 overruns:0 frame:0
          TX packets:572 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:46364 (46.3 KB)  TX bytes:46364 (46.3 KB)

laney at raleigh> more /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto br0
iface br0 inet dhcp
    bridge_ports eth0
    bridge_stp off
    bridge_fd 0
    bridge_maxwait 0

laney at raleigh> sudo ifup eth0 br0
ifup: failed to open lockfile /run/network/.ifstate.lock: No such file or directory

Then copying from /etc/init/networking.conf's pre-start

laney at raleigh> sudo mkdir -p /run/network
laney at raleigh> sudo ifup -a
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/br0/30:85:a9:9d:63:f6
Sending on   LPF/br0/30:85:a9:9d:63:f6
Sending on   Socket/fallback
DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 3 (xid=0x1b02ce25)
DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 7 (xid=0x1b02ce25)
DHCPREQUEST of 192.168.1.136 on br0 to 255.255.255.255 port 67 (xid=0x1b02ce25)
DHCPOFFER of 192.168.1.136 from 192.168.1.1
DHCPACK of 192.168.1.136 from 192.168.1.1
bound to 192.168.1.136 -- renewal in 39350 seconds.
laney at raleigh> cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.1

I feel like there's probably an existing systemd-ish way of doing this.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ifupdown 0.7.47.2ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Apr 25 18:01:25 2014
InstallationDate: Installed on 2012-10-07 (564 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
SourcePackage: ifupdown
UpgradeStatus: Upgraded to trusty on 2013-05-07 (353 days ago)

** Affects: ifupdown (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug systemd-boot third-party-packages trusty

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1312836

Title:
  Doesn't bring up interfaces from /etc/network/interfaces

Status in “ifupdown” package in Ubuntu:
  New

Bug description:
  I had no networking when I booted up with systemd just now.

  laney at raleigh> cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

  laney at raleigh> ifconfig
  lo        Link encap:Local Loopback  
            inet addr:127.0.0.1  Mask:255.0.0.0
            inet6 addr: ::1/128 Scope:Host
            UP LOOPBACK RUNNING  MTU:65536  Metric:1
            RX packets:572 errors:0 dropped:0 overruns:0 frame:0
            TX packets:572 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:0 
            RX bytes:46364 (46.3 KB)  TX bytes:46364 (46.3 KB)

  laney at raleigh> more /etc/network/interfaces
  # interfaces(5) file used by ifup(8) and ifdown(8)
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet manual

  auto br0
  iface br0 inet dhcp
      bridge_ports eth0
      bridge_stp off
      bridge_fd 0
      bridge_maxwait 0

  laney at raleigh> sudo ifup eth0 br0
  ifup: failed to open lockfile /run/network/.ifstate.lock: No such file or directory

  Then copying from /etc/init/networking.conf's pre-start

  laney at raleigh> sudo mkdir -p /run/network
  laney at raleigh> sudo ifup -a
  Internet Systems Consortium DHCP Client 4.2.4
  Copyright 2004-2012 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/br0/30:85:a9:9d:63:f6
  Sending on   LPF/br0/30:85:a9:9d:63:f6
  Sending on   Socket/fallback
  DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 3 (xid=0x1b02ce25)
  DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 7 (xid=0x1b02ce25)
  DHCPREQUEST of 192.168.1.136 on br0 to 255.255.255.255 port 67 (xid=0x1b02ce25)
  DHCPOFFER of 192.168.1.136 from 192.168.1.1
  DHCPACK of 192.168.1.136 from 192.168.1.1
  bound to 192.168.1.136 -- renewal in 39350 seconds.
  laney at raleigh> cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 192.168.1.1

  I feel like there's probably an existing systemd-ish way of doing
  this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ifupdown 0.7.47.2ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 25 18:01:25 2014
  InstallationDate: Installed on 2012-10-07 (564 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: ifupdown
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (353 days ago)

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



More information about the foundations-bugs mailing list