Hello,
Sorry for the confusion.
I wrote:
> On Wed, 20 Jan 1999, Karel van Houten wrote:
>
> > > To all DECstatoin hackers: shows `ifconfig` such amount of errors?
>
> > eth0 Link encap:Ethernet HWaddr 08:00:2B:37:63:76
> > inet addr:139.63.1.12 Bcast:139.63.1.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:635500 errors:0 dropped:0 overruns:0
> > TX packets:0 errors:445581665 dropped:741538 overruns:0
> > Interrupt:2 Memory:a0020000-a0040000
> >
> > Running NFS-root without TX-ing packets :-), I think the driver mixes up
> > some statistics.
>
> I think the statistics are right, in case of the LANCE error doesn't mean
> there is no packet transmitted, it means that there was a transmitter
> timeout. Look at the number of dropped packets. I'm trying to figure out
> what's causing this. First thing that made me suspect LANCE's functioning
> was ping'ing from a DS:
`cat /proc/net/dev` gives a more relaible result [removed some for
clearity sake]:
Inter-| Receive | Transmit
face |bytes packets errs drop|bytes packets errs drop
lo: 0 0 0 0 0 0 0 0
eth0: 7019384 11425 0 0 1360244 8690 0 0
btw `cat /proc/net/dev_stat` produces only zero's...
where ifconfig shortly after says
[root@mips linux]# ifconfig
eth0 Link encap:Ethernet HWaddr 08:00:2B:30:8D:2B
inet addr:192.168.1.15 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11476 errors:0 dropped:0 overruns:0
TX packets:0 errors:1366072 dropped:8724 overruns:0
Interrupt:2 Memory:a0020000-a0040000
> [root@mips /root]# ping 192.168.1.1
> PING 192.168.1.1 (192.168.1.1): 56 data bytes
> 64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=10.0 ms
> ping: recvfrom: Unknown error 512
> 64 bytes from 192.168.1..1: icmp_seq=1 ttl=64 time=0.0 ms
> ping: recvfrom: Unknown error 512
> 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.0 ms
> ping: recvfrom: Unknown error 512
Still some that leaves me puzzled. :-)
Regards,
Richard
|