Dewayne Geraghty wrote:
We're looking to deploy FreeBSD on our main firewall. The firewall config
is a VIA C7 (padlock), racoon(ipsec-tools-0.7), IPSec. We're testing racoon
with a windows box, however the firewall doesn't function correctly when
net.inet.ipsec.crypto_support=1 is set. With
On Dec 3, 2007, at 9:39 AM, Michael Proto wrote:
Not that this solves your problem, but doesn't the padlock crypto
engine
only provide acceleration for AES symmetric encryption? From the man
page:
The boot messages on my C7 based system shows this:
PadLock: HW support loaded for
My apologies for the confusion, yes, the C7 only helps with AES.
The configuration detail is: between branch offices I use FreeBSD ipsec
(AES), and within the branches Windows boxes access the firewall boxes. The
firewalls run samba inside a jail. Due to sensitive information (see your
local
Dewayne Geraghty wrote:
My apologies for the confusion, yes, the C7 only helps with AES.
The configuration detail is: between branch offices I use FreeBSD ipsec
(AES), and within the branches Windows boxes access the firewall boxes. The
firewalls run samba inside a jail. Due to sensitive
We're looking to deploy FreeBSD on our main firewall. The firewall config
is a VIA C7 (padlock), racoon(ipsec-tools-0.7), IPSec. We're testing racoon
with a windows box, however the firewall doesn't function correctly when
net.inet.ipsec.crypto_support=1 is set. With a