9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu, paurea@plan9.escet.urjc.es
Subject: [9fans] Re: IP_DF bit and broken connections
Date: Thu,  5 Dec 2002 11:34:56 +0100	[thread overview]
Message-ID: <08fdc73b5f22a6134f7ef266a02a68a0@plan9.escet.urjc.es> (raw)

This is what we found regarding broken connections when
going through some routers. The setting is

	Plan 9 <-⋯ether⋯-> adsl router <--> Linux.

Linux always sets the DF bit in outgoing packets.
Plan 9 doesnt, but setting it does not change things (we tested that).

Some routers eat packets with size 1500 (eg.  adsl from telefonica in
spain) without fragmenting or sending icmps. Too bad.

With icmp (sized 1500), Linux sends two fragments despite the mtu
being big enough.  We get both fragments in Plan 9 but since they came
with the DF bit set, the reply is dropped by the if in ip.c.
Perhaps once reassembled, the DF bit could be cleared; I don't know.

With tcp, Linux has its mtu at 1500 and negotiates its mss of 1460.
The same does Plan 9, but despite this, Linux sends packets of at most
1444 bytes when going through the router and Plan 9 sends up to 1500
(which IMHO is legitimate). Thus, the linux packets get through and our
1500 packets don't get through. (The connection gets hanged so that
Plan 9 retransmits the poor 1500 packet once and again).

The workaround is simply to adjust the mtu not to reach 1500. Doing so
either on Linux or on Plan 9 lets things work (because the negotiated
mss is smaller).

I don't know how linux discovers that it shouldn't send 1500 bytes.
There are no icmp packets, and the negotiated mss is the same (as I
said before).



             reply	other threads:[~2002-12-05 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05 10:34 Fco.J.Ballesteros [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-05 21:06 Richard Miller
2002-12-05 14:23 presotto
2002-12-05  3:19 paurea

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=08fdc73b5f22a6134f7ef266a02a68a0@plan9.escet.urjc.es \
    --to=nemo@plan9.escet.urjc.es \
    --cc=9fans@cse.psu.edu \
    --cc=paurea@plan9.escet.urjc.es \
    /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).