From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Clamping tcp mss values to decrease latency
Date: Mon, 25 Feb 2002 11:58:54 +0000 [thread overview]
Message-ID: <marc-lartc-101463844428720@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101461408005658@msgid-missing>
> > other tcp connections to have the normal full packet size. Enter
> > MSS-clamping. My pppoe client for linux can do mss clamping on every
> > packet that goes out and come in. Not enough control. There is an option
> > to do mss-clamping in iptables, however this only works in the forward
> > table. I can't match and control outgoing web connections, just
>
> Control and outgoing can be done with regular MTU settings. Just lower the
> MTU size of your ppp interface and the kernel will set a lower MSS
> automatically.
Be VERY careful when doing it. There is too many websites blocking
MTU discovery protocol and you will be no longer able to reach them.
These system maintainers should be shot. :-\
Setting max MSS in route is better way ..
> You can also set MTU per route.
you probably wanted to say MSS here ?
devik
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2002-02-25 11:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 5:13 [LARTC] Clamping tcp mss values to decrease latency Ross Skaliotis
2002-02-25 6:55 ` Martin Devera
2002-02-25 9:00 ` bert hubert
2002-02-25 11:58 ` Martin Devera [this message]
2002-02-25 12:26 ` bert hubert
2002-02-25 13:23 ` Martin Devera
2002-02-25 13:37 ` Ross Skaliotis
2002-02-25 13:44 ` Martin Devera
2002-02-25 13:48 ` bert hubert
2002-02-25 13:54 ` Martin Devera
2002-02-28 9:05 ` bert hubert
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-101463844428720@msgid-missing \
--to=devik@cdi.cz \
--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.