All of lore.kernel.org
 help / color / mirror / Atom feed
* [LARTC] rules/routes traversal misunderstanding
@ 2004-01-24 18:16 Raphael Benedet
  0 siblings, 0 replies; only message in thread
From: Raphael Benedet @ 2004-01-24 18:16 UTC (permalink / raw)
  To: lartc

Hi,

I've been experimenting with ip route for the last few days to get load 
sharing accross 2 providers working. While it works most of the time, on 
a few occasions, packets are routed to the wrong interface.
I'm not sure to understand rules and routes traversal correctly (I 
couldn't find answers in the howto). So, here are my questions:

1. How does the rule traversal work exactly? If I have rules like this:
100: from all lookup provider1
200: from all lookup provider2
What does make stop the traversal? For instance, does a default route in 
provider1 would stop the traversal?

2. are tables entirely separated? Say, if you have this:
100: from all lookup table_part1
200: from all lookup table_part2
and table_part1 contains the route for a provider and table_part2 
contains the default route statement for this provider. Obviously, both 
tables would be checked. But once in table_part2, would the default 
route work with what was defined in table_part1 or are routes 
"forgotten" from table to table?

I'm pretty new to all this stuff. So, this may sound like stupid 
questions but I couldn't find the answers in the howto nor the man pages.

Thanks in advance.

Raphael Benedet

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2004-01-24 18:16 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-01-24 18:16 [LARTC] rules/routes traversal misunderstanding Raphael Benedet

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.