Re: Soekris net4501 - repetitive reboots

[Chuck Yerkes <chuck+obsd@2004.snew.com>]

Quoting Saad Kadhi (saad@docisland.org):
> On Wed, Feb 18, 2004 at 11:41:06AM -0500, Dan Harnett wrote:
> [snip]
> > > your suggestions solved the problem partly. I had a 800mA power supply.
> > > replaced it with a 1.2A one. now the soekris doesn't reboot anymore.
> > > however, scp still tops at 1.4MBs and the soekris is almost unresponsive
> > > on the console. any ideas?
> > 
> > I also have a net4501 and a mini-PCI wireless card from netgate.com.
> > scp (and rsync) caused the net4501 to become completely unresponsive
> > when transferring files from the wireless segment to the wired segment.
> > From what I have determined, the mini-PCI card was failing miserably
> > when using 104-bit WEP (firmware-based) and became unresponsive.  Using
> > 40-bit WEP (or none) everything would work just fine.
> I'm using the wireless connection for email/web/ssh(admin). I do not
> transfer files through it.
> 
> anyone knows how much mA/A can a net4501 handle without causing _any_
> damage to the board && components? I'd like to see if going from 1.2A to
> 1.4A would do any good as one poster suggested.

How you missed the mantra on the soekris lists of:
"Your power supply is inadequate" for 99.9% of the reboot/reset
problems is beyond me...

12v/1A is MINIMUM.  You could power it from a PC's power
supply at 10A and it would draw only what it needs.


Note too that the soekris can take up to 56V via PoE (4511/4521)
and the 4501 can accept perhaps 26V on the DC-in socket.  Its
documented.  A 20v power supply works fine.


WEP will slow down wireless but I thought it never reached the
computer.  I know that lots of IPSec will beat a soekris into
submission without a coprocessor.  SCP involves encryption and
WILL beat up the CPU.  Perhaps you can test with RCP.

When debugging, however, simplify:
  No WEP
  straight through.

Try also TTCP as a bandwidth measurement.  It can blast a 1GB
file and track how long it takes and at what speeds.

It won't encrypt, so most of the work will be passing packets.