Your message dated Sun, 10 Jan 2016 23:26:57 +0100 with message-id <[email protected]> and subject line Re: /sbin/ifup: Bridges without any 'ports' are not created properly has caused the Debian Bug report #612357, regarding /sbin/ifup: Bridges without any 'ports' are not created properly to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 612357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612357 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ifupdown Version: 0.6.10 Severity: normal File: /sbin/ifup It should be to create a bridge and add ports to that bridge at a later time. In my case the bridge will be used by virtual containers that are started long after ifupdown has finished. This works fine without ifupdown, by simply issuing the following two commands: # brctl add br1 # ifconfig br1 10.5.0.1 255.255.255.0 This is of course not persistent between reboots, and since I'm not that fond of using alternative boot script to set up networking, I created an equivalent configuration in /etc/network/interfaces: auto br1 iface br1 inet static address 10.5.0.1 netmask 255.255.255.0 bridge_fd 0 bridge_maxwait 0 If I use that configuration however, the following error messages are generated: # ifup br1 SIOCSIFADDR: No such device br1: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device br1: ERROR while getting interface flags: No such device Failed to bring up br1. The bridge is indeed not active when ifup finished. This can be 'fixed' by adding a dummy interface to the bridge_ports section like this: bridge_ports dummy0 But then I end up with a useless interface in my bridge. Could ifupdown be fixed/adjusted to allow bridges without any ports added to them? Also, feel free to tell me if I'm doing something wrong here :) -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (101, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ifupdown depends on: ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii net-tools 1.60-23 The NET-3 networking toolkit ifupdown recommends no packages. Versions of packages ifupdown suggests: ii dhcp3-client 4.1.1-P1-15 ISC DHCP server (transitional pack ii iproute 20100519-3 networking and traffic control too ii isc-dhcp-client [dhcp3-clien 4.1.1-P1-15 ISC DHCP client pn ppp <none> (no description available) -- no debconf information
--- End Message ---
--- Begin Message ---This seems to have been a configuration error, closing this bug report. -- Met vriendelijke groet / with kind regards, Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
