[ previous ] [ next ] [ threads ]
 From:  Peter Curran <peter at closeconsultants dot com>
 To:  Manuel Kasper <mk at neon1 dot net>
 Cc:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] More throughput testing - m0n0wall to m0n0wall (wired) IPSec
 Date:  Fri, 4 Jun 2004 18:39:44 +0100

Does that mean that you have an expectation of a Hifn 7955 working OK in 1.0 
or 1.11bn?

I ask because I am scratching my head as to why I can't get it initialised by 
either a FreeBSD 4.9 or 4.10 kernel.  It detects the card OK but then barfs 
when it tries to initialise it:

This is what a 1.1b12 has to say...

Jun  3 11:10:26 Safespot /kernel: hifn0 mem 
0xa0008000-0xa000ffff,0xa0002000-0xa0003fff,0xa0000000-0xa0000fff irq 10 at 
device 16.0 on pci0
Jun  3 11:10:26 /kernel: hifn0: proc unit did not reset
Jun  3 11:10:26 /kernel: hifn0: proc unit did not reset
Jun  3 11:10:26 /kernel: hifn0: crypto enabling failed
Jun  3 11:10:26 /kernel: device_probe_and_attach: hifn0 attach returned 6

This is a net4501 with a vpn1411 card.

I have tried a different 4501 and a 4511 with 3 different vpn1411 cards all 
with the same results.

Everything works ok with a vpn1211

On Friday 04 June 2004 17:22, Manuel Kasper wrote:
> On 04.06.2004 09:06 -0700, James Baber wrote:
> > Yep, I just pulled the VPN cards and the numbers are the same!  How
> > odd, both devices report the VPN cards when they boot and the webgui
> > states "Hifn 7955" in both config screens.  I even replaced both VPN
> > cards with new VPN cards with no luck.  I'm at a loss...
> Hmm, use /exec.php to get at the dmesg output, and check for any
> errors related to hifn0.
> Oh, and BTW, the Hifn 7955 doesn't support Blowfish anyway. I
> recommend using AES once you get it working.
> - Manuel



This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.