On 01/10/2017 03:40 PM, Rick Stevens wrote:
> On 01/10/2017 01:56 PM, Chris Murphy wrote:
>> On Tue, Jan 10, 2017 at 12:44 PM, Rick Stevens <ricks@xxxxxxxxxxxxxx> wrote:
>>> On 01/10/2017 11:30 AM, Chris Murphy wrote:
>>>> On Tue, Jan 10, 2017 at 12:22 PM, Joe Zeff <joe@xxxxxxx> wrote:
>>>>> On 01/10/2017 11:19 AM, Chris Murphy wrote:
>>>>>>
>>>>>> Ostensibly this is an 802.11n connection, so 9MB/s is consistent with
>>>>>> that, where 3MB/s is consistent with half that of 802.11g.
>>>>>
>>>>>
>>>>> No, it's one third of what Windows is getting.
>>>>
>>>> It's both. 802.11g is 54Mbps, I'm getting 24-26Mbps. So it sounds like
>>>> to me the kernel or firmware being used when using Fedora, is doing
>>>> some kind of aggressive fallback and thus a much lower rate.
>>>>
>>>> The distance laptop to AP is about 8 feet, and unimpeded line of site.
>>>
>>> I believe you said the F25 server is running Samba to supply the files.
>>> Are you certain it isn't the F25 Samba client that's causing this?
>>
>> No.
>>
>>> Try
>>> having the F25 server share the same directory via NFS and use the F25
>>> NFS client for testing. See if that improves things.
>>
>> How about ssh? When I use ssh on Fedora 25 to drag down a file I'm
>> getting slightly different results, 4.4MB/s. So it's faster than the
>> GNOME samba client, whatever that's using, but it's still slower by 2x
>> than the Windows 10 samba client.
>
> Have you tried the iperf suggestion? First on the server, open up
> TCP port 5001 on the firewall (just is just temporarily--iperf
> defaults to port 5001), then run "iperf -s" on the server.
>
> On the client, run "iperf -c ip-address-of-server" and wait, oh, 15
> seconds or so. Both the client and server should show some results.
> This is from my laptop as the client over a 100Mbps wired link to my
> server (yes, it's an old laptop with a built-in 100Mbps NIC):
>
> [root@golem4 ~]# iperf -c 192.168.1.50
> ------------------------------------------------------------
> Client connecting to 192.168.1.50, TCP port 5001
> TCP window size: 85.0 KByte (default)
> ------------------------------------------------------------
> [ 3] local 192.168.1.52 port 38964 connected with 192.168.1.50 port 5001
> [ ID] Interval Transfer Bandwidth
> [ 3] 0.0-10.0 sec 112 MBytes 94.2 Mbits/sec
>
> So, over my 100Mbps wired link, I got 94.2Mbps.
I'm just trying to isolate this by getting file I/O, filesystems and
network filesystem protocols out of the way. iperf is fairly close to
"being on the bare wire" so we're really just checking the hardware,
firmware and kernel network stack using iperf.
You can do similar tests using netcat (nc), but that requires
filesystem I/O and not just raw bytes as iperf does.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- su -; find / -name someone -exec touch \{\} \; -
- - The UNIX way of touching someone -
----------------------------------------------------------------------
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
