From: WorkerBee (ciscobee@gmail.com)
Date: Wed Oct 11 2006 - 13:19:33 ART
I saw that MD5 error coming from 140.1.14.4 port 179 BGP peering not RIP.
Probably that router 140.1.14.4 is also running off some other routing
protocol beside
RIP. Check it out.
On 10/11/06, Keith Bizzell <mkbcoolman@gmail.com> wrote:
> I'm seeing a strange issue with RIP. This showed up on IE Core 1 between R1
> and R4. It's a simple RIP authentication using MD5. I recieve all my
> routes on R1 from R4, but this error keeps popping up. R1 is a 2611XM
> running 12.4 advanced enterprise. I think this is just a bug, but I'm not
> sure. From the output below, you can see RIP is working:
>
> *Mar 2 23:16:40.485: RIP: sending v2 update to 224.0.0.9 via
> FastEthernet0/0 (140.1.14.1)
> *Mar 2 23:16:40.485: RIP: Update contains 1 routes
> *Mar 2 23:16:40.485: RIP: Update queued
> *Mar 2 23:16:40.485: RIP: Update sent via FastEthernet0/0
> Rack1R1(config-router)#
> *Mar 2 23:16:45.998: %TCP-6-BADAUTH: No MD5 digest from 140.1.14.4(179) to
> 140.1.14.1(47046) (RST)
> Rack1R1(config-router)#
> *Mar 2 23:16:48.230: RIP: received v2 update from 140.1.14.4 on
> FastEthernet0/0
> *Mar 2 23:16:48.230: RIP: Update contains 18 routes
>
> Any ideas on why I'm getting that bad auth?
>
> Thanks,
> Keith
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Nov 01 2006 - 07:29:05 ART