https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162010-07-20T14:48:30ZpfSense bugtrackerpfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=25132010-07-20T14:48:30ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Category</strong> changed from <i>OpenVPN</i> to <i>Operating System</i></li></ul><p>where is this patch?</p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=25522010-07-26T13:31:11ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>Needs testing on 8.1 and a pointer to the mentioned patch if such a thing exists.</p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=25552010-07-26T15:06:45ZMr Horizontalzzing123@gmail.com
<ul></ul><p>I'm no expert at knowing whether this is any good - you have to trawl through the archives, but this one seems pretty promising:</p>
<p><a class="external" href="http://gnats.netbsd.org/26673">http://gnats.netbsd.org/26673</a></p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=25612010-07-27T03:47:30ZMr Horizontalzzing123@gmail.com
<ul></ul><p>8.1 hasn't changed anything. Here's the output on an ALIX 2D3:</p>
<ol>
<li>uname -a<br />FreeBSD gateway.X.X.X 8.1-RC2 FreeBSD 8.1-RC2 #0: Mon Jul 26 06:24:21 EDT 2010 sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386 i386
#</li>
<li>openssl engine -c<br />(cryptodev) BSD cryptodev engine<br /> [RSA, DSA, DH, DES-CBC, DES-EDE3-CBC, AES-128-CBC]<br />(padlock) VIA PadLock (no-RNG, no-ACE)<br />(dynamic) Dynamic engine loading support
#</li>
<li>openssl speed -evp aes-256-cbc -engine cryptodev<br />engine "cryptodev" set.<br />To get the most accurate results, try to run this<br />program when this computer is idle.<br />Doing aes-256-cbc for 3s on 16 size blocks: 736145 aes-256-cbc's in 2.99s<br />Doing aes-256-cbc for 3s on 64 size blocks: 202072 aes-256-cbc's in 2.97s<br />Doing aes-256-cbc for 3s on 256 size blocks: 52063 aes-256-cbc's in 2.98s<br />Doing aes-256-cbc for 3s on 1024 size blocks: 13132 aes-256-cbc's in 2.98s<br />Doing aes-256-cbc for 3s on 8192 size blocks: 1643 aes-256-cbc's in 2.98s<br />OpenSSL 0.9.8n 24 Mar 2010<br />built on: date not available<br />options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes(partial) blowfish(idx) <br />compiler: cc<br />available timing options: USE_TOD HZ=128 [sysconf value]<br />timing function used: getrusage<br />The 'numbers' are in 1000s of bytes per second processed.<br />type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes<br />aes-256-cbc 3939.52k 4357.76k 4470.99k 4514.63k 4519.40k</li>
</ol> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=27432010-08-06T03:52:06ZMr Horizontalzzing123@gmail.com
<ul></ul><p>There's also a FreeBSD bug report relating to this that's been open since Feb 2008: <a class="external" href="http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/120270">http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/120270</a></p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=36192010-11-10T07:00:40ZMr Horizontalzzing123@gmail.com
<ul></ul><p>This is still not fixed as of 10 Nov 2010...</p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=38452010-11-27T15:27:46ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>New</i></li></ul><p>need to determine if there is a reason this patch in kern/120270 hasn't been committed.</p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=39092010-11-29T17:56:17ZScott Ullrichsullrich@gmail.com
<ul><li><strong>Target version</strong> changed from <i>2.0</i> to <i>2.1</i></li></ul><p>Still not fixed in FreeBSD. Delaying ticket to 2.1.</p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=39122010-11-29T18:11:42ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Target version</strong> changed from <i>2.1</i> to <i>2.0</i></li></ul><p>We need to follow up on the PR above, a customer needs this.</p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=49382011-02-11T17:14:59ZErmal Luçieri@pfsense.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>This has been committed to repo.<br />Please test.</p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=49442011-02-14T09:36:34ZA B
<ul></ul><p>I did a test with my alix 2d2 box and a vpn1411 card.</p>
<p>Here are the results with the fresh updated image (pfSense-2.0-RC1-4g-i386-20110214-0324-nanobsd-upgrade.img.gz) on the alix box:</p>
<p>root(1): openssl engine -c<br />(cryptodev) BSD cryptodev engine<br /> [RSA, DSA, DH, DES-CBC, DES-EDE3-CBC, AES-128-CBC]<br />(padlock) VIA PadLock (no-RNG, no-ACE)<br />(dynamic) Dynamic engine loading support</p>
<p>First test with aes-128-cbc:</p>
<p>/root(4): openssl speed -evp aes-128-cbc -engine cryptodev<br />engine "cryptodev" set.<br />To get the most accurate results, try to run this<br />program when this computer is idle.<br />Doing aes-128-cbc for 3s on 16 size blocks: 59274 aes-128-cbc's in 0.08s<br />Doing aes-128-cbc for 3s on 64 size blocks: 50889 aes-128-cbc's in 0.07s<br />Doing aes-128-cbc for 3s on 256 size blocks: 46414 aes-128-cbc's in 0.04s<br />Doing aes-128-cbc for 3s on 1024 size blocks: 28853 aes-128-cbc's in 0.04s<br />Doing aes-128-cbc for 3s on 8192 size blocks: 6377 aes-128-cbc's in 0.01s<br />OpenSSL 0.9.8n 24 Mar 2010<br />built on: date not available<br />options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes(partial) blowfish(idx)<br />compiler: cc<br />available timing options: USE_TOD HZ=128 [sysconf value]<br />timing function used: getrusage<br />The 'numbers' are in 1000s of bytes per second processed.<br />type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes<br />aes-128-cbc 11926.96k 43881.06k 292746.23k 799087.79k 4099857.48k</p>
<p>Second test with aes-192-cbc:</p>
<p>/root(5): openssl speed -evp aes-192-cbc -engine cryptodev<br />engine "cryptodev" set.<br />To get the most accurate results, try to run this<br />program when this computer is idle.<br />Doing aes-192-cbc for 3s on 16 size blocks: 796761 aes-192-cbc's in 2.90s<br />Doing aes-192-cbc for 3s on 64 size blocks: 223249 aes-192-cbc's in 2.93s<br />Doing aes-192-cbc for 3s on 256 size blocks: 58179 aes-192-cbc's in 2.95s<br />Doing aes-192-cbc for 3s on 1024 size blocks: 14786 aes-192-cbc's in 2.98s<br />Doing aes-192-cbc for 3s on 8192 size blocks: 1835 aes-192-cbc's in 2.95s<br />OpenSSL 0.9.8n 24 Mar 2010<br />built on: date not available<br />options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes(partial) blowfish(idx)<br />compiler: cc<br />available timing options: USE_TOD HZ=128 [sysconf value]<br />timing function used: getrusage<br />The 'numbers' are in 1000s of bytes per second processed.<br />type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes<br />aes-192-cbc 4400.92k 4871.91k 5042.90k 5083.21k 5104.08k</p>
<p>Third test with aes-256-cbc:</p>
<p>/root(2): openssl speed -evp aes-256-cbc -engine cryptodev<br />engine "cryptodev" set.<br />To get the most accurate results, try to run this<br />program when this computer is idle.<br />Doing aes-256-cbc for 3s on 16 size blocks: 726153 aes-256-cbc's in 2.94s<br />Doing aes-256-cbc for 3s on 64 size blocks: 190858 aes-256-cbc's in 2.81s<br />Doing aes-256-cbc for 3s on 256 size blocks: 49574 aes-256-cbc's in 2.84s<br />Doing aes-256-cbc for 3s on 1024 size blocks: 12053 aes-256-cbc's in 2.75s<br />Doing aes-256-cbc for 3s on 8192 size blocks: 1473 aes-256-cbc's in 2.69s<br />OpenSSL 0.9.8n 24 Mar 2010<br />built on: date not available<br />options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes(partial) blowfish(idx)<br />compiler: cc<br />available timing options: USE_TOD HZ=128 [sysconf value]<br />timing function used: getrusage<br />The 'numbers' are in 1000s of bytes per second processed.<br />type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes<br />aes-256-cbc 3953.05k 4343.71k 4476.49k 4492.25k 4482.33k</p>
<p>Looks like it doesn't work for me. Or did I something wrong at the tests?</p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=49492011-02-15T03:20:52ZF Spfsense@d0mini0n.net
<ul></ul><p>Test System: alix 2d2 + vpn1411 card.<br />Beta Version: pfSense-2.0-RC1-4g-i386-20110214-0324</p>
<p>seems like the vpn card is used according to cryptostats. But the shuffeling from kernel to userland and back again takes all the performance gains. With OpenVPN set to aes-128-cbc and using cryptodev, the max speed was approx. 10-12Mbit which is with a CPU usage of 90% same as it would be on bare metal. Maybe I missing some other configuration to make this work propper?!?</p>
<ol>
<li>cryptostats<br />30253149 symmetric crypto ops (0 errors, 0 times driver blocked)<br />0 key ops (0 errors, 0 times driver blocked)<br />14967680 crypto dispatch thread activations<br />0 crypto return thread activations</li>
</ol> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=49502011-02-15T07:42:19ZJim Pingle
<ul></ul><p>F S wrote:</p>
<blockquote>
<p>Test System: alix 2d2 + vpn1411 card.<br />Beta Version: pfSense-2.0-RC1-4g-i386-20110214-0324</p>
<p>seems like the vpn card is used according to cryptostats. But the shuffeling from kernel to userland and back again takes all the performance gains. With OpenVPN set to aes-128-cbc and using cryptodev, the max speed was approx. 10-12Mbit which is with a CPU usage of 90% same as it would be on bare metal. Maybe I missing some other configuration to make this work propper?!?</p>
</blockquote>
<p>Did you disable glxsb under System > Advanced, on the misc tab? Unless you disable glxsb, the Hifn won't be used.</p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=49512011-02-15T08:40:40ZA B
<ul></ul><p>I did the test with and without glxsb activated. There was no difference in the results.</p>
<p>Could it be that the hifn driver isn't loaded correct?<br />How could I check this?</p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=50512011-03-02T15:25:49ZAlexander Norbergalexander.norberg@gmail.com
<ul></ul><p>pfSense 2.0-RC1-nanoBSD (i386) built on Sat Feb 26 16:33:51 EST 2011 <br />Running on Soekris net5501 with Hardware crypto card Hifn 7955</p>
<p>[2.0-RC1][<a class="email" href="mailto:admin@pfsense.home">admin@pfsense.home</a>]/root(1): openssl speed -evp aes-128-cbc -engine cryptodev<br />engine "cryptodev" set.<br />To get the most accurate results, try to run this<br />program when this computer is idle.<br />Doing aes-128-cbc for 3s on 16 size blocks: 18183 aes-128-cbc's in 0.06s<br />Doing aes-128-cbc for 3s on 64 size blocks: 17926 aes-128-cbc's in 0.07s<br />Doing aes-128-cbc for 3s on 256 size blocks: 16731 aes-128-cbc's in 0.04s<br />Doing aes-128-cbc for 3s on 1024 size blocks: 13808 aes-128-cbc's in 0.06s<br />Doing aes-128-cbc for 3s on 8192 size blocks: 5112 aes-128-cbc's in 0.01s<br />OpenSSL 0.9.8n 24 Mar 2010<br />built on: date not available<br />options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes(partial) blowfish(idx)<br />compiler: cc<br />available timing options: USE_TOD HZ=128 [sysconf value]<br />timing function used: getrusage<br />The 'numbers' are in 1000s of bytes per second processed.<br />type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes<br />aes-128-cbc 5133.81k 16332.56k 106439.76k 224199.92k 5177732.94k</p>
<p>[2.0-RC1][<a class="email" href="mailto:admin@pfsense.home">admin@pfsense.home</a>]/root(2): openssl speed -evp aes-192-cbc -engine cryptodev<br />engine "cryptodev" set.<br />To get the most accurate results, try to run this<br />program when this computer is idle.<br />Doing aes-192-cbc for 3s on 16 size blocks: 788966 aes-192-cbc's in 2.85s<br />Doing aes-192-cbc for 3s on 64 size blocks: 219687 aes-192-cbc's in 2.85s<br />Doing aes-192-cbc for 3s on 256 size blocks: 55989 aes-192-cbc's in 2.83s<br />Doing aes-192-cbc for 3s on 1024 size blocks: 13800 aes-192-cbc's in 2.78s<br />Doing aes-192-cbc for 3s on 8192 size blocks: 1666 aes-192-cbc's in 2.69s<br />OpenSSL 0.9.8n 24 Mar 2010<br />built on: date not available<br />options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes(partial) blowfish(idx)<br />compiler: cc<br />available timing options: USE_TOD HZ=128 [sysconf value]<br />timing function used: getrusage<br />The 'numbers' are in 1000s of bytes per second processed.<br />type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes<br />aes-192-cbc 4423.20k 4925.50k 5068.97k 5080.86k 5082.34k</p>
<p>[2.0-RC1][<a class="email" href="mailto:admin@pfsense.home">admin@pfsense.home</a>]/root(3): openssl speed -evp aes-256-cbc -engine cryptodev<br />engine "cryptodev" set.<br />To get the most accurate results, try to run this<br />program when this computer is idle.<br />Doing aes-256-cbc for 3s on 16 size blocks: 731079 aes-256-cbc's in 2.97s<br />Doing aes-256-cbc for 3s on 64 size blocks: 202640 aes-256-cbc's in 2.98s<br />Doing aes-256-cbc for 3s on 256 size blocks: 52026 aes-256-cbc's in 2.96s<br />Doing aes-256-cbc for 3s on 1024 size blocks: 12135 aes-256-cbc's in 2.75s<br />Doing aes-256-cbc for 3s on 8192 size blocks: 1643 aes-256-cbc's in 2.98s<br />OpenSSL 0.9.8n 24 Mar 2010<br />built on: date not available<br />options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes(partial) blowfish(idx)<br />compiler: cc<br />available timing options: USE_TOD HZ=128 [sysconf value]<br />timing function used: getrusage<br />The 'numbers' are in 1000s of bytes per second processed.<br />type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes<br />aes-256-cbc 3942.66k 4356.92k 4492.45k 4511.50k 4518.60k</p>
<p>[2.0-RC1][<a class="email" href="mailto:admin@pfsense.home">admin@pfsense.home</a>]/root(4): cryptostats<br />71914 symmetric crypto ops (0 errors, 0 times driver blocked)<br />0 key ops (0 errors, 0 times driver blocked)<br />0 crypto dispatch thread activations<br />154 crypto return thread activations</p>
<p>[2.0-RC1][<a class="email" href="mailto:admin@pfsense.home">admin@pfsense.home</a>]/root(5): openssl engine -c<br />(cryptodev) BSD cryptodev engine<br /> [RSA, DSA, DH, DES-CBC, DES-EDE3-CBC, AES-128-CBC]<br />(padlock) VIA PadLock (no-RNG, no-ACE)<br />(dynamic) Dynamic engine loading support</p>
<p>If more tests are needed, please let me know.</p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=50732011-03-05T07:49:58ZMr Horizontalzzing123@gmail.com
<ul><li><strong>File</strong> <a href="/attachments/285">test1.txt</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/285/test1.txt">test1.txt</a> added</li><li><strong>File</strong> <a href="/attachments/286">test2</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/286/test2">test2</a> added</li><li><strong>File</strong> <a href="/attachments/287">test3</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/287/test3">test3</a> added</li></ul><p>Below I've posted results for the following series of commands, so you get a summary as well as all the output:</p>
<ol>
<li>openssl engine -c</li>
<li>cryptostats</li>
<li>hifnstats</li>
<li>cryptotest -z</li>
<li>cryptostats</li>
<li>hifnstats</li>
<li>openssl speed -evp aes-128-cbc -engine cryptodev</li>
<li>cryptostats</li>
<li>hifnstats</li>
<li>openssl speed -evp aes-192-cbc -engine cryptodev</li>
<li>cryptostats</li>
<li>hifnstats</li>
<li>openssl speed -evp aes-256-cbc -engine cryptodev</li>
<li>cryptostats</li>
<li>hifnstats</li>
</ol>
<p>I then conducted 3 tests each after a clean reboot on an Alix 2D2. The hifn card is a Soekris vpn1411 card:<br />[Test 1]: disable glxsb and remove hifn.<br />[Test 2]: enable glxsb and remove hifn.<br />[Test 3]: disable glxsb and insert hifn.</p>
<p>Results are attached if you want to read through the output.</p>
<p>Test 1 and 2 work as expected, with the CPU being slower than the glxsb acceleration. This is backed up by the fact that cryptostats shows activity, while hifnstats shows nothing happening.</p>
<p>Test 3 shows that AES 128 is accelerated, but 192 and 256 don't do anything.</p>
<p>In the meantime, cryptotest -z tests all the functions of the HIFN card withoud using OpenSSL, so...</p>
<p>- There are 3 parts where the hifn wouldn't be working:<br />- The hifn(4) driver itself, but I don't expect this to be bad since cryptotest <del>z works<br /></del> OpenSSL 0.9.8n seems to have the new engine table format, see<br /> <a class="external" href="http://cvs.openssl.org/rlog?f=openssl/crypto/engine/eng_cryptodev.c">http://cvs.openssl.org/rlog?f=openssl/crypto/engine/eng_cryptodev.c</a><br /> which may break support for hifn, given that it has recently been touched for adding direct<br /> AES-NI support in Intel Westmere and later CPUs<br />- To use hifn, OpenSSL loads the BSD cryptodev engine which may also have broken support, as the<br /> latest cryptodev engine code in FreeBSD's source tree is quite new:<br /> FreeBSD source shows:<br /> <a class="external" href="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/opencrypto/cryptodev.h">http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/opencrypto/cryptodev.h</a><br /> <a class="external" href="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/opencrypto/cryptodev.c">http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/opencrypto/cryptodev.c</a><br />compared to another source, in DragonflyBSD:<br /> <a class="external" href="http://cvsweb.dragonflybsd.org/cvsweb/src/sys/opencrypto/cryptodev.h">http://cvsweb.dragonflybsd.org/cvsweb/src/sys/opencrypto/cryptodev.h</a><br /> <a class="external" href="http://cvsweb.dragonflybsd.org/cvsweb/src/sys/opencrypto/cryptodev.c">http://cvsweb.dragonflybsd.org/cvsweb/src/sys/opencrypto/cryptodev.c</a></p>
<p>Alternatively, given all the above, they basically require compiler flags to be set correctly and could have been compiled wrong?</p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=66882011-08-13T23:07:08ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Target version</strong> deleted (<del><i>2.0</i></del>)</li></ul> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=96332012-08-11T17:52:22ZStephen Gaglairdostephen.gagliardo@gmail.com
<ul></ul><p>Just would like to confirm that fairly identical results are produced on my ALIX.6F2 with my soekris VPN1411 (HIFN 7955). Reproduces exactly as these posters have said, with nearly identical numbers when I access via serial port and run them.</p>
<p>Has there been any progress on this for the next stable release (whenever that should be)?</p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=123392013-09-03T08:16:55ZIgor Liebermannigor.liebermann@email.de
<ul></ul><p>I can confirm the problem on pfSense 2.0.3, Alix.2D13 and soekris VPN1411 (hifn 7955).<br />There is no difference in throughput in the OpenVPN AES256-Tunnel.</p>
<p>Is it planned to fix this issue? Any target release?</p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=125622013-09-28T08:41:55ZScott Douglasscooterdouglas@hotmail.com
<ul><li><strong>File</strong> <a href="/attachments/856">Soekris5501_VPN1401(HIFN 7955)-2.03R.txt</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/856/Soekris5501_VPN1401(HIFN%207955)-2.03R.txt">Soekris5501_VPN1401(HIFN 7955)-2.03R.txt</a> added</li><li><strong>File</strong> <a href="/attachments/857">Soekris5501_VPN1401(HIFN 7955)-2.1R</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/857/Soekris5501_VPN1401(HIFN%207955)-2.1R">Soekris5501_VPN1401(HIFN 7955)-2.1R</a> added</li></ul><p>I've attached a couple of text files showing the Soekris VPN-1401 (Hifn-7955 / PCI Bus) version working in a Soekris 5501-70.</p>
<p>- Soekris VPN-1401 (PCI Bus) and a Soekris 5501-70 seems to be working OK.<br />- Soekris VPN-1411 (mini-PCI bus) and an ALIX.2D2 or ALIX.6F2 does not seem to be working.</p>
<p>What is the output from the command, "dmesg | grep -i hifn" on the various ALIX systems?</p>
<p>My Soekris 5501-70 shows the following output for both v2.03-RELEASE and v2.1-RELEASE:</p>
<p>root(17): dmesg | grep -i hifn<br />hifn0 mem 0xa0005000-0xa0005fff,0xa0006000-0xa0007fff,0xa0008000-0xa000ffff irq 10 at device 14.0 on pci0<br />hifn0: [ITHREAD]<br />hifn0: Hifn 7955, rev 0, 32KB dram, pll=0x801<ext clk, 4x mult></p>
<p>Is there anything else that you need tested?</p> pfSense - Bug #754: hifn driver and AES192 and 256https://redmine.pfsense.org/issues/754?journal_id=185632015-06-01T18:14:13ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Needs Patch</i></li></ul><p>if someone wants to put the efforts into fixing this (if it isn't already on 2.2x with FreeBSD 10.1 base), please pursue and get fixed upstream in FreeBSD.</p>