[lkml]   [2000]   [Oct]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectwhy would you want /proc/sys/net/ipv4/route/min_delay to not be zero?
I figured out why my IP takeover was taking a couple seconds to take
effect even though it returned immediately--the
/proc/sys/net/ipv4/route/min_delay setting is by default set to 2,
giving a 2 second delay before the route cache is updated or flushed.
This meant that packets continued to go out the old interface for two
seconds, until the route cache was flushed and the new route was used.

Now what I'm trying to figure out is why anyone would want this value to
NOT be set to zero. When would you not want route flushes and route
changes to take immediate effect?

Thanks again,


Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email:
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:41    [W:0.106 / U:4.208 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site