From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: netdev@vger.kernel.org, edumazet@google.com, fan.du@windriver.com
Subject: Re: IPv6 path MTU discovery broken
Date: Mon, 7 Oct 2013 10:37:52 +0200 [thread overview]
Message-ID: <20131007083752.GA20271@sesse.net> (raw)
In-Reply-To: <20131007015252.GE9295@order.stressinduktion.org>
On Mon, Oct 07, 2013 at 03:52:52AM +0200, Hannes Frederic Sowa wrote:
>> pannekake:~> cat /proc/net/ipv6_route
>> 2001067c00a400037c4d9ae8ab73230f 80 00000000000000000000000000000000 00 fe80000000000000023048fffe555743 00000000 00000001 00000137 01000023 eth0
> This one does look like the most probable route which could have the problem.
> It has a RTF_MODIFIED flag indicating it received a pmtu update.
I got the idea to correlate auth.log with the email I sent:
Oct 6 14:01:12 pannekake sshd[13211]: Accepted keyboard-interactive/pam for
sesse from 2001:67c:a4:3:7c4d:9ae8:ab73:230f port 60116 ssh2
So that's definitely the right address.
/* Steinar */
--
Homepage: http://www.sesse.net/
prev parent reply other threads:[~2013-10-07 8:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 20:14 IPv6 path MTU discovery broken Steinar H. Gunderson
2013-09-28 20:33 ` Hannes Frederic Sowa
2013-09-28 20:51 ` Steinar H. Gunderson
2013-09-28 21:19 ` Hannes Frederic Sowa
2013-10-06 12:06 ` Steinar H. Gunderson
2013-10-06 12:44 ` Hannes Frederic Sowa
2013-10-06 12:48 ` Steinar H. Gunderson
2013-10-07 1:52 ` Hannes Frederic Sowa
2013-10-07 3:09 ` Hannes Frederic Sowa
2013-10-07 8:32 ` Steinar H. Gunderson
2013-10-07 14:32 ` Hannes Frederic Sowa
2013-10-07 14:34 ` Steinar H. Gunderson
2013-10-07 15:49 ` Eric Dumazet
2013-10-13 10:40 ` Steinar H. Gunderson
2013-10-13 16:51 ` Eric Dumazet
2013-10-13 17:56 ` Hannes Frederic Sowa
2013-10-07 8:29 ` Steinar H. Gunderson
2013-10-07 8:37 ` Steinar H. Gunderson [this message]
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=20131007083752.GA20271@sesse.net \
--to=sgunderson@bigfoot.com \
--cc=edumazet@google.com \
--cc=fan.du@windriver.com \
--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.