All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: Carrier detection for network interfaces
Date: Sat, 15 Nov 2003 22:53:40 +0200	[thread overview]
Message-ID: <1068929620.5033.36.camel@nosferatu.lan> (raw)
In-Reply-To: <3FB68F59.1050909@pobox.com>

On Sat, 2003-11-15 at 22:40, Jeff Garzik wrote:
> Martin Schlemmer wrote:
> > On Sat, 2003-11-15 at 18:22, Jeff Garzik wrote:
> > 
> >>Martin Schlemmer wrote:
> >>
> >>>Is there any proper way to detect a carrier signal with network
> >>>interfaces ?  I have recently come across a problem where we tried
> >>>to do with with checking for 'RUNNING', which do not work for all
> >>>drivers, as well as mii-tool that fails in some cases.
> >>
> >>
> >>What kernel version?
> >>
> >>In 2.6 you have linkwatch.  In 2.4 and 2.6, you have ETHTOOL_GLINK, and 
> >>mii-tool.
> >>
> > 
> > 
> > Anything more shell accessible (sysfs/proc) ?
> 
> 
> ethtool is shell accessible.
> 

Yep, thanks.  Was just wondering if there was a way
that did not depend on additional tools beyond cat,
sed, grep, etc.


Thanks,

-- 
Martin Schlemmer


  reply	other threads:[~2003-11-15 20:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-15 16:16 Carrier detection for network interfaces Martin Schlemmer
2003-11-15 16:22 ` Jeff Garzik
2003-11-15 20:28   ` Martin Schlemmer
2003-11-15 20:40     ` Jeff Garzik
2003-11-15 20:53       ` Martin Schlemmer [this message]
2003-11-16 10:20   ` Ben Greear
2003-11-16 13:15   ` Matthias Andree
2003-11-16 18:22     ` Jeff Garzik

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=1068929620.5033.36.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.