On Mon, Nov 11, 2019 at 06:47:35PM +0100, Tobias Heider wrote:
> With IKEv2 message fragmentation a message is split into several fragments,
> which all have the same sequence number. In the original commit this was
> handled with an explicit exception to accept the same sequence number as
> before
With IKEv2 message fragmentation a message is split into several fragments,
which all have the same sequence number. In the original commit this was
handled with an explicit exception to accept the same sequence number as
before, in case the number of stored fragments is not 0.
Another recent fix