Hello List,

we have at the moment an strange problem in our OSPF setup.
>From time to time we do have LOG Messages like (IP's are replaced for security 
reasons):

OSPF: Bad packet from 10.1.2.3 - authentication failed

As the LOG messages increases, we try to debug this and enable 
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 
13229786, old 13229787)
2014-03-07 10:59:20 <ERR> OSPF: Bad packet from 10.1.2.3 - authentication 
failed
2014-03-07 10:59:20 <TRACE> aclctrans: OSPF_auth: lower sequence number (rcv 
13229786, old 13229787)
2014-03-07 10:59:20 <ERR> OSPF: Bad packet from 10.1.2.3 - authentication 
failed
2014-03-07 10:59:20 <TRACE> aclctrans: OSPF_auth: lower sequence number (rcv 
13229786, old 13229787)
2014-03-07 10:59:20 <ERR> OSPF: Bad packet from 10.1.2.3 - authentication 
failed
2014-03-07 10:59:20 <TRACE> aclctrans: OSPF_auth: lower sequence number (rcv 
13229786, old 13229787)
2014-03-07 10:59:20 <ERR> OSPF: Bad packet from 10.1.2.3 - authentication 
failed
2014-03-07 10:59:20 <TRACE> aclctrans: OSPF_auth: lower sequence number (rcv 
13229786, old 13229787)
2014-03-07 10:59:20 <ERR> OSPF: Bad packet from 10.1.2.3 - authentication 
failed
2014-03-07 10:59:20 <TRACE> aclctrans: OSPF_auth: lower sequence number (rcv 
13229786, old 13229787)
2014-03-07 10:59:20 <ERR> OSPF: Bad packet from 10.1.2.3 - authentication 
failed

We do not have any clue about where the decremented sequence number came from.
As this is an internal network and we have an helo interval of 5 second we can 
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 have 
bird 1.4.0. The problem seems not only bird generated as we also have from IPs 
which are router in our network.

-- 

Mit freundlichen Grüßen
---------------------------------
Daniel Wendler

Reply via email to