From: Jorge Martinez (jorge_bgp@yahoo.com)
Date: Fri Aug 10 2007 - 19:39:04 ART
OK, the other thing you can do is to erase the RIP
configuration on both sides and then start it from
scratch ...
I have seen weird things when using authentication
over RIP specially,
--- Julian Rodriguez <jumaroyu@gmail.com> wrote:
> On 8/10/07, Julian Rodriguez <jumaroyu@gmail.com>
> wrote:
> >
> > Answers between lines...
> >
> >
> > On 8/10/07, Jorge Martinez <jorge_bgp@yahoo.com>
> wrote:
> > >
> > > Hello Julian,
> > >
> > > - have you tried getting rid on both sides of
> the
> > > authentication over RIP?
> >
> >
> > Yes I did, same result
> >
> > - have you tried using a different key-string on
> both
> > > sides, just as a test?
> >
> >
> > Yes, did that too, using plain text mode as well.
> >
> > Sometimes one leave a space at the end of the
> password
> > > and that will also be counted as a character ...
> >
> >
> > that was the first test, no luck.
> >
> >
> > > Hope any of this clues can help you ...
> > >
> > >
> > > --- Julian Rodriguez < jumaroyu@gmail.com>
> wrote:
> > >
> > > > This one has been killing me for the past
> couple of
> > > > days, I am working on
> > > > IEWB Core Lab 1 Task 4.5, following are the
> configs
> > > > on both BB2 and SW2,
> > > > which are supposed to use md5 to exchange RIP.
> I
> > > > verified the solution
> > > > because I couldn't find out what the problem
> was,
> > > > can't see the RIP routes
> > > > on SW2 anyways, but to my surprise my config
> was
> > > > exactly what the solution
> > > > stated. Any clues? I really don't see a way to
> put
> > > > the routes into SW2
> > > > routing table without changing the current
> config.
> > > >
> > > > BB2:
> > > >
> > > > interface FastEthernet0/0
> > > > description Ethernet to SW2 Fa0/24
> > > > ip address 192.10.1.254 255.255.255.0
> > > > ip rip authentication mode md5
> > > > ip rip authentication key-chain RIP
> > > > duplex auto
> > > > speed auto
> > > > ipv6 address 2001:192:10:1::254/64
> > > > ipv6 rip RIPng enable
> > > > ipv6 ospf 1 area 0
> > > >
> > > >
> > > > key chain RIP
> > > > key 1
> > > > key-string CISCO
> > > >
> > > > SW2:
> > > >
> > > > interface Vlan82
> > > > ip address 192.10.1.8 255.255.255.0
> > > > ip rip authentication mode md5
> > > > ip rip authentication key-chain RIP
> > > >
> > > > interface FastEthernet0/24
> > > > switchport access vlan 82
> > > >
> > > > key chain RIP
> > > > key 1
> > > > key-string CISCO
> > > >
> > > >
> > > > Troubleshooting OUPUTS:
> > > >
> > > >
> > > > Rack1SW2#ping 192.10.1.254
> > > >
> > > > Type escape sequence to abort.
> > > > Sending 5, 100-byte ICMP Echos to 192.10.1.254
> ,
> > > > timeout is 2 seconds:
> > > > !!!!!
> > > > Success rate is 100 percent (5/5), round-trip
> > > > min/avg/max = 1/2/8 ms
> > > > Rack1SW2#
> > > >
> > > > Rack1SW2#
> > > > 01:19:04: RIP: sending v2 update to 224.0.0.9
> via
> > > > Vlan82 ( 192.10.1.8)
> > > > 01:19:04: RIP: build update entries -
> suppressing
> > > > null update
> > > > Rack1SW2#
> > > > 01:19:32: RIP: sending v2 update to 224.0.0.9
> via
> > > > Vlan82 (192.10.1.8)
> > > > 01:19:32: RIP: build update entries -
> suppressing
> > > > null update
> > > > Rack1SW2#
> > > > Mar 1 01:25:45.707: %TCP-6-BADAUTH: No MD5
> digest
> > > > from 192.10.1.8(179) to
> > > > 192.10.1.254(14382) (RST)
> > > > Mar 1 01:25:49.707: %TCP-6-BADAUTH: No MD5
> digest
> > > > from 192.10.1.8(179) to
> > > > 192.10.1.254(14382) (RST)
> > > > Mar 1 01:25: 57.499: RIP: sending v2 update
> to
> > > > 224.0.0.9 via
> > > > FastEthernet0/0 ( 192.10.1.254)
> > > > Mar 1 01:25:57.499: RIP: build update entries
> -
> > > > suppressing null update
> > > >
> > > >
> > >
>
This archive was generated by hypermail 2.1.4 : Sat Sep 01 2007 - 11:32:10 ART