All of lore.kernel.org
 help / color / mirror / Atom feed
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 13:23:48 +0000	[thread overview]
Message-ID: <marc-lartc-101464348411258@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101461408005658@msgid-missing>

> > 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 ..
> 
> Not for locally generated packets - if you lower MTU, MSS will get set too.

At my production server when I set MTU to 640 (I hoped in better link
utilization) I suddenly was not able to reach some webs from it. I
discovered that the are sending me 1500 byte packets with DF set and
they didn't pay atttention to my MTU. It is obvious problem in MTU
discovery.

You are roght that MSS is set to MTU but it is bad luck it you have
small MSS but you can't reach some hosts.

MSS setting for routes works well for me even for localy generated
flows. Is there some problem I don't see ?

regards, devik

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  parent reply	other threads:[~2002-02-25 13:23 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
2002-02-25 12:26 ` bert hubert
2002-02-25 13:23 ` Martin Devera [this message]
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-101464348411258@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.