PROTECTED] On
Behalf Of Scott Morris
Sent: Sunday, August 21, 2005 9:21 AM
To: 'Tom Sanders'; [EMAIL PROTECTED]
Subject: RE: Rip again!
How about the source IP?
RIP v1 is sent to 255.255.255.255 broadcast. RIPv2 is sent
to 224.0.0.9 multicast. Both are local-link only, so won'
MAIL PROTECTED]
> Subject: RE: Rip again!
>
>
> How about the source IP?
>
> RIP v1 is sent to 255.255.255.255 broadcast. RIPv2 is sent
> to 224.0.0.9 multicast. Both are local-link only, so won't
> go THROUGH a router. The sending source IP will tell you
>
gain, Cisco world you can use
"no validate-update-source" to override this check)
But that gives you a tracking method on packets.
Scott
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom
Sanders
Sent: Sunday, August 21, 2005 12:13 PM
To: [
Hi,
There isnt IMO a way in RIP to identify the source of the RIP packet
(the way we have Router ID in OSPF, system ID in ISIS, etc.)
Now assume we have 2 vlans defined on an ethernet. Thus we would have
two IP interfaces, 1.1.1.1/24 and 2.2.2.2/24 and both using the same
physical interface. RIP
