From: Jeffrey Laramie <JALaramie@Loudoun-Fairfax.com>
To: nf <netfilter@lists.netfilter.org>
Subject: Re: NAT, MANGLE, and TOS
Date: Thu, 23 Oct 2003 14:22:46 -0400 [thread overview]
Message-ID: <3F981C76.9020407@Loudoun-Fairfax.com> (raw)
In-Reply-To: <20031023175634.87744.qmail@web40201.mail.yahoo.com>
SBlaze wrote:
>Currently I run a very and common setup for my home network.
>
>My Linux box acts as my router and gateway for my home network and simply NATs
>everything out to the cable modem and onto the internet.
>
>My question is this. I have read awhile ago that changing the TOS of packets
>can be beneficial in ganing small performance. Logically I thought this would
>pretty much be limited to a Point to Point systems. However by posting to some
>forums for broadband, i hearf through the perverbial grapevine that my
>ISP(Charter Communications) will honor user or application set TOS values
>unless they are under network congestion. I can of course not verify this.
>
>This is my quandry. Currently this is all I do..
>
>iptables -t nat -A POSTROUTING -o eth0 -j SNAT --to 68.119.49.97
>
>Is it possible to mangle NAT in a way that all my nat traffic carries slightly
>higher TOS values? Will this give me a slight to any boost in upstream?
>
>As always thanks for any info in advance and hail to the open source community.
>SBlaze
>
>
You can use the appropriately named mangle table to set TOS like this:
$iptables -t mangle -A OUTPUT -p tcp -m state --state
NEW,RELATED,ESTABLISHED -m tcp --sport 80 -j TOS --set-tos 0x08
I don't have enough traffic on my network to see a noticeable difference
when I change TOS, but given your situation, setting TOS might help.
Jeff
next prev parent reply other threads:[~2003-10-23 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 17:56 NAT, MANGLE, and TOS SBlaze
2003-10-23 18:22 ` Jeffrey Laramie [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-23 18:30 Daniel Chemko
2003-10-23 19:01 ` Jeffrey Laramie
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
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=3F981C76.9020407@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