From: akyccie (akyccie@gmail.com)
Date: Wed Aug 27 2008 - 15:28:46 ART
I guess even if you put the return traffic in ACL. I don't think that helps
here becuase policy will only look for the traffic going out of that interface
not incoming.
----- Original Message -----
From: Igor M.
To: akyccie ; Rick Mur
Cc: ccielab@groupstudy.com
Sent: Tuesday, August 26, 2008 2:08 AM
Subject: Re: CBWFQ
You are dealing with tcp traffic, so if you adjust your acl to look
for return traffic to R2 you should be able to apply the policy in the
outbound direction on R1
----------------------
I.M., M.Eng. P.Eng.
Network Architect
CI Investments
----------------------
--- On Mon, 8/25/08, Rick Mur <rick.mur@gmail.com> wrote:
From: Rick Mur <rick.mur@gmail.com>
Subject: Re: CBWFQ
To: "akyccie" <akyccie@gmail.com>
Cc: ccielab@groupstudy.com
Received: Monday, August 25, 2008, 3:55 PM
Make your access-list more specific for the address or subnet that the web
traffic is coming from and apply it outbound to the outgoing interface(s)On
25 aug 2008, at 12:20, akyccie wrote:> R1 is connected to R2 and R3 over
ethernet. I wanted to allocated > 2mb of> bandwidth on R1 for the web
traffice coming from R2. It's seems > CBWFQ can't be> applied on input. So I
guess we need to use rate limit here if aksed > to make> the change only on
R1>> R1>
access-list 100 permit ip any any eq 80> !> class-map match-all C1> match
access-group 100> !> policy-map P1> class C1> bandwidth 2000> !>
R1(config)#int fa0/0> R1(config-if)#service-policy input P1> CBWFQ : Can be
enabled as an output feature only> !> R1(config-if)#service-policy output P1>
R1(config-if)#exit>>> -aky>>> Blogs and organic groups at
http://www.ccie.net>>
This archive was generated by hypermail 2.1.4 : Mon Sep 01 2008 - 08:15:32 ART