Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] PRIO not working?
Date: Sun, 14 Apr 2002 10:26:05 +0000	[thread overview]
Message-ID: <marc-lartc-101878004323896@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101873313203800@msgid-missing>

On Sat, Apr 13, 2002 at 05:24:10PM -0400, Jacob Elder wrote:
> 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:

PRIO works just fine - you probably have it configured wrong.

> iptables -A OUTPUT -t mangle -p tcp --dport ftp-data -j TOS --set-tos Maximize-throughput

OUTPUT is only for locally generated packets, by the way. To mangle
forwarded packets, use PREROUTING.

> 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?

I would advise rechecking the output of tcpdump before and after applying
the iptables mangle rules.

Regards,

bert hubert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2002-04-14 10:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-13 21:24 [LARTC] PRIO not working? Jacob Elder
2002-04-14 10:26 ` bert hubert [this message]
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-101878004323896@msgid-missing \
    --to=ahu@ds9a.nl \
    --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