All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Worthington <lartc@tww.cx>
To: lartc@vger.kernel.org
Subject: [LARTC] Does -j TOS actually do anything?
Date: Wed, 05 Nov 2003 12:34:20 +0000	[thread overview]
Message-ID: <marc-lartc-106803586322000@msgid-missing> (raw)

Very simple setup: I have several machines, one of which (192.168.0.198) 
is used exclusively as a vnc client to a remote site. I want it to get 
priority over guff like email and web etc.

tc qdisc add dev eth1 root handle 1: prio
tc qdisc add dev eth1 parent 1:1 handle 10: pfifo
tc qdisc add dev eth1 parent 1:2 handle 20: pfifo
tc qdisc add dev eth1 parent 1:3 handle 30: pfifo

iptables -t mangle -I OUTPUT -p icmp -s 192.168.0.198 -j TOS --set-tos 16

Effect: zero. All the vnc traffic from x.198 goes into 1:2.

I've tried all the tables (PREROUTE etc) to no avail. I even tried 
applying the TOS change to ALL traffice bound for eth1 (the outside line) 
and still saw no change in the queuing despite tcpdump showing that the 
tos bits were being set.

Why does this not work? It seems as if the priority is being set before 
iptables' mangle rules are applied.

Thomas Worthington

-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2003-11-05 12:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05 12:34 Thomas Worthington [this message]
2003-11-05 14:03 ` [LARTC] Does -j TOS actually do anything? Thomas Worthington
2003-11-05 20:11 ` Stef Coene
2003-11-05 21:26 ` Thomas Worthington
2003-11-05 22:25 ` Patrick McHardy
2003-11-06  8:54 ` Thomas Worthington
2003-11-06 21:47 ` Stef Coene
2003-11-06 22:34 ` Thomas Worthington

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-106803586322000@msgid-missing \
    --to=lartc@tww.cx \
    --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.