[ Date Index ][
Thread Index ]
[ <= Previous by date /
thread ]
[ Next by date /
thread => ]
On Wed, 20 Oct 2004 02:03:41 +0100 Mark Mitchell <m.l.mitchell@xxxxxxxxx> wrote:
Dear List, I'm having a slight problem with my home "network" and I'm not sure where to start looking for a solution. The problem is I'm not getting anything like the speeds I should be. Basically I've got two computers connected via a Netgear 10/100M Ethernet Switch. One computer is running Mandrake 10 and the other OpenBSD 3.5. File transfers with sftp are reporting speeds of around "100KB/s" - I'm not sure if this is Bytes or Bits, but either way it's a fraction of the 100 Mbits/s I should get.
As a general rule, B is for Bytes and b is for bits. This can be applied to the K/M/G as well... K for 1024, k for 1000. Also worth a note is that, very often, it would be *B/s for bytes/sec and *bps for bits/sec. Please note, however, that many people do not stick to this convention and just use whatever they want. 100KB/s (100 kilo-bytes/sec) = 819,200 bits/second (100x1024x8) 100mbps (100 mega-bits/sec) = 100,000,000 bits/second (100x1000x1000)
I checked out the NIC configuration to make sure both cards were
100Mb/s and they both seem to be: ifconfig on Mandrake gives -
eth0 Link encap:Ethernet HWaddr 00:09:5B:1D:18:3E
inet addr:10.0.0.9 Bcast:255.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::209:5bff:fe1d:183e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2954050 errors:0 dropped:0 overruns:0 frame:99
TX packets:2279725 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:99044883 (94.4 Mb) TX bytes:170102856 (162.2 Mb)
Interrupt:3 Base address:0x300
and OpenBSD gives -
sis0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 04:26:02:50:80:00
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 10.0.0.3 netmask 0xffffff00 broadcast 10.0.0.255
inet6 fe80::626:2ff:fe50:8000%sis0 prefixlen 64 scopeid 0x1
The Linux output doesn't seem to show duplex or speed. You can find out with grep -i "duplex" /var/log/syslog The kernel will, I believe, either display full-duplex or half-duplex, rather than simplex. Makes it easier for grepping, too!
I found something on the internet saying problems like this can sometimes be caused by misconfiguring "duplex" but it wasn't very specific and I didn't really understand. I'd be very grateful for any help. Mark
Duplex is the ability to do two things at the same time. In this case, transmit and receive at the same time. Since you're using UTP, there is no reason that you shouldn't use full duplex. Obviously if your NIC doesn't support it then you can't use it, but the likelihood of a 100mbps NIC _not_ supporting FD these days is really quite slim. Also in your favour is the fact that you're connecting to a switch rather than a hub. Since the transmit and receive are on physically different pairs of wires, using full-duplex is _the_ best option. -- Grant Sewell Cisco Tutor Cornwall College Camborne Trevenson Road Pool, Redruth Cornwall. TR15 3RD Tel: 07866-065964 Email: g.sewell@xxxxxxxxxxxxxxxxxx -- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.