From: Tetja Rediske <tetja@tetja.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: christoph.paasch@uclouvain.be,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
djduanjiong@gmail.com, netdev@vger.kernel.org,
steffen.klassert@secunet.com,
Neal Cardwell <ncardwell@google.com>,
David Miller <davem@davemloft.net>
Subject: Re: PROBLEM: IPv6 TCP-Connections resetting
Date: Sat, 06 Apr 2013 20:27:42 +0200 [thread overview]
Message-ID: <5160691E.2080105@tetja.de> (raw)
In-Reply-To: <1365270879.3887.4.camel@edumazet-glaptop>
Hi,
> OK, it seems bug was added in commit
> ec18d9a2691d69cd14b48f9b919fddcef28b7f5c
> (ipv6: Add redirect support to all protocol icmp error handlers.)
> Not sure why Tetja Rediske bisected t
> 093d04d42fa094f6740bb188f0ad0c215ff61e2c
there could be an simple explenation, because i couldn't realy provoke
it with direct connected machines I did it on one of our least important
DNS-Server, I did a "bad" everytime the connection fault and did a
"good" after a some succesful connects (with waiting Time in between).
If the Bug is based on an ICMPv6 redirect in the meantime a redirect
could be sent out without me noticing. I did not keep the tcpdump
running while bisect(?ing?).
I will happily try the patch, when I get to work Monday, weekend is
mostly for family. ;)
Tetja
next prev parent reply other threads:[~2013-04-06 18:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 15:48 PROBLEM: IPv6 TCP-Connections resetting Tetja Rediske
2013-04-05 17:54 ` Neal Cardwell
2013-04-05 17:58 ` Eric Dumazet
2013-04-06 4:35 ` Hannes Frederic Sowa
2013-04-06 4:37 ` Hannes Frederic Sowa
2013-04-06 9:14 ` Christoph Paasch
2013-04-06 9:18 ` Christoph Paasch
2013-04-06 17:43 ` Sergei Shtylyov
2013-04-06 17:54 ` Eric Dumazet
2013-04-06 18:27 ` Tetja Rediske [this message]
2013-04-07 14:37 ` Christoph Paasch
2013-04-08 9:56 ` Tetja Rediske
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=5160691E.2080105@tetja.de \
--to=tetja@tetja.de \
--cc=christoph.paasch@uclouvain.be \
--cc=davem@davemloft.net \
--cc=djduanjiong@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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 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.