Howdy, As a follow-up, I've just checked the newreno setting on the boxes I experienced the problems with - newreno is on. I'll try turning it off and see if I experience any problems. BTW, what does it do exactly? Also, a query on my timesheets shows that I had the same FTP problems on a FreeBSD 3.2 box with the dc driver talking to an NT4 Terminal Server with onboard Intel 8255x controller via a 10/100 hub (full duplex), and also a FreeBSD 4.0 box with the rl driver talking to an NT4 Terminal Server with onboard Intel 8255x controller via a 10Mbit/s hub (full duplex). Disabling autonegotiation on the FreeBSD NIC fixed it. Only FTP was affected in both cases - SMTP, HTTP and SSH were all fine. It's beginning to look like a full duplex and autonegotiation problem. I hope this is of help to someone.
Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au > -----Original Message----- > From: Chris Knight [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, 28 November 2001 20:08 > To: 'Nate Williams' > Cc: '[EMAIL PROTECTED]' > Subject: RE: FreeBSD performing worse than Linux? > > > Howdy, > > I had a similar problem, especially with different FreeBSD > 4.x boxes (4.1.1, 4.2, 4.3, 4.4-stable after dirpref merge) > and with Windows NT systems, but the crap performance was > only limited to FTP. SSH, NFS and CVS operations were all > fine. The pre-4.3 boxes are all using RTL8029 cards, and the > 4.3+ boxes are all Intel 8255x-based cards. The laptop has > 4.4-stable and a D-Link DFE-650. The poor performance showed > up in interactions with the 100Mbit/s cards (Intel, D-Link). > They have all disappeared since I've explicitly set the links > to 100Mbit/s with full-duplex. The switches and hubs are all > 10/100 D-Links. > My guess is that the autonegotiation feature of both the fxp > and ed drivers somehow adversely affects FTP. > However this is only surmise. My fix was based more on an > inspired guess than methodical practice and I didn't get the > opportunity to delve deeper into the reasons for the problem. > Sometimes the real world can be a pain :-) > > Regards, > Chris Knight > Systems Administrator > AIMS Independent Computer Professionals > Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 > Web: http://www.aims.com.au > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Nate Williams > > Sent: Wednesday, 28 November 2001 18:51 > > To: Poul-Henning Kamp > > Cc: Nate Williams; Greg Lehey; [EMAIL PROTECTED]; > FreeBSD Hackers > > Subject: Re: FreeBSD performing worse than Linux? > > > > > > > >Note, some of the performance issues were made better by > > disabling the > > > >TCP newreno implementation, but it's still poor and very > > inconsistent > > > >for hosts not on the local network, while the Linux box > > next to it gets > > > >much more consistent results. > > > > > > For what it's worth I have disabled newreno at my customer > > sites as well > > > and felt and heard less "bogosity" since. > > > > It's actually pretty awful. However, even with the fix I > merged back > > into RELENG_4, the performance with/without newreno is still *much* > > worse (in terms of consistantly giving the same results) > than the code > > in FreeBSD 3.x. > > > > The interesting thing is that the application that's > getting the most > > press is one of our field technicians downloading a file over > > anonymous > > ftp by hand, so it's not like we're generating tons of traffic, or > > alot of parallel connections. > > > > The connections hang, abort, and those that complete have > numbers that > > are *all* over the map. However, when connected to a Linux > box on the > > same network, none of these bad things occur. :( > > > > (And, we've verified the network is up by running ping in another > > window.) > > > > > > > > > > Nate > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-hackers" in the body of the message > > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
