From: Thomas Worthington <lartc@tww.cx>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Does -j TOS actually do anything?
Date: Thu, 06 Nov 2003 22:34:42 +0000 [thread overview]
Message-ID: <marc-lartc-106815814629337@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106803586322000@msgid-missing>
On Thu, 6 Nov 2003 22:47:06 +0100, Stef Coene <stef.coene@docum.org> wrote:
> On Wednesday 05 November 2003 22:26, Thomas Worthington wrote:
>> Chain OUTPUT (policy ACCEPT 805 packets, 97871 bytes)
>> pkts bytes target prot opt in out source
>> destination
>> 0 0 TOS all -- * * 192.168.0.198
>> 0.0.0.0/0 TOS set 0x10
> None of the packets are matchde by the iptables rule.
> Are you sure you have to do this in OUTPUT? See :
> http://www.docum.org/stef.coene/qos/kptd/
> If you are trying this on a router, try to change the tos in POSTROUTING.
>
> Stef
>
I tried all five tables! It appears that I was simply misguided: setting
TOS doe indeed have no effect as it happens after the priority has been
set; a different filter is needed.
I'm leaving the list now as it seems to be a great way to instantly sign
up for tons of spam (as you can imagine, this is the only thing that I've
ever used this email address for and after only two days it's become a
spam magnet).
Thanks to everyone that helped; I'll try some of the other methods.
Thomas Worthington
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-11-06 22:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 12:34 [LARTC] Does -j TOS actually do anything? Thomas Worthington
2003-11-05 14:03 ` 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 [this message]
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-106815814629337@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.