Reference: LINUX 2.4.7-10smp Redhat 7.2
Driver: eepro100
Hello,
As you can see in the above output, I have an interface having too many
collisions. This device is linked to a switch at 100MB FullDuplex (I
hope)
eth0 Link encap:Ethernet HWaddr 00:30:48:22:0F:83
inet addr:10.1.2.9 Bcast:10.255.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2296912 errors:0 dropped:0 overruns:0 frame:0
TX packets:1758043 errors:0 dropped:0 overruns:0 carrier:20
collisions:9734 txqueuelen:100
RX bytes:1919377793 (1830.4 Mb) TX bytes:173437853 (165.4 Mb)
Interrupt:31 Base address:0x5000
Two questions around:
a) How to know the connection type negotiated between the interface
and the switch (full, half) ?
b) How to enter into collisions problem to determine who is responsible
for ?
My major problem here is that a data transfer of 20MB requires 3 minutes
and 40 seconds between two systems declaring a network speed of
100Mb Full Duplex. Continuing this way it would be better for
me to use floppies.
Additionally, I am using another system with the same LINUX version
but with an ns83820 linked at 1Gb. It works very well but it is the
only one in the network to be lonked at such speed.
Makes sense as it is the server.
So, I starterd at same time from two Linux systems linked at 100Mb
FullDuplex a data
transfer using FTP who announced at the two sending systems a transfer
speed of 9.+e03KB which is very close of the maximum transfer speed of
each sending system.
Pending point is (not a problem) that ifconfig says that no RX nor
TX packets were received. On this example server box was
running since two days receiving and sending a lot of data:
eth0 Link encap:Ethernet HWaddr 00:40:F4:17:72:3C
inet addr:194.3.100.163 Bcast:194.3.100.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Thanks for your help.
Bye
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
