On 01/09/2018 05:58 PM, Gé Weijers wrote:
> On Wed, Jan 3, 2018 at 2:32 PM, Walter Parker wrote:
>> On Wed, Jan 3, 2018 at 2:25 PM, Steve Yates wrote:
>>> I'm not a developer but I would think it's dependent on FreeBSD releasing
>>> the update, plus
I have not had such an issue. Using 2.4.2 with System Information widget
saying "AES-NI CPU Crypto: No".
On 02/15/2018 11:55 AM, Eero Volotinen wrote:
> Please note that next pfsense will not install hardware that is not
> supporting aes-ni?
> On Thu, F
>> I believe I read somewhere that the new version that requires aes-ni will
>> be 3.x, and they plan to continue the 2.x line alongside it, as 3.x will be
>> a major rewrite
>> -Original Message-
This board does round-up gigabit (something like 976 Mb/s) in both
directions on all 4 interfaces: https://www.amazon.com/dp/B00XNR4HE2/
The key for me here was the interrupt coalescence of these particular
Intel NICs. A very similar board with Broadcom NICs that lacked this
feature maxed out the
edded/dev boards using older Celeron processors.
> On Thu, Feb 15, 2018 at 9:37 AM, Kyle Marek <pspps...@gmail.com> wrote:
>> This is silly. I shouldn't have to replace my hardware to support a
>> feature I will not use...
>> I sh
I understand that a lot of people are effectively threatening to switch
to OpnSense due to this, but I fear that I will *have to* if I can't
replace my hardware by the time support for software AES ends entirely.
> Sent: Tuesday, January 9, 2018 5:32 PM
> To: pfSense Support and Discussion Mailing List <email@example.com>
> Subject: Re: [pfSense] 'Kernel memory leaking' Intel processor design flaw
> forces Linux, Windows redesign • The Register - patch to pfsense?
I have created a similar network and this is exactly what I do. Not
translating addresses greatly simplifies any DNS configuration where you
give names to all of your devices, too.
On 03/30/2018 12:41 PM, Steve Yates wrote:
> Wouldn't it be easier to just create a firewall rule to allow the Guest