No subject

ecurity=20
reasons):

OSPF: Bad packet from 10.1.2.3 - authentication failed

As the LOG messages increases, we try to debug this and enable=20
debug protocols { packets }
so we see this as the case of the LOG messages:

2014-03-07 10:59:20 <TRACE> aclctrans: OSPF_auth: lower sequence number=
 (rcv=20
13229786, old 13229787)
2014-03-07 10:59:20 <ERR> OSPF: Bad packet from 10.1.2.3 - authenticati=
on=20
failed
2014-03-07 10:59:20 <TRACE> aclctrans: OSPF_auth: lower sequence number=
 (rcv=20
13229786, old 13229787)
2014-03-07 10:59:20 <ERR> OSPF: Bad packet from 10.1.2.3 - authenticati=
on=20
failed
2014-03-07 10:59:20 <TRACE> aclctrans: OSPF_auth: lower sequence number=
 (rcv=20
13229786, old 13229787)
2014-03-07 10:59:20 <ERR> OSPF: Bad packet from 10.1.2.3 - authenticati=
on=20
failed
2014-03-07 10:59:20 <TRACE> aclctrans: OSPF_auth: lower sequence number=
 (rcv=20
13229786, old 13229787)
2014-03-07 10:59:20 <ERR> OSPF: Bad packet from 10.1.2.3 - authenticati=
on=20
failed
2014-03-07 10:59:20 <TRACE> aclctrans: OSPF_auth: lower sequence number=
 (rcv=20
13229786, old 13229787)
2014-03-07 10:59:20 <ERR> OSPF: Bad packet from 10.1.2.3 - authenticati=
on=20
failed
2014-03-07 10:59:20 <TRACE> aclctrans: OSPF_auth: lower sequence number=
 (rcv=20
13229786, old 13229787)
2014-03-07 10:59:20 <ERR> OSPF: Bad packet from 10.1.2.3 - authenticati=
on=20
failed

We do not have any clue about where the decremented sequence number cam=
e from.
As this is an internal network and we have an helo interval of 5 second=
 we can=20
not imagin that this could be an "late" or "old" paket.

At the Moment we use mainly bird 1.3.11 with some exceptions where we h=
ave=20
bird 1.4.0. The problem seems not only bird generated as we also have f=
rom IPs=20
which are router in our network.

--=20

Mit freundlichen Gr=FC=DFen
---------------------------------
Daniel Wendler