Re: TCP interactions (was: Re: Linux and FreeBSD poor network performance)

2002-12-22 Thread Matthew Dillon
: :Hmm, same cables, same switch, different card, now it all works. : :I did do some ICMP ping testing with ping -f and only lost 3 :packets after letting it run for a good 10s. : : :-matt If it is working properly you should not lose *ANY* packets on an otherwise idle connection, except

Re: TCP interactions (was: Re: Linux and FreeBSD poor network performance)

2002-12-22 Thread matthew c. mead
Hmm, same cables, same switch, different card, now it all works. I did do some ICMP ping testing with ping -f and only lost 3 packets after letting it run for a good 10s. -matt On Sun, Dec 22, 2002 at 01:06:18PM -0800, Matthew Dillon wrote: > By your description, it is almost certainly a pa

Re: TCP interactions (was: Re: Linux and FreeBSD poor network performance)

2002-12-22 Thread Matthew Dillon
By your description, it is almost certainly a packet loss problem... a cabling issue or a switch issue most likely. Try doing large pings, like this, and see if you get hicups: bsdbox# ping -i 0.1 -s 3000 linuxbox -Matt

Re: TCP interactions (was: Re: Linux and FreeBSD poor network performance)

2002-12-22 Thread matthew c. mead
On Sun, Dec 22, 2002 at 10:59:52AM -0500, Robert Watson wrote: > On Sat, 21 Dec 2002, matthew c. mead wrote: > > I have a Linux box and FreeBSD box sitting on a 100Mbit ethernet segment > > that cannot seem to talk to one another faster than 150K/s. I've been > > using scp, ftp, http, to test thi

TCP interactions (was: Re: Linux and FreeBSD poor network performance)

2002-12-22 Thread Robert Watson
On Sat, 21 Dec 2002, matthew c. mead wrote: > I have a Linux box and FreeBSD box sitting on a 100Mbit ethernet segment > that cannot seem to talk to one another faster than 150K/s. I've been > using scp, ftp, http, to test this. And you've done tests in both directions, or just in one? > A Wi

Re: Linux and FreeBSD poor network performance

2002-12-21 Thread Daniel Schrock
matthew c. mead wrote: On Sun, Dec 22, 2002 at 08:16:28AM +1000, Steve Baxter wrote: Check out the duplex setting on the ethernet ports. Use 'ifconfig' and 'netstat -I dev -w 1' on FreeBSD ifconfig fxp0: fxp0: flags=8843 mtu 1500 inet 192.168.1.99 netmask 0xff00 broadcast 192.168.1.2

Re: Linux and FreeBSD poor network performance

2002-12-21 Thread matthew c. mead
Sorry to follow-up to my own message, but using a FreeBSD 4.6.2-RELEASE box with the Linux box works just fine. It uses an xl0 instead of an fxp0. I've done a sysctl -a on each box. Here's the differences. Anything look suspicious? Thanks. -matt --- sysctl Sat Dec 21 17:43:49 2002 +++

Re: Linux and FreeBSD poor network performance

2002-12-21 Thread matthew c. mead
On Sun, Dec 22, 2002 at 08:16:28AM +1000, Steve Baxter wrote: > Check out the duplex setting on the ethernet ports. Use > 'ifconfig' and 'netstat -I dev -w 1' on FreeBSD ifconfig fxp0: fxp0: flags=8843 mtu 1500 inet 192.168.1.99 netmask 0xff00 broadcast 192.168.1.255 inet6 fe8

Re: Linux and FreeBSD poor network performance

2002-12-21 Thread Steve Baxter
Check out the duplex setting on the ethernet ports. Use 'ifconfig' and 'netstat -I dev -w 1' on FreeBSD and 'ifconfig', 'mii-tool' and 'cat /proc/net/dev' on Linux Any sort of errors may lead to this sort of behaviour. You need to match the hosts to the switch port they are connected to. SB