All of lore.kernel.org
 help / color / mirror / Atom feed
From: jake@lucidpark.net (Jacob Elder)
To: lartc@vger.kernel.org
Subject: [LARTC] PRIO not working?
Date: Sat, 13 Apr 2002 21:24:10 +0000	[thread overview]
Message-ID: <marc-lartc-101873313203800@msgid-missing> (raw)

I'm trying to prioritize interactive traffic over other traffic on my 56k
dialup link. I wrote some chains to set the ToS in PREROUTING and OUTGOING,
and I'm using a PRIO queue with three SFQ children:

iptables -A OUTPUT -t mangle -p tcp --dport ftp-data -j TOS --set-tos Maximize-throughput
iptables -A OUTPUT -t mangle -p tcp --dport domain -j TOS --set-tos Maximize-throughput
iptables -A OUTPUT -t mangle -p tcp --dport www -j TOS --set-tos Maximize-throughput
iptables -A OUTPUT -t mangle -p tcp --dport smtp -j TOS --set-tos Minimize-cost
iptables -A OUTPUT -t mangle -p tcp --dport telnet -j TOS --set-tos Minimize-delay
iptables -A OUTPUT -t mangle -p tcp --dport ssh -j TOS --set-tos Minimize-delay
iptables -A OUTPUT -t mangle -p udp --dport domain -j TOS --set-tos Minimize-delay
iptables -A OUTPUT -t mangle -p tcp --dport ftp -j TOS --set-tos Minimize-delay
iptables -A OUTPUT -t mangle -p tcp --dport 5900 -j TOS --set-tos Minimize-delay
iptables -A OUTPUT -t mangle -p tcp --dport imaps -j TOS --set-tos Minimize-delay
iptables -A OUTPUT -t mangle -p tcp --dport 9898 -j TOS --set-tos Minimize-delay
iptables -A OUTPUT -t mangle -p tcp --dport 5190 -j TOS --set-tos Minimize-delay
iptables -A OUTPUT -t mangle -p tcp --dport 6667 -j TOS --set-tos Minimize-delay

tc qdisc add dev $DEV root handle 1: prio
tc qdisc add dev $DEV parent 1:1 handle 10: sfq perturb 5 # interactive
tc qdisc add dev $DEV parent 1:2 handle 20: sfq perturb 5 # throughput
tc qdisc add dev $DEV parent 1:3 handle 30: sfq perturb 5 # lowcost

According to tcpdump, the ToS bits are indeed being set like I asked, but
"watch tc -s qdisc show dev ppp0" shows that everything is going into the
"througput" queue regardless. The only traffic that increments the counter
for the "interactive" queue is post-handshake SSH traffic, and from what
I've read, SSH sets the ToS explicitly. What am I doing wrong?

-- 
Jacob Elder
http://www.lucidpark.net/

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

             reply	other threads:[~2002-04-13 21:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-13 21:24 Jacob Elder [this message]
2002-04-14 10:26 ` [LARTC] PRIO not working? bert hubert
2002-04-14 16:29 ` Jacob Elder
2004-09-20  8:33 ` Phill
2004-10-08 13:28 ` Andy Furniss

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-101873313203800@msgid-missing \
    --to=jake@lucidpark.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.