• Rx over 2 minutes: 310-320 Mbits/sec

• Tx over 2 minutes: 40-50 Mbits/sec

• Rx Rate of 866.6Mbps-80MHz/2S/SGI

• Tx率433.3 mbps - 80 mhz / 1 s / SGI。

• Intel Dual Band-Wireless-AC 8265 (2x2) (Q1/16)

• Intel Wi-Fi 6 AX2/01 (2x2) (Q2/19)

• 325Mbps-80MHz/1S/SGI
  292.5Mbps-80MHz/1S/SGI
  263.2Mbps-80MHz/1S

• performed another reboot after boot immediately after update to 7.2.1

• no other devices connected/registered except the one device (Intel Dual Band-Wireless-AC 8265 (2x2) (Q1/16)) to perform the test

• distance between cAP ac and device approx 5ft/~1,5-1,6m with direct line of sight

• no other networks nearby, I am using channel 58, "nearest" other network uses channel 42

• Tx Rate: 195Mbps-80MHz/1S/SGI

• Rx Rate: 866.6Mbps-80MHz/2S/SGI

• Tx Rate Set: OFDM:6-54 BW:1x-4x SGI:1x-4x HT:0-15 VHTMCS:SS1=0-9,SS2=0-9

• using Intel Wi-Fi 6 AX201 (2x2) (Q2/19)

• using Intel Centrino Ultimate-N 6300 (802.11 a/b/g/n)

• 处方:320 - 390 MBit / swith two streams

• Tx: 90-190 MBit/s with only one stream

Any ideas how to achieve acceptable data rates/throughput for Tx?

try this nic config

config-nic-intel-wifi.png

• Mixed Mode Protection - My setting is "RTS/CTS Enabled", I didn't change it, since I am not using 802.11b oder 802.11g in the 2.4 GHz band.

• Preferred Band - I kept "No Preference" as the network uses 5 GHz only

• Roaming Aggressiveness - Kept "Medium" as roaming is not applicable with only one access point

• Throughput booster - According to Intel's documentation this only effects the upload from the device to the access point. That was never an issue.

• Rx 40.5Mbps-40MHz/1S

• Tx 234Mbps-80MHz/2S

• Rx 31 MBit/s

• Tx 103 MBit/s

• Rx is ok as usual: most of the time 780Mbps-80MHz/2S/SGI (sometimes even 866.6Mbps-80MHz/2S/SGI), resulting in 304 MBit/s.

• Tx still uses one stream only: most of the time 325Mbps-80MHz/1S/SGI resulting in 183 MBit/s.

• using a different access point (Qualcomm Atheros QCA9880, see my post Wed Oct 27, 2021 11:35 pm) the problems mentioned do not occur

• the issue is the same with three different network adapters (Intel 8265, Intel AX201, TP Link T3U Plus)

• in each test the placement of the devices was different

• the same issue occurs on two laptops (#1: internal Intel AX201, #2: a. internal Intel 8265 b. TP Link T3U Plus)

• the problem does not occur when using a different access point

Another observation: when I move futher away and other devices are connected, too, the Tx Rate changes to for example 390Mbps-80MHz/2S/SGI. However, for Tx (cAP ac to device) 866.6Mbps-80MHz/2S or anything near that is never achieved.

52-64 are 5 GHz non-overlapping channels.

Code:Select all

/caps-man> export

- "SMPS is a problem if enabled (reduces the max # receive antenna to just 1 on the client)

- "line of sight" and close proximity are not the good conditions for spatial streams (MIMO) operation. Multipath is a must. Seehttps://www.ieee.li/pdf/viewgraphs/intr ... s_mimo.pdf
(Having the client In the backplane direction of the cAP, the spreading of the antenna might be sub-optimal, (seen in a small angle))

- if RTS/CTS is needed for "auto SMPS" then it should be enabled on the AP.

but the MCS encoding had to be strongly reduced to MCS04 or 16-QAM for the noise or interference.

What is meant here? 5260Ceee, 5280eCee, 5300eeCe , and 5320eeeC use one and the same 80 MHz channel. If 5300Ceee would have been selected, then there would be serieus interference with the previous channels.

add band=5ghz-a/n/ac control-channel-width=20mhz frequency=5180 name=channels-5-non-overlapping-36-48 add band=5ghz-a/n/ac control-channel-width=20mhz frequency=5260 name=channels-5-non-overlapping-52-64 add band=5ghz-a/n/ac control-channel-width=20mhz frequency=5500,5580 name=channels-5-non-overlapping-100-128 add band=5ghz-a/n/ac control-channel-width=20mhz frequency=5745,5825 name=channels-5-non-overlapping-149-177

show these settings CAP ac

• upgraded from 7.2.1 to 7.2.3

• changed the channels according to the information above

• Changed the setting on the client from "Auto SPMS" to "No SPMS"

- "line of sight" and close proximity are not the good conditions for spatial streams (MIMO) operation.Multipath is a must.

1. the most straight forward way is polarization diversity. There are only two orthogonal polarization planes so it's only good for 2x2. It's achieved by having a pair of antennae set at right angle between them, professional antennae actually have the two one over another like a cross. Multipath makes things worse in this case, polarity generally changes at every reflection. So for clear LOS cases, MIMO 2x2 with polarization diversity should work close to ideally. Ideal orientation of receiving antennae helps, so one xan try to rotate antennae around the direction pointing at the transmitter to match Rx polarization planes with Tx polarization planes as good as possible.
   
   
2. spatial diversity, which means that antennae are set certain distance apart. It works fairly for higher orders of MIMO, but to do it properly, distance between any pair of Tx or Rx antennae has to be at least few wavelengths. For transmitters operating at 2.4 GHz, wavelength is around 12 cm, so antennae should be separated at least 30-50 cm apart. Which obviously doesn't happen with any consumer electronic device (except for carefully engineered laptops). Wifi at 5GHz is a bit better with this regard, wavelength is approx 2.2 to 2.5 times shorter which makes construction of better antenna much easier. BTW, mobile networks sometimes use spatial diversity even on low bands ... with frequencies as low as 700MHz this means distance between antenna of at least 3 meters ... but when looking up at tower keep in mind that panel antennae used for that frequency are 2.5m to 3m high.
   Now, with spatial diversity multipath can help because (multiple) reflections can make actual distance difference between Tx antennae appear larger at receiver ... but can make it vanish as well. So the effect can vary a lot even with small receiver movements. OTOH multipath can cause receiver to sense increased interference if it can't cope with multipath properly (it's not exactly trivial and I can imagine low cost receivers lacking DSP processing power and/or shitty DSP software burp in some cases) and in that case LOS SISO might give better results.

... what to do with omnidirectional antenna orientation.

1) Give up support for last millennium's 802.11a and 802.11b standards. Support for which greatly reduces the useful bandwidth. In 2.4GHz use "n only" in 5GHz use "ac only" or "n/ac ".

2. Abandon HW.Protection Mode set None for hidden node protection. This mode also significantly reduces useful bandwidth. At current transmission speeds, it does more harm than good.

3. HT Guard Interval instead of any, set long. This significantly improves stability. In the table of wireless registrations will no longer beautiful Rate 866.6Mbps-80MHz/2S/SGI instead it will be more stable Rate 780Mbps-80MHz/2S

4. In order to assign CAP radio settings data manually set Action create-enabled instead of crete-dynamic-enabled

5. To scan the air and manually assign the frequencies of the least loaded channels from the non-intersecting channels. Because if the settings specify 5745, 5825, then all points will work on the frequency 5745, to the second almost never go. Because with normal settings, the frequency is selected only once when switching on.

i think will be nice to see an export of that cAP ac radios configuration

Try netbooting the device with OpenWrt and seeing if the same behavior occurs there. This would rule out hardware issues.

1) Give up support for last millennium's 802.11a and 802.11b standards. Support for which greatly reduces the useful bandwidth. In 2.4GHz use "n only" in 5GHz use "ac only" or "n/ac ".

I changed the setting from5ghz-a/n/acto5ghz-n/ac.

2. Abandon HW.Protection Mode set None for hidden node protection. This mode also significantly reduces useful bandwidth. At current transmission speeds, it does more harm than good.

Changed from "not set" toNone.

3. HT Guard Interval instead of any, set long. This significantly improves stability. In the table of wireless registrations will no longer beautiful Rate 866.6Mbps-80MHz/2S/SGI instead it will be more stable Rate 780Mbps-80MHz/2S

Changed from "not set" tolong.

4. In order to assign CAP radio settings data manually set Action create-enabled instead of crete-dynamic-enabled

Didn't change this, as I prefer the automatic setting.

5. To scan the air and manually assign the frequencies of the least loaded channels from the non-intersecting channels. Because if the settings specify 5745, 5825, then all points will work on the frequency 5745, to the second almost never go. Because with normal settings, the frequency is selected only once when switching on.

Sorry, didn't understand what you meant by number 5.



Laptop -> cap ac (Rx) : two streams, average 309 MBits/s ...fine as usual
cap ac (Tx) -> Laptop : one stream, average 81 MBits/s ... same problem

Therefore I reverted the changes for now.

i think will be nice to see an export of that cAP ac radios configuration

Would you be so kind and give me the terminal command. With that I can copy and paste specifically what you need.

Try netbooting the device with OpenWrt and seeing if the same behavior occurs there. This would rule out hardware issues.

Is there a manual, tutorial, ... somewhere? If so, would you be so kind and provide a link to me.

Code:Select all

[admin@雷竞技网站MikroTik-cap-ac-01] / caps-man >导出/帽子-man channel add band=2ghz-b/g/n control-channel-width=20mhz frequency=2437 name=channel6 add band=5ghz-a/n/ac control-channel-width=20mhz frequency=5260 name=channels-5-non-overlapping-52-64 /caps-man datapath add local-forwarding=yes name=datapath-WifiB vWifiA-id=31 vWifiA-mode=use-tag add local-forwarding=yes name=datapath-WifiC vWifiA-id=34 vWifiA-mode=use-tag add local-forwarding=yes name=datapath-WifiD vWifiA-id=35 vWifiA-mode=use-tag /caps-man security add authentication-types=wpa2-psk encryption=aes-ccm name=WifiA add authentication-types=wpa2-psk encryption=aes-ccm name=WifiB add authentication-types=wpa2-psk encryption=aes-ccm name=WifiC add authentication-types=wpa2-psk encryption=aes-ccm name=WifiD /caps-man configuration add country=austria datapath=datapath-WifiB datapath.local-forwarding=yes installation=any name=WifiB security=WifiB ssid=WifiB add country=austria datapath=datapath-WifiC datapath.local-forwarding=yes installation=any name=WifiC security=WifiC ssid=WifiC add country=austria datapath=datapath-WifiD datapath.local-forwarding=yes installation=any name=WifiD security=WifiD ssid=WifiD /caps-man configuration add channel=channels-5-non-overlapping-52-64 datapath=datapath-WifiA mode=ap name=WifiA-5Ghz security=WifiA ssid=WifiA add channel=channel6 country=austria datapath=datapath-WifiA installation=any mode=ap name=WifiA-2.4GHz security=WifiA ssid=WifiA2 /caps-man datapath add bridge=bridgeLocal local-forwarding=yes name=datapath-WifiA /caps-man interface add channel.frequency=5260 configuration=WifiA-5Ghz disabled=no l2mtu=1600 mac-address=C4:AD:**:**:**:** master-interface=none name=cap18 radio-mac=C4:AD:**:**:**:** radio-name=C4A******E53 add configuration=WifiB disabled=no l2mtu=1600 mac-address=C6:AD:**:**:**:** master-interface=cap18 name=cap19 radio-mac=00:00:00:00:00:00 radio-name=C6A********3 add configuration=WifiC disabled=no l2mtu=1600 mac-address=C6:AD:**:**:**:** master-interface=cap18 name=cap20 radio-mac=00:00:00:00:00:00 radio-name=C6A********4 /caps-man manager set enabled=yes /caps-man provisioning add action=create-dynamic-enabled hw-supported-modes=ac,an,a master-configuration=WifiA-5Ghz slave-configurations=WifiB,WifiC add action=create-dynamic-enabled hw-supported-modes=b,g,gn master-configuration=WifiA-2.4GHz slave-configurations=WifiD [admin@MikroTik-cap-ac-01] /interface/wireless> export /interface wireless # managed by CAPsMAN # channel: 2437/20-Ce/gn(18dBm), SSID: *******24, local forwarding set [ find default-name=wlan1 ] disabled=no ssid=MikroTik /interface wireless security-profiles set [ find default=yes ] supplicant-identity=MikroTik add authentication-types=wpa2-psk eap-methods="" mode=dynamic-keys name=lan supplicant-identity="" /interface wireless # managed by CAPsMAN # channel: 5260/20-Ceee/ac/DP(79dBm), SSID: *******2, local forwarding set [ find default-name=wlan2 ] antenna-gain=200 band=5ghz-a/n/ac channel-width=20/40/80mhz-Ceee country=austria disabled=no mode=ap-bridge security-profile=lan ssid=*******2 supported-rates-a/g=6Mbps,54Mbps \ wps-mode=disabled /interface wireless cap # set bridge=bridgeLocal discovery-interfaces=bridgeLocal enabled=yes interfaces=wlan1,wlan2

/interface wireless set [ find default-name=wlan2 ] country=no_country_set distance=indoors frequency-mode=manual-txpower keepalive-frames=disabled mode=ap-bridge tx-power-mode=all-rates-fixed wireless-protocol=802.11 wmm-support=enabled wps-mode=disabled

Hey, I stumbled across this issue as well, where capsman controlled ap's never allowed/enabled client connections for more than 1 spatial stream on 5Ghz ac, using 80Mhz band. Resulting in max 433mbit , never reaching potential higher speeds.

I believe this is due to VHT MCS rates vs HT MCS rates. Using the table found at:

https://travelingpacket.com/2019/12/19/ ... wireshark/

I have defined rates now, to be included in my 5Ghz configuration('s). I only setup HT supported rates 8-15 to "force" 2 minimum spatial streams.

I am not allowing VHT MCS at all. Right now I see clients successfully connect upto 867Mbit using 2 Streams.

I am not allowing VHT MCS at all. Right now I see clients successfully connect upto 867Mbit using 2 Streams.

我需要做一些额外的阅读,understand what to do with omnidirectional antenna orientation. So still puzzled with either both antenna parallel or perpendicular on a device like RB2011 , or more general on those spider like devices with many antenna. So far I considered only the donut shape of the signal transmitted and receive sensitivity gain.