From: Askar <askarali@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: what is --set-mes 128
Date: Thu, 13 Jan 2005 11:13:56 +0500 [thread overview]
Message-ID: <a0f69e50501122213291aa355@mail.gmail.com> (raw)
In-Reply-To: <1105593361.8185.10.camel@hubcap.ljm.dom>
Thank you very much simpson ..ooops imean jason :)
On Thu, 13 Jan 2005 00:16:01 -0500, Jason Opperisano <opie@817west.com> wrote:
> On Wed, 2005-01-12 at 23:50, Askar wrote:
> > Hello,
> >
> > can someone help mevto understand these rules...
> >
> > $iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --set-mss 128
> > $iptables -t nat -A PREROUTING -p tcp --tcp-flags SYN,RST SYN -j
> > TCPMSS --set-mss 128
> >
>
> MSS == Maximum Segment Size
>
> in english--it's the maximum amount of data that can be contained in a
> TCP packet.
>
> normal MSS calculation is:
>
> MSS = MTU - 40
>
> so--for example on an ethernet interface; where MTU = 1500, the MSS
> would be 1460.
>
> a common reason to mess around with "-j TCPMSS --set-mss" is when you're
> tunneling your traffic over IPsec, and/or when PMTU discovery is broken.
>
> maybe i'm missing something, but 128 seems like an *awfully* low value
> to be forcing your MSS to.
>
> > Secondly is there any benefit of changing TOS of packets going out i-e...
> >
> > $iptables -A OUTPUT -t mangle -p tcp --dport http -j TOS --set-tos
> > Maximize-throughput
>
> i doubt it.
>
> -j
>
> --
> "We only get thirty sweet noggy days. Then the government takes it
> away again."
> --The Simpsons
>
>
--
(after bouncing head on desk for days trying to get mine working, I'll make
your life a little easier)
prev parent reply other threads:[~2005-01-13 6:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 4:50 what is --set-mes 128 Askar
2005-01-13 5:16 ` Jason Opperisano
2005-01-13 6:13 ` Askar [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=a0f69e50501122213291aa355@mail.gmail.com \
--to=askarali@gmail.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