hAP be3 Media TERRIBLE 6 GHz performance

SwiftJ19 · July 27, 2026, 8:32am

I've recently received my hAP be3 Media, and it's really a wonderful "all-in-one" device. Containers run great, the 2.5 Gbps ports work perfectly for me (no flapping or anything like that) but the WiFi...

I use my MikroTik on a 1 Gbps down/500 Mbps up internet connection, how is it that on 5 GHz I get around 900 Mbps down and on 6 GHz, it's a maximum of 250-300 Mbps?!

I use the default config, which does this to the WiFi:

 /interface wifi {
  :local ifcId [/interface wifi find where default-name=wifi1]
    set $ifcId configuration.mode=ap channel.band=2ghz-be disabled=no
    set $ifcId channel.width=20/40mhz;
    set $ifcId channel.skip-dfs-channels=10min-cac;
    set $ifcId security.authentication-types=wpa2-psk,wpa3-psk .passphrase=$defconfWifiPassword .ft=yes .ft-over-ds=yes
    :local wlanMac [/interface get [/interface find where default-name=wifi1] mac-address];
    :set ssid "MikroTik-$[:pick $wlanMac 9 11]$[:pick $wlanMac 12 14]$[:pick $wlanMac 15 17]"
    set $ifcId configuration.ssid=$ssid
  }
  /interface wifi {
  :local ifcId [/interface wifi find where default-name=wifi2]
    set $ifcId configuration.mode=ap channel.band=5ghz-be disabled=no
    set $ifcId channel.width=20/40/80mhz;
    set $ifcId channel.skip-dfs-channels=10min-cac;
    set $ifcId security.authentication-types=wpa2-psk,wpa3-psk .passphrase=$defconfWifiPassword .ft=yes .ft-over-ds=yes
    :local wlanMac [/interface get [/interface find where default-name=wifi1] mac-address];
    :set ssid "MikroTik-$[:pick $wlanMac 9 11]$[:pick $wlanMac 12 14]$[:pick $wlanMac 15 17]"
    set $ifcId configuration.ssid=$ssid
  }
  /interface wifi {
  :local ifcId [/interface wifi find where default-name=wifi3]
    set $ifcId configuration.mode=ap channel.band=6ghz-be disabled=no
    set $ifcId channel.width=20/40/80/160/320mhz;
    set $ifcId channel.skip-dfs-channels=10min-cac;
    set $ifcId security.authentication-types=wpa3-psk .passphrase=$defconfWifiPassword .ft=yes .ft-over-ds=yes
    :local wlanMac [/interface get [/interface find where default-name=wifi1] mac-address];
    :set ssid "MikroTik-$[:pick $wlanMac 9 11]$[:pick $wlanMac 12 14]$[:pick $wlanMac 15 17]"
    set $ifcId configuration.ssid=$ssid
  /interface wifi set mld1 disabled=no configuration.ssid=$ssid \
    security.authentication-types=wpa3-psk .passphrase=$defconfWifiPassword
  /interface wifi set [find where default-name~"wifi"] mld-interface=mld1 security.ft=no .ft-over-ds=no
  }

I've tested this with multiple WiFi-7 clients (that support 6 GHz), like the iPhone 17. Any ideas?

I am from Austria, if it helps (since 6 GHz works differently depending on the country). I did not have this issue with my previous 6 GHz (WiFi 6e) router.

wdl · July 27, 2026, 8:45am

I wonder if it’s WiFi 7 specific, or really is related to a poor 6Ghz band.

I know some reported that updating to latest ROS made it work better.

Have you tried with any WiFi 6E device (like the M4 Macs)?

SwiftJ19 · July 27, 2026, 9:28am

I've tried a lot already I've disabled mld and all the other bands, so that I had a 6 GHz-only WiFi, but it was still the same. And yes, I've also tested this with a MacBook that is still on WiFi 6E.

I've also installed the latest 'testing' version (7.24rc2) an hour ago, just to see if it's better but no, sadly not.

The only thing left for me to "blame" might really be the radio (but how is it even worse than the 5 GHz radio?) or regulatory requirements, but other routers here in Austria do work just fine with 6 GHz, so regulatory requirements shouldn't be in the way.

wdl · July 27, 2026, 9:50am

I’m still waiting for my own units to arrive, so I’ll be in the same boat sooner or later. Especially given that the 6Ghz band is one of the main reasons why I went with this model.

It could be the radio itself, but it’s more likely to be a configuration or a firmware issue if you ask me, which than could be solved in software.

I’d suggest you to open a ticket with mikrotik and see what they have to say about it.

Keep us updated.

erlinden · July 27, 2026, 10:09am

Can you supply export instead of the initial script?
/export file=anynameyoulike

Remove serial and any other private info.
Did you also upgrade the firmware?

SwiftJ19 · July 27, 2026, 10:47am

Here is the current config. Keep in mind that I've tried quite a lot already, I'm not really on the default config (anymore), not even on the stable version anymore.

But I had this issue right from the beginning, with the default wireless network it creates (with the password printed on the device), which is why I've provided that initial script above and why I've even tried so much like upgrading to the latest testing version for example.

# 2026-07-27 12:25:07 by RouterOS 7.24rc2
# software id = REMOVED
#
# model = MA53UG+HbeH
# serial number = REMOVED
/disk
add file-path=/usb1/swap file-size=1914.9MiB slot=file-usb1-swap swap=yes \
    type=file
set usb1 comment=USBStick1
/interface bridge
add admin-mac=REMOVED auto-mac=no \
    frame-types=admit-only-vlan-tagged name=bridge1 vlan-filtering=yes
add name=internal protocol-mode=none
add name=netbird-client
/interface ethernet
set [ find default-name=ether1 ]
set [ find default-name=ether2 ] \
    l2mtu=1598
set [ find default-name=ether3 ] \
    l2mtu=1598
set [ find default-name=ether4 ] l2mtu=1598
set [ find default-name=ether5 ] l2mtu=1598
/interface veth
add address="" container-mac-address=REMOVED dhcp=yes gateway="" \
    gateway6="" mac-address=REMOVED name=veth-app-netbird-client
add address=172.18.0.2/24 container-mac-address=REMOVED dhcp=no \
    gateway=172.18.0.1 gateway6="" mac-address=REMOVED name=\
    veth-app-technitium
/interface vlan
add interface=ether1 name=UPLINK-VLAN2 vlan-id=2
add interface=bridge1 name=vlan5 vlan-id=5
add interface=bridge1 name=vlan7 vlan-id=7
add interface=bridge1 name=vlan10 vlan-id=10
add interface=bridge1 name=vlan20 vlan-id=20
/container
add hosts=technitium:172.18.0.2 interface=veth-app-technitium layer-dir=\
    /usb1/apps/layers mount=/usb1/apps/technitium/config:/etc/dns:rw name=\
    app-technitium remote-image=docker.io/technitium/dns-server root-dir=\
    /usb1/apps/technitium/technitium_root stop-time=30s
add env="NB_DISABLE_CUSTOM_ROUTING=true,NB_HOSTNAME=REMOVED,NB_LOG_LEV\
    EL=info,NB_MANAGEMENT_URL=REMOVED,NB_NAME=REMOVED,N\
    B_SETUP_KEY=REMOVED,NB_USE_LEGACY_ROUTING=tru\
    e" hosts=netbird-client:10.0.201.3 interface=veth-app-netbird-client \
    layer-dir=/usb1/apps/layers mount=\
    /usb1/apps/netbird-client/netbird-client:/var/lib/netbird:rw name=\
    app-netbird-client remote-image=docker.io/netbirdio/netbird:latest \
    root-dir=/usb1/apps/netbird-client/netbird-client_root stop-time=30s
/interface pppoe-client
add add-default-route=yes comment="PPPoE Internet" disabled=no interface=\
    Internet-VLAN2 max-mru=1500 max-mtu=1500 name=PPPoE-Internet user=REMOVED
/interface list
add comment=Internet name=WAN
add comment=VLAN10-LAN name=VLAN10-LAN
add comment="Allow Winbox via MAC" name=WinboxMac
/interface wifi configuration
add channel.band=2ghz-be .skip-dfs-channels=10min-cac .width=20/40mhz \
    comment="WiFi 2.4 GHz" country=Austria datapath.bridge=bridge1 .vlan-id=\
    10 disabled=no name=WiFi-2G security.authentication-types=wpa3-psk .ft=no \
    .ft-over-ds=no ssid=WiFi
add channel.band=5ghz-be .skip-dfs-channels=10min-cac .width=20/40/80mhz \
    comment="WiFi 5 GHz" country=Austria datapath.bridge=bridge1 .vlan-id=10 \
    disabled=no name=WiFi-5G security.authentication-types=wpa3-psk .ft=no \
    .ft-over-ds=no ssid=WiFi
add channel.band=6ghz-be .skip-dfs-channels=10min-cac .width=\
    20/40/80/160/320mhz comment="WiFi 6 GHz" country=Austria datapath.bridge=\
    bridge1 .vlan-id=10 disabled=no name=WiFi-6G \
    security.authentication-types=wpa3-psk .ft=no .ft-over-ds=no ssid=WiFi
add comment="MLD WiFi Config" datapath.bridge=bridge1 .vlan-id=10 disabled=no \
    name=MLD-WiFi security.authentication-types=wpa3-psk .ft=no .ft-over-ds=\
    no ssid=WiFi
add channel.band=2ghz-be .skip-dfs-channels=10min-cac .width=20/40mhz \
    comment="WiFiDevices 2.4 GHz" country=Austria datapath.bridge=bridge1 \
    .vlan-id=10 disabled=no name=WiFiDevices-2G \
    security.authentication-types=wpa2-psk .ft=yes .ft-over-ds=yes ssid=\
    WiFiDevices
add comment="WiFi 2.4 GHz Legacy" country=Austria datapath.vlan-id=10 \
    disabled=no name=WiFi-2G-Legacy security.authentication-types=wpa2-psk \
    .ft=no .ft-over-ds=no ssid=WiFi
add channel.band=5ghz-ax .skip-dfs-channels=10min-cac comment=\
    "WiFi 5 GHz Legacy" country=Austria datapath.bridge=bridge1 .vlan-id=10 \
    disabled=no name=WiFi-5G-Legacy security.authentication-types=wpa3-psk \
    .ft=no .ft-over-ds=no ssid=WiFi
add comment="MLD WiFi Plus Config" country=Austria datapath.bridge=bridge1 \
    .vlan-id=10 disabled=no name=MLD-WiFiPlus security.authentication-types=\
    wpa3-psk .ft=no .ft-over-ds=no ssid="WiFi Plus"
add channel.band=6ghz-be .skip-dfs-channels=10min-cac .width=\
    20/40/80/160/320mhz comment="WiFi Plus 6 GHz" country=Austria \
    datapath.bridge=bridge1 .vlan-id=10 disabled=no name=WiFiPlus-6G \
    security.authentication-types=wpa3-psk .ft=no .ft-over-ds=no ssid=\
    "WiFi Plus"
/interface wifi
add configuration=MLD-WiFi configuration.mode=ap disabled=no mac-address=\
    REMOVED mld-name=mld-REMOVED name=WiFi-mld \
    security.authentication-types=wpa3-psk
add configuration=MLD-WiFiPlus configuration.mode=ap mac-address=\
    REMOVED mld-name=mld-REMOVED name=WiFiPlus-mld
set [ find default-name=wifi1 ] configuration=WiFi-2G configuration.mode=ap \
    disabled=no mld-interface=WiFi-mld name=WiFi-2G
set [ find default-name=wifi2 ] configuration=WiFi-5G configuration.mode=ap \
    disabled=no mld-interface=WiFi-mld name=WiFi-5G
set [ find default-name=wifi3 ] configuration=WiFi-6G configuration.mode=ap \
    disabled=no mld-interface=WiFi-mld name=WiFi-6G
add configuration=WiFiDevices-2G configuration.mode=ap disabled=no \
    mac-address=REMOVED master-interface=WiFi-2G name=\
    WiFiDevices-2G
add configuration=WiFiPlus-6G configuration.mode=ap mac-address=\
    REMOVED master-interface=WiFi-6G mld-interface=WiFiPlus-mld \
    name=WiFiPlus-6G
/ip pool
add comment=VLAN10-LAN name=LAN-DHCP ranges=10.0.0.150-10.0.0.250
add comment=NETBIRD-CLIENT name=NETBIRD-CLIENT ranges=10.0.201.2/31
/ip dhcp-server
add address-pool=LAN-DHCP comment=VLAN10-LAN interface=vlan10 name=LAN-DHCP
add address-pool=NETBIRD-CLIENT comment=NETBIRD-CLIENT interface=\
    netbird-client name=NETBIRD-DHCP
/interface ppp-client
add apn=internet name=ppp-out1 port=usb2
/queue type
add kind=cake name=cake
/queue tree
add max-limit=240M name=queue-upload packet-mark=no-mark parent=PPPoE-Internet \
    queue=cake
add disabled=yes max-limit=900M name=queue-download packet-mark=no-mark \
    parent=bridge1 queue=cake
/app
set HA-otbr-matter required-hw-devices=ttyACM0:usb2:default:/dev/ttyACM0
set firefox use-https=no
add disabled=no network=netbird-client use-https=no yaml="name: netbird-client\
    \ndescr: NetBird mesh VPN client\
    \npage: https://netbird.io/\
    \ncategory: networking\
    \n\
    \nservices:\
    \n  netbird-client:\
    \n    image: docker.io/netbirdio/netbird:latest\
    \n    environment:\
    \n      NB_SETUP_KEY: REMOVED\
    \n      NB_NAME: \"REMOVED\"\
    \n      NB_HOSTNAME: \"REMOVED\"\
    \n      NB_LOG_LEVEL: \"info\"\
    \n      NB_DISABLE_CUSTOM_ROUTING: \"true\"\
    \n      NB_USE_LEGACY_ROUTING: \"true\"\
    \n      NB_MANAGEMENT_URL: REMOVED\
    \n    volumes:\
    \n      - netbird-client:/var/lib/netbird"
set otbr network-pvid=10 required-hw-devices=\
    ttyACM0:usb2:default:/dev/ttyACM0 use-https=no
set technitium disabled=no use-https=no
/app settings
set disk=usb1 lan-bridge=bridge1 router-ip=10.0.0.1
/container config
set registry-url=https://registry-1.docker.io tmpdir=/usb1/pull
/interface bridge port
add bridge=bridge1 frame-types=\
    admit-only-vlan-tagged interface=ether2
add bridge=bridge1 frame-types=\
    admit-only-vlan-tagged interface=ether3
add bridge=bridge1 interface=ether4 pvid=10
add bridge=bridge1 interface=ether5 pvid=10
/ip neighbor discovery-settings
set discover-interface-list=WinboxMac
/interface bridge vlan
add bridge=bridge1 comment="ALL VLANs" tagged=bridge1,ether2,ether3 vlan-ids=\
    5,7,10,20
/interface list member
add interface=ether1 list=WAN
add interface=Internet-VLAN2 list=WAN
add interface=PPPoE-Internet list=WAN
add interface=vlan10 list=VLAN10-LAN
add interface=ether5 list=WinboxMac
add interface=vlan5 list=WinboxMac
/interface wifi cap
set caps-man-addresses=127.0.0.1
/interface wifi capsman
set enabled=no
/interface wifi provisioning
add action=create-dynamic-enabled disabled=no master-configuration=\
    WiFi-5G-Legacy name-format=%I-5G supported-bands=5ghz-ax
add action=create-dynamic-enabled disabled=yes master-configuration=\
    WiFi-2G-Legacy name-format=%I-2G supported-bands=2ghz-ax
/ip address
add address=10.0.0.1/24 interface=vlan10 network=10.0.0.0
add address=10.0.5.1/24 interface=vlan5 network=\
    10.0.5.0
add address=10.0.201.1/24 interface=netbird-client \
    network=10.0.201.0
/ip dhcp-server lease
REMOVED
/ip dhcp-server network
add address=10.0.0.0/24 comment=VLAN10-LAN dns-server=10.0.0.1 gateway=\
    10.0.0.1
add address=10.0.201.0/24 comment=NETBIRD-CLIENT dns-server=10.0.0.1 gateway=\
    10.0.201.1
/ip dns
set servers=9.9.9.9
/ip firewall address-list
add address=10.0.0.10 list=REMOVED
add address=172.18.0.2 list=Technitium
/ip firewall filter
add action=accept chain=input comment=\
    "ACCEPT ESTABLISHED, RELATED, UNTRACKED" connection-state=\
    established,related,untracked
add action=drop chain=input comment="DROP INVALID" connection-state=invalid
add action=accept chain=input comment="ACCEPT ICMP" protocol=icmp
add action=accept chain=input comment=\
    "ACCEPT TO LOCAL LOOPBACK (FOR CAPSMAN)" dst-address=127.0.0.1 \
    in-interface=lo src-address=127.0.0.1
add action=jump chain=input in-interface=vlan10 jump-target=\
    ZONE-LAN-to-Router
add action=jump chain=input in-interface=netbird-client \
    jump-target=ZONE-NETBIRD-to-Router
add action=jump chain=input in-interface=vlan5 \
    jump-target=ZONE-MIKROTIK-to-Router
add action=reject chain=input comment="REJECT EVERYTHING ELSE | input" \
    reject-with=icmp-network-unreachable
add action=fasttrack-connection chain=forward comment=FASTTRACK \
    connection-mark=no-mark connection-state=established,related
add action=accept chain=forward comment=\
    "ACCEPT ESTABLISHED, RELATED, UNTRACKED" connection-state=\
    established,related,untracked
add action=drop chain=forward comment="DROP INVALID" connection-state=invalid
add action=drop chain=forward comment="DROP ALL FROM WAN NOT DSTNATed" \
    connection-nat-state=!dstnat in-interface-list=WAN
add action=jump chain=forward in-interface=vlan10 \
    jump-target=ZONE-LAN-to-WAN out-interface-list=WAN
add action=jump chain=forward in-interface=\
    vlan10 jump-target=ZONE-LAN-to-INTERNALAPPS out-interface=internal
add action=jump chain=forward in-interface=\
    netbird-client jump-target=ZONE-NETBIRD-to-INTERNALAPPS out-interface=\
    internal
add action=jump chain=forward comment="INTERNALAPPS -> WAN" in-interface=\
    internal jump-target=ZONE-INTERNALAPPS-to-WAN out-interface-list=WAN
add action=jump chain=forward comment="NETBIRD -> WAN" in-interface=\
    netbird-client jump-target=ZONE-NETBIRD-to-WAN out-interface-list=WAN
add action=jump chain=forward comment="LAN -> MIKROTIK" in-interface=vlan10 \
    jump-target=ZONE-LAN-to-MIKROTIK out-interface=vlan5
add action=jump chain=forward comment="NETBIRD -> MIKROTIK" in-interface=\
    netbird-client jump-target=ZONE-NETBIRD-to-MIKROTIK out-interface=vlan5
add action=jump chain=forward comment="MIKROTIK -> WAN" in-interface=vlan5 \
    jump-target=ZONE-MIKROTIK-to-WAN out-interface-list=WAN
add action=reject chain=forward comment="REJECT EVERYTHING ELSE | forward" \
    reject-with=icmp-network-unreachable
add action=accept chain=ZONE-LAN-to-Router comment="Allow ALL for now"
add action=accept chain=ZONE-LAN-to-WAN comment="Accept ALL for now"
add action=accept chain=ZONE-MIKROTIK-to-Router
add action=accept chain=ZONE-MIKROTIK-to-WAN
add action=accept chain=ZONE-LAN-to-MIKROTIK
add action=accept chain=ZONE-LAN-to-INTERNALAPPS disabled=yes
add action=accept chain=ZONE-INTERNALAPPS-to-WAN
add action=accept chain=ZONE-LAN-to-INTERNALAPPS comment="Allow DNS TCP" \
    dst-address-list=Technitium dst-port=53 protocol=tcp
add action=accept chain=ZONE-NETBIRD-to-INTERNALAPPS comment="Allow DNS TCP" \
    dst-address-list=Technitium dst-port=53 protocol=tcp
add action=accept chain=ZONE-LAN-to-INTERNALAPPS comment="Allow DNS UDP" \
    dst-address-list=Technitium dst-port=53 protocol=udp
add action=accept chain=ZONE-NETBIRD-to-INTERNALAPPS comment="Allow DNS UDP" \
    dst-address-list=Technitium dst-port=53 protocol=udp
add action=accept chain=ZONE-LAN-to-INTERNALAPPS comment=\
    "Allow WebInterface Technitium" dst-address-list=Technitium dst-port=5380 \
    protocol=tcp src-address-list=REMOVED
add action=accept chain=ZONE-NETBIRD-to-WAN
add action=accept chain=ZONE-NETBIRD-to-Router
add action=accept chain=ZONE-NETBIRD-to-MIKROTIK
/ip firewall nat
add action=masquerade chain=srcnat comment="masquerade for WAN" ipsec-policy=\
    out,none out-interface-list=WAN
add action=masquerade chain=srcnat comment="app NETBIRD-CLIENT network masquer\
    ade rule to allow outgoing traffic be routed back" in-interface=\
    netbird-client
/ip route
add comment=NETBIRD-CLIENT disabled=no distance=1 dst-address=100.0.0.0/24 \
    gateway=10.0.201.3 routing-table=main scope=30 target-scope=10
/ipv6 address
add address=::1 comment="Public IPv6 for LAN" from-pool=Internet-IPv6 interface=\
    vlan10
add address=fd42:10::1 comment=IPv6-VLAN10 interface=vlan10
/ipv6 dhcp-client
add add-default-route=yes comment=Internet-IPv6 interface=PPPoE-Internet pool-name=\
    Internet-IPv6 pool-prefix-length=64 request=address,prefix
/ipv6 firewall address-list
add address=::/128 comment="defconf: unspecified address" list=bad_ipv6
add address=::1/128 comment="defconf: lo" list=bad_ipv6
add address=fec0::/10 comment="defconf: site-local" list=bad_ipv6
add address=::ffff:0.0.0.0/96 comment="defconf: ipv4-mapped" list=bad_ipv6
add address=::/96 comment="defconf: ipv4 compat" list=bad_ipv6
add address=100::/64 comment="defconf: discard only " list=bad_ipv6
add address=2001:db8::/32 comment="defconf: documentation" list=bad_ipv6
add address=2001:10::/28 comment="defconf: ORCHID" list=bad_ipv6
add address=3ffe::/16 comment="defconf: 6bone" list=bad_ipv6
/ipv6 firewall filter
add action=accept chain=input comment=\
    "ACCEPT ESTABLISHED, RELATED, UNTRACKED" connection-state=\
    established,related,untracked
add action=drop chain=input comment="DROP INVALID" connection-state=invalid
add action=accept chain=input comment="ACCEPT ICMPv6" protocol=icmpv6
add action=accept chain=input comment="ACCEPT UDP TRACEROUTE" dst-port=\
    33434-33534 protocol=udp
add action=accept chain=input comment=\
    "ACCEPT DHCPv6-CLIENT PREFIX DELEGATION" dst-port=546 protocol=udp \
    src-address=fe80::/10
add action=accept chain=input comment="ACCEPT IKE" dst-port=500,4500 \
    protocol=udp
add action=reject chain=input comment="REJECT EVERYTHING ELSE | input" \
    reject-with=icmp-no-route
add action=fasttrack-connection chain=forward comment=FASTTRACK6 \
    connection-mark=no-mark connection-state=established,related
add action=accept chain=forward comment=\
    "ACCEPT ESTABLISHED, RELATED, UNTRACKED" connection-state=\
    established,related,untracked
add action=drop chain=forward comment="DROP INVALID" connection-state=invalid
add action=drop chain=forward comment="DROP PACKETS WITH BAD SRC IPv6" \
    src-address-list=bad_ipv6
add action=drop chain=forward comment="DROP PACKETS WITH BAD DST IPv6" \
    src-address-list=bad_ipv6
add action=drop chain=forward comment="rfc4890 drop hop-limit=1" hop-limit=\
    equal:1 protocol=icmpv6
add action=accept chain=forward comment="ACCEPT ICMPv6" protocol=icmpv6
add action=accept chain=forward comment="ACCEPT HIP" protocol=139
add action=accept chain=forward comment="ACCEPT IKE" dst-port=500,4500 \
    protocol=udp
add action=jump chain=forward comment="LAN -> WAN" in-interface=vlan10 \
    jump-target=ZONE-LAN-to-WAN out-interface-list=WAN
add action=reject chain=forward comment="REJECT EVERYTHING ELSE | forward" \
    reject-with=icmp-no-route
add action=accept chain=ZONE-LAN-to-WAN
/ipv6 firewall mangle
add action=change-mss chain=forward comment="Clamp IPv6 MSS (Outbound)" \
    new-mss=clamp-to-pmtu out-interface-list=WAN protocol=tcp tcp-flags=syn
/system clock
set time-zone-name=Europe/Vienna
/system identity
set name=MikroTik-Home-1
/system package update
set channel=testing
/system resource irq rps
set ether1 disabled=no
set ether2 disabled=no
set ether3 disabled=no
set ether4 disabled=no
set ether5 disabled=no
/tool mac-server
set allowed-interface-list=WinboxMac
/tool mac-server mac-winbox
set allowed-interface-list=WinboxMac

patrikg · July 27, 2026, 11:16am

On my Chateau 5G R17 ax, to get good wifi speed i have to set the Skip DFS to "all" instead of "10min-cac" like this on my 2.4GHz and 5Ghz band, and everything else just default config. Because of noisy neighbors.

mkx · July 27, 2026, 12:01pm

You should check actual Tx power used by AP ... by running command something like this

/interface/wifi/print [ find default-name=wifi3 ] once

According to wikipedia list of channels some 6GHz channels are LPI (low-power indoor) and some might even be VLP (very low power). I don't know what kind of power limit is associated with LPI, it might be 23dBm or less (and VLP seems to be around 14dBm).

You can check what are country limits coded into your device by running

/interface/wifi/radio/reg-info country=Austria number=0

I don't have any device capable of running in 6GHz band, but my wAP ax shows pretty low Tx limits on upper part of 5GHz band. Could be that 6GHz comes with something similar.

Mind that Tx power is spread over whole channel width and when using 320MHz channels it might get quite low compared to using 20MHz channels (difference in channel width of factor 16 means difference in Tx power 12dB) ... adding that high modulation schemes (required for fastest transfer rates) require higher SINR ... so using wide channels without being able to use adequate Tx power can easily mean lower actual throughputs than when using narrower channels.

jaclaz · July 27, 2026, 12:40pm

That is according to ETSI requirements:
Wi-Fi channels cheatsheet
From channel 144 up you only have 13 or 14 dBm.

But for 6 GHz you have max 23 dBm (or if device is VLP - but this is not the case for an AP/router only 14 dBm), so besides issues with obstacles a 6 GHz should behave in theory like the low channels (36-48) of 5 GHz.

SwiftJ19 · July 27, 2026, 1:04pm

THANK YOU for the recommendation to lower the channel width. If I select 20/40/80 MHz, it got even worse BUT with 20/40/80/160 MHz instead of the default 20/40/80/160/320 MHz, I get my full 1 Gbps internet speed over Wifi 6 GHz, so this "fixed it"!

But why is 320 MHz the default configuration? If I check the country limits, I see that Latvia has the same limits as Austria. So, to me, the default configuration seems to make no sense, at least for Europe.

Or is there any benefit to running this at 320 MHz with the current limits within the EU? Or would only people from outside the EU benefit from it?

TX power for 6 GHz is at 21 by the way.

And here is the country limits output for Austria, Germany and also Latvia, which I've compared just to see if there's a difference but there isn't:

  ranges: 2402-2482/20dBm/40MHz              
          5170-5250/23dBm/160MHz/indoor      
          5250-5330/23dBm/160MHz/indoor/dfs  
          5490-5710/30dBm/160MHz/dfs         
          5735-5835/14dBm/80MHz/indoor       
          5945-6425/23dBm/10psd/320MHz/indoor
          5945-6425/14dBm/1psd/320MHz/vlp

jaclaz · July 27, 2026, 1:09pm

23 is the max, as you posted it:

5945-6425/23dBm/10psd/320MHz/indoor

SwiftJ19 · July 27, 2026, 6:12pm

A quick update: It turns out it wasn't the 320 MHz option after all, but rather the channel used. Anything above 6175 is extremely slow, so if I set the frequency to 5955-6175, it's consistently fast (even with 320 MHz selected). Before I guess I was tricked, since switching the options also changed the channel every time, sometimes picking a "good one".

I don't yet know why that is an issue. When I do a scan, none of the channels are "busy" (I also have only one neighbour), but at least it works ... If it helps, I only have Apple Devices with WiFi 7 (or 6E), so maybe it's some issue with Apple <-> MikroTik.

infabo · July 27, 2026, 6:14pm

there are channels with vlp. very low power - does this affect range?

jaclaz · July 27, 2026, 8:41pm

@infabo
No, the channels/frequencies 5945-6425 are the same, in ETSI regulations It Is the device that makes a difference (the limitations are very different from those on the lower bands they take into account the type of device).
A "fixed indoor" device (router, access points and similar) can use 23 dBm (and 10 psd), and only indoors.
A "very low power" device (portable, battery operated, etc.) only 14 dBm (and 1 psd), both indoors and outdoors.

sirbryan · July 28, 2026, 3:10pm

Two things here:

The power level is aggregate across the total bandwidth. More bandwidth (80/160/32) = less distance/range from the AP. Lower bandwidth = more power per bit (as it were), so better range.

Regulatory rules vary across world regions, so as you found out, some channels are better than others, normally to protect incumbent licensed users of those channels. Our outdoor Ubiquiti/Cambium/etc. gear all use GPS and AFC to coordinate and adjust power levels to protect any licensed links in the area.

Some WiFi selection algorithms prioritize wider channels over narrower channels (80 vs. 40 for example).
6GHz performs marginally worse through walls than 5GHz, so it's really only good within the same room, especially on VLP. So unless you have an absolute need for 1-1.5Gbps, such as laptop that's close to the router, I'd put 2.4 on 20MHz (50-100Mbps), 5GHz on 40MHz (300Mbps+) or 80MHz (600Mbps+), and 6GHz on the same or lower than 5GHz (40 or 80).

jaclaz · July 28, 2026, 4:59pm

Not really-really.
That is true for 2.4 GHz and 5 GHz, 6 GHz is different.

https://blogs.cisco.com/networking/networking-demystified-why-wi-fi-6e-is-hot-and-why-you-should-care

Power Spectral Density You Say?

The 6 GHz rules bring another interesting twist. In 5 GHz and 2.4 GHz, the transmission rules are driven by the notion of maximum Effective Isotropic Radiated Power (EIRP), which is the maximum quantity of energy emitted by a client or an AP. As the max EIRP is fixed, a system that transmits over a 20-MHz channel transmits more energy per unit of frequency (per MHz) than a system that radiates the same total amount of energy, but over a wider channel, for example, 80 MHz.

The idea is the same as a water hose. If your hose delivers 1 liter per second, it will spray less water per unit of surface if you spread the jet as a flat 3-meter-wide mist than if you focus the water, power washer style, over just a half square centimeter target. A direct, and sometimes hidden consequence of this rule is that if you set your AP channel to a width of 80 MHz (instead of 20 MHz), your cell size is mechanically reduced because the amount of signal available over each MHz of the channel at a given distance is now lower. A common way to express this reduction is to say that the signal-to-noise ratio (SNR), over each MHz of frequency, reduces as the channel width increases.

The Wi-Fi community expressed this concern when the 6 GHz allocation was being discussed by worldwide regulatory bodies. The great news is that the community was heard, and the rules are different for 6 GHz band. In this new band, the max power is no longer a ‘total max’ EIRP but is defined as max Power Spectral Density (PSD) or the max power per MHz—in the hose analogy, that’s the water delivered per unit of surface. This limit is per MHz and does not change as the channel width changes. In practice, this means that a 6 GHz system can send the same amount of energy per MHz in an 80 MHz channel as it would in a 20 MHz channel, and therefore that the cell size stays the same, regardless of the channel width. It just sends more total energy as the channel size increases.

Power-rule-comparison-between-5-GHz-and-6-GHz-v2947×365 25.2 KB

As SwiftJ19 posted, the limits for ETSI (which tops anyway at 23 dBm for LP devices, VLP are irrelevant when talking of routers/AP's) are allowing:

5945-6425/23dBm/10psd/320MHz/indoor
5945-6425/14dBm/1psd/320MHz/vlp

A psd of 10 dBm per Megahertz (ETSI) is a lot BUT it is in practice truncated by the (low) max allowed of 23 dBm (but in any case the power is the same no matter the width).

FCC and its 5 dBM per Megaherts is seemingly half, BUT since the overall cap is 30 dBm, paradoxically in the US the wider the channel, the better:
https://docs.zebra.com/us/en/mobile-computers/software/bm-6ghz-for-cisco-wlan-best-practices-guide-ditamap/c-6ghz-channel-and-regulatory-information/r-6ghz-tx-power-per-channel-5ghz-versus-6-ghz.html

sirbryan · July 29, 2026, 1:30am

That's good to know. I still have horrible coverage with 6GHz, so setting it to the same bandwidth (or less) as the 5GHz radio will keep devices from preferring it.

jaclaz · July 29, 2026, 8:29am

I still stand by my theory that the "one AP to rule 'em all" in normal houses/apartments (let's say up to 80-100 sqm in size) is a thing of the past and limited to 2.4 GHz.

Already 5 GHz has much lower penetration.

And 6 GHz (from the single test I did, so do not take this as the one and only truth) seems to me much worse than 5 GHz.

The future is very likely one (low power) AP per room at 6 GHz, with very wide channel.

IMHO the good Mikrotik guys should think about re-vamping a device like the wsap (adding 6 GHz):
https://mikrotik.com/product/wsap_ac_lite

that would suitable to this new approach.

holvoetn · July 29, 2026, 8:34am

Simple physics.
The higher the frequency, the higher the damping when crossing solid objects.

jaclaz · July 29, 2026, 8:38am

Sure , only I didn't expect such a difference.

In the room adjoining the one where the AP was, across one wall (to be fair fairly thick) I got in Wi-Fi analyzer some -9 dBm difference, around -60 dBm at 5 Ghz, -70 at 6 GHz.
But as said it is the one and only experiment I had the occasion to carry, so it is only anecdata.