From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] tcp!
Date: Wed, 22 Aug 2012 14:46:23 -0400 [thread overview]
Message-ID: <6c9560f6acda638101a746d924ea57df@ladd.quanstro.net> (raw)
In-Reply-To: <CAGGHmKFokgrbH1P_j+31teoO9ubEvLu2Ti7_QP1+WPLXQ291Mg@mail.gmail.c>
On Wed Aug 22 14:31:13 EDT 2012, sstallion@gmail.com wrote:
> On Wed, Aug 22, 2012 at 10:18 AM, Gorka Guardiola <paurea@gmail.com>
> wrote:
> > I had this problem several years ago with an adsl router (9fans
> > archive may know about this). There was a bug in my adsl router
> > (which seems to be common, I have seen it since more than once) that
> > dropped ethernet frames of size greater than 1480 (someone counted a
> > header twice probably). Linux adapts the mss to 1480 if there are
> > problems so it works in this case.
> >
> Not so much a bug as ATM overhead.
atm overhead is 5 bytes per 48 bytes transmitted.
the original problem is a limit of 1496 bytes,
not 1460, which is more constent with mpls
than l2tp (1460) or pppoe (1492). but all that's
guesswork.
the "bug" here, if there is one, is that there's
neither an icmp message nor fragmentation
nor mss rewriting at the local gateway, which
should (since it's eithernet) not silently drop
mtu-sized frames that it's responsible for
gatewaying.
- erik
next prev parent reply other threads:[~2012-08-22 18:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 18:32 Richard Miller
2012-08-22 17:18 ` Gorka Guardiola
2012-08-22 18:29 ` Steven Stallion
[not found] ` <CAGGHmKFokgrbH1P_j+31teoO9ubEvLu2Ti7_QP1+WPLXQ291Mg@mail.gmail.c>
2012-08-22 18:46 ` erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-18 20:11 erik quanstrom
2012-08-18 20:26 ` erik quanstrom
2012-08-19 13:37 ` Richard Miller
2012-08-19 13:55 ` cinap_lenrek
2012-08-19 14:05 ` Richard Miller
2012-08-19 15:07 ` erik quanstrom
2012-08-19 14:48 ` erik quanstrom
2012-08-19 13:17 ` Richard Miller
2012-08-19 15:43 ` erik quanstrom
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=6c9560f6acda638101a746d924ea57df@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).