summaryrefslogtreecommitdiffstats
path: root/proto/rip
diff options
context:
space:
mode:
authorMartin Mares <mj@ucw.cz>2000-05-19 13:00:47 +0200
committerMartin Mares <mj@ucw.cz>2000-05-19 13:00:47 +0200
commitf7ad556f2017075abaef659bf018a0ce215b13b3 (patch)
tree8e375205bf3c05af4fe9ab7ef0ff54acfbac2bad /proto/rip
parent76dfda9e74580b6c07206b7afbbdafeea36ad08f (diff)
downloadbird-f7ad556f2017075abaef659bf018a0ce215b13b3.tar
bird-f7ad556f2017075abaef659bf018a0ce215b13b3.zip
Commented out the `inserting entry which is already there' message since
it's pretty normal: during feeding of the protocol, a new route can appear which will be announced normally and then repeated by the feeding process.
Diffstat (limited to 'proto/rip')
-rw-r--r--proto/rip/rip.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/proto/rip/rip.c b/proto/rip/rip.c
index dddf1a5..5bb1069 100644
--- a/proto/rip/rip.c
+++ b/proto/rip/rip.c
@@ -777,8 +777,11 @@ rip_rt_notify(struct proto *p, struct network *net, struct rte *new, struct rte
if (new) {
struct rip_entry *e;
+#if 0
+ /* This can happen since feeding of protocols is asynchronous */
if (fib_find( &P->rtable, &net->n.prefix, net->n.pxlen ))
log( L_BUG "Inserting entry which is already there?" );
+#endif
e = fib_get( &P->rtable, &net->n.prefix, net->n.pxlen );
e->nexthop = new->attrs->gw;