bridge is configured too late (for openvpn and openntpd at least)

Bug #687631 reported by Jim Cheetham
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bridge-utils (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: bridge-utils

I have a bridge interface specified in /etc/network/interfaces, but when the machine starts up the bridge device is not available early enough -- other packages (specifically OpenVPN and OpenNTPd) try to bind to the requested interface, but fail.

The OpenVPN listen interface is specified by IP address only, not device name. The OpenNTPd interface is "*". OpenSSH works just fine, and does not have any device specified in its config; but there are syslog comments saying the ssh is terminating, so perhaps there is a retry somewhere that is masking this issue.

----

/etc/network/interfaces (NB my two main interfaces are renamed by udev to be /dev/officenet and /dev/prodnet):-

root@moonshine:/etc/ssh# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The bridge network that will hold officenet and openVPN clients
auto officebr
iface officebr inet static
        address 10.1.1.2
        network 10.1.1.0
        netmask 255.255.255.0
        gateway 10.1.1.1
        bridge_ports officenet tap0
        bridge_fd 9
        bridge_hello 2
        bridge_maxage 12
        bridge_stp off

# The production network
auto prodnet
iface prodnet inet static
        address 10.90.1.1
        netmask 255.255.255.0

----

Apport says :-

ProblemType: Bug
Architecture: amd64
Date: Thu Dec 9 14:35:47 2010
Dependencies:
 coreutils 7.4-2ubuntu3
 debconf 1.5.28ubuntu4
 debconf-i18n 1.5.28ubuntu4
 dpkg 1.15.5.6ubuntu4.4
 findutils 4.4.2-1ubuntu1
 gcc-4.4-base 4.4.3-4ubuntu5
 libacl1 2.2.49-2
 libattr1 1:2.4.44-1
 libc-bin 2.11.1-0ubuntu7.5
 libc6 2.11.1-0ubuntu7.5
 libgcc1 1:4.4.3-4ubuntu5
 liblocale-gettext-perl 1.05-6
 libselinux1 2.0.89-4
 libstdc++6 4.4.3-4ubuntu5
 libtext-charwidth-perl 0.04-6
 libtext-iconv-perl 1.7-2
 libtext-wrapi18n-perl 0.06-7
 lzma 4.43-14ubuntu2
 perl-base 5.10.1-8ubuntu2
 tzdata 2010o-0ubuntu0.10.04
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2)
Package: bridge-utils 1.4-5ubuntu2
PackageArchitecture: amd64
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-26.48-server 2.6.32.24+drm33.11
SourcePackage: bridge-utils
Tags: lucid
Uname: Linux 2.6.32-26-server x86_64

Revision history for this message
Jim Cheetham (jim.cheetham) wrote :
Scott Moser (smoser)
Changed in bridge-utils (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Peter Matulis (petermatulis) wrote :

On a fresh (vmbuilder) install Maverick (server 64-bit) I can't even get a vanilla bridge to come up via /etc/network/interfaces [1]. A manual restart of the networking service gets it to work however:

$ sudo /etc/init.d/networking restart

Should I open a new bug or should we change focus of the current one?

[1]

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto br0
iface br0 inet static
        bridge_ports eth0
        address 10.153.107.93
        netmask 255.255.255.0
        network 10.153.107.0
        broadcast 10.153.107.255
        gateway 10.153.107.1

Revision history for this message
Stéphane Graber (stgraber) wrote :

Could you try on an up to date 11.10 or 12.04 system? I'd think some of the timing improvements in the network scripts over the past two cycles should have solved most if not all of that issue.

Changed in bridge-utils (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for bridge-utils (Ubuntu) because there has been no activity for 60 days.]

Changed in bridge-utils (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.