<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I started (in /etc/rc.local) with<div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class="">/usr/sbin/modprobe tcrypt alg="pcrypt(rfc4106(gcm(aes)))" type=3</div></div><div class=""><div class="">/usr/sbin/modprobe tcrypt alg="pcrypt(rfc4106(gcm(aes-aesni)))" type=3</div></div></blockquote><div class=""><div class=""><br class=""></div><div class="">That dropped me in to a reboot loop with Centos 7 on AWS.</div><div class=""><br class=""></div><div class="">I then moved to (in /etc/rc.modules)</div><div class=""><br class=""></div></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class="">modprobe tcrypt alg="pcrypt(rfc4106(gcm(aes)))" type=3</div></div><div class=""><div class="">modprobe tcrypt alg="pcrypt(rfc4106(gcm(aes-aesni)))" type=3</div></div></blockquote><div class=""><div class=""><br class=""></div><div class="">No reboot loop, but no effect either. I do ignore the output (saw that part of the doc on the site)</div><div class=""><br class=""></div><div class="">EKG</div><div class=""><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class="">On Oct 2, 2017, at 2:46 AM, Noel Kuntze <<a href="mailto:noel.kuntze+strongswan-users-ml@thermi.consulting" class="">noel.kuntze+strongswan-users-ml@thermi.consulting</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi Ericm<br class=""><br class=""><blockquote type="cite" class="">I’ve gone down the path of exploring parallelization of crypto in Strongswan from [1].<br class=""></blockquote><br class="">s/Strongswan/Linux kernel/<br class=""><br class=""><br class=""><blockquote type="cite" class="">My question to the group is, how does one make it stick across boots? I tried the trick of putting the modprobe in /etc/rc.local and That Was Bad (continuous reboot loop). Backed it out and we’re ok. Obviously there has to be a better way. Wondering what the proper way in Centos 7 is for this module.<br class=""></blockquote><br class="">Well, load pcrypt, but then load tcrypt with the parameters *and do not care about the exit code*. Loading tcrypt will always error out, even if it configured everything as you wanted.<br class=""><br class="">What did you do exactly?<br class=""><br class="">Kind regards<br class=""><br class="">Noel<br class=""><br class="">On 02.10.2017 02:24, Eric Germann wrote:<br class=""><blockquote type="cite" class="">I’ve gone down the path of exploring parallelization of crypto in Strongswan from [1].<br class=""><br class="">It seems to be working as a) the expected output shows up in ‘cat /proc/crypto’ and b) under load in htop, it’s now showing kernel activity on all cores vs. a single core before (not sophisticated, but it definitely changed after the modprobe).<br class=""><br class="">My question to the group is, how does one make it stick across boots? I tried the trick of putting the modprobe in /etc/rc.local and That Was Bad (continuous reboot loop). Backed it out and we’re ok. Obviously there has to be a better way. Wondering what the proper way in Centos 7 is for this module.<br class=""><br class="">The process in [2] doesn’t seem to work for installing them.<br class=""><br class="">Thanks for sharing any experiences.<br class=""><br class="">EKG<br class=""><br class="">[1] <a href="https://wiki.strongswan.org/projects/strongswan/wiki/Pcrypt" class="">https://wiki.strongswan.org/projects/strongswan/wiki/Pcrypt</a><br class="">[2] <a href="https://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-kernel-modules-persistant.html" class="">https://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-kernel-modules-persistant.html</a><br class=""></blockquote><br class=""></div></div></blockquote></div><br class=""></div></body></html>