From owner-freebsd-net@FreeBSD.ORG Sun Mar 9 18:45:06 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 33697D4E; Sun, 9 Mar 2014 18:45:06 +0000 (UTC) Received: from vms173019pub.verizon.net (vms173019pub.verizon.net [206.46.173.19]) by mx1.freebsd.org (Postfix) with ESMTP id 02DEA8DE; Sun, 9 Mar 2014 18:45:05 +0000 (UTC) Received: from yeaguy.com ([unknown] [173.60.122.163]) by vms173019.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0N26002G4MQCZY30@vms173019.mailsrvcs.net>; Sun, 09 Mar 2014 13:44:41 -0500 (CDT) Received: from yeaguy.com (localhost [127.0.0.1]) by yeaguy.com (Postfix) with ESMTP id 01CD3112529; Sun, 09 Mar 2014 11:44:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at yeaguy.com Received: from yeaguy.com ([127.0.0.1]) by yeaguy.com (yeaguy.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oGga4nVMJuJu; Sun, 09 Mar 2014 11:44:34 -0700 (PDT) Received: from [192.168.1.8] (sabertooth.home [192.168.1.8]) by yeaguy.com (Postfix) with ESMTPSA id 3A016112524; Sun, 09 Mar 2014 11:44:34 -0700 (PDT) Message-id: <531CB691.8030001@yeaguy.com> Date: Sun, 09 Mar 2014 11:44:33 -0700 From: justin victoria User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-version: 1.0 To: Kevin Oberman Subject: Re: LAN network performance issues References: <201403071319.06548.jhb@freebsd.org> In-reply-to: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-net@freebsd.org" , John Baldwin 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: Sun, 09 Mar 2014 18:45:06 -0000 On 3/9/2014 10:40 AM, Kevin Oberman wrote: > On Fri, Mar 7, 2014 at 2:57 PM, jcv > wrote: > > > > On Fri, 7 Mar 2014, John Baldwin wrote: > > 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 > _______________________________________________ > freebsd-net@freebsd.org > mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to > "freebsd-net-unsubscribe@freebsd.org > " > > > > Sure John -- > > Here is the fbsd nic info: > > [vic@yeaguy ~] cat /var/run/dmesg.boot | grep re0 > re0: > port 0xe800-0xe8ff mem 0xfdfff000-0xfdffffff,0xfdff8000-0xfdffbfff > irq 18 at device 0.0 on pci3 > re0: Using 1 MSI-X message > re0: Chip rev. 0x48000000 > re0: MAC rev. 0x00000000 > miibus0: on re0 > re0: Ethernet address: d8:50:e6:ba:c8:99 > > > > [vic@yeaguy ~] ifconfig > re0: flags=8843 metric 0 > mtu 1500 > > options=8209b > ether d8:50:e6:ba:c8:99 > inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255 > inet6 fe80::da50:e6ff:feba:c899%re0 prefixlen 64 scopeid 0x1 > nd6 options=29 > media: Ethernet autoselect (1000baseT ) > status: active > lo0: flags=8049 metric 0 mtu 16384 > options=600003 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > inet 127.0.0.1 netmask 0xff000000 > nd6 options=21 > [vic@yeaguy ~] > > I tried to remove rxcsum and txcsum, but that didnt really improve > the behavior.... I almost convinced its a iperf issue? maybe.. > after iperf testing i did a FTP transfer and it exceeded what > iperf is claiming the throughput is.. so im not sure what to make > of it. > > > You might try installing iperf3 and testing with that. iperf3 is a > major rewrite of iperf and is totally incompatible with the older > version, so you will need to install iperf3 on all systems > > I doubt iperf is the issue, but this is a way to check. > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com iperf3 on windows isnt playing nice..