Date: Wed, 2 Jan 2002 20:08:46 +1100 From: Greg Lane <gregory.lane@anu.edu.au> To: David Kelly <dkelly@hiwaay.net> Cc: oberman@es.net, ertr1013@student.uu.se, freebsd-questions@FreeBSD.org Subject: Re: Pathetic 11 kbytes/s with ed driver (Netgear EA201) Message-ID: <20020102200846.A95983@nucl03.anu.edu.au> In-Reply-To: <200201020404.g0244nU03160@grumpy.dyndns.org>; from dkelly@hiwaay.net on Tue, Jan 01, 2002 at 10:04:49PM -0600 References: <gregory.lane@anu.edu.au> <200201020404.g0244nU03160@grumpy.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > If you are plugged into a 10Base-T hub (and not a switch), your MUST > > > run half-duplex. > > > > There's the problem then. I do have a 10BaseT hub. > > If thats the case then there is no point in proceeding. Unless you are > connecting two machines direct without hub. I don't understand your point. I just changed the card to half-duplex with the Netgear DOS program and everything works great now: 1>xxxxx@router:~$ fetch http://rene/mysql_manual.pdf Receiving mysql_manual.pdf (3314090 bytes): 100% 3314090 bytes transferred in 4.5 seconds (721.60 kBps) > > You can't set the duplex within FreeBSD anyway. You must > > use the DOS configuration program. > > You stopped too soon in snipping your ifconfig output. Is the media > line which matters. The SIMPLEX on the first line means something > completely different. See how fxp0 is full duplex but fxp1 is not? No I didn't snip it too early. Its just not reported. This is from the web server. $ ifconfig ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 192.168.128.32 netmask 0xffffff00 broadcast 192.168.128.255 ether 00:40:05:a2:15:fc lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 127.0.0.1 netmask 0xff000000 This is from my router (de0 is the DSL line, vr0 to the hub): 2>xxxxx@router:~$ ifconfig de0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 ether 00:00:92:90:79:3b media: Ethernet 10baseT/UTP status: active vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 192.168.128.1 netmask 0xffffff00 broadcast 192.168.128.255 ether 00:80:c8:d9:ff:0e media: Ethernet autoselect (10baseT/UTP) status: active Some drivers mustn't report the media line. In my first email I also showed that you cannot set the media or mediaopt for the EA201. > rene# ifconfig ed0 media 10baseT > ifconfig: SIOCGIFMEDIA: Invalid argument > rene# ifconfig ed0 mediaopt full-duplex > ifconfig: SIOCGIFMEDIA: Invalid argumentn e > Be aware there are early collisions and late collisions. And not all > ethernet hardware reports the early collision which you are monitoring > above. Think the 3Com hardware using the vx driver never tallies early > collisions. Late collisions are very very bad and should never occur > unless hardware or software is broken. Early collisions are not so bad. > Used to be a white paper posted on an employee's home page at sgi.com > with a detailed analysis of collisions. If I remember correctly a 200% > early collision rate works out to a 15% reduction in network thruput. > All because the collision happens so early (within the first 64 octets) > that very little time is lost. > > There is nothing wrong with running half duplex on a switch connection > other than half duplex is a bit less desirable than full duplex. It > won't bother any of the other hosts on the network. The switch will > buffer for you just as it will probably buffer your 10M bps to others > at 100M bps. Thanks for the info!!! I really need to learn more about all this. Can you recommend a good book? Thanks to everyone who replied. This box will be in service as our departmental web server from tomorrow. Cheers, Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020102200846.A95983>