From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, blueness@gentoo.org,
kernel@gentoo.org
Subject: Re: [Bugme-new] [Bug 36122] New: New cache learned PMTU information in inetpeer causes ssh to fail when tunneled via an IPSEC VPN
Date: Mon, 6 Jun 2011 13:48:41 -0700 [thread overview]
Message-ID: <20110606134841.d7700212.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-36122-10286@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Sat, 28 May 2011 21:50:32 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=36122
>
> URL: http://bugs.gentoo.org/show_bug.cgi?id=369025
> Summary: New cache learned PMTU information in inetpeer causes
> ssh to fail when tunneled via an IPSEC VPN
> Product: Networking
> Version: 2.5
> Kernel Version: 2.6.39
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: IPV4
> AssignedTo: shemminger@linux-foundation.org
> ReportedBy: blueness@gentoo.org
> CC: kernel@gentoo.org
> Regression: No
>
>
> When trying to ssh from a box running 2.6.39 on one private subnet to another
> box on another private subnet via an IPSEC vpn, ssh freezes and times out at:
>
> debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
>
> This was traced down to commit 2c8cec5c10bced2408082a6656170e74ac17231c.
>
> This type of error is known to occur when there is fragmentation due to
> mismatched mtu's which the commit addresses.
>
> Notice the problem does not occur when ssh-ing directly, ie not via an IPSEC
> tunnel. I have not tested if other tunnels are affected.
>
> Please see the downstream bug for more details.
>
parent reply other threads:[~2011-06-06 20:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-36122-10286@https.bugzilla.kernel.org/>]
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=20110606134841.d7700212.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=blueness@gentoo.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=kernel@gentoo.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.