Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 136889 - network bridge after dhcp failed not removable
Summary: network bridge after dhcp failed not removable
Status: VERIFIED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] baselayout (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Roy Marples (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-15 07:15 UTC by Devils-Hawk
Modified: 2006-06-19 03:27 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Devils-Hawk 2006-06-15 07:15:55 UTC
/etc/conf.d/net.br0:
config_eth0=( "null" )
config_eth1=( "null" )
bridge_br0="eth0 eth1"
config_br0=( "dhcp" )

after starting net.br0 the dhcpcd failed to get an ip address because no cable was connected to eth0 or eth1. afterwards it was not possible to stop the net.br0 service anymore. It quietly restarted itself after every /etc/init.d/net.br0 stop.  only removing the device drivers for the 2 network interfaces from kernel stopped the service from restarting but did not stop the br0 interface to reappearing after deletion leading to following strange behaviour:
>brctl show && brctl delbr br0 && brctl show && sleep 1 && brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.000000000000       no
bridge name     bridge id               STP enabled     interfaces
bridge name     bridge id               STP enabled     interfaces
br0             8000.000000000000       no

only commenting out the line
#bridge_br0="eth0 eth1"
from /etc/conf.d/net.br0 and doing a restart and then a stop it was possible to finally get rid of the bridge, so i figured it is probably a bug in the gentoo bridge module code
Comment 1 Roy Marples (RETIRED) gentoo-dev 2006-06-15 09:57:32 UTC
You neglected to attach emerge --info
Comment 2 Devils-Hawk 2006-06-15 10:37:41 UTC
Here u go:
Portage 2.1 (default-linux/x86/2006.0, gcc-4.1.1, glibc-2.3.6-r3, 2.6.16-gentoo-r9-reiser4-devh i686)
=================================================================
System uname: 2.6.16-gentoo-r9-reiser4-devh i686 AMD Athlon(TM) XP 2200+
Gentoo Base System version 1.6.14
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
ccache version 2.3 [enabled]
dev-lang/python:     2.3.5-r2, 2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     2.3
dev-util/confcache:  0.4.2-r1
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1-r2
sys-devel/gcc-config: 1.3.13-r2
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo"
CXXFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache confcache distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://gentoo.inode.at/ ftp://gentoo.inode.at/source/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage /usr/portage/local/layman/portage-xgl"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="x86 3dnow 3dnowext X Xaw3d a52 aac aalib acpi alsa apache apache2 apm arts audiofile avi bash-completion berkdb bitmap-fonts bzip2 cairo ccache cdr cli crypt cups curl dbus devil dri dts dvd dvdr dvdread emacs emboss encode esd exif ffmpeg firefox flac foomaticdb fortran ftp gcj gdbm gif gpm gstreamer gtk gtk2 hal ieee1394 imlib ipv6 isdnlog jack java jpeg jpeg2k kde kdeenablefinal libcaca libg++ libwww lm_sensors lua mad mikmod mjpeg mmx mmxext mng motif mp3 mpeg multislot multitarget mysql ncurses network nls nptl nptlonly nsplugin nvidia odbc ogg openal opengl pam pcre pdflib perl png posix ppds pppd python qt qt4 quicktime rar readline real reflection ruby samba sdl session sharedext sharedmem sndfile spell spl sqlite sse ssl svg tcltk tcpd tetex theora threads tiff truetype truetype-fonts type1-fonts udev unicode usb v4l v4l2 vorbis win32codecs xinerama xml xml2 xorg xpm xv xvid xvmc zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux userland_GNU video_cards_nv video_cards_nvidia"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS
Comment 3 Roy Marples (RETIRED) gentoo-dev 2006-06-15 11:01:50 UTC
Lastly, which dhcp client and which version?
Comment 4 Devils-Hawk 2006-06-15 12:56:53 UTC
net-misc/dhcpcd-2.0.5  USE="-build -debug -static"
Comment 5 Roy Marples (RETIRED) gentoo-dev 2006-06-16 02:09:09 UTC
Please test with baselayout-1.12.1
Comment 6 Devils-Hawk 2006-06-18 05:17:43 UTC
works just fine! Thank you! One suggestion though: the log output is a little bit unreadable if you just have lots "* servic x starting", "* service x started", something like "* service x started    [ok]" and on failure the usual [!!] on the left makes identifying a problem a lot easier.
Comment 7 Roy Marples (RETIRED) gentoo-dev 2006-06-18 09:09:34 UTC
(In reply to comment #6)
> works just fine! Thank you! One suggestion though: the log output is a little
> bit unreadable if you just have lots "* servic x starting", "* service x
> started", something like "* service x started    [ok]" and on failure the usual
> [!!] on the left makes identifying a problem a lot easier.
> 

Can't use the [ok] or [!!] as they wouldn't align properly - this is due to parallel startup being really parallel. Of course, if you can fix this then patches are always welcome :)
Comment 8 Devils-Hawk 2006-06-19 03:27:41 UTC
hmm! Your are printing the line "service x started", or "service x failed to start" anyway, it should not be a problem to but an [ok] or [!!] at the end of this line just for better visualization, to see at one glance oh something failed/everythings fine. At the moment its pretty easy to miss the 1 red start indicating something failed.
like:
* service a starting
* service b starting
* service a started                  [ok]
* service c starting
* service b failed to start          [!!]