linux-kernel - IPSEC in 2.6.25 causes stalled connections

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 8 Jun 2008 03:08:58 +0200
From:	Thomas Zeitlhofer <tzeitlho+lkml@...tuwien.ac.at>
To:	linux-kernel@...r.kernel.org
Cc:	netdev@...r.kernel.org
Subject: IPSEC in 2.6.25 causes stalled connections

Hello,

I have two machines (x86_64) connected via a direct network link (i.e.
directly connected by cable).

IPSEC is used for all traffic over this link. 

Everything works fine as long as the traffic is low. E.g. several
interactive ssh sessions are ok.

If a TCP or UDP connection (e.g. cat /dev/zero | netcat [-u] ...)
produces a lot of traffic then this connection typically stalls within
a couple minutes. Some but not all of the other open connections (e.g.
ssh sessions) get stuck too. The stalled connections do not recover and
the ssh sessions finally terminate with a timeout error.

This happens with 2.6.25.4 (also tested with 2.6.25) and IPSEC. Without
IPSEC there is no problem with stalled connections.

The problem also goes away if I switch back to 2.6.24.4.

Is this a known issue?

Thanks,

Thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/