From: Stephen Hemminger <shemminger@vyatta.com>
To: thomas yang <lampsu@gmail.com>
Cc: hadi@cyberus.ca, netdev@vger.kernel.org
Subject: Re: [iproute2] iproute2 question
Date: Thu, 18 Mar 2010 23:27:26 -0700 [thread overview]
Message-ID: <20100318232726.47f800e1@nehalam> (raw)
In-Reply-To: <f4f837ab1003182253x12727855k118f7d67115daf23@mail.gmail.com>
On Fri, 19 Mar 2010 13:53:23 +0800
thomas yang <lampsu@gmail.com> wrote:
> 2010/3/18 Stephen Hemminger <shemminger@vyatta.com>:
> > On Thu, 18 Mar 2010 17:02:16 +0800
> > thomas yang <lampsu@gmail.com> wrote:
> >
> >> Hi,
> >>
> >> Linux router R (has some interfaces) use the table "main" as default
> >> routing table to route packets. If some link connected to R failed,
> >> I want to use another table "backup_tbl" to route packets; if the
> >> broken link repaired , go back to use table "main" . How to do this?
> >
> > That's now it works. Use a real routing daemon.
> >
>
> I want to reduce the packet loss that happens while routers converge
> after a topology change due to a failure, use precalculated backup
> table to do rapid failure repair (repair faster than routing daemon,
> fast reroute).
> I do static routing on my linux routers. When some link failed,
> I want to use backup tables to route packets. Can iproute2 do this?
You could probably kludge something with multiple route tables
and modifying a single 'ip rule'.
Something like:
http://www.linuxhorizon.ro/iproute2.html
next prev parent reply other threads:[~2010-03-19 6:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 9:02 [iproute2] iproute2 question thomas yang
2010-03-18 15:59 ` Stephen Hemminger
2010-03-19 5:53 ` thomas yang
2010-03-19 6:27 ` Stephen Hemminger [this message]
[not found] ` <f4f837ab1003221011v6657bebx3a741df5c781adf3@mail.gmail.com>
2010-03-22 17:12 ` thomas yang
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=20100318232726.47f800e1@nehalam \
--to=shemminger@vyatta.com \
--cc=hadi@cyberus.ca \
--cc=lampsu@gmail.com \
--cc=netdev@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