From: SFeldberg@xxxxxxxxxxxxx
Date: Fri Nov 09 2001 - 18:41:07 GMT-3
All of the information below is RIP v1. What I see from the debugs is that
the receiver can acertain the source IP of its neighbor
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 42.0.0.0 in 1 hops
from the broadcast that was sent out on the Ethernet.
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.2)
1d21h: network 42.0.0.0, metric 1
Rip V2 is different, as it multicasts updates:
hostname r2
router rip
version 2
network 40.0.0.0
network 42.0.0.0
2d00h: RIP: sending general request on Ethernet0 to 224.0.0.9
2d00h: RIP: received v2 update from 40.1.1.4 on Ethernet0
2d00h: 44.0.0.0/8 -> 0.0.0.0 in 1 hops
2d00h: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (40.1.1.2) -
suppressing null update
2d00h: RIP: received v2 update from 40.1.1.4 on Ethernet0
2d00h: 44.0.0.0/8 -> 0.0.0.0 in 1 hops
2d00h: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (40.1.1.2)
2d00h: 42.0.0.0/8 -> 0.0.0.0, metric 1, tag 0
2d00h: RIP: sending v2 update to 224.0.0.9 via Loopback0 (42.1.1.2)
2d00h: 40.0.0.0/8 -> 0.0.0.0, metric 1, tag 0
2d00h: 44.0.0.0/8 -> 0.0.0.0, metric 2, tag 0
2d00h: RIP: ignored v2 packet from 42.1.1.2 (sourced from one of our
addresses)
2d00h: RIP: received v2 request from 40.1.1.4 on Ethernet0
2d00h: RIP: sending update with long TTL
2d00h: RIP: sending v2 update to 40.1.1.4 via Ethernet0 (40.1.1.2)
2d00h: 42.0.0.0/8 -> 0.0.0.0, metric 1, tag 0
2d00h: RIP: received v2 update from 40.1.1.4 on Ethernet0
2d00h: 44.0.0.0/8 -> 0.0.0.0 in 1 hops
2d00h: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (40.1.1.2)
2d00h: 42.0.0.0/8 -> 0.0.0.0, metric 1, tag 0
2d00h: RIP: sending v2 update to 224.0.0.9 via Loopback0 (42.1.1.2)
2d00h: 40.0.0.0/8 -> 0.0.0.0, metric 1, tag 0
2d00h: 44.0.0.0/8 -> 0.0.0.0, metric 2, tag 0
2d00h: RIP: ignored v2 packet from 42.1.1.2 (sourced from one of our
addresses)
2d00h: RIP: received v2 update from 40.1.1.4 on Ethernet0
2d00h: 44.0.0.0/8 -> 0.0.0.0 in 1 hops
hostname r4
router rip
version 2
network 40.0.0.0
network 44.0.0.0
2d00h: RIP: received v2 request from 40.1.1.2 on Ethernet0
2d00h: RIP: sending update with long TTL
2d00h: RIP: sending v2 update to 40.1.1.2 via Ethernet0 (40.1.1.4)
2d00h: RIP: build update entries
2d00h: 44.0.0.0/8 via 0.0.0.0, metric 1, tag 0
2d00h: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (40.1.1.4)
2d00h: RIP: build update entries
2d00h: 44.0.0.0/8 via 0.0.0.0, metric 1, tag 0
2d00h: RIP: sending v2 update to 224.0.0.9 via Loopback0 (44.1.1.4)
2d00h: RIP: build update entries
2d00h: 40.0.0.0/8 via 0.0.0.0, metric 1, tag 0
2d00h: 42.0.0.0/8 via 0.0.0.0, metric 2, tag 0
2d00h: RIP: ignored v2 packet from 44.1.1.4 (sourced from one of our
addresses)
2d00h: RIP: received v2 update from 40.1.1.2 on Ethernet0
2d00h: 42.0.0.0/8 via 0.0.0.0 in 1 hops
2d00h: RIP: sending request on Ethernet0 to 224.0.0.9
2d00h: RIP: sending request on Loopback0 to 224.0.0.9
2d00h: RIP: ignored v2 packet from 44.1.1.4 (sourced from one of our
addresses)
2d00h: RIP: received v2 update from 40.1.1.2 on Ethernet0
2d00h: 42.0.0.0/8 via 0.0.0.0 in 1 hops
2d00h: RIP: sending v2 flash update to 224.0.0.9 via Ethernet0 (40.1.1.4)
2d00h: RIP: build flash update entries
2d00h: 44.0.0.0/8 via 0.0.0.0, metric 1, tag 0
2d00h: RIP: sending v2 flash update to 224.0.0.9 via Loopback0 (44.1.1.4)
2d00h: RIP: build flash update entries
2d00h: 40.0.0.0/8 via 0.0.0.0, metric 1, tag 0
2d00h: 42.0.0.0/8 via 0.0.0.0, metric 2, tag 0
2d00h: RIP: ignored v2 packet from 44.1.1.4 (sourced from one of our
addresses)
2d00h: RIP: received v2 update from 40.1.1.2 on Ethernet0
2d00h: 42.0.0.0/8 via 0.0.0.0 in 1 hops
2d00h: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (40.1.1.4)
2d00h: RIP: build update entries
2d00h: 44.0.0.0/8 via 0.0.0.0, metric 1, tag 0
2d00h: RIP: sending v2 update to 224.0.0.9 via Loopback0 (44.1.1.4)
2d00h: RIP: build update entries
2d00h: 40.0.0.0/8 via 0.0.0.0, metric 1, tag 0
2d00h: 42.0.0.0/8 via 0.0.0.0, metric 2, tag 0
2d00h: RIP: ignored v2 packet from 44.1.1.4 (sourced from one of our
addresses)
Updates for RIP v2 are sent to the address 224.0.0.9 reserved for "All RIP
v2 routers". Again, the address of the sender is captured by the receiver
from source address of the update packet.
r2(config)#router rip
r2(config-router)#nei 40.1.1.4
r2(config-router)#pass e0
2d00h: RIP: received v2 update from 40.1.1.4 on Ethernet0
2d00h: 44.0.0.0/8 -> 0.0.0.0 in 1 hops
2d00h: RIP: sending v2 update to 224.0.0.9 via Loopback0 (42.1.1.2)
2d00h: 40.0.0.0/8 -> 0.0.0.0, metric 1, tag 0
2d00h: 44.0.0.0/8 -> 0.0.0.0, metric 2, tag 0
2d00h: RIP: sending v2 update to 40.1.1.4 via Ethernet0 (40.1.1.2)
2d00h: 40.1.1.0/24 -> 0.0.0.0, metric 1, tag 0
2d00h: 42.0.0.0/8 -> 0.0.0.0, metric 1, tag 0
2d00h: RIP: ignored v2 packet from 42.1.1.2 (sourced from one of our
addresses)
r4(config)#router rip
r4(config-router)#nei 40.1.1.2
r4(config-router)#pass e0
2d00h: RIP: sending v2 update to 224.0.0.9 via Loopback0 (44.1.1.4)
2d00h: RIP: build update entries
2d00h: 40.0.0.0/8 via 0.0.0.0, metric 1, tag 0
2d00h: 42.0.0.0/8 via 0.0.0.0, metric 2, tag 0
2d00h: RIP: sending v2 update to 40.1.1.2 via Ethernet0 (40.1.1.4)
2d00h: RIP: build update entries
2d00h: 44.0.0.0/8 via 0.0.0.0, metric 1, tag 0
2d00h: RIP: ignored v2 packet from 44.1.1.4 (sourced from one of our
addresses)
2d00h: RIP: received v2 update from 40.1.1.2 on Ethernet0
2d00h: 40.1.1.0/24 via 0.0.0.0 in 1 hops
2d00h: 42.0.0.0/8 via 0.0.0.0 in 1 hops
2d00h: RIP: sending v2 update to 224.0.0.9 via Loopback0 (44.1.1.4)
2d00h: RIP: build update entries
2d00h: 40.0.0.0/8 via 0.0.0.0, metric 1, tag 0
2d00h: 42.0.0.0/8 via 0.0.0.0, metric 2, tag 0
2d00h: RIP: sending v2 update to 40.1.1.2 via Ethernet0 (40.1.1.4)
2d00h: RIP: build update entries
2d00h: 44.0.0.0/8 via 0.0.0.0, metric 1, tag 0
2d00h: RIP: ignored v2 packet from 44.1.1.4 (sourced from one of our
addresses)
2d00h: RIP: received v2 update from 40.1.1.2 on Ethernet0
2d00h: 40.1.1.0/24 via 0.0.0.0 in 1 hops
2d00h: 42.0.0.0/8 via 0.0.0.0 in 1 hops
As expected after examining the behavior of RIP v1, the addition of
neighbor and passive-interface statements removes the multicast updates
while the unicast updates to the neighbor remain.
Steve
"Wright,
Jeremy" To: "'SFeldberg@edeltacom.com'"
<JA_WRIGHT@adm <SFeldberg@edeltacom.com>
world.com> cc:
Subject: RE: Rip Neigbor statment
11/09/2001
04:22 PM
so if you enable rip version 2 between 2 routers and advertise your
networks(no neighbor statements) they will be learned dynamically but it
will be through broadcasts or after they are discovered it will be
unicasts??
-----Original Message-----
From: SFeldberg@edeltacom.com [mailto:SFeldberg@edeltacom.com]
Sent: Friday, November 09, 2001 12:51 PM
To: RB
Cc: ccielab; nobody@groupstudy.com
Subject: Re: Rip Neigbor statment
Before any neighbor statements are in place between RIP peers 40.1.1.2 and
40.1.1.4.
r4#debug ip rip
RIP protocol debugging is on
r4#
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (44.1.1.4)
1d21h: RIP: build update entries
1d21h: network 40.0.0.0 metric 1
1d21h: network 42.0.0.0 metric 2
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 42.0.0.0 in 1 hops
r4#conf t
Enter configuration commands, one per line. End with CNTL/Z.
r4(config)#router rip
r4(config-router)#nei 40.1.1.2
r4(config-router)#
After neighbor statement on R4 referencing R2:
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (44.1.1.4)
1d21h: RIP: build update entries
1d21h: network 40.0.0.0 metric 1
1d21h: network 42.0.0.0 metric 2
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 42.0.0.0 in 1 hops
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (44.1.1.4)
1d21h: RIP: build update entries
1d21h: network 40.0.0.0 metric 1
1d21h: network 42.0.0.0 metric 2
1d21h: RIP: sending v1 update to 40.1.1.2 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 42.0.0.0 in 1 hops
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (44.1.1.4)
1d21h: RIP: build update entries
1d21h: network 40.0.0.0 metric 1
1d21h: network 42.0.0.0 metric 2
1d21h: RIP: sending v1 update to 40.1.1.2 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 42.0.0.0 in 1 hops
Debug output on R2 with neighbor statement only configured on R4
1d21h: RIP: received v1 update from 40.1.1.4 on Ethernet0
1d21h: 44.0.0.0 in 1 hops
1d21h: RIP: received v1 update from 40.1.1.4 on Ethernet0
1d21h: 44.0.0.0 in 1 hops
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.2)
1d21h: network 42.0.0.0, metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (42.1.1.2)
1d21h: network 40.0.0.0, metric 1
1d21h: network 44.0.0.0, metric 2
1d21h: RIP: received v1 update from 40.1.1.4 on Ethernet0
1d21h: 44.0.0.0 in 1 hops
1d21h: RIP: received v1 update from 40.1.1.4 on Ethernet0
1d21h: 44.0.0.0 in 1 hops
r2#
r2(config)#router rip
r2(config-router)#nei 40.1.1.4
r2(config-router)#^Z
Debug output on R2 after both neighbor statements are in place
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.2)
1d21h: network 42.0.0.0, metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (42.1.1.2)
1d21h: network 40.0.0.0, metric 1
1d21h: network 44.0.0.0, metric 2
1d21h: RIP: sending v1 update to 40.1.1.4 via Ethernet0 (40.1.1.2)
1d21h: subnet 40.1.1.0, metric 1
1d21h: network 42.0.0.0, metric 1
1d21h: RIP: received v1 update from 40.1.1.4 on Ethernet0
1d21h: 44.0.0.0 in 1 hops
1d21h: RIP: received v1 update from 40.1.1.4 on Ethernet0
1d21h: 44.0.0.0 in 1 hops
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.2)
1d21h: network 42.0.0.0, metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (42.1.1.2)
1d21h: network 40.0.0.0, metric 1
1d21h: network 44.0.0.0, metric 2
1d21h: RIP: sending v1 update to 40.1.1.4 via Ethernet0 (40.1.1.2)
1d21h: subnet 40.1.1.0, metric 1
1d21h: network 42.0.0.0, metric 1
Debug output on R4 after both neighbor statements are in place
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 42.0.0.0 in 1 hops
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 40.1.1.0 in 1 hops
1d21h: 42.0.0.0 in 1 hops
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (44.1.1.4)
1d21h: RIP: build update entries
1d21h: network 40.0.0.0 metric 1
1d21h: network 42.0.0.0 metric 2
1d21h: RIP: sending v1 update to 40.1.1.2 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 42.0.0.0 in 1 hops
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 40.1.1.0 in 1 hops
1d21h: 42.0.0.0 in 1 hops
The answer to your question is that there is a unicast update that is
generated for the referenced neighbor AND the normal broadcast updates
continue as well.
Steve
"RB"
<slowgo@home. To: "ccielab"
<ccielab@groupstudy.com>
com> cc:
Sent by: Subject: Rip Neigbor statment
nobody@groups
tudy.com
11/09/2001
01:27 PM
Please
respond to
"RB"
I know that the neigbor statement in rip sends out unicast updates to that
neighbor, but does it also send no other updates? Let's say you had
several
routers on an ethernet segment with RIP running, and you used a neigbor
statement from a-b, does c no longer receive rip updates from a?
Thanks,
RBI
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:11 GMT-3