OSPF: Fix wrong LSA collisions detection
In some circumstances (old LSA flushed but not acknowledged and not removed) origination of a new LSA may wrongly triggers LSA collision code. The patch fixes that. Thanks to Asbjorn Mikkelsen for the bugreport and @mdelagueronniere for the original patch.
This commit is contained in:
parent
1cab2b4a7c
commit
cea2e25f41
1 changed files with 2 additions and 0 deletions
|
@ -404,6 +404,8 @@ ospf_refresh_lsa(struct ospf_proto *p, struct top_hash_entry *en)
|
||||||
void
|
void
|
||||||
ospf_flush_lsa(struct ospf_proto *p, struct top_hash_entry *en)
|
ospf_flush_lsa(struct ospf_proto *p, struct top_hash_entry *en)
|
||||||
{
|
{
|
||||||
|
en->nf = NULL;
|
||||||
|
|
||||||
if (en->next_lsa_body)
|
if (en->next_lsa_body)
|
||||||
{
|
{
|
||||||
mb_free(en->next_lsa_body);
|
mb_free(en->next_lsa_body);
|
||||||
|
|
Loading…
Reference in a new issue