Slow 802.11ac drivers (Bootcamp Win 10 x64)

mensa84 wrote:

Yes, it is exactly the same behavior in Windows an OS X.

This eliminates any OS/Driver specific issues, since they have different drivers. This is good to know.

File copy tests are with a 2 GB file from a Samba Share on a NAS (can send via LAN up to 880 Megabit/s).

This almost Gigabit with overhead. Looks to be fine.

I always test my WAN download speed at speedtest.net. So 80 Megabit download (5 GHz) and 30 Megabit (2.4 GHz) are the results from there.

This measure end-to-end speed from the client to the Speediest.net server crossing WLAN, Gateway and intermediate public servers.

You can measure your internal network performance by using iPerf (https://www.macports.org/ports.php?by=name&substr=iperf) and setting up a client on your Mac and a server on another Mac. If you have Windows machine, there is a iPerf server for Windows. Once you verify the internal network speeds and throughput to your router and do not see any packet drop issues, or latency, you can go one step further and go to a public iPerf server (https://iperf.fr/iperf-servers.php) and run the same tests.

2.4G and 5G will differ in speeds on your local LAN. If you are concerned about your WLAN, Wireshark is the best tool to look at the radio frames and check if there are any RF issues.

mensa84 wrote:

So as it seems both WLANs should be faster than my WAN connection (80/20 Mbit/s).

The default for iPerf should be 64-byte packets. Is the server TCP or UDP? One suggestion is to look at the Wireshark packets when you transfer files over WLAN on 2.4G and see the average packet size and the protocol used and check if iPerf shows similar throughput.

On 2.4G, you are getting better speeds than 802.11g (54Mbps) which is a good sign. There does not seem to be many other devices in the 2.4G channels close by. You can use Mac's Wireless diagnostics to see all the radios that your adapter can see. On the Windows side, you can use Netspot or Acrylic WiFi.

I had around only 5 MB/s (and jumping up and down a lot) when copying files over wlan.

Is this the only slow performing case? I think we should try and address this case first. Can you describe the source and destination and the tool(s) used to transfer the file(s)? The size of the files is also a useful metric.

Do browsing, email, Skype, IM applications work reasonably well?

Usual use of Wireshark is to check issues with initial connection setup or teardown - AP Associate and Connect/Disconnect flow. Once a connection has been established, unless the client gets very busy handling beacon information or is being asked to change SSIDs frequently, it is a higher level set of protocols that should be considered. TCP and UDP is where we should look.

On the file client and server, start Wireshark, and pick the IP/Port of the opposite end to filter. Are using SSH (or SFTP/SCP) to transfer files?

Do you have dual-band APs - 2.4G and 5G? Is 2.4G running in b/g compatibility?