Re: Ethernet not so good.

[Michael Schmitz <schmitz@mail.biophys.uni-duesseldorf.de>]

> > 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:

slink expects the 2.0 kernel /proc/net/dev format

> <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 

Looks OK (otherwise you'd have something like 5000 Tx packets 16 errors) 

> > 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?

cat /proc/interrupts some times before and after the telnet attempt.

	Michael