I have a pfSense 2.0.3 box with 5 interfaces, two of which are on
motherboard ethernet controllers using the NVIDIA nForce4 CK804 MCP9
Networking Adapter chipset.
These two connections connect to the upstream IP (WAN) and to the old IP
space for the local network (LAN).
I've been seeing the the c
I think the people with the relevant skill are willing to fix it, when
they're show that what they did (cryptdev support) doesn't provide any
benefit.
read: it's being taken care of.
On Mon, Nov 11, 2013 at 1:20 PM, Vick Khera wrote:
> Did you get the sense people with the relevant skill were o
Did you get the sense people with the relevant skill were open to a bounty
for implementing the necessary fixes?
On Mon, Nov 11, 2013 at 1:36 PM, Jim Thompson wrote:
> I was at the FreeBSD Vendor Summit last week, and raised the AES-NI
> issue as "important to be solved in the next six months".
I was at the FreeBSD Vendor Summit last week, and raised the AES-NI
issue as "important to be solved in the next six months".
The issue and fix are understood, it just needs someone to implement
it (and then, presumably, backport it to 8.3, so we can release an
update to 2.1 (2.1.1 or similar).
J
