Re: Named acl's not allowed

From: Kirk Graham (kgraham@instructors.net)
Date: Sat Nov 13 2004 - 14:46:02 GMT-3


It annoys the heck out of me too. Here's another place.

>Router#debug ip packet ?
> <1-199> Access list
> <1300-2699> Access list (expanded range)
> detail Print more debugging detail
> <cr>
>

Just because of that, I don't use Named ACLs unless required.

And it doesn't matter anyway, since you can now edit numbered ACLs with the
named ACL format...

>Router(config)#ip access-list standard ?
> <1-99> Standard IP access-list number
> <1300-1999> Standard IP access-list number (expanded range)
> WORD Access-list name
>

--kg

At 11:34 AM 11/13/2004, ccie2be wrote:
>Hi guys,
>
>I prefer to use named acl's whenever possible. But, as I do practice labs, I
>sometimes find that after I've created the named acl and go to apply it,
>that's not allowed. I have to still use a numbered acl. And, I'm always
>annoyed when that happens. I bet this happens to others as well.
>
>Off hand, I can list 2 places named acl's aren't allowed.
>
>1) On vty lines with the access-class command
>
>2) When defining interesting traffic for isdn in the dialer-list command.
>
>
>I know there are other places which still don't allow named acl's, but I can't
>think of them at the moment.
>
>Besides the 2 instances above, does anybody know where else named acl's can't
>be used?
>
>Thanks, Tim
>
>_______________________________________________________________________
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Thu Dec 02 2004 - 06:57:43 GMT-3