Group missing MD5 digest message types under the BGP_MD5_INCORRECT
notification, as I'm thinking it's virtually the same (i.e., missing
is approximatively the same as incorrect).
I've also noticed that the current configuration wouldn't match v6 peers,
so I'm correcting this on this occasion.
Coverage remained the same at 41.747% when pulling 116fba251d78fe05f13562a7cfe82fdaf12cd359 on bgp-md5-missing into 7ddf15473d36f3b591f114150af5842be932d6c1 on develop.
Group
missing MD5 digest
message types under the BGP_MD5_INCORRECT notification, as I'm thinking it's virtually the same (i.e., missing is approximatively the same as incorrect).I've also noticed that the current configuration wouldn't match v6 peers, so I'm correcting this on this occasion.