Re: Ethernet not so good.

[Lon Shapiro <lshapiro@sun.iwu.edu>]

> > Would that show up in ifconfig's error report?
> 
> It should, but what exactly are these numbers reported by ifconfig? Are
> you sure your ifconfig matches the kernel version (the /proc/net/dev
> format was changed in 2.1)? 

Used slink for complete reinstall late summer so I assume (maybe
incorrectly) that I should have ok ifconfig. Here is example output:
<snipped>

          inet addr:192.168.0.80  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:17 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          Collisions:0 
          Interrupt:60 Memory:fd0d0000-fd0d4000 

after rebooting. I noticed (before reboot) that I had accumulated a number
(160+) frame errors for RX - but haven't been able to track down the cause
in a repeatable manner yet.

> > > What kernel does show this problem?  Did you try a more recent kernel
> > > version? 
> > 
> >  2.2.10 #1 Fri Oct 15 12:37:26 EDT 1999 m68k unknown
> 
> Should be recent enough. Do you see further ethernet (or Nubus) interrupts
> after the TCP connect stalls? 

Over my head here - how do I monitor this?

Lon