From: Jeffrey Laramie <JALaramie@Loudoun-Fairfax.com>
To: nf <netfilter@lists.netfilter.org>
Subject: Re: NAT, MANGLE, and TOS
Date: Thu, 23 Oct 2003 15:01:08 -0400 [thread overview]
Message-ID: <3F982574.10001@Loudoun-Fairfax.com> (raw)
In-Reply-To: <7C9884991ADAE0479C14F10C858BCDF52E3766@alderaan.smgtec.com>
Daniel Chemko wrote:
>>$iptables -t mangle -A OUTPUT -p tcp -m state --state
>>NEW,RELATED,ESTABLISHED -m tcp --sport 80 -j TOS --set-tos 0x08
>>
>>
>
>You probably want this on the FORWARD chain to boost the performance of
>your actual client machines instead of just the firewall.
>
>
>
>
Good point. Is there any reason I shouldn't put my rules on the mangle
POSTROUTING table and kill 2 birds with one rule?
next prev parent reply other threads:[~2003-10-23 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 18:30 NAT, MANGLE, and TOS Daniel Chemko
2003-10-23 19:01 ` Jeffrey Laramie [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-23 19:35 Daniel Chemko
2003-10-23 20:25 ` SBlaze
2003-10-23 20:47 ` Ramin Dousti
2003-10-23 21:19 ` SBlaze
2003-10-23 21:03 ` Jeffrey Laramie
2003-10-23 17:56 SBlaze
2003-10-23 18:22 ` Jeffrey Laramie
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=3F982574.10001@Loudoun-Fairfax.com \
--to=jalaramie@loudoun-fairfax.com \
--cc=netfilter@lists.netfilter.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