From owner-freebsd-net@FreeBSD.ORG Fri Mar 7 18:48:16 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AA325592 for ; Fri, 7 Mar 2014 18:48:16 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 83B6296 for ; Fri, 7 Mar 2014 18:48:16 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 763DBB9A3; Fri, 7 Mar 2014 13:48:15 -0500 (EST) From: John Baldwin To: freebsd-net@freebsd.org Subject: Re: LAN network performance issues Date: Fri, 7 Mar 2014 13:19:06 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201403071319.06548.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 07 Mar 2014 13:48:15 -0500 (EST) Cc: jcv X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Mar 2014 18:48:16 -0000 On Friday, March 07, 2014 12:17:05 am jcv wrote: > Hi - I am seeing some strange IPERF results.. Everything goes through my > WIFI/GIGABIT router. > > For these tests everything is plugged directly into the router via > Ethernet cable. > > My issue is the transfer rate from Windows to FreeBSD. > > There are 3 different computers in this lab running 3 different OS. > > Here are the results: > > > > FreeBSD as server: > > [vic@yeaguy ~] iperf -s > ------------------------------------------------------------ > Server listening on TCP port 5001 > TCP window size: 64.0 KByte (default) > ------------------------------------------------------------ > > > [ 4] local 192.168.1.3 port 5001 connected with 192.168.1.8 port 52505 > [ ID] Interval Transfer Bandwidth > [ 4] 0.0-10.1 sec 157 MBytes 131 Mbits/sec <----- WINDOWS 8.1 as > client on same LAN/ROUTER > > > > > [ 5] local 192.168.1.3 port 5001 connected with 192.168.1.12 port 60926 > [ 5] 0.0-10.0 sec 1.10 GBytes 941 Mbits/sec <------ MACBOOK PRO as > client on same LAN/ROUTER > > > Windows as the server: > > ------------------------------------------------------------ > Server listening on TCP port 5001 > TCP window size: 64.0 KByte (default) > ------------------------------------------------------------ > [ 4] local 192.168.1.8 port 5001 connected with 192.168.1.3 port 60529 > [ ID] Interval Transfer Bandwidth > [ 4] 0.0-10.0 sec 1014 MBytes 850 Mbits/sec <--------- Freebsd 10 as > client on same LAN/ROUTER > > > > [ 4] local 192.168.1.8 port 5001 connected with 192.168.1.12 port 60933 > [ 4] 0.0-10.0 sec 1.08 GBytes 931 Mbits/sec <------ MACBOOK PRO as > client on same LAN/ROUTER > > > > Macbook Pro as the server: > > [ 3] local 192.168.1.8 port 52509 connected with 192.168.1.12 port 5001 > [ ID] Interval Transfer Bandwidth > [ 3] 0.0-10.0 sec 823 MBytes 690 Mbits/sec <------ WINDOWS 8.1 as > client on same LAN/ROUTER > > [ 3] local 192.168.1.3 port 23190 connected with 192.168.1.12 port 5001 > [ ID] Interval Transfer Bandwidth > [ 3] 0.0-10.0 sec 1016 MBytes 852 Mbits/sec <------ Freebsd 10 as > client on same LAN/ROUTER > > > With FreeBSD being the server, Windows transfer to FreeBSD is slow, > compared to Macbook to FreeBSD transfer.. > With Windows as the server, FreeBSD and Macbook to Windows transfer is > great. > With Macbook as server, Windows and FreeBSD transfer is good. > > The only bad transfer is Windows to FreeBSD. Windows transfer to Mac is > good. Cant really blame Windows for the poor transfer to FreeBSD then. > Macbook to FreeBSD is outstanding, cant really blame FreeBSD for poor > receive performance. Can you tell us more about the FreeBSD box such as the NIC being used? -- John Baldwin