From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: slow tcp connect when using IPsec
Date: Fri, 25 Mar 2011 09:58:45 +0100 [thread overview]
Message-ID: <20110325085845.GH1290@secunet.com> (raw)
In-Reply-To: <20110325.012749.235670347.davem@davemloft.net>
On Fri, Mar 25, 2011 at 01:27:49AM -0700, David Miller wrote:
>
> > So now I know why it did not behave as expected, but unfortunately I
> > still don't know why it magically started to work after 20
> > seconds...
>
> After some time, TCP will mark routing path as having trouble, then it
> will relookup the route. At this point source and dest will no longer
> be wildcarded in the socket, and thus neither will be the resulting
> route keys in the relooked-up route.
>
> Look for the dst_negative_advice() paths to see where this happens.
Ok, I see. Thanks for the explanation.
prev parent reply other threads:[~2011-03-25 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 6:41 slow tcp connect when using IPsec Steffen Klassert
2011-03-25 6:42 ` [PATCH] route: Take the right src and dst addresses in ip_route_newports Steffen Klassert
2011-03-25 8:29 ` David Miller
2011-03-25 8:27 ` slow tcp connect when using IPsec David Miller
2011-03-25 8:58 ` Steffen Klassert [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=20110325085845.GH1290@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--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 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).