Re: RIP authentication / BADAUTH

From: William Walla (wwalla@gmail.com)
Date: Thu Sep 28 2006 - 13:55:54 ART


not sure that is a RIP error there. I see that too, but its related to preconfigured BGP on that other side.
Rip is probably fine, I would verify with a rip debug.
-----Original Message-----
From: Udo <ccie_groupstudy@yahoo.de>
Date: Thursday, Sep 28, 2006 10:03 am
Subject: Re: RIP authentication / BADAUTH

Hi,
is it possible that there is a bgp peer configured ?
one side like to authenticate and the other not ?

"%TCP-6-BADAUTH: No MD5 digest from 192.10.1.8(179)
port 179 means BGP !?

greetz
udo

Am Donnerstag, den 28.09.2006, 10:19 +0200 schrieb Frank:
 Hi,
 
 two routers talking RIP with MD5 authentication and sometime the message
 "%TCP-6-BADAUTH: No MD5 digest from 192.10.1.8(179) to
 192.10.1.254(11017) (RST)" appears in the log of one router. The other
 one is fine. Sometime it seems, that there is a mismatch in
 Authentication. But not always.
 Has someone an idea? Running c2500-is-l.122-8.T on the router.
 
 Frank
 
 
 Both are configured like this:
 
 interface Vlan28
  ip address 192.10.1.8 255.255.255.0
  ip rip authentication mode md5
  ip rip authentication key-chain RIP
 
 
 interface Ethernet0
  ip address 192.10.1.254 255.255.255.0
  ip rip authentication mode md5
  ip rip authentication key-chain RIP
 
 
 
 Mar 1 00:04:44.511: RIP: received packet with MD5 authentication
 Mar 1 00:04:44.511: RIP: received v2 update from 192.10.1.8 on Ethernet0
 Mar 1 00:04:44.515: 150.1.3.3/32 via 0.0.0.0 in 1 hops
 Mar 1 00:04:44.519: 150.1.8.0/24 via 0.0.0.0 in 1 hops
 Mar 1 00:04:44.523: 187.1.3.0/24 via 0.0.0.0 in 1 hops
 Mar 1 00:04:44.639: %TCP-6-BADAUTH: No MD5 digest from 192.10.1.8(179)
 to 192.10.1.254(11017) (RST)
 Mar 1 00:04:47.263: RIP: sending v2 update to 224.0.0.9 via Ethernet0
 (192.10.1.254)
 Mar 1 00:04:47.267: RIP: build update entries
 Mar 1 00:04:47.271: 205.90.31.0/24 via 0.0.0.0, metric 7, tag 0
 Mar 1 00:04:47.275: 220.20.3.0/24 via 0.0.0.0, metric 7, tag 0
 Mar 1 00:04:47.279: 222.22.2.0/24 via 0.0.0.0, metric 7, tag 0
 Mar 1 00:04:48.635: %TCP-6-BADAUTH: No MD5 digest from 192.10.1.8(179)
 to 192.10.1.254(11017) (RST)
 Mar 1 00:04:56.635: %TCP-6-BADAUTH: No MD5 digest from 192.10.1.8(179)
 to 192.10.1.254(11017) (RST)
 Mar 1 00:05:11.291: RIP: received packet with MD5 authentication
 Mar 1 00:05:11.291: RIP: received v2 update from 192.10.1.8 on Ethernet0
 Mar 1 00:05:11.295: 150.1.3.3/32 via 0.0.0.0 in 1 hops
 Mar 1 00:05:11.299: 150.1.8.0/24 via 0.0.0.0 in 1 hops
 Mar 1 00:05:11.303: 187.1.3.0/24 via 0.0.0.0 in 1 hops
 Mar 1 00:05:14.511: RIP: sending v2 update to 224.0.0.9 via Ethernet0
 (192.10.1.254)
 Mar 1 00:05:14.515: RIP: build update entries



This archive was generated by hypermail 2.1.4 : Sun Oct 01 2006 - 16:55:41 ART