Re: prefix and acl

Question is very clear and it is not required to waste your time ellabarate
it unnessasaraly

On Monday, June 25, 2012, Hasse wrote:

> Thanks Narbik, I did that one late Sunday :) I am doing well in the
> Advanced WB.
> I am planning to finnish them before bootcamp in Burbank Julie-Aug
>
> See you there. Looking forward to the new bootcamp.
>
>
>
> 2012/6/25 Narbik Kocharians <narbikk_at_gmail.com <javascript:;>>:
> > Hasse,
> > There is a much better section for Prefix-list in the "Advanced CCIE
> Routing
> > and Switching 4.0". That book (Soup to Nuts), is a very old book.
> >
> >
> > On Sun, Jun 24, 2012 at 2:57 PM, Hasse <eriksson.hans_at_gmail.com> wrote:
> >>
> >> Thanks all,
> >>
> >> John I am just playing with prefix and access-lists. I was inspiried
> >> by some WB I am doing.
> >> I did find this exercise in Narbiks free workbook (Soup to nuts) its
> >> available via Micronicstraning
> >> I was week on prefix-list before but not now :)
> >>
> >> Then I did extend this exercises and was thinking, how far can a ACL
> >> or Extended ACL take me.
> >> Can I solve this with one liner ACL standard or extended. Pushing the
> >> limits. I was playing around.
> >>
> >> Daniel and Sarad thanks.
> >>
> >> Topology
> >>
> >> R1---------------R2
> >>
> >> Router 2 recive following from R1 via RIP, I have filter those routes
> >> with different prefix-lists,
> >>
> >> Ex, only permit A network that are not subnetted.
> >> ip prefix-list 0.0.0.0/1 ge 8 le 8
> >>
> >> Ex, only permit B network that are not subnetted.
> >> ip prefix-list 128.0.0.0/2 ge 16 le 16
> >>
> >> Ex, only permit C network that are not subnetted.
> >> ip prefix-list 192.0.0.0/3 ge 24 le 24
> >>
> >> Ex, only permit A network that are or are not subnetted.
> >> ip prefix-list 0.0.0.0/1 ge 8 le 16
> >>
> >> etc..
> >>
> >> All route received from R1 via RIP
> >>
> >> R2# show ip rou rip
> >> R 1.0.0.0/8 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> R 2.0.0.0/8 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> R 3.0.0.0/8 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> R 223.1.1.0/24 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> 4.0.0.0/16 is subnetted, 1 subnets
> >> R 4.4.0.0 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> R 191.1.0.0/16 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> 5.0.0.0/24 is subnetted, 1 subnets
> >> R 5.5.5.0 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> R 200.1.1.0/24 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> 6.0.0.0/26 is subnetted, 1 subnets
> >> R 6.6.6.0 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> R 128.1.0.0/16 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> R 125.0.0.0/8 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> R 131.1.0.0/16 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> 193.1.1.0/25 is subnetted, 1 subnets
> >> R 193.1.1.0 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> 132.1.0.0/24 is subnetted, 1 subnets
> >> R 132.1.1.0 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> R 192.1.1.0/24 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> 133.1.0.0/25 is subnetted, 1 subnets
> >> R 133.1.1.0 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> R 195.1.1.0/24 [120/1] via 10.1.12.1, 00:00:07, FastEthernet0/0
> >> 194.1.1.0/26 is subnetted, 1 subnets

Blogs and organic groups at http://www.ccie.net
Received on Mon Jun 25 2012 - 19:43:46 ART