From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] $100 USD to the first person that can provide the rules/scripts that will solve the QOS
Date: Thu, 04 Dec 2003 19:32:43 +0000 [thread overview]
Message-ID: <marc-lartc-107056787826561@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107047454124998@msgid-missing>
On Thursday 04 December 2003 03:33, Greg Freeman wrote:
> I tried the following rules and had the same bad latency results for the
> corp site to remote site. Below are the rules I tried which gave the bad
> (avg. 350ms) latency:
>
> ----corp rules----
>
> tc qdisc add dev ipsec0 handle 1: root cbq bandwidth 600kbit avpkt 1000
> tc class add dev ipsec0 parent 1: classid 1:1 cbq bandwidth 240kbit
> avpkt 500 prio 1 rate 240kbit bounded isolated
> tc filter add dev ipsec0 parent 1:0 protocol ip prio 100 route
> tc filter add dev ipsec0 parent 1:0 protocol ip prio 1 u32 match ip dst
> 10.0.1.20 flowid 1:1
> tc filter add dev ipsec0 parent 1:0 protocol ip prio 1 u32 match ip dst
> 10.0.1.21 flowid 1:1
> tc filter add dev ipsec0 parent 1:0 protocol ip prio 1 u32 match ip dst
> 10.0.1.22 flowid 1:1
>
>
>
> ----remote rules------
>
> tc qdisc add dev ipsec0 handle 1: root cbq bandwidth 580kbit avpkt 1000
> tc class add dev ipsec0 parent 1: classid 1:1 cbq bandwidth 240kbit
> avpkt 500 prio 1 rate 240kbit bounded isolated
> tc filter add dev ipsec0 parent 1:0 protocol ip prio 100 route
> tc filter add dev ipsec0 parent 1:0 protocol ip prio 1 u32 match ip dst
> 10.0.0.7 flowid 1:1
>
>
>
>
>
> Any help would be greatly appreciated.
The bandwidth must be your NIC bandwidth. So 10mbit or 100mbit. And remove
the isolated parameter.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-12-04 19:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 18:04 [LARTC] $100 USD to the first person that can provide the rules/scripts that will solve the QOS late Greg Freeman
2003-12-03 20:12 ` [LARTC] $100 USD to the first person that can provide the rules/scripts that will solve the QOS Stef Coene
2003-12-04 2:33 ` Greg Freeman
2003-12-04 19:32 ` Stef Coene [this message]
2003-12-04 19:39 ` [LARTC] $100 USD to the first person that can provide the rules/scripts Darryl Miles
2003-12-04 20:24 ` [LARTC] $100 USD to the first person that can provide the rules/scripts that will solve the QOS Greg Freeman
2003-12-04 20:36 ` Stef Coene
2003-12-04 20:45 ` Greg Freeman
2003-12-04 20:57 ` Greg Freeman
2003-12-04 21:11 ` Stef Coene
2003-12-04 23:15 ` [LARTC] $100 USD to the first person that can provide the rules/scripts Darryl Miles
2003-12-04 23:29 ` Darryl Miles
2003-12-05 23:35 ` [LARTC] $100 USD to the first person that can provide the rules/scripts that will solve the QOS Greg Freeman
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-107056787826561@msgid-missing \
--to=stef.coene@docum.org \
--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.