summaryrefslogtreecommitdiffstats
path: root/gdb
diff options
context:
space:
mode:
authorMartin Buck <mb-tmp-tvguho.pbz@gromit.dyndns.org>2021-05-10 22:48:32 +0200
committerMartin Buck <mb-tmp-tvguho.pbz@gromit.dyndns.org>2021-05-11 11:52:07 +0200
commit2d84ae9c29205065b10aa6873fa269080d55338f (patch)
tree6633a516771a8b4c3b3c8f383e794168c67a58e6 /gdb
parentMerge pull request #8601 from Fredi-raspall/pr_fix_lfa_debug (diff)
downloadfrr-2d84ae9c29205065b10aa6873fa269080d55338f.tar.xz
frr-2d84ae9c29205065b10aa6873fa269080d55338f.zip
ospf6d: Send MAXAGE LS update for received old self-originated LSAs
Fixes OSPFv3-26.13 ANVL RFC conformance bug #8576 by improving the bugfix for #7030 from 4c63a76a. That commit changed handling of received old non-MAXAGE LSAs with a MAXAGE counterpart in the LSDB from "add all LSAs to LSDB and flood non-self-originated ones" to "add & flood only non-self-originated LSAs and ignore self-originated LSAs". The new behaviour is similar but adds sending a MAXAGE LS Update for received self-originated LSAs to remove the old LSAs from the network, resulting in "add & flood non-self-originated LSAs, don't add but send MAXAGE LS Update for self-originated LSAs". The missing MAXAGE LS Update is what OSPFv3-26.13 ANVL complained about. Signed-off-by: Martin Buck <mb-tmp-tvguho.pbz@gromit.dyndns.org>
Diffstat (limited to 'gdb')
0 files changed, 0 insertions, 0 deletions