<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[VIA Padlock Hardware Crypto für IPSec]]></title><description><![CDATA[<p dir="auto">Servus!</p>
<p dir="auto">Mein VIA C7-D hat ja VIA Padlock onboard, welches ich gerne für IPSec nutzen möchte. Anhand der CPU-Auslastung und des Durchsatzes vermute ich das Padlock nicht genutzt wird.</p>
<p dir="auto">Ich habe auch mal ne Runde getestet:</p>
<blockquote>
<p dir="auto">[2.0-RELEASE][root@pfsense.localdomain]/boot/modules(31): openssl speed -elapsed -evp aes128 -engine cryptodev<br />
engine "cryptodev" set.<br />
You have chosen to measure elapsed time instead of user CPU time.<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: 789674 aes-128-cbc's in 3.00s<br />
Doing aes-128-cbc for 3s on 64 size blocks: 986427 aes-128-cbc's in 3.01s<br />
Doing aes-128-cbc for 3s on 256 size blocks: 909672 aes-128-cbc's in 3.01s<br />
Doing aes-128-cbc for 3s on 1024 size blocks: 654516 aes-128-cbc's in 3.01s<br />
Doing aes-128-cbc for 3s on 8192 size blocks: 124498 aes-128-cbc's in 3.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: gettimeofday<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       4205.63k    20976.12k    77370.13k   222675.38k   338788.64k</p>
</blockquote>
<blockquote>
<p dir="auto">[2.0-RELEASE][root@pfsense.localdomain]/boot/modules(51): openssl speed -elapsed -evp aes128 -engine padlock<br />
engine "padlock" set.<br />
You have chosen to measure elapsed time instead of user CPU time.<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: 12252187 aes-128-cbc's in 3.01s<br />
Doing aes-128-cbc for 3s on 64 size blocks: 12904150 aes-128-cbc's in 3.01s<br />
Doing aes-128-cbc for 3s on 256 size blocks: 7637010 aes-128-cbc's in 3.01s<br />
Doing aes-128-cbc for 3s on 1024 size blocks: 2885193 aes-128-cbc's in 3.02s<br />
Doing aes-128-cbc for 3s on 8192 size blocks: 376539 aes-128-cbc's in 3.00s<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: gettimeofday<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      65180.92k   274383.34k   649544.77k   978813.40k  1027706.80k</p>
</blockquote>
<p dir="auto">Somit ist Padlock da, läuft auch aber halt anscheinend nicht mit IPSec. Ich habe IPSec auf AES gestellt.</p>
<p dir="auto">Syslog vermeldet</p>
<blockquote>
<p dir="auto">kernel: padlock0: &lt;aes-cbc,sha1,sha256&gt;on motherboard und kernel: VIA Padlock Features=0xffcc&lt;rng,aes,aes-ctr,sha1,sha256,rsa&gt;&lt;/rng,aes,aes-ctr,sha1,sha256,rsa&gt;&lt;/aes-cbc,sha1,sha256&gt;</p>
</blockquote>
<p dir="auto">Kann mir de jemand helfen? Für OpenVPN kann man die Hardware-Crypt nämlich gezielt auswählen.</p>
<p dir="auto">Danke!</p>
]]></description><link>https://forum.netgate.com/topic/38526/via-padlock-hardware-crypto-für-ipsec</link><generator>RSS for Node</generator><lastBuildDate>Thu, 15 Oct 2026 07:52:26 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/38526.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 24 Oct 2011 13:56:10 GMT</pubDate><ttl>60</ttl></channel></rss>