# Ipsec differences between devices: is kmod-crypto-ctr the problem?

**URL:** <https://forum.openwrt.org/t/ipsec-differences-between-devices-is-kmod-crypto-ctr-the-problem/44461>\
**Category:** For Developers\
**Created:** [September 12, 2019, 11:05am UTC](https://forum.openwrt.org/t/ipsec-differences-between-devices-is-kmod-crypto-ctr-the-problem/44461 "2019-09-12T11:05:38Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![cotequeiroz](https://forum.openwrt.org/user_avatar/forum.openwrt.org/cotequeiroz/32/6503_2.png) [@cotequeiroz](https://forum.openwrt.org/u/cotequeiroz)\
**Post date:** [October 10, 2019, 6:07pm UTC](https://forum.openwrt.org/t/ipsec-differences-between-devices-is-kmod-crypto-ctr-the-problem/44461/14 "2019-10-10T18:07:58Z")

</div>

I don't have the hardware, so I won't be able to check this on my own. I caught the bug by looking at the output of `/proc/crypto` that @chunkeey posted [here](https://forum.openwrt.org/t/comparing-cpu-soc-performance/36115/17)

@jeff, @chunkeey can you also confirm if the patch works? I just mean that `/proc/crypto` should show blocksize=1 for ctr(aes) with the ctr-aes-qce driver.

I don't necessarily think that this will bring up rfc3686 support on its own (I'm just hoping, really); it may require more effort, but the block size should be fixed, so, I will send patches to openwrt and upstream after confirmation.

---

_[View the full topic](https://forum.openwrt.org/t/ipsec-differences-between-devices-is-kmod-crypto-ctr-the-problem/44461)._