Date: Tue, 31 May 2005 09:38:12 +1200 From: Mark Kirkwood <markir@paradise.net.nz> To: Sebastian Ahndorf <webmaster@it-is-warlock.de> Cc: Imobach ??? Sosa <imobachgs@banot.net>, freebsd-stable@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: Poor network performance: a lot of timeouts Message-ID: <429B87C4.5080907@paradise.net.nz> In-Reply-To: <429B7DF6.8040704@it-is-warlock.de> References: <20050529221024.4fu2p4yjusk04k0g@mail.banot.net> <20050529212705.GA64753@xor.obsecurity.org> <1117447400.5384.4.camel@localhost.localdomain> <20050530104928.GB79877@sr.se> <1117465224.9934.7.camel@localhost.localdomain> <429B44BD.7070806@pp.nic.fi> <20050530191843.GA82875@xor.obsecurity.org> <429B7DF6.8040704@it-is-warlock.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Sebastian Ahndorf wrote:
> Kris Kennaway wrote:
>
>>> Both sides must have same config, autosense should work if there is
>>> no config possibility in other end.
>>
>>
>>
>> autosense may in fact not work, especially on low-quality NICs like rl.
>>
>
> I don't agree to that.
> I had similar problems with my network using a cheap switch with some
> realtek nics. I had the nics running 100baseTX Full Duplex.
> Changing this to autosense made the problems gone.
>
I would second that. My cheap rl card performs better with auto than
with either 100TX-full or 100TX-half ('tho its always auto'ed to 100TX
full duplex anyway).
And by way of interest, I have just experienced a similar problem with
NICs + 100 baseT switch - it was a 3Com Office connect card (xl driver)
that I had the issues with, and ended up replacing it with a DLink (vr
driver).
Cheers
Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?429B87C4.5080907>