From: "AHM" <ahm10@quicksoft.it>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] wondershaper + htb prio + qdisc prio
Date: Sun, 29 Dec 2002 18:28:45 +0000 [thread overview]
Message-ID: <marc-lartc-104118652106076@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104118607605812@msgid-missing>
Hi,<BR><BR>I think that imcp is not the solution. I've tested with mohaa
and that game uses an own sort of ping on a udp port (so via tcp and not
imcp)<BR><BR>Maby u should check if counterstrike does that
too.<BR><BR>Regards,<BR>Andre<BR><BR><BR>> hello,<BR>> <BR>> a
friend of mine have this configuration:<BR>> <BR>> 10 x PC --
router/linux/rh8 -- ADSL Modem -- ISP<BR>> <BR>> let's say that the
bandwidth is: 5M and 800K<BR>> <BR>> he does dc++ and
counter-strike, so let's say the UP is full, and the<BR>> ping from the
counter server is 300ms, the server cut the connection,<BR>> and no
more game, the player is unhappy. The normal ping is 50ms.<BR>>
<BR>> so he thinks to put some prio on the ping-echo packets to make
the ping<BR>> be extra small, he try the wondershapper from the lartc,
don't work,<BR>> make a simplified script just for icmp with
is:<BR>> <BR>> $tc qdisc del $IF_EXT root<BR>> $tc qdisc add
$IF_EXT handle 1: root htb default 2<BR>> $tc class add $IF_EXT parent
1: classid 1:9 htb rate 500kbit burst 6k<BR>> $tc class add $IF_EXT
parent 1:9 classid 1:1 htb rate 500kbit ceil<BR>> 500kbit burst 6k prio
1<BR>> $tc class add $IF_EXT parent 1:9 classid 1:2 htb rate 64kbit
ceil<BR>> 500kbit burst 6k prio 2<BR>> <BR>> $tc filter add
$IF_EXT protocol ip prio 2 parent 1: u32 \<BR>> match ip protocol 1
0xff flowid 1:1<BR>> <BR>> first tryed it with ceil 800kbit, after
with a smaller value, the "real"<BR>> bandwidth was somewhere around
700kbit, at that moment.<BR>> <BR>> didn't work<BR>> <BR>> so
he tryed with just a prio qdisc and put the icmp packets in the 0<BR>>
band, the script:<BR>> <BR>> $iptables -t mangle -A POSTROUTING -p
icmp -j TOS --set-tos 0x10<BR>> $tc qdisc del $IF_EXT root<BR>> $tc
qdisc add $IF_EXT root handle 10: prio<BR>> <BR>> $tc qdisc add
$IF_EXT parent 10:1 handle 20: est 1sec 8sec bfifo<BR>> $tc qdisc add
$IF_EXT parent 10:2 handle 30: est 1sec 8sec bfifo<BR>> $tc qdisc add
$IF_EXT parent 10:3 handle 40: est 1sec 8sec bfifo<BR>> <BR>> $tc
filter add $IF_EXT parent 10: protocol ip prio 1 u32 match ip tos<BR>>
0x10 0xff flowid 10:1<BR>> $tc filter add $IF_EXT parent 10: protocol
ip prio 1 u32 match ip tos<BR>> 0x06 0xff flowid 10:2<BR>> $tc
filter add $IF_EXT parent 10: protocol ip prio 1 u32 match ip tos<BR>>
0x0c 0xff flowid 10:3<BR>> <BR>> <BR>> still with no result the
ping from the counter server is always 300ms,<BR>> what's
wrong????<BR>> <BR>> C<BR>> -- <BR>> Ciprian Niculescu<BR>>
<BR>> _______________________________________________<BR>> LARTC
mailing list / LARTC@mailman.ds9a.nl<BR>>
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/<BR>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-12-29 18:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-29 18:19 [LARTC] wondershaper + htb prio + qdisc prio lartc
2002-12-29 18:28 ` AHM [this message]
2002-12-29 18:55 ` Andre Meij
2002-12-30 10:54 ` Tornado
2002-12-30 11:21 ` Ciprian Niculescu
2002-12-30 21:22 ` Tornado
2002-12-30 23:23 ` Ciprian Niculescu
2002-12-31 10:49 ` sufcrusher
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-104118652106076@msgid-missing \
--to=ahm10@quicksoft.it \
--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