public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Ethernet NIC dual homing
Date: 29 Oct 2001 19:15:39 -0800	[thread overview]
Message-ID: <9rl60r$g50$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0110291831160.9540-100000@anime.net> <p05100304b803c6908755@[10.128.7.49]>

Followup to:  <p05100304b803c6908755@[10.128.7.49]>
By author:    Jonathan Lundell <jlundell@pobox.com>
In newsgroup: linux.dev.kernel
> >
> >It doesn't work to detect link state through bridging device (say, bridged
> >ethernet over T3). The T3 might go down, but your MII link to the local
> >router will remain "up", so you will never know about the loss of link and
> >your packets will happily go into the void...
> 
> ARP isn't going to do much for you once the failure is beyond the 
> local segment, is it?
> 

ARP is broadcast to the layer 2 local segment; link detection refers
to the layer 1 local segment, which is not necessarily the same.

On the other hand, doing link detection is extremely useful for a
portable computer: when I plug in my Ethernet cable in a portable
system I want it to try to start doing DHCP detection and anything
else that is normally associated with the interface being "up" at that
time.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  reply	other threads:[~2001-10-30  3:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29 13:39 Ethernet NIC dual homing willy tarreau
2001-10-29 19:59 ` Laurent Deniel
2001-10-29 22:17   ` Laurent Deniel
2001-10-29 22:32     ` willy tarreau
2001-10-29 22:26   ` willy tarreau
2001-10-29 22:59     ` Christopher Friesen
2001-10-29 23:07       ` willy tarreau
2001-10-30  2:33       ` Dan Hollis
2001-10-30  2:55         ` Jonathan Lundell
2001-10-30  3:15           ` H. Peter Anvin [this message]
2001-10-30  3:30             ` Jonathan Lundell
2001-10-30  4:57               ` Dan Hollis
2001-10-30 15:33               ` Christopher Friesen
2001-10-30  4:55           ` Dan Hollis
  -- strict thread matches above, loose matches on Subject: below --
2001-10-30 11:14 Chemolli Francesco (USI)
2001-10-30 11:05 Chemolli Francesco (USI)
2001-10-30 11:33 ` Alan Cox
     [not found] <Pine.LNX.4.10.10110281727070.5138-100000@coffee.psychology.mcmaster.ca>
2001-10-28 22:42 ` Laurent Deniel
     [not found] <Pine.LNX.4.10.10110281248320.5138-100000@coffee.psychology.mcmaster.ca>
2001-10-28 22:23 ` Laurent Deniel
2001-10-28 17:23 Laurent Deniel
2001-10-29 13:24 ` Martin Eriksson

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='9rl60r$g50$1@cesium.transmeta.com' \
    --to=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox