From: "Ciprian Niculescu" <lartc@cnicules.4email.net>
To: lartc@vger.kernel.org
Subject: [LARTC] re: wondershaper + htb prio + qdisc prio
Date: Tue, 31 Dec 2002 13:13:24 +0000 [thread overview]
Message-ID: <marc-lartc-104134048901253@msgid-missing> (raw)
On Tue, 31 Dec 2002 11:49:15 +0100, "sufcrusher" <sufcrusher@zonnet.nl>
said:
> But you are not listening to what I and others have been saying. Forget
> about the ICMP pings! They don't mean nothing!
i do, but, forget CS, my problem is that the prio don't work
here the script to start the discusion
$tc qdisc del $IF_EXT root
$tc qdisc add $IF_EXT handle 1: root htb default 2
$tc class add $IF_EXT parent 1: classid 1:9 htb rate 500kbit burst 6k
$tc class add $IF_EXT parent 1:9 classid 1:1 htb rate 500kbit ceil
500kbit burst 6k prio 1
$tc class add $IF_EXT parent 1:9 classid 1:2 htb rate 64kbit ceil
500kbit burst 6k prio 2
$tc filter add dev $IF_EXT protocol ip prio 2 parent 1: u32 \
match ip protocol 1 0xff flowid 1:1
fizical ADSL 5mbit/700kbit, the desired: even the upload is full, i want
to have a wonderfull ping response
the problem is that the above script don't work, why????
and for your script below, nice marks, but the tc where is it???
C
P.S. Happy New Year!!!!
>
> Use the script I attached (change a few settings, like your own speeds,
> interface and executables, speeds are in kbit!). Then use the following
> iptables rules:
>
> (eth0=my internet-interface, eth2=my LAN interface, change if needed !)
>
> # ICMP packets have an even higher priority (so you can test it with
> ping,
> but this doesn't help CounterStrike at all!)
> # Don't do massive pings/traceroutes because that would choke other
> traffic
> (including CS)!
> iptables -I PREROUTING -t mangle -i eth2 -j MARK --set-mark 1 -p ICMP
> iptables -I OUTPUT -t mangle -o eth0 -j MARK --set-mark 1 -p ICMP
> # And here's Counter Strike:
> # if you want you could add: -m multiport --destination-port 27000:27050
> iptables -I PREROUTING -t mangle -i eth2 -j MARK --set-mark 1 -p
> DP --source-port 27005
>
> # ACK Packets get higher priority than 'normal' packets
> iptables -I PREROUTING -t mangle -i eth2 -j MARK --set-mark 2 -p TCP -m
> length --length 0:100
> iptables -I OUTPUT -t mangle -o eth0 -j MARK --set-mark 2 -p TCP -m
> length --length 0:100
>
> And add some more yourself, remember:
> - All rules are tested for each packet: MARK does _not_ stop like ACCEPT
> and
> RETURN do.
> - Therefore the order in which you place these rules is important.
> - Rules are inserted (-I) in the table, so eventually (use iptables -L
> -n)
> the rules will be 'upside down' in the table.
> - Thus higher priorities rules (lower MARK numbers) should go first in
> your
> script, otherwise they might be overruled by later rules.
>
> Jannes Faber
>
> ----- Original Message -----
> From: "Ciprian Niculescu" <lartc@cnicules.4email.net>
> To: "Tornado" <tornado@linuxfromscratch.org>; <lartc@mailman.ds9a.nl>
> Sent: Tuesday, December 31, 2002 12:23 AM
> Subject: Re: [LARTC] wondershaper + htb prio + qdisc prio
>
>
> > On Mon, 30 Dec 2002 22:22:28 +0100, "Tornado"
> > <tornado@linuxfromscratch.org> said:
> > > > >
> > > > this is what i try, beacouse i dont realy play the game, i generate
> > > > trafic to saturate the link, and ping from shell from an externat host
> > >
> > > In which case, you should check if your downstream is not chocking. Even
> > > if
> > > you shape outgoing packets, you can still get get bad pings, if your
> > > downstream is running at max.
> >
> > no a 1Mbit trafic on a 5M no chocking :))))
> >
> > C
> >
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-12-31 13:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-104134048901253@msgid-missing \
--to=lartc@cnicules.4email.net \
--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.