From: "David du Colombier" <0intro@gmail.com>
To: "g_patrickb via 9fans" <9fans@9fans.net>
Subject: Re: [9fans] 127.0.0.1 considered harmful
Date: Sat, 11 Jul 2020 20:24:14 +0200 [thread overview]
Message-ID: <7f356ef1-9ddf-4e68-9304-5d62fbe9fd90@www.fastmail.com> (raw)
In-Reply-To: <6a1536c9-6e3c-4f6a-8000-5aa0b97d42b1@www.fastmail.com>
I think you may be experiencing an issue I investigated
and fixed a few years ago, due to the TCP stack not
setting up the MTU properly on incoming connections.
You can look at this old thread from 9fans:
https://www.mail-archive.com/9fans@9fans.net/msg33754.html
The fix is available here:
http://9legacy.org/9legacy/patch/9-tcp-mss.diff
--
David du Colombier
next prev parent reply other threads:[~2020-07-11 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 11:04 Richard Miller
2020-07-11 15:46 ` [9fans] " Ethan Gardener
2020-07-11 18:24 ` David du Colombier [this message]
2020-07-11 18:57 ` Richard Miller
2020-07-13 7:04 ` Lucio De Re
2020-07-17 9:40 ` Ethan Gardener
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=7f356ef1-9ddf-4e68-9304-5d62fbe9fd90@www.fastmail.com \
--to=0intro@gmail.com \
--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).