From: "James Ring" <sjr@jdns.org>
To: netdev@vger.kernel.org
Subject: IPsec and EAGAIN
Date: Tue, 13 Jun 2006 15:51:25 +1000 (EST) [thread overview]
Message-ID: <61418.152.91.8.100.1150177885.squirrel@webmail.jdns.org> (raw)
Hi all,
I have recently run into the issue where connect() returns -EAGAIN
if the remote host is on the other end of an IPsec tunnel for which no
SAD exists yet.
I have read a few threads on the topic, and it seems that the idea is to
implement a scheme similar to ARP for queueing outgoing packets until the
SAD has been negotiated by the IKE process.
I have a couple of questions: are there any patches out which solve this
problem?
Also, what is the purpose of the code in the xfrm_lookup function
(in net/xfrm_policy.c) when `flags' is true? I have applied a patch
similar to
http://sourceforge.net/mailarchive/message.php?msg_id=8621194
which gives desirable behaviour (ie. telnet appears to pause while the
racoon negotiation is performed, after which it connects just fine, no
EAGAIN).
Please CC me to any responses, I am not subscribed to the list.
Thanks for your time,
James
--
James Ring
next reply other threads:[~2006-06-13 5:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 5:51 James Ring [this message]
2006-06-13 11:44 ` IPsec and EAGAIN Herbert Xu
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=61418.152.91.8.100.1150177885.squirrel@webmail.jdns.org \
--to=sjr@jdns.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox