RE: RIP v2 Authentication not working

From: Chuck Mason (romason0916@xxxxxxxxxxx)
Date: Thu Jun 13 2002 - 02:10:14 GMT-3


   
Try sh key chain BB2 and for R1

I added a space in the key for R1. This show command is very handy for
tracking down those blanks that can get trapped in your keys.
r1#sh key chain r1
Key-chain r1:
    key 1 -- text "ccie "
        accept lifetime (always valid) - (always valid) [valid now]
        send lifetime (always valid) - (always valid) [valid now]

r3#sh key chain r3
Key-chain r3:
    key 1 -- text "ccie"
        accept lifetime (always valid) - (always valid) [valid now]
        send lifetime (always valid) - (always valid) [valid now]

You can see the blank in key 1 on r1.
HTH,
cm

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Emmanuel Oppong
Sent: Thursday, June 13, 2002 12:19 PM
To: ccielab@groupstudy.com
Subject: RIP v2 Authentication not working

Hi folks,

I have the following configs for authenticating routing updates between 2
RIP v2 routers: BB2 and r4. I thought this config should work fine. But it
doesn't. Without the authentication I receive routes between the 2 routers.
Debug shows that I have invalid authentication. What could be wrong. Any
ideas?

Router BB2:
key chain r4
 key 1
  key-string cisco4
!
interface TokenRing0
 ip rip authentication mode md5
 ip rip authentication key-chain r4
!

Router r4:
key chain bb2
 key 1
  key-string cisco4
!
interface TokenRing0
 ip rip authentication mode md5
 ip rip authentication key-chain bb2
!

BB2:
debug ip rip events
-----sample output----
06:26:23: RIP: ignored v2 packet from 204.205.5.1 (sourced from one of our
addresses)
06:26:25: RIP: ignored v2 packet from 172.16.40.4 (invalid authentication)



This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:32 GMT-3