Thanks Tobias for the advise, adding a kernel Task to pull in the kernel team as well (confirmed to stop the bot from asking for logs).
@bugproxy: "configure the encryption with aes128gcm8 for IPsec" can probably be done in more than one way. To avoid wasting effort could you just provide the config files you used on both ends This is -not- overriding the question of xnox if it works in a newer strongswan. @bugproxy: As the kernel might be important (see the comment above), another check is to verify if the same occurs with the HWE kernel "linux-generic-hwe-18.04" currently at 4.18.0.18.68. Furthermore you should try 5.1 from [1] This is -not- overriding the question of xnox if it works in a newer strongswan either. [1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1/ ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828035 Title: StrongSwan with GCM and large packet sizes produces unstable behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
