From: Diana Eichert (deichertwrench.com)
Date: Sat Apr 02 2005 - 23:14:13 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sat, 2 Apr 2005, Ted Unangst wrote:
SNIP
> > The system actually quit responding for awhile, but it just started
> > responding again.
>
> what does netstat -I sis0 say about Ierrs? had a sis that just plain
> received packets wrong (or claimed it did). i believe this was similar to
> the "short cable" problem, which was supposedly fixed ages ago.

Ted

BINGO!!!

$ netstat -I sis0
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Colls
sis0 1500 <Link> 00:0b:6a:c5:df:b8 5571413 6756 57468 0 847
sis0 1500 216.31.69/2 obsd-dev 5571413 6756 57468 0 847
sis0 1500 fe80::%sis0 fe80::20b:6aff:fe 5571413 6756 57468 0 847
$

I'm connected to a switch, so I shouldn't be seeing any collisions. Also,
when I ran tcpdump on the interface when it wasn't talking on the network,
I would see malformed packets coming back to it on a DNS lookup, but
looking on the system sending the packets everything looked fine.

Unfortunately it's at the office at a friend so I can't get to it right
now.

FWIW, I ran it for a day with the Linux install it came with from Walmart
and it worked AOK, didn't see any problem until I moved the 3.6 hard drive
over to it. The problem showed up within minutes of firing up the system.

I do have some 4-port dc cards I can throw in to it if I need to, but I
thought I'd report the problem.

Doesn't the Soekris have sis NICs also? that's where the "short cable"
problem was originally reported?

thanks for the help

diana

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]