From: Sachin D (networker.ccie@gmail.com)
Date: Sun Sep 28 2008 - 08:39:11 ART
You are receiving the reply because you are pinging the broadcast address of
subnet 192.168.20.48/29 hence you are getting the reply from loopback0 of
R2. Here is the debug ip packet detail on R2
*Sep 28 11:41:05.111: IP: s=192.168.20.33 (FastEthernet0/0), *d=
192.168.20.48 (Loopback0*), len 100, rcvd 5
*Sep 28 11:41:05.111: ICMP: echo reply sent, src 192.168.20.34, dst
192.168.20.33
Regards
Sachin
On Sun, Sep 28, 2008 at 4:54 PM, Mohamed El Henawy <m.henawy@link.net>wrote:
> Hello ,
>
> i did the same setup and got the /32 as well strange that it doesnt have
> entry for it in R2
>
> *Mar 1 00:04:30.247: RIP-DB: redist 192.168.20.48/29(metric<http://192.168.20.48/29%28metric>0, last interface Loopback0) to RIP
> *Mar 1 00:04:30.247: RIP-DB: Get redist for network 192.168.20.48
> *Mar 1 00:04:30.247: RIP-DB: adding 192.168.20.48/29 (metric 0) via
> 0.0.0.0 on Loopback0 to RIP database
> *Mar 1 00:04:30.251: RIP-DB: add 192.168.20.48/29 (metric 0) via 0.0.0.0on Loopback0 (donot_age)
> *Mar 1 00:04:30.259: RIP-DB: Adding new rndb entry 192.168.20.48/29
>
> On R1
>
> *Mar 1 00:06:34.607: RIP-DB: network_update with 192.168.20.48/24succeeds
> *Mar 1 00:06:34.611: RIP-DB: adding 192.168.20.48/0 (metric 1) via
> 192.168.20.34 on FastEthernet0/0 to RIP database
> *Mar 1 00:06:34.615: RIP-DB: add 192.168.20.48/32 (metric 1) via
> 192.168.20.34 on FastEthernet0/0
> *Mar 1 00:06:34.615: RIP-DB: Adding new rndb entry 192.168.20.48/32
>
>
> R1#ping 192.168.20.48
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 192.168.20.48, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 8/27/80 ms
> R1#
>
> R2#
> *Mar 1 00:20:07.755: ICMP: echo reply sent, src 192.168.20.34, dst
> 192.168.20.33
> *Mar 1 00:20:07.807: ICMP: echo reply sent, src 192.168.20.34, dst
> 192.168.20.33
> *Mar 1 00:20:07.831: ICMP: echo reply sent, src 192.168.20.34, dst
> 192.168.20.33
> *Mar 1 00:20:07.835: ICMP: echo reply sent, src 192.168.20.34, dst
> 192.168.20.33
> *Mar 1 00:20:07.847: ICMP: echo reply sent, src 192.168.20.34, dst
> 192.168.20.33
>
> R2#ping 192.168.20.48
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 192.168.20.48, timeout is 2 seconds:
> .....
>
> Regards ,
>
>
>
>
> ----- Original Message ----- From: "Vibeesh S" <vibselva@gmail.com>
> To: "Cisco certification" <ccielab@groupstudy.com>; "Vibeesh S" <
> vibselva@gmail.com>
> Sent: Sunday, September 28, 2008 9:50 AM
> Subject: Routing Table for RIP ver 1
>
>
>
> Hi All,
>>
>> I have two router connected back to back. I just started configuring rip
>> on
>> them. I got a lil confused by seeing the route table.
>> I want to know how the subnet masks are being shown when i am using ver1
>> of
>> rip. *[192.168.20.48/32 ]*
>> I have been practicing a lil while now & my head is aching, am not able to
>> reason out. It will be nice if somebody can help me out here.
>>
>>
>> R1 (f0/0) ---------------------------------- (f0/0) R2
>>
>> R1Config
>> --------------
>> interface Loopback0
>> ip address 192.168.20.129 255.255.255.224
>> !
>> interface Loopback1
>> ip address 192.168.20.65 255.255.255.224
>> !
>> interface FastEthernet0/0
>> ip address 192.168.20.33 255.255.255.224
>> duplex auto
>> speed auto
>> !
>> !
>> router rip
>> network 192.168.20.0
>> version 1
>>
>>
>> R2 Config
>> --------------
>> interface Loopback0
>> ip address 192.168.20.49 255.255.255.248
>> !
>> interface Loopback1
>> ip address 192.168.20.41 255.255.255.248
>> !
>> interface FastEthernet0/0
>> ip address 192.168.20.34 255.255.255.248
>> duplex auto
>> speed auto
>> !
>> interface FastEthernet0/1
>> no ip address
>> shutdown
>> duplex auto
>> speed auto
>> !
>> router rip
>> version 1
>> network 192.168.20.0
>>
>>
>> R1 show ip route
>> -------------------------
>> Gateway of last resort is not set
>>
>> 192.168.20.0/24 is variably subnetted, 5 subnets, 2 masks
>> C 192.168.20.64/27 is directly connected, Loopback1
>> R 192.168.20.48/32 [120/1] via 192.168.20.34, 00:00:01,
>> FastEthernet0/0
>> R 192.168.20.40/32 [120/1] via 192.168.20.34, 00:00:01,
>> FastEthernet0/0
>> C 192.168.20.32/27 is directly connected, FastEthernet0/0
>> C 192.168.20.128/27 is directly connected, Loopback0
>>
>> R1 Deb ip rip
>> --------------------
>>
>> R1#debug ip rip
>> RIP protocol debugging is on
>> *Mar 1 00:03:49.935: RIP: sending v1 update to 255.255.255.255 via
>> FastEthernet0/0 (192.168.20.33)
>> *Mar 1 00:03:49.935: RIP: build update entries
>> *Mar 1 00:03:49.935: subnet 192.168.20.64 metric 1
>> *Mar 1 00:03:49.939: subnet 192.168.20.128 metric 1
>> *Mar 1 00:03:58.463: RIP: sending v1 update to 255.255.255.255 via
>> Loopback1 (192.168.20.65)
>> *Mar 1 00:03:58.463: RIP: build update entries
>> *Mar 1 00:03:58.463: subnet 192.168.20.32 metric 1
>> *Mar 1 00:03:58.463: subnet 192.168.20.40 metric 2
>> *Mar 1 00:03:58.467: subnet 192.168.20.48 metric 2
>> *Mar 1 00:03:58.467: subnet 192.168.20.128 metric 1
>> *Mar 1 00:04:00.371: RIP: sending v1 update to 255.255.255.255 via
>> Loopback0 (192.168.20.129)
>> *Mar 1 00:04:00.371: RIP: build update entries
>> *Mar 1 00:04:00.371: subnet 192.168.20.32 metric 1
>> *Mar 1 00:04:00.375: subnet 192.168.20.40 metric 2
>> *Mar 1 00:04:00.375: subnet 192.168.20.48 metric 2
>> *Mar 1 00:04:00.375: subnet 192.168.20.64 metric 1
>> *Mar 1 00:04:00.775: RIP: received v1 update from 192.168.20.34 on
>> FastEthernet0/0
>> *Mar 1 00:04:00.775: 192.168.20.40 in 1 hops
>> *Mar 1 00:04:00.779: 192.168.20.48 in 1 hops
>> R1#
>> R1#u all
>>
>>
>> Thanks,
>> Vibeesh
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sat Oct 04 2008 - 09:26:20 ART