Date: Sun, 09 Mar 2014 11:44:33 -0700 From: justin victoria <jv@yeaguy.com> To: Kevin Oberman <rkoberman@gmail.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, John Baldwin <jhb@freebsd.org> Subject: Re: LAN network performance issues Message-ID: <531CB691.8030001@yeaguy.com> In-Reply-To: <CAN6yY1vfyrq-roDUMDAG5RgKdcJ=dJbwEZX4M8omCS7sAauamA@mail.gmail.com> References: <alpine.BSF.2.00.1403062115530.99217@yeaguy.com> <201403071319.06548.jhb@freebsd.org> <alpine.BSF.2.00.1403071455020.59880@yeaguy.com> <CAN6yY1vfyrq-roDUMDAG5RgKdcJ=dJbwEZX4M8omCS7sAauamA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/9/2014 10:40 AM, Kevin Oberman wrote: > On Fri, Mar 7, 2014 at 2:57 PM, jcv <jv@yeaguy.com > <mailto:jv@yeaguy.com>> 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 <mailto: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 > <mailto:freebsd-net-unsubscribe@freebsd.org>" > > > > Sure John -- > > Here is the fbsd nic info: > > [vic@yeaguy ~] cat /var/run/dmesg.boot | grep re0 > re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> > 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: <MII bus> on re0 > re0: Ethernet address: d8:50:e6:ba:c8:99 > > > > [vic@yeaguy ~] ifconfig > re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 > mtu 1500 > > options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_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<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > media: Ethernet autoselect (1000baseT <full-duplex>) > status: active > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 > options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > inet 127.0.0.1 netmask 0xff000000 > nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> > [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 <mailto:rkoberman@gmail.com> iperf3 on windows isnt playing nice..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?531CB691.8030001>