[IPSec] connect: Resource temporarily unavailable

2 messages, 2 authors, 2004-02-24 · open the first message on its own page

[IPSec] connect: Resource temporarily unavailable

From: Felipe Alfaro Solana <hidden>
Date: 2004-02-24 13:48:53

When using Racoon to manage SAs between two IPv4/IPSec hosts running 2.6
kernels and IPSec in transport mode with mandatory ESP/AH support, the
first packet exchange between both hosts triggers IKE Phase 1 but,
instead of queueing the userspace packet that triggered the IKE exchange
until IKE Phase 2 has ended and the SA has been established, userspace
receives the following errpr:

connect: Resource temporarily unavailable

Any further attempt to exchange packets between both hosts succeeds
after a while, (once the IKE Phase 2 ends and the SA has been correctly
established).

Is this a bug? Shouldn't the kernel queue (hold) userspace packets until
IKE Phase 2 has completed (either successfully or with error)? Why am I
receiving "connect: Resource temporarily unavailable" error when there
is no SA set up?

This is reproducible by either pinging or telnetting the other peer or
the IPSec link. Both hosts are running 2.6.3 kernels and ipsec-tools
0.2.2. Once IKE Phase 2 ends, ping and telnet work with no error and
tcpdump reveals that AH/ESP protocols are being used.

Re: [IPSec] connect: Resource temporarily unavailable

From: David S. Miller <hidden>
Date: 2004-02-24 18:12:54

On Tue, 24 Feb 2004 14:48:41 +0100
Felipe Alfaro Solana [off-list ref] wrote:
connect: Resource temporarily unavailable
Known behavior, and it's unlikely to be changing soon as doing the correct
thing here requires a lot of work.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help