dnssec-keygen just hangs on Three Different FreeBSD Systems.

[Mark_Andrews at isc.org]

> 	Thank you for the information.  I successfully got the
> systems in question listening to the interrupts and a couple of
> them I have tried now output some data if I cat /dev/random |more
> or in to a file, but dnssec-keygen still only sits there doing
> nothing if I run it.
> 
> 	So far, I added the interrupts to rndcontrol which
> verifies that they are being used.  I also added
> 
>         rand_irqs="3 14 15"
> 
> As recommended and booted one of the systems and, yes, they were
> still there.  Am I missing anything else?
> 
> 	There is no t.conf on this system in /etc/defaults.  I
> suspect the seed is still not present.  On one system, only a
> byte or 2 emerged when I performed the cat /dev/random >somefile.
> This is after over twelve hours of supposedly catching entropy.:-)

	Well you need to match the irq's with the hardware (see dmseg)
	and you also need to exercise the hardware so that it results in
	interupts being generated.

	If you are looking at disk interrupts then run "ls -lR /".
	If you are looking at ethernet interrupts then run "ls -lR /"
	on a remote machine.
 
> phn at icke-reklam.ipsec.nu writes:
> >You might need to get /dev/random working. This needs a seed , configured
> >into /etc/rc.conf , see /etc/defaults/t.conf :
> >rand_irqs="NO"          # Stir the entropy pool (like "5 11" or NO).
> >
> >replace with used irq in your machine.
> >
> >
> >-- 
> >Peter Håkanson         
> >        IPSec  Sverige      ( At Gothenburg Riverside )
> >           Sorry about my e-mail address, but i'm trying to keep spam out,
> >	   remove "icke-reklam" if you feel for mailing me. Thanx.
> >
> 
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org