All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arthur van Leeuwen <arthurvl@sci.kun.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] detecting link failure
Date: Tue, 19 Nov 2002 08:43:14 +0000	[thread overview]
Message-ID: <marc-lartc-103769548203870@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103769435003065@msgid-missing>



On Tue, 19 Nov 2002, nitin panjwani wrote:

> Hi All,
>
> I am running some tests in which I have to bring down
> my interface down as soon as I tear down the cable.
> Cable tearing results only in the link failure(as link
> light went off), but it doens't bring my interface
> down.
>
> Is there a way to bring the interface down as soon as
> my link fails, probably using 'ip link' or 'ip
> monitor'. Does anyone know about it.

Monitor using mii-tool.

> If there is some hardware monitering tool that can
> detect the link failure, probably I can use this to
> write a small program which will bring down the
> interface as soon as I link failure is detected

Well, you *could* theoretically write a kernel module that would monitor
link status and call back to userland... that would result in the
quickest teardown of the link.

Doei, Arthur.

-- 
  /\    / |      arthurvl@sci.kun.nl      | Work like you don't need the money
 /__\  /  | A friend is someone with whom | Love like you have never been hurt
/    \/__ | you can dare to be yourself   | Dance like there's nobody watching

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2002-11-19  8:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19  8:24 [LARTC] detecting link failure nitin panjwani
2002-11-19  8:43 ` Arthur van Leeuwen [this message]

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=marc-lartc-103769548203870@msgid-missing \
    --to=arthurvl@sci.kun.nl \
    --cc=lartc@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.