All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] TCP MSS clampage
Date: Thu, 28 Feb 2002 16:50:42 +0000	[thread overview]
Message-ID: <marc-lartc-101491509817177@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101491222506911@msgid-missing>

On Thu, Feb 28, 2002 at 04:02:54PM +0000, Tim Carr wrote:
> Hey,
> 
> My internet is provided via ADSL using PPPoE. When I take a look at 
> ifconfig's output, I see that eth0 has an MTU of 1500, and ppp0 has an MTU 
> of 1492. I don't _think_ that rp-pppoe (my pppoe util) is clamping the MSS. 
> I am noticing some latency when there's a lot of bandwidth in use (but not 

Don't think, meassure :-)

>  >90%). What should I clamp, eth0/ppp0? How much? And what with, rp-pppoe, 
> or tc/iproute2/etc ?  I guess I don't really understand clamping MSS, can 
> someone explain it in laymans terms? I have read the lartc-FAQ, and the only 
> time I see clamping-MSS mentioned is section 15.7, which doesn't really 
> explain why you'd do it.

If you don't experience any problems then by all means do not tcp clamp.
rp-pppoe comes with wonderful documentation, I suggest you read it :-)

Regards,

bert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2002-02-28 16:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28 16:02 [LARTC] TCP MSS clampage Tim Carr
2002-02-28 16:50 ` bert hubert [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=marc-lartc-101491509817177@msgid-missing \
    --to=ahu@ds9a.nl \
    --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.