netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "J.A. Magallon" <jamagallon@able.es>,
	"Bryan O'Sullivan" <bos@keyresearch.com>,
	linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [ANNOUNCE] netplug, a daemon that handles network cables getting plugged in and out
Date: Fri, 29 Aug 2003 00:45:53 +0200	[thread overview]
Message-ID: <20030828224553.GC23528@werewolf.able.es> (raw)
In-Reply-To: <3F4E8373.1040204@pobox.com>; from jgarzik@pobox.com on Fri, Aug 29, 2003 at 00:34:27 +0200


On 08.29, Jeff Garzik wrote:
> J.A. Magallon wrote:
> > On 08.28, Bryan O'Sullivan wrote:
> > 
> >>Netplug is a daemon that responds to network cables being plugged in or
> >>out by bringing a network interface up or down.  This is extremely
> >>useful for DHCP-managed systems that move around a lot, such as laptops
> >>and systems in cluster environments.
> >>
> >>For more details and download instructions, see the netplug homepage:
> >>http://www.red-bean.com/~bos/
> >>
> > 
> > 
> > I feel sorry, but did you ever knew this existed ?
> > 
> > http://www.stud.uni-hamburg.de/users/lennart/projects/ifplugd/
> 
> 
> ifplugd doesn't appear to use netlink.  Did I miss something?
> 
> netlink is definitely the preferred way to get link notification.  Maybe 
> the two authors can work together to merge the best parts of both...
> 

That would be very nice, but there is still a problem.
Does netlink solve the fact that there are cards (at least in 2.4)
that do not support any detection method:

ne2k-pci
    SIOCETHTOOL failed (Operation not permitted)
    SIOCGMIIPHY failed (Operation not permitted)
    SIOCDEVPRIVATE failed (Operation not supported)

3c59x (3c980-TX)
    SIOCETHTOOL failed (Operation not permitted)
    SIOCGMIIPHY failed (Operation not permitted)
    SIOCDEVPRIVATE: unplugged

3c59x (3c905C-TX/TX-M)
    SIOCETHTOOL failed (Operation not supported)
    SIOCGMIIPHY: link beat detected
    SIOCDEVPRIVATE: link beat detected
 
e100
    SIOCETHTOOL: link beat detected
    SIOCGMIIPHY: link beat detected
    SIOCDEVPRIVATE failed (Operation not supported)

e1000
    SIOCETHTOOL: link beat detected
    SIOCGMIIPHY: link beat detected
    SIOCDEVPRIVATE failed (Operation not supported)

-- 
J.A. Magallon <jamagallon@able.es>      \                 Software is like sex:
werewolf.able.es                         \           It's better when it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.22-jam1m (gcc 3.3.1 (Mandrake Linux 9.2 3.3.1-1mdk))

  reply	other threads:[~2003-08-28 22:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28 21:21 [ANNOUNCE] netplug, a daemon that handles network cables getting plugged in and out Bryan O'Sullivan
2003-08-28 21:35 ` Jeff Garzik
2003-08-28 21:46 ` Christoph Hellwig
2003-08-28 21:50   ` Bryan O'Sullivan
2003-08-28 21:54 ` J.A. Magallon
2003-08-28 22:34   ` Jeff Garzik
2003-08-28 22:45     ` J.A. Magallon [this message]
2003-08-28 22:49       ` Bryan O'Sullivan
2003-09-03  8:42       ` Stefan Rompf
2003-08-29  0:34 ` Aaron Lehmann
2003-08-29  2:11   ` David T Hollis
2003-08-29 17:43     ` Bryan O'Sullivan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030828224553.GC23528@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=bos@keyresearch.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).