Hi. I'm using zebra to advert RIPv2 pkts out every 10 secs and I'm afraid
the hardcoded RIP jitter might cause flaps. I'm wondering if it could be
made tunable:
piiascs1b1 /ms/dev/aurora/zebra/0.96.4/src/quagga-0.96.4/ripd 21$ diff
-uwb ripd.c ripd.c.orig
--- ripd.c 2004-01-13 09:56:03.000000000 -0500
+++ ripd.c.orig 2004-01-08 17:01:12.000000000 -0500
@@ -2600,7 +2600,7 @@
int
rip_update_jitter (unsigned long time)
{
- return ((rand () % (RIP_UPDATE_JITTER + 1)) - (RIP_UPDATE_JITTER / 2));
+ return ((rand () % (time + 1)) - (time / 2));
}
void
piiascs1b1 /ms/dev/aurora/zebra/0.96.4/src/quagga-0.96.4/ripd 22$ diff
-uwb ripd.h ripd.h.orig
--- ripd.h 2004-01-09 10:42:32.000000000 -0500
+++ ripd.h.orig 2004-01-08 17:01:18.000000000 -0500
@@ -61,8 +61,6 @@
#define RIP_TIMEOUT_TIMER_DEFAULT 180
#define RIP_GARBAGE_TIMER_DEFAULT 120
-#define RIP_UPDATE_JITTER 2
-
/* RIP peer timeout value. */
#define RIP_PEER_TIMER_DEFAULT 180
or maybe a compile time option?
Cheers,
Anthony
the hardcoded RIP jitter might cause flaps. I'm wondering if it could be
made tunable:
piiascs1b1 /ms/dev/aurora/zebra/0.96.4/src/quagga-0.96.4/ripd 21$ diff
-uwb ripd.c ripd.c.orig
--- ripd.c 2004-01-13 09:56:03.000000000 -0500
+++ ripd.c.orig 2004-01-08 17:01:12.000000000 -0500
@@ -2600,7 +2600,7 @@
int
rip_update_jitter (unsigned long time)
{
- return ((rand () % (RIP_UPDATE_JITTER + 1)) - (RIP_UPDATE_JITTER / 2));
+ return ((rand () % (time + 1)) - (time / 2));
}
void
piiascs1b1 /ms/dev/aurora/zebra/0.96.4/src/quagga-0.96.4/ripd 22$ diff
-uwb ripd.h ripd.h.orig
--- ripd.h 2004-01-09 10:42:32.000000000 -0500
+++ ripd.h.orig 2004-01-08 17:01:18.000000000 -0500
@@ -61,8 +61,6 @@
#define RIP_TIMEOUT_TIMER_DEFAULT 180
#define RIP_GARBAGE_TIMER_DEFAULT 120
-#define RIP_UPDATE_JITTER 2
-
/* RIP peer timeout value. */
#define RIP_PEER_TIMER_DEFAULT 180
or maybe a compile time option?
Cheers,
Anthony