From: Fabrice Bobes (study@6colabs.com)
Date: Sat Jan 11 2003 - 23:42:29 GMT-3
Mark,
My understanding is that Classical IP and ARP over ATM (RFC 1577)
doesn't support Multicast.
RIP v2 multicasts its updates and this shouldn't work on CLIP over ATM.
This is also true for EIGRP for example. RIP will work with CLIP if it
unicasts its updates instead of multicasting them. Try using a neighbor
statement and this should fix the problem.
I hope this is the answer you were looking for.
Thanks,
Fabrice
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Mark Knellinger
Sent: Saturday, January 11, 2003 1:33 PM
To: ccielab@groupstudy.com
Subject: LAB 24 - ATM & RIP - arp-server problem
On lab 24 R13 and R14 are connected via Atm using R14 as an arp-server.
I
cannot get R14 to receive RIP v1 or 2 updates from R13. Its my
understand
that broadcasts and multicasts are delivered to all destinations from
the
arp-server. Therefore R14 gets the multicast update from its own source
address of 172.150.150.14 and drops the packet. The supplied
configurations
don't reflect any changes to rip or the ATM interface from my
configuration.
How did the final configurations for R13 and R14 actually work? If I
drop
the arp server and config map-lists across the PVC everything is fine.
Any
help is appreciated.
Here's the error message:
00:22:23: RIP: ignored v2 packet from 172.150.150.14 (sourced from one
of
our addresses)
Thanks in advance,
Mark
.
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:47 GMT-3