Re: RIP route filtering using Extended ACL

From: Fahad Khan (fahad.khan@gmail.com)
Date: Tue Jul 22 2008 - 04:38:17 ART

Why aint you using Prefix-list? use Prefix-lists for defining "prefix" and
"gateway",

ip prefix-list prefix seq 5 deny 150.1.7.0/24
ip prefix-list prefix seq 5 permit 0.0.0.0/0 le 32
ip prefix-list gw seq 5 permit 155.10.1/32

distribute-list prefix prefix gateway gw in serial0

I think this will meet your requirements

Thanks and regards,

On Mon, Jul 21, 2008 at 11:26 PM, Huan Pham <Huan.Pham@peopletelecom.com.au>
wrote:

> Hi GS,
>
> I can not find the guide on the use of extended ACL to filter RIP
> routes. May someone please point me the link to this section. Many
> thanks.
>
> The following config is from a vendor workbook. It's to prevent the
> route 150.1.7.0/24 learnt via router 155.1.0.1 off interface Serial0.
>
> access-list 199 deny ip host 155.1.0.1 host 150.1.7.0
> access-list 199 permit ip any any
>
> router rip
> version 2
> network 150.1.0.0
> network 155.1.0.0
> distribute-list 199 in Serial0
> no auto-summary
>
>
> I usually make mistake with creating extended ACL for this purpose. I do
> tend to put subnet route first (source address portion), and the gateway
> after (destination address). The right ACL should be created in the
> reverse order, as above. I can not find relevant info in the RIP
> configuration guide, nor in command reference. Help in understanding
> this command is appreciated.
>
>
> Huan,
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
> 

-- 
*FAHAD KHAN

BE Computer Systems NED,

CCNA,CCDA,CCNP,FOUNDFE,CLSE,QOS,JNCIA,JNCIS,MCP,CCIE (Written)

Systems Support Engineer, Premier Systems (Pvt) limited,

Karachi, Pakistan

92-321-2370510.*

This archive was generated by hypermail 2.1.4 : Mon Aug 04 2008 - 06:11:56 ART