Differences

This shows you the differences between two versions of the page.

--- training:sanog32:6-securing-bgp [2018/07/20 08:12] – created philip
+++ training:sanog32:6-securing-bgp [2018/08/06 19:19] (current) – [Configure passwords on the iBGP sessions] philip
@@ Line 26: / Line 26: @@
 Watch the router logs – with the BGP session neighbour changes being logged, any mismatch in the password should be easy to spot. A missing password on one side of the BGP session will result in the neighbouring router producing these errors:
+  %TCP-6-BADAUTH: No MD5 digest from 2001:18:0:10::1(54614) to 2001:18:0:10::(179)
-  %TCP-6-BADAUTH: No MD5 digest from 3.3.3.3:179 to 2.2.2.2:11272
+  %TCP-6-BADAUTH: No MD5 digest from 2001:18:0:10::1(54614) to 2001:18:0:10::(179)
-  %TCP-6-BADAUTH: No MD5 digest from 3.3.3.3:179 to 2.2.2.2:11272
+  %TCP-6-BADAUTH: No MD5 digest from 2001:18:0:10::1(54614) to 2001:18:0:10::(179)
-  %TCP-6-BADAUTH: No MD5 digest from 3.3.3.3:179 to 2.2.2.2:11272
 whereas a mismatch in the configured passwords will result in these messages:
+  %TCP-6-BADAUTH: Invalid MD5 digest from 2001:18:0:10::1(54614) to 2001:18:0:10::(179)
-  %TCP-6-BADAUTH: Invalid MD5 digest from 3.3.3.3:11024 to 2.2.2.2:179
+  %TCP-6-BADAUTH: Invalid MD5 digest from 2001:18:0:10::1(54614) to 2001:18:0:10::(179)
-  %TCP-6-BADAUTH: Invalid MD5 digest from 3.3.3.3:11024 to 2.2.2.2:179
+  %TCP-6-BADAUTH: Invalid MD5 digest from 2001:18:0:10::1(54614) to 2001:18:0:10::(179)
-  %TCP-6-BADAUTH: Invalid MD5 digest from 3.3.3.3:11024 to 2.2.2.2:179