OPNsense Forum

Archive => 17.7 Legacy Series => Topic started by: cardins2u on October 14, 2017, 08:45:11 am

Title: AES-IN
Post by: cardins2u on October 14, 2017, 08:45:11 am

Does OPNsense plan on forcing us to have AES-IN forced CPu requirement for future versions?

I hope this is not the case so I can keep deploying OPNSense to my customers with your hardware

Title: Re: AES-IN
Post by: franco on October 14, 2017, 09:27:15 am

No. OPNsense code is open source, freely available on the internet an can be built for any purpose or hardware.

Do you accept anything less from open source? ;)


Cheers,
Franco

Title: Re: AES-IN
Post by: cardins2u on October 14, 2017, 09:55:33 am

I'm an idiot so open-source or not wouldn't make sense.

What make sense to me is stability and good community to hang around with. I made a huge switch to OPNSense because of the constant updates. It makes my network feel safer.

Though I miss some features from PFSense like SquidProxy stats (hit statistics), and traffic per ips, monthly etcs. But I can live without those. I'm using SolarWinds Orion to netflow those out so I'm fine for now.

The beauty of OPNSense is not being force to use certain hardware AES-NI. For smaller environment like home customers we use lower end hardware. For higher customer we use hardware that can be bought from your store.

we all find what works best for us. But being transparent is what I like about this community.

PFSense admins are dicks. I ask question they reply  and treat me like a moron to go "search the forums"

you dont, you probably seen many many question repeats but you dont treat people like idiots.