I have an Intel NUC 11 Pro Kit (BNUC11TNHV50L00), unfortunately the network card does not work in the current OPNsense. When can you expect the drivers to be integrated?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts Menu| Rechner: | Intel® NUC 11 Pro Kit NUC11TNHv50L |
| CPU: | Intel® Core™ i5-1145G7 Processor (8M Cache, up to 4,40 GHz, with IPU) |
| RAM: | 2 x Crucial DDR4-3200 16GB SO-DIMM |
| ETH: | Dual Intel® Ethernet Controller i225-LM |
root@rt:~ # openssl speed -elapsed -evp aes-256-cbc
You have chosen to measure elapsed time instead of user CPU time.
Doing aes-256-cbc for 3s on 16 size blocks: 2147483647 aes-256-cbc's in 2.73s
Doing aes-256-cbc for 3s on 64 size blocks: 949352368 aes-256-cbc's in 3.02s
Doing aes-256-cbc for 3s on 256 size blocks: 108571095 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 1024 size blocks: 27283440 aes-256-cbc's in 3.01s
Doing aes-256-cbc for 3s on 8192 size blocks: 3404923 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 16384 size blocks: 1753082 aes-256-cbc's in 3.09s
OpenSSL 1.1.1d-freebsd 10 Sep 2019
built on: reproducible build, date unspecified
options:bn(64,64) rc4(16x,int) des(int) aes(partial) idea(int) blowfish(ptr)
compiler: clang
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes
aes-256-cbc 12565847.17k 20147913.47k 9264733.44k 9288558.57k 9297709.74k 9284038.95k
root@rt:~ # openssl speed -elapsed -evp aes-256-gcm
You have chosen to measure elapsed time instead of user CPU time.
Doing aes-256-gcm for 3s on 16 size blocks: 1813578232 aes-256-gcm's in 3.06s
Doing aes-256-gcm for 3s on 64 size blocks: 1141754627 aes-256-gcm's in 3.00s
Doing aes-256-gcm for 3s on 256 size blocks: 661257838 aes-256-gcm's in 3.05s
Doing aes-256-gcm for 3s on 1024 size blocks: 219639263 aes-256-gcm's in 3.01s
Doing aes-256-gcm for 3s on 8192 size blocks: 33312238 aes-256-gcm's in 3.01s
Doing aes-256-gcm for 3s on 16384 size blocks: 16918974 aes-256-gcm's in 3.00s
OpenSSL 1.1.1d-freebsd 10 Sep 2019
built on: reproducible build, date unspecified
options:bn(64,64) rc4(16x,int) des(int) aes(partial) idea(int) blowfish(ptr)
compiler: clang
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes
aes-256-gcm 9475020.97k 24357432.04k 55417127.46k 74775473.97k 90728346.16k 92400156.67k
QuoteUm über die Netzwerkschnittstellen auch eine Verschlüsselung anbieten zu können, verbaut Intel seine QuickAssist Technology (QAT) für alle erdenklichen Verschlüsselungstechnologien, Schlüsselgeneration und Kompressionsverfahren (maximal 30 GBit/s Durchsatz und 30.000 OPS insgesamt). Die 30 GBit/s sollen beispielsweise für SSL und IPSec erreicht werden.
2020-08-07T22:29:50 haproxy[32735]: Connect from 80.175.fff.zzz:56011 to 192.168.3.2:80 (http_lan_wan/HTTP)
2020-08-07T22:29:50 haproxy[32735]: Connect from 80.175.fff.zzz:56008 to 192.168.3.2:80 (http_lan_wan/HTTP)
2020-08-07T22:17:44 haproxy[32735]: 80.187.xxx.yy:18061 [07/Aug/2020:22:17:44.135] https_lan_wan/192.168.3.2:443: SSL handshake failure
2020-08-07T22:17:43 haproxy[32735]: 80.187.xxx.yy:18040 [07/Aug/2020:22:17:43.353] https_lan_wan/192.168.3.2:443: SSL handshake failure
2020-08-07T22:17:38 haproxy[32735]: 80.187.xxx.yy:17830 [07/Aug/2020:22:17:38.652] https_lan_wan/192.168.3.2:443: SSL handshake failure
2020-08-07T22:17:38 haproxy[32735]: 80.187.xxx.yy:17828 [07/Aug/2020:22:17:38.649] https_lan_wan/192.168.3.2:443: SSL handshake failure
2020-08-07T22:17:37 haproxy[32735]: 80.187.xxx.yy:17733 [07/Aug/2020:22:17:37.201] https_lan_wan/192.168.3.2:443: SSL handshake failure
DSL <--> (Port 80) OPNsense <--> (weiterleitung auf die VM) Webserver