On Thu, Mar 13, 2008 at 6:10 AM, Edel SM <[EMAIL PROTECTED]> wrote:
> hello,
>
> thank you very much for the pointers, fooler. im also deciding to get
> an eepro1000 card as orly (thanks sir) pointed out in his reply.
>
> here's ethtool output:
> # ethtool -S eth1
> NIC statistics:
>     early_rx: 0
>     tx_buf_mapped: 0
>     tx_timeouts: 0
>     rx_lost_in_ring: 0
>
> and ifconfig:
> # ifconfig eth1
> eth1      Link encap:Ethernet  HWaddr 00:05:5D:30:A9:62
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:24325413 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:26892676 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:2914412942 (2.7 GiB)  TX bytes:859714313 (819.8 MiB)
>          Interrupt:20 Base address:0x8800
>
>
> it seems all is ok.

youve got a good link (layer 1) and nic (layer 2) there.... no dropped
or overruns packets in there... it means your rtl8139 was doing
perfectly well.. but it is better to bombarded more packets to your
router (eg. big file transfer between two subnets so that the packets
will pass thru to your router and run top to see the cpu utilization
if there is an increase in cpu load during heavy network i/o) and see
the statistics if indeed youve got a clean errors... if it is clean
then you can narrow down your troubleshooting from device driver
(layer 2) and up (layer 3 and other factors) as what i indicated in my
previous post...

fooler.
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph

Reply via email to