From: David Brownell <david-b@pacbell.net>
To: Janos Farkas <jf-ml-k1-1087813225@lk8rp.mail.xeon.eu.org>
Cc: David Ford <david+challenge-response@blue-labs.org>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
Art Haas <ahaas@airmail.net>
Subject: Re: 2.6.11-rc2 TCP ignores PMTU ICMP (Re: Linux 2.6.11-rc2)
Date: Thu, 27 Jan 2005 15:11:57 -0800 [thread overview]
Message-ID: <200501271511.58086.david-b@pacbell.net> (raw)
In-Reply-To: <200501271128.48411.david-b@pacbell.net>
I just got an interesting "I see these problems too" report. It
may provide a useful clue. According to "Art Haas" <ahaas@airmail.net>:
> I'm running the current BK kernel now, and I'm not seeing the problems
> right now because, I found, I do not have some of the IP masquerading
> modules installed on my machine. When these modules get installed then
> the cvs/rsync problems appear.
I do have CONFIG_IP_NF_TARGET_MASQUERADE=y on the system where I'm
seeing this, though it's not doing anything just now. Haven't yet
made time to see if disabling it improves things ... but if that's
a factor, it could explain why more people aren't suffering with
this problem.
- Dave
next prev parent reply other threads:[~2005-01-27 23:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200501232251.42394.david-b@pacbell.net>
[not found] ` <41F6916F.7060000@blue-labs.org>
[not found] ` <200501251054.37053.david-b@pacbell.net>
2005-01-27 9:02 ` 2.6.11-rc2 TCP ignores PMTU ICMP (Re: Linux 2.6.11-rc2) Janos Farkas
2005-01-27 19:28 ` David Brownell
2005-01-27 20:00 ` Janos Farkas
2005-01-27 23:11 ` David Brownell [this message]
2005-01-27 23:41 ` David S. Miller
2005-01-28 1:33 ` Patrick McHardy
2005-01-28 3:00 ` Rusty Russell
2005-01-28 14:04 ` Art Haas
2005-01-31 22:13 ` Bill Davidsen
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=200501271511.58086.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=ahaas@airmail.net \
--cc=david+challenge-response@blue-labs.org \
--cc=jf-ml-k1-1087813225@lk8rp.mail.xeon.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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).