Show ip route with prefix-list and fastethernet 1/0 which working great !!!
C 200.200.200.0/24 is directly connected, Loopback3
1.0.0.0/30 is subnetted, 2 subnets
R 1.1.1.0 [120/1] via 172.29.1.1, 00:00:00, FastEthernet0/0
R 1.1.1.4 [120/1] via 172.29.1.1, 00:00:00, FastEthernet0/0
2.0.0.0/30 is subnetted, 2 subnets
C 2.2.2.0 is directly connected, Loopback0
C 2.2.2.4 is directly connected, Loopback1
100.0.0.0/24 is subnetted, 1 subnets
R 100.100.100.0 [120/1] via 172.29.1.1, 00:00:00, FastEthernet0/0
* 3.0.0.0/30 is subnetted, 1 subnets
R 3.3.3.8 [120/1] via 172.29.1.1, 00:00:00, FastEthernet0/0
*R 223.1.1.0/24 [120/1] via 172.30.1.2, 00:00:00, FastEthernet1/0
20.0.0.0/24 is subnetted, 1 subnets
C 20.20.20.0 is directly connected, Loopback2
172.29.0.0/30 is subnetted, 1 subnets
C 172.29.1.0 is directly connected, FastEthernet0/0
172.30.0.0/30 is subnetted, 1 subnets
C 172.30.1.0 is directly connected, FastEthernet1/0
10.0.0.0/24 is subnetted, 1 subnets
R 10.10.10.0 [120/1] via 172.29.1.1, 00:00:00, FastEthernet0/0
30.0.0.0/24 is subnetted, 1 subnets
R 30.30.30.0 [120/1] via 172.30.1.2, 00:00:00, FastEthernet1/0
R2#
Show ip route with the prefix-list and gateway which is not working as I
Planned.
C 200.200.200.0/24 is directly connected, Loopback3
1.0.0.0/30 is subnetted, 2 subnets
R 1.1.1.0 [120/1] via 172.29.1.1, 00:00:00, FastEthernet0/0
R 1.1.1.4 [120/1] via 172.29.1.1, 00:00:00, FastEthernet0/0
2.0.0.0/30 is subnetted, 2 subnets
C 2.2.2.0 is directly connected, Loopback0
C 2.2.2.4 is directly connected, Loopback1
100.0.0.0/24 is subnetted, 1 subnets
R 100.100.100.0 [120/1] via 172.29.1.1, 00:00:00, FastEthernet0/0
20.0.0.0/24 is subnetted, 1 subnets
C 20.20.20.0 is directly connected, Loopback2
172.29.0.0/30 is subnetted, 1 subnets
C 172.29.1.0 is directly connected, FastEthernet0/0
172.30.0.0/30 is subnetted, 1 subnets
C 172.30.1.0 is directly connected, FastEthernet1/0
10.0.0.0/24 is subnetted, 1 subnets
R 10.10.10.0 [120/1] via 172.29.1.1, 00:00:00, FastEthernet0/0
R2#
On 5/25/09, WW)W WWWW W <eshedalonie_at_gmail.com> wrote:
>
> Yeah, But its not getting 3.0.0.0/8 either from R1.
>
> from what I can see , this command blocks the prefix 3.0.0.0/8 from not
> matter what gateway, and blocks everything from the gateway that I
> mentioned.
>
> On 5/25/09, Divin Mathew John <divinjohn_at_gmail.com> wrote:
>>
>> hEY...
>>
>> READ
>>
http://www.cisco.com/en/US/docs/ios/12_1/iproute/command/reference/1rdrip.htm
l#wp1025003
>> ..
>>
>> See when u use the gateway keyword in the distribute list u basically tell
>> the RIP process(or any other IGP) whom should it get updates from. Here in
>> your config...
>> ip prefix-list NOT_FROM_R3 seq 5 deny 172.30.1.2/32
>> ip prefix-list NOT_FROM_R3 seq 10 permit 0.0.0.0/0 le 32
>> u denied R3. so it wont receive updates from R3.!
>>
>> Thanking You
>>
>> Yours Sincerely
>>
>> Divin Mathew John
>> divinjohn_at_gmail.com
>> divin_at_dide3d.com
>> http://www.dide3d.com
>> +91 9945430983
>> +91 9846697191
>> +974 5008916
>> PGP PUBLIC KEY BLOCK @ http://www.dide3d.com/divin_Public_PGP_key.txt
>> Sent from Bangalore, KA, India
>>
>> 2009/5/26 WW)W WWWW W <eshedalonie_at_gmail.com>
>>
>>> en I try with another command ->
Blogs and organic groups at http://www.ccie.net
Received on Mon May 25 2009 - 21:11:18 ART
This archive was generated by hypermail 2.2.0 : Mon Jun 01 2009 - 07:04:43 ART