From: Roberto Nibali <ratz@drugphish.ch>
To: Stefan Rompf <srompf@isg.de>
Cc: linux-kernel@vger.kernel.org, jgarzik@mandrakesoft.com
Subject: Re: Interface operative status detection
Date: Sat, 19 Jan 2002 19:34:05 +0100 [thread overview]
Message-ID: <3C49BC1D.8050901@drugphish.ch> (raw)
In-Reply-To: <3C498CC9.6FAED2AF@isg.de>
Hi,
> interface, f.e. the ethernet link beat. This is a major show stopper
> against using Linux for "serious" IP routing.
[...]
> So what about the following idea: The network interface drivers use the
> netif_carrier_on() and netif_carrier_off() functions to update their
> interface card status (a bunch of drivers already do). To get this
> information forwarded to user mode via netlink socket, we use a kernel
> thread that goes through the device list, and everytime IFF_RUNNING
> and netif_carrier_ok() differ, IFF_RUNNING is updated and a message is
> sent via netlink.
A slightely different approach could be to use the alternative routes
using the patch from Julian Anastasov [1] and set RTNH_F_BADSTATE. With
the RTNH_F_DEAD we can select a new route in the multipath route setup.
You set up multiple routes and in case of link state problems you mark
the route dead and the routeing code will not select the routes defined
with that interface anymore. Together with an active NUD you get a
fairly decent responsive HA system. But maybe I'm way off-topic and I
missunderstood your concerns.
[1] http://www.linux-vs.org/~julian/01_alt_routes-2.4.12-5.diff
Cheers,
Roberto Nibali, ratz
next prev parent reply other threads:[~2002-01-19 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-19 15:12 Interface operative status detection Stefan Rompf
2002-01-19 15:29 ` Jeff Garzik
2002-01-19 18:34 ` Roberto Nibali [this message]
2002-02-08 10:16 ` Jeff Garzik
[not found] <3C498CC9.6FAED2AF@isg.de.suse.lists.linux.kernel>
2002-01-19 17:40 ` Andi Kleen
2002-01-20 0:51 ` Stefan Rompf
2002-02-12 14:52 ` David L. Parsley
2002-02-12 15:58 ` Chris Friesen
2002-02-12 16:08 ` Stefan Rompf
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=3C49BC1D.8050901@drugphish.ch \
--to=ratz@drugphish.ch \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srompf@isg.de \
/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