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.
This commit is contained in:
parent
76dfda9e74
commit
f7ad556f20
1 changed files with 3 additions and 0 deletions
|
@ -777,8 +777,11 @@ rip_rt_notify(struct proto *p, struct network *net, struct rte *new, struct rte
|
||||||
|
|
||||||
if (new) {
|
if (new) {
|
||||||
struct rip_entry *e;
|
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 ))
|
if (fib_find( &P->rtable, &net->n.prefix, net->n.pxlen ))
|
||||||
log( L_BUG "Inserting entry which is already there?" );
|
log( L_BUG "Inserting entry which is already there?" );
|
||||||
|
#endif
|
||||||
e = fib_get( &P->rtable, &net->n.prefix, net->n.pxlen );
|
e = fib_get( &P->rtable, &net->n.prefix, net->n.pxlen );
|
||||||
|
|
||||||
e->nexthop = new->attrs->gw;
|
e->nexthop = new->attrs->gw;
|
||||||
|
|
Loading…
Reference in a new issue