public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-kernel@schottelius.org>
To: linux-kernel@vger.kernel.org
Subject: PMTU, MSS and "fragmentation needed" problem with linux?
Date: Thu, 7 Apr 2005 14:22:17 +0200	[thread overview]
Message-ID: <20050407122217.GE5211@schottelius.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]

Hello!

[I hope this is the correct list, if not, please tell me where to ask]

The following scenario:

Linux-client <-- Ethernet --> Linux-router <-- PPPoE --> Internet.
Linux-client has MTU==1500, so the MSS is 1460.
Linux-router has MTU==1500 on eth0 and MTU=1492 on ppp0.
The MSS is set to 1452 via pppoe command line.

My question: May the MSS on ppp0 be 1460? Imho not, as

RFC 879 defines the MSS as MTU-40, which would be 1452.
But tcpdump says 1460 on ppp0.
On another box the MTU is set to 1460 and I still see packets
with MSS 1460. Is this correct?
Should not the Linux-router send the client a packet ICMP type 3,
subtype 4, Frag needed, but DF-Bit set?

I ask htis, because of a problem I  have on the first box:
If the clients have a mtu of 1500, theycannot connect
to some servers and get timeouts.

The firewall was tested with iptables of (only MASQUERADE on), so that
all icmp packets are allowed.

Thank you for any hint!

Nico

-- 
Keep it simple & stupid, use what's available.
Please use pgp encryption: 8D0E 27A4 is my id.
http://nico.schotteli.us | http://linux.schottelius.org

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

             reply	other threads:[~2005-04-07 12:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-07 12:22 Nico Schottelius [this message]
2005-04-07 17:33 ` PMTU, MSS and "fragmentation needed" problem with linux? Florian Attenberger
2005-04-08  0:35   ` Nico Schottelius

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=20050407122217.GE5211@schottelius.org \
    --to=nico-kernel@schottelius.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox