Hi Totti, > Particularly it seems to > occur if the previous request is fragmented and has been already > responded and then receiving retransmission of already responded request > only partially. After that Strongswan server is not responding to next > request coming from client.
Yes, I can see how this may happen. The current defragmentation state is only cleared after all fragments of a message have been received. Until then, fragments of other messages are ignored because the message ID does not match. I've pushed a fix to the clear-defrag branch [1]. Regards, Tobias [1] https://git.strongswan.org/?p=strongswan.git;a=shortlog;h=refs/heads/clear-defrag
