I've been running ifplugd 0.24 for a long time, and it was completely stable and always started and stopped my net.eth0 connection based on whether the cable was in the jack. ifplugd 0.25 starts/stops/restarts without any errors, but does not bring net.eth0 up when the cable is plugged in, or if the cable is in the computer on startup. Reproducible: Always Steps to Reproduce: 1. Use 0.24 2. Upgrade to 0.25 3. Plug in the ethernet cable Actual Results: net.eth0 was not brought up. Expected Results: Bring net.eth0 up. Here is my /etc/conf.d/ifplugd, which worked fine with 0.24: # -*-sh-*- # $Id: gentoo-ifplugd-conf-v3,v 1.1 2003/11/15 16:47:58 wmertens Exp $ # This file is part of ifplugd. # # ifplugd is free software; you can redistribute it and/or modify it under # the terms of the GNU General Public License as published by the Free # Software Foundation; either version 2 of the License, or (at your # option) any later version. # # ifplugd is distributed in the hope that it will be useful, but WITHOUT # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or # FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License # for more details. # # You should have received a copy of the GNU General Public License # along with ifplugd; if not, write to the Free Software Foundation, # Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA. # ifplugd configuration file # Please note that this is a bourne shell fragment sourced by the # init script of ifplugd. # Specify the interfaces to control here, separated by spaces. # Ifplugd processes will be started for each of these interfaces when # the ifplugd init script is called with the "start" argument. You may # use the magic string "auto" to make the init script start or stop # ifplugd processes for ALL eth and wlan interfaces that are available # according to /proc/net/dev. Note that the list of interfaces # appearing in /proc/net/dev may depend on which kernel modules you # have loaded. INTERFACES="eth0 eth1" # Additional parameters for ifplugd. # See manual page ifplugd.8 for details. # If you set AUTO to yes, you have to read http://bugs.gentoo.org/show_bug.cgi?id=28362 # I recommend a delay of 0, both ways, since then, you can swap ethernet # cables on different networks and get a new ip address. # None of the programs I tested had a problem with the interface being # gone in the mean time. AUTO="no" BEEP="yes" IGNORE_FAIL="yes" IGNORE_FAIL_POSITIVE="no" IGNORE_RETVAL="yes" POLL_TIME="1" DELAY_UP="0" DELAY_DOWN="0" API_MODE="auto" SHUTDOWN="yes" WAIT_ON_FORK="no" MONITOR="no" ARGS="" # Additional parameters for ifplugd for the specified interface. Note that # the global variable is ignored, when a variable like this is set for an # interface # MONITOR_wlan0="yes" # DELAY_UP_wlan0="5" # DELAY_DOWN_wlan0="5" And here is my emerge info: Portage 2.0.51-r3 (default-linux/x86/2004.2, gcc-3.4.3, glibc-2.3.4.20040808-r1, 2.6.9-nitro4 i686) ================================================================= System uname: 2.6.9-nitro4 i686 Pentium III (Coppermine) Gentoo Base System version 1.4.16 distcc 2.16 i386-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -mtune=pentium3 -march=pentium3 -fforce-addr -momit-leaf-frame-pointer -fomit-frame-pointer -frename-registers -fweb -ftracer -pipe " CHOST="i386-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mtune=pentium3 -march=pentium3 -fforce-addr -momit-leaf-frame-pointer -fomit-frame-pointer -frename-registers -fweb -ftracer -pipe -fvisibility-inlines-hidden" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://prometheus.cs.wmich.edu/gentoo http://gentoo.chem.wisc.edu/gentoo/ http://mirror.datapipe.net/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X acpi alsa apm arts avi berkdb bitmap-fonts cdr crypt cups dga dvd emacs encode esd f77 fam flac foomaticdb fortran gdbm gif gpm gtk gtk2 imagemagick imlib java jpeg junit ldap libg++ libwww mad mikmod mmx mmx2 motif mpeg ncurses nls nptl oggvorbis opengl oss pam pcmcia pdflib perl png python qt quicktime readline samba sdl slang spell sse ssl svga tcltk tcpd tiff truetype x86 xml2 xmms xv zlib video_cards_rage128"
Just so I can rule this out as the problem, can you please recompile with sane CFLAGS? "-O2 -march=pentium3 -fomit-frame-pointer -pipe" should do, and let me know if the problem still remains. For future reference, most devs wont investigate other wise, as some flags/flag combos can cause obscure bugs.
Tried this: CFLAGS="" emerge ifplugd Still doesn't work.
I am having similar problems. Ifplugd now seems to take long to bring up the interface. This usually only happends once I log in to gnome. This means that the interface is not up in time to use kerberos logging etc.
Having the same issues here. Using the ifplugd init.d script with the configuration below does not bring eth0 up, regardless of the cable being unplugged or plugged at startup and regardless of any plug out / plug in manouvers during run. Anoying, running ifplugd from console in non-daemonised mode, makes it operate fully as expected. Here's the config: INTERFACES="eth0" AUTO="no" BEEP="yes" IGNORE_FAIL="no" IGNORE_FAIL_POSITIVE="no" IGNORE_RETVAL="no" POLL_TIME="1" DELAY_UP="0" DELAY_DOWN="0" API_MODE="auto" SHUTDOWN="no" WAIT_ON_FORK="no" MONITOR="yes" ARGS="" Followed by this output in /var/log/daemon.log: May 24 10:30:03 DLD8-FBLK31J ifplugd(eth0)[25253]: ifplugd 0.27 initializing, using NETLINK device monitoring. May 24 10:30:03 DLD8-FBLK31J ifplugd(eth0)[25253]: Using interface eth0/00:0F:1F:0F:62:CD with driver <tg3> (version: 3.14) May 24 10:30:03 DLD8-FBLK31J ifplugd(eth0)[25253]: Using detection mode: SIOCETHTOOL May 24 10:30:03 DLD8-FBLK31J ifplugd(eth0)[25253]: Initialization complete, link beat not detected, interface enabled. On console, I simply use: ifplugd --no-daemon and I see ifplugd 0.27 initializing. Using interface eth0/00:0F:1F:0F:62:CD with driver <tg3> (version: 3.14) Using detection mode: SIOCETHTOOL Initialization complete, link beat not detected. Link beat detected. Executing '/usr/sbin/ifplugd.action eth0 up'. client: Configuration not set for eth0 - assuming dhcp Program executed successfully.
this is a request for enhancement, not a bug report: is there any reason why the gentoo default net.eth0 scripts do not check whether there is a linkbeat---before they time out for just about 2 minutes for dhcpcd before the boot continues? may I humbly suggest that the gentoo developers makes link check behavior the default, so that everyone benefits from this---especially those of us who are less versed in the magic of networks? (Who would not want to have this capability?) sincerely, /iaw
(In reply to comment #5) > this is a request for enhancement, not a bug report: > is there any reason why the gentoo default net.eth0 scripts do not check whether > there is a linkbeat---before they time out for just about 2 minutes for dhcpcd > before the boot continues? > may I humbly suggest that the gentoo developers makes link check behavior the > default, so that everyone benefits from this---especially those of us who are > less versed in the magic of networks? (Who would not want to have this capability?) I have wondered the same thing myself? I never had to deal with this in RedHat. The network just enabled or didn't if I had a cable plugged in or not. May I also suggest that 2 minutes is way too long. So either shorten that time down to something less annoying, or start this as a parallel task as soon as possible. I hate sitting there waiting for my network to time-out. I've gotten to the point in Gentoo where i just turn it on manually now. GRRRR.
emerge --info Portage 2.0.51.22-r2 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r1, 2.6.12-morph7-0813 i686) ================================================================= System uname: 2.6.12-morph7-0813 i686 Intel(R) Pentium(R) M processor 1.70GHz Gentoo Base System version 1.12.0_pre5 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.4 [enabled] dev-lang/python: 2.3.5, 2.4.1-r1 sys-apps/sandbox: 1.2.12 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 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-Os -march=pentium-m -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/alias /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-Os -march=pentium-m -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig buildpkg buildsyspkg ccache distcc distlocks fixpackages sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ " LDFLAGS="-Wl,-O1 -Wl,--sort-common -s" LINGUAS="fr" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage /usr/local/zugaina-portage /usr/local/portage-gentopia" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="x86 X acpi acpi4linux alsa apache2 avi bash-completion berkdb bitmap-fonts bootsplash cdda cddb cdr codecs crypt dbus dga divx divx4linux dvd dvdr dvdread eds emboss encode ffmpeg flac font-server foomaticdb fortran gdbm gif gimp gkrellm gnome gstreamer gtk gtk2 hal howl ibm icc icq imap imlib ithreads jack java jikes jpeg lcd libg++ libwww lirc lm_sensors mad mikmod mmx motif mozilla moznocompose moznoirc moznomail moznoxft mp3 mpeg mpeg4 mplayer ncurses nls nocd nptl nptlonly offensive ogg oggvorbis opengl pam pcmcia pda pdflib perl pic png python quicktime radeon readline real rtc samba screensaver sdl spell sqlite sse sse2 ssl svg tcpd theora threads truetype truetype-fonts type1-fonts unicode usb userlocales vidix vim vnc vorbis wifi win32codecs wxwindows xanim xine xml2 xosd xv xvid xvmc zlib linguas_fr userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL
(In reply to comment #5) > this is a request for enhancement, not a bug report: Open a new bug then > > is there any reason why the gentoo default net.eth0 scripts do not check whether > there is a linkbeat---before they time out for just about 2 minutes for dhcpcd > before the boot continues? Yes - not every ethernet device supports linkbeat > > may I humbly suggest that the gentoo developers makes link check behavior the > default, so that everyone benefits from this---especially those of us who are > less versed in the magic of networks? (Who would not want to have this capability?) > We did - many people complained so we removed it. ifplugd is the preferred method.
A combination of baselayout-1.12.0_pre7-r1 and ifplugd-0.28-r1 should fix this bug :)
