From: Chris Allen (chris.allen@xxxxxxxxxxxx)
Date: Thu Aug 02 2001 - 00:38:14 GMT-3
What do you have for the interface config? Should be (see below) on both
serial interfaces.
ip rip authentication key-chain annu
ip rip authentication mode md5
If you have that correct??? Must be a bug!
chris
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Annu
Sent: Wednesday, August 01, 2001 11:09 PM
To: ccielab@groupstudy.com
Cc: annu_roopa@yahoo.com
Subject: Weird RIP Authentication errors (repost)
Group,
I am posting this once again..did not hear anything
maybe its too preliminary stuff for the group.I have
checked archives on this.
In anticipation.Thanks
Annu
> Gurus,
>
> The following config is giving me Authentication
> errors. I have tried but in vain to confirm why ( I
> feel it could be the IOS version on R1) ? If anyone
> is aware or come across this please let me know .The
> connectivity is as follows - (Refer page 222 Jeff
> doyle for fig only)
>
>
> r2 -------| |---r3
> | .1 .2 |
> |---r1 ---wan----r8-----|
> | 192.168.3.0/24 |---r7
r4------|
>
>
> r2-r4-r1 are on Ethernet 192.168.2.0/27
> r1-----r8 wan link is 192.168.3.0 /24
> r8---r3---r7 are on Ethernet 192.168.4.0/192.168.5.0
> /27
>
> ------------------
> R1 is running version 1 RIP with r2/r4.
> R1 is running version2 RIP with R8 with plain text
> authentication.
> R8 is running RIPV2 with R3 and with authentication
> and Rip v1 with R7.
>
> I am getting invalid authen errors at R1. I have
> checked for white space/case and also key #. The
> following are the config and debug messages at R1/R8
> .
> There is no problem between R8 and R3.
> ---------------------
> R1
> key chain annu
> key 1
> key-string pass
>
> r1#show key chain
> Key-chain annu:
> key 1 -- text "pass"
> accept lifetime (always valid) - (always
> valid) [valid now]
> send lifetime (always valid) - (always
> valid)
> [valid now]
>
> r1#debug ip packet
> RIP: received v1 update from 192.168.2.193 on
> TokenRing0
> 192.168.2.128 in 1 hops
> RIP: ignored v2 packet from 192.168.3.2 (invalid
> authentication)
> RIP: sending v2 update to 224.0.0.9 via Serial3
> (192.168.3.1)
> 192.168.2.0/24 -> 0.0.0.0, metric 1, tag 0
> RIP: sending v1 update to 255.255.255.255 via
> TokenRing0 (192.168.2.194)
> network 192.168.3.0, metric 1
> RIP: ignored v2 packet from 192.168.3.2 (invalid
> authentication)
> RIP: received v1 update from 192.168.2.195 on
> TokenRing0
> 192.168.2.96 in 1 hops
>
> #show ver
> IOS (tm) 4000 Software (C4000-J-M), Experimental
> Version 11.3(19971029:195120) [
> iwu-pim_v2_f.BLD 1128]
> Synced to mainline version: 11.3(0.9)P
>
> ---------
> R8 router
> key chain annu
> key 1
> key-string pass
>
> r8#show key chain
> Key-chain annu:
> key 1 -- text "pass"
> accept lifetime (always valid) - (always
> valid) [valid now]
> send lifetime (always valid) - (always
> valid)
> [valid now]
>
> r8#debug ip packet
> 00:15:52: RIP: received packet with text
> authentication pass
> 00:15:52: RIP: received v2 update from 192.168.4.1
> on
> Ethernet0
> 00:15:52: 192.168.5.0/24 -> 0.0.0.0 in 1 hops
> 00:15:52: 192.168.2.0/24 -> 0.0.0.0 in 16 hops
> (inaccessible)
> 00:15:52: RIP: received packet with text
> authentication pass
> 00:16:04: RIP: ignored v2 packet from 192.168.3.1
> (invalid authentication)
> 00:16:09: RIP: sending v1 update to 255.255.255.255
> via Ethernet0 (192.168.4.3)
> 00:16:09: network 192.168.3.0, metric 1
> 00:16:09: RIP: sending v2 update to 224.0.0.9 via
> Ethernet0 (192.168.4.3)
> 00:16:09: 192.168.3.0/24 -> 0.0.0.0, metric 1,
> tag 0
> 00:16:09: RIP: sending v1 update to 255.255.255.255
> via Ethernet0 (192.168.5.129
>
> #show ver
> Cisco Internetwork Operating System Software
> IOS (tm) 2500 Software (C2500-JS56I-L), Version
> 12.0(8), RELEASE SOFTWARE (fc1)
> Copyright (c) 1986-1999 by cisco Systems, Inc.
>
> My feeling is it is the version at Router R1.
> Thanks in advance for the help.
>
> Annu.
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:43 GMT-3