From owner-freebsd-net@FreeBSD.ORG Sun Mar 9 17:40:56 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D21D085D; Sun, 9 Mar 2014 17:40:56 +0000 (UTC) Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A1D5D197; Sun, 9 Mar 2014 17:40:56 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id v10so6138861pde.11 for ; Sun, 09 Mar 2014 10:40:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=OTZhjfkSKcLvh7WTflPpqyj3yNiD2kpo0FzbdGXL/j0=; b=zfKQBi5tllSorQecUlOllSx9QxEedX7+dqfukb31N38vtU+/OKIg5Ube/E+bFW+Z7g OsQ9+E4qWfgo+OsDfHdQpCKWbeo/LsPZxLfWVaTD1PRjekXQUfD6QsyYj6hcBdZ82+Pm nVhVv1+TKmhFs54OW6bWyTOvHOhjNzd6QUqYjLQ3RGzx46flEAvApob2hLP2S3khC3RF eYDkrmqqeKMUtoihR3lrJo93I/SSr8L1waaR0lKtNydr+AQQEUSYorcpnlW0dMlv6W9K w5WO4rdvg2LhKcyRxvzjwQbC60xpmEzi/cnFbbwUTVvAEkfBtHfkRCd34WfV453tNvKY MHUQ== MIME-Version: 1.0 X-Received: by 10.67.8.102 with SMTP id dj6mr35288841pad.10.1394386856256; Sun, 09 Mar 2014 10:40:56 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.66.0.164 with HTTP; Sun, 9 Mar 2014 10:40:56 -0700 (PDT) In-Reply-To: References: <201403071319.06548.jhb@freebsd.org> Date: Sun, 9 Mar 2014 10:40:56 -0700 X-Google-Sender-Auth: 1OrYbn4Wtp6YCQXhZp0eQLgY6cE Message-ID: Subject: Re: LAN network performance issues From: Kevin Oberman To: jcv Content-Type: text/plain; charset=UTF-8 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 17:40:56 -0000 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 HWCSUM,WOL_MAGIC,LINKSTATE> > 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