Re: Prefix-list VS Access-list [7:53582]
I believe that it's the same. -- RFC 1149 Compliant. JohnZ wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Can I use access-list to produce the same effect as prefix-list ? Any thoughts on which is a better way to use in redistribution over other. I am just trying to find which one I should stick with. Thanks router rip redistribute ospf 1 network 135.11.0.0 default-metric 5 distribute-list prefix test out ospf 1 ip prefix-list test seq 5 deny 199.172.4.0/24 ip prefix-list test seq 10 deny 199.172.6.0/24 ip prefix-list test seq 15 deny 199.172.8.0/24 ip prefix-list test 20 permit 0.0.0.0/0 le 32 or router rip redistribute ospf 1 network 135.11.0.0 default-metric 5 distribute-list 10 out ospf 1 access-list 10 deny 199.172.4.0/24 access-list 10 deny 199.172.6.0/24 access-list 10 deny 199.172.8.0/24 access-list 10 permit any Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=53584t=53582 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Prefix-list VS Access-list [7:53582]
On Thu, 19 Sep 2002, JohnZ wrote: Can I use access-list to produce the same effect as prefix-list ? Any thoughts on which is a better way to use in redistribution over other. I am just trying to find which one I should stick with. Thanks ip prefix-list test seq 5 deny 199.172.4.0/24 ip prefix-list test seq 10 deny 199.172.6.0/24 ip prefix-list test seq 15 deny 199.172.8.0/24 ip prefix-list test 20 permit 0.0.0.0/0 le 32 Prefix lists can permit annoucements in a range of netmasks. For example, the following prefix-list entry will permit announcements of 192.168.1.0/24, or any prefix within that. ip prefix-list example seq 5 permit 192.168.1.0/24 le 32 I don't believe there's a way to do that using access-lists. The other major advantage is you can pull entries out of a sequence, and insert them without re-writing the entire prefix-list again. For example, 'no ip prefix-list example seq 10' will remove only sequence 10, rather than the entire prefix list. These two features however need to ba taken with a grain of salt. Firstly you may want explicit routing control rather than a blanket cover, and secondly configurations like this are usually built out of databases so you're not going to be manually inserting entries. Rgds, - I. -- Ian Henderson CCNA, CCNP Senior Network Engineer, Chime Communications Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=53592t=53582 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Prefix-list VS Access-list [7:53582]
Thanks Ian, I appreciate your answer and your help. Cheers, JZ Ian Henderson wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... On Thu, 19 Sep 2002, JohnZ wrote: Can I use access-list to produce the same effect as prefix-list ? Any thoughts on which is a better way to use in redistribution over other. I am just trying to find which one I should stick with. Thanks ip prefix-list test seq 5 deny 199.172.4.0/24 ip prefix-list test seq 10 deny 199.172.6.0/24 ip prefix-list test seq 15 deny 199.172.8.0/24 ip prefix-list test 20 permit 0.0.0.0/0 le 32 Prefix lists can permit annoucements in a range of netmasks. For example, the following prefix-list entry will permit announcements of 192.168.1.0/24, or any prefix within that. ip prefix-list example seq 5 permit 192.168.1.0/24 le 32 I don't believe there's a way to do that using access-lists. The other major advantage is you can pull entries out of a sequence, and insert them without re-writing the entire prefix-list again. For example, 'no ip prefix-list example seq 10' will remove only sequence 10, rather than the entire prefix list. These two features however need to ba taken with a grain of salt. Firstly you may want explicit routing control rather than a blanket cover, and secondly configurations like this are usually built out of databases so you're not going to be manually inserting entries. Rgds, - I. -- Ian Henderson CCNA, CCNP Senior Network Engineer, Chime Communications Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=53593t=53582 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Prefix-list VS Access-list [7:53582]
Prefix lists can permit annoucements in a range of netmasks. For example, the following prefix-list entry will permit announcements of 192.168.1.0/24, or any prefix within that. ip prefix-list example seq 5 permit 192.168.1.0/24 le 32 I don't believe there's a way to do that using access-lists. actually, i think that the following would do the same: access-list 101 permit ip 192.168.1.0 0.0.0.255 255.255.255.0 0.0.0.255 don't have any way of testing right now... anyone confirm/deny? Thanks, Charles -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ian Henderson Sent: Wednesday, September 18, 2002 8:56 PM To: [EMAIL PROTECTED] Subject: Re: Prefix-list VS Access-list [7:53582] On Thu, 19 Sep 2002, JohnZ wrote: Can I use access-list to produce the same effect as prefix-list ? Any thoughts on which is a better way to use in redistribution over other. I am just trying to find which one I should stick with. Thanks ip prefix-list test seq 5 deny 199.172.4.0/24 ip prefix-list test seq 10 deny 199.172.6.0/24 ip prefix-list test seq 15 deny 199.172.8.0/24 ip prefix-list test 20 permit 0.0.0.0/0 le 32 Prefix lists can permit annoucements in a range of netmasks. For example, the following prefix-list entry will permit announcements of 192.168.1.0/24, or any prefix within that. ip prefix-list example seq 5 permit 192.168.1.0/24 le 32 I don't believe there's a way to do that using access-lists. The other major advantage is you can pull entries out of a sequence, and insert them without re-writing the entire prefix-list again. For example, 'no ip prefix-list example seq 10' will remove only sequence 10, rather than the entire prefix list. These two features however need to ba taken with a grain of salt. Firstly you may want explicit routing control rather than a blanket cover, and secondly configurations like this are usually built out of databases so you're not going to be manually inserting entries. Rgds, - I. -- Ian Henderson CCNA, CCNP Senior Network Engineer, Chime Communications Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=53600t=53582 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
