The card in the laptop is the one that configs with the 
ne2 driver. Here is a link to the card. (You'll have to 
cut-n-paste it into your browser because the line is too 
long to include the protocol -- I'm emailing from AT&T 
because KMail is broken on NetBSD today)

www.linksys.com/products/product.asp?prid=41&grid=11

Note that it is a full-duplex card. Either I have fed the 
wrong args into ifconfig or else the ne driver in NetBSD 
is not appropriate, or else it is not very full featured 
as a driver --  which?

Thanks to Robert Elz for the heads-up.

Regards,

Gan Starling

--
Mysterious Starling -- Rarest Extinct Bird
     _         
   <(+)__        Gan Uesli Starling 
     ((__/)=-    Kalamazoo, MI, USA
      `||`      
       ++        http://starling.ws 

Newbie-2-Newbie NetBSD Unix How-To Pages at... 
http://om-ah-hum.com/share/gus_netbsd_index.html
                    
>     Date:        Tue, 18 Sep 2001 09:53:20 +0000
>     From:        oinkfreebiker@att.net
>     Message-ID:  
> <20010918095323.XUUG21828.mtiwmhc24.worldnet.att.net@webmail.worldnet.att.net>
> 
>   | On laptop, doing get from tower:   4.19 KB/s
>   | On laptop, doing put to tower:   941.09 KB/s
>   | On tower, doing get from laptop:   1.28 MB/s
>   | On tower, doing put to laptop:    35.43 KB/s
> 
> This is the kind of behaviour you expect when one end is half duplex
> and the other is full.
> 
>   |    media: Ethernet autoselect (100baseTX full-duplex)
> 
> So that one is full duplex.
> 
>   |    media: Ethernet manual
> 
> and that one apparently can't be altered, so you can be pretty sure
> it is half duplex (half duplex is standard ethernet, full duplex is
> an optional extra...)
> 
> Force the tower into half duplex mode, you'll get collisions, and defers,
> instead of smashed packets (and TCP retransmits), and everything is likely
> to be much much happier.
> 
> ifconfig fxp0 media 100baseTX media-opt half-duplex
> 
> kre
> 
>