From: Robert Olsson <Robert.Olsson@data.slu.se>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: netdev@oss.sgi.com
Subject: suggestion for routing code improvement
Date: Wed, 10 Apr 2002 22:15:17 +0200 [thread overview]
Message-ID: <15540.40277.772027.111512@robur.slu.se> (raw)
In-Reply-To: <3CB47B90.B4CF1FAD@nortelnetworks.com>
Chris Friesen writes:
> So, what do you guys think? Is this a reasonable thing to do? I think that it
> makes the system nicely symmetrical, as opposed to the asymmetrical handling of
> current kernels.
Hello!
Why not leave the routing policy job to a routing daemon?
There is risk of routing havoc if the kernel start acting as one.
L-uu1:/# ip route list | wc -l
110441
This Linux box has 110441 bgp routes. Internet routing is very much
like a living organism. Routes comes and goes.
If some interface goes down for some reason the routing daemon gets it's
netlink message "link down" and recalcs the routing topologi.
If the interface comes back the router daemon recalcs again and installs
appropriate routes for this moment which may very well be different
compared to before "link down".
Cheers.
--ro
next prev parent reply other threads:[~2002-04-10 20:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 17:51 suggestion for routing code improvement Chris Friesen
2002-04-10 18:53 ` Andi Kleen
2002-04-10 20:15 ` Robert Olsson [this message]
2002-04-10 20:56 ` Chris Friesen
2002-04-10 23:02 ` Robert Olsson
2002-04-11 2:24 ` Julian Anastasov
2002-04-11 11:29 ` Robert Olsson
2002-04-11 12:08 ` Julian Anastasov
2002-04-11 12:18 ` jamal
2002-04-11 12:58 ` Julian Anastasov
2002-04-11 13:05 ` jamal
2002-04-11 13:01 ` Robert Olsson
2002-04-11 13:06 ` Julian Anastasov
2002-04-11 14:53 ` Robert Olsson
2002-04-11 15:24 ` Julian Anastasov
2002-04-11 16:05 ` Robert Olsson
2002-04-10 21:37 ` Julian Anastasov
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 20:41 Nivedita Singhvi
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=15540.40277.772027.111512@robur.slu.se \
--to=robert.olsson@data.slu.se \
--cc=cfriesen@nortelnetworks.com \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).