Hi guys,
I have a problem with the 2GHz speed on the WAP AC, 5GHz works as it should! There’s little to no interference on the site at 2GHz. I’ve also written to support with the supout.rif to which they responded with
/caps-man configuration add tx-chains=0 rx-chains=0 name=2ghz
which made no improvement at all…
The stable fw at the time was 6.37 on which the 2GHz network was unusable… ping was anywhere from 2-200ms, max speed was 10-12 Mbps (Line speed is 50/50 Mbps). On the 5GHz there was no issues at all…full speed with normal pings.
This issue was even worse on the 6.37.1 version (maximum was 5-20MBps, with ping timeouts… only on 2.4GHz, the 5GHz band worked fine), that’s why I’ve upgraded to the RC… I haven’t upgraded to the latest (at the time) RC build of the 6.38 (there’s no mention of the 2.4GHz fix).
So then I upgraded to the 6.38rc10 which made little improvement (about 30Mbps throughput, usually it fluctuates between 17-32MBps) and the pings were somewhat stable…
The CAP device (only one) is also a WAP AC.
Can someone please give me some insight on what’s going on? point me to the config mistake which I did?
Thank you!
/caps-man> export compact hide-sensitive
# feb/03/1970 20:52:30 by RouterOS 6.38rc10
# software id = 3M60-M7VG
#
/caps-man channel
add band=2ghz-b/g/n comment=2GHz extension-channel=disabled frequency=2462 name=channel11 width=20
add band=5ghz-a/n/ac comment=5Ghz extension-channel=disabled frequency=5200 name=channel40 width=40
add band=2ghz-b/g/n comment=2GHz extension-channel=disabled frequency=2412 name=channel1 width=20
add band=5ghz-a/n/ac comment=5Ghz extension-channel=disabled frequency=52040 name=channel48 width=40
/caps-man datapath
add bridge=bridge-trunk client-to-client-forwarding=yes local-forwarding=yes name=internal vlan-id=3 vlan-mode=\
use-tag
add bridge=bridge-trunk name=*** vlan-id=7 vlan-mode=use-tag
add bridge=bridge-trunk name=guest vlan-id=6 vlan-mode=use-tag
add bridge=bridge-trunk client-to-client-forwarding=yes local-forwarding=yes name=mgmt vlan-id=5 vlan-mode=use-tag
/caps-man security
add authentication-types=wpa2-psk encryption=aes-ccm group-encryption=aes-ccm name=guest
add authentication-types=wpa2-psk encryption=aes-ccm group-encryption=aes-ccm name=***
add authentication-types=wpa2-psk encryption=aes-ccm group-encryption=aes-ccm name=***
add authentication-types=wpa2-psk encryption=aes-ccm group-encryption=aes-ccm name=mgmt
/caps-man configuration
add country=*** datapath=inkubator datapath.client-to-client-forwarding=no datapath.local-forwarding=no mode=ap \
name=*** security=*** ssid=***
add country=*** datapath=guest datapath.client-to-client-forwarding=no datapath.local-forwarding=no mode=ap \
name=guest security=guest ssid=guest
add country=*** datapath=internal datapath.client-to-client-forwarding=no datapath.local-forwarding=no mode=ap \
name=internal security=internal ssid=***
/caps-man access-list
add action=accept interface=all signal-range=-80..120
add action=reject interface=all signal-range=-120..-81
/caps-man manager
set ca-certificate=auto certificate=auto enabled=yes
/caps-man provisioning
add action=create-dynamic-enabled master-configuration=*** slave-configurations=guest,internal,*4,*5,*6,*7,*8