From: Andre Correa <andre.correa@pobox.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ingress policing
Date: Wed, 14 Jan 2004 11:48:36 +0000 [thread overview]
Message-ID: <40052C94.3060106@pobox.com> (raw)
In-Reply-To: <marc-lartc-101498104311743@msgid-missing>
Hi Vinh, I've noticed the same thing some months ago and couldn't figure
out why. The workarround for this is to use half speed in your
"upload" classes... It seens that it just happens to outgoing traffic
(ingress or not).
Maybe somone else can explian it... I just figured out the same problem...
Andre
Vinh Nguyen wrote:
> Hi,
>
> I'm trying to police the incoming traffic by using ingress qdisc,this is what I have in my script
>
> tc qdisc add dev eth0 handle ffff: ingress
>
> tc filter add dev eth0 parent ffff: protocol ip prio 4 \
> handle 1: u32 divisor 1
>
> tc filter add dev eth0 parent ffff: protocol ip prio 4 u32 \
> match ip dport 4001 0xffff \
> police rate 2000kbit burst 50k drop \
> flowid 1:1
>
> I'm sending a 9Mb traffic using iperf but noticed that the bandwith at the receiving end is 4 MB instead of 2M. When Im changing the police rate to 3MB, the traffic at the receiving end is 6MB. Any ideas why does this happen? Your help is greatly appreciated.
>
> Vince
>
>
>
> UTS CRICOS Provider Code: 00099F
>
> DISCLAIMER
> ====================================
> This email message and any accompanying attachments may contain
> confidential information. If you are not the intended recipient, do not
> read, use, disseminate, distribute or copy this message or attachments.
> If you have received this message in error, please notify the sender
> immediately and delete this message. Any views expressed in this message
> are those of the individual sender, except where the sender expressly,
> and with authority, states them to be the views the University of
> Technology Sydney. Before opening any attachments, please check them for
> viruses and defects.
> ====================================
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-01-14 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 11:09 [LARTC] Ingress policing Jan Coppens
2002-03-06 14:19 ` Radosław Łoboda
2002-03-06 14:30 ` bert hubert
2002-03-07 11:17 ` Radosław Łoboda
2002-04-12 15:09 ` Jan Coppens
2002-04-14 10:19 ` bert hubert
2002-04-15 8:06 ` Jan Coppens
2002-12-28 11:32 ` [LARTC] ingress policing lartc
2002-12-28 12:02 ` Patrick McHardy
2004-01-13 22:26 ` Vinh Nguyen
2004-01-14 11:48 ` Andre Correa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40052C94.3060106@pobox.com \
--to=andre.correa@pobox.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox