All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Owens <justin@commtech.ie>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Some help please !
Date: Fri, 24 May 2002 17:26:14 +0000	[thread overview]
Message-ID: <marc-lartc-102226287414922@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102226221414235@msgid-missing>

Right...yeah...578 and 868 and I'm looking for 600 and 900 :-)
How accurate would you normally expect HTB to be ??



-----Original Message-----
From: Martin Devera [mailto:devik@cdi.cz]
Sent: 24 May 2002 18:47
To: Justin Owens
Cc: lartc
Subject: Re: [LARTC] Some help please !


Ehh and another hint, what is kbps in your mind ? BYTES or BITS ?

On Fri, 24 May 2002, Justin Owens wrote:

> Hello,
>
> I am testing HTB using Iperf to generate traffic on a couple of ports and
> trying to shape the traffic. I am using the script following but my
results
> don't seem to make sense.
> I am seeing 4627Kbps on port 100 and 6944 on port 150.
> I'm sure there's a reasonable explaination for this but I can't find it !
>
> Any help would be appreciated.
>
> Rgds.
> Justin
>
>
> tc qdisc del dev eth1 root
>
> tc qdisc add dev eth1 root handle 1: htb default 12
>
> tc class add dev eth1 parent 1: classid 1:1 htb rate 600kbps ceil 600kbps
> tc class add dev eth1 parent 1: classid 1:2 htb rate 900kbps ceil 900kbps
>
> tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32 match ip dport
100
> 0xffff flowid 1:1
> tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32 match ip dport
150
> 0xffff flowid 1:2
>
>
>
> The information contained in this email is privileged and confidential,
intended only for the use of the individual or entity to whom it is
addressed. If the reader of this email is not the intended recipient, you
are hereby notified that any dissemination, distribution or copying of this
email is strictly prohibited. If you have received this email in error,
please notify the sender immediately by email and delete this email. Any
views expressed in this email are those of the individual sender unless the
sender specifically states
> This mail was virus scanned by SurfControl.
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>


The information contained in this email is privileged and confidential, intended only for the use of the individual or entity to whom it is addressed. If the reader of this email is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify the sender immediately by email and delete this email. Any views expressed in this email are those of the individual sender unless the sender specifically states 
This mail was virus scanned by SurfControl.


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2002-05-24 17:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-24 17:15 [LARTC] Some help please ! Justin Owens
2002-05-24 17:26 ` Justin Owens [this message]
2002-05-24 17:46 ` Martin Devera
2002-05-24 17:46 ` Martin Devera
2002-05-24 17:50 ` Stef Coene
2002-05-24 17:52 ` Justin Owens
2002-05-24 18:02 ` Justin Owens
2002-05-24 18:05 ` Martin Devera
2002-05-24 18:11 ` Justin Owens
2002-05-24 18:23 ` Martin Devera
2002-05-24 18:51 ` Martin Devera
2002-05-24 18:53 ` Martin Devera

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=marc-lartc-102226287414922@msgid-missing \
    --to=justin@commtech.ie \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.