Skip to content

WiFi Band Selection Guide

Choosing the right WiFi frequency band is one of the most important design decisions for any wireless network. This guide covers when to use each band and how to configure channel settings for optimal MikroTik deployments.

ScenarioRecommended BandChannel Width
IoT / Smart home devices2.4 GHz20 MHz
Outdoor long-range2.4 GHz20 MHz
General home/office5 GHz80 MHz
High-density office5 GHz40 MHz
Maximum throughput5 GHz / 6 GHz160 MHz
Legacy device support2.4 GHz20 MHz
Characteristic2.4 GHz5 GHz6 GHz (WiFi 6E)
Frequency range2400–2483 MHz5150–5850 MHz5925–7125 MHz
Channel width20 / 40 MHz20 / 40 / 80 / 160 MHz20 / 40 / 80 / 160 MHz
Max data rate (WiFi 6)1147 Mbps2404 Mbps2404 Mbps
Typical indoor range35–50 m15–25 m10–15 m
PenetrationGoodModeratePoor
InterferenceHighModerateLow
Device compatibilityUniversalMost modernNewer devices only

  • IoT and smart home devices — Many devices (Philips Hue, Sonoff, Tuya) only support 2.4 GHz
  • Long-range outdoor coverage — Better wall and obstacle penetration
  • Legacy devices — Older hardware without 5 GHz support
  • Maximum coverage — When wall penetration matters more than speed

Forum users consistently report these 2.4 GHz wins:

  1. Smart home deployments — IoT devices that cannot connect to 5 GHz
  2. Outdoor point-to-point links — Longer reach with better obstacle handling
  3. Basement/garage coverage — Where 5 GHz signal doesn’t reach
  4. Guest networks for unknown devices — Maximum compatibility
# Create 2.4 GHz AP with 20 MHz for stability
/interface wifi channel add name=ch-2ghz band=2ghz-n width=20mhz frequency=2437
/interface wifi security add name=sec-wpa2 authentication-types=wpa2-psk,wpa3-psk \
encryption=ccmp
/interface wifi add channel=ch-2ghz security=sec-wpa2 ssid=Office-2G disabled=no

Verify the configuration:

/interface wifi channel print
/interface wifi print

Warning: Avoid 40 MHz on 2.4 GHz in congested environments. It forces overlap with adjacent channels and increases interference. Stick to 20 MHz for stability.

  • Congestion — Only 3 non-overlapping channels (1, 6, 11 in US)
  • Interference — Bluetooth, microwaves, Zigbee, cordless phones share this band
  • Lower throughput — Maximum 400 Mbps (WiFi 6), typically 100–200 Mbps real-world

  • High-throughput applications — Video streaming, large file transfers, VoIP
  • Primary network — Serve all modern devices
  • Dense environments — More non-overlapping channels available
  • Performance-critical connections — Gaming, video conferencing

5 GHz fails first in these scenarios (from forum observations):

  1. Obstacle-rich environments — Multiple walls, metal objects, concrete
  2. Long distances — Beyond 25 meters indoors, 2.4 GHz often outperforms
  3. Suboptimal antenna placement — 5 GHz requires precise alignment
  4. High humidity — Water absorption affects 5 GHz more than 2.4 GHz
# Create 5 GHz AP with 80 MHz channel width
/interface wifi channel add name=ch-5ghz band=5ghz-ac width=80mhz frequency=5180
/interface wifi security add name=sec-wpa3 authentication-types=wpa3-psk \
encryption=ccmp
/interface wifi add channel=ch-5ghz security=sec-wpa3 ssid=Office-5G disabled=no

Verify the configuration:

/interface wifi channel print
/interface wifi print

Tip: Use lower 5 GHz channels (36, 40, 44, 48) for indoor deployments. Higher channels (149–165) have higher power limits but may experience more interference.

DFS (Dynamic Frequency Selection) is required on many 5 GHz channels to avoid radar interference. Forum users report frequent issues:

Symptoms:

  • 5 GHz connection drops unexpectedly
  • AP switches channels frequently
  • Certain channels become unavailable

Affected channels: 52–144 (varies by region)

Solution: Use non-DFS channels for residential deployments:

  • UNII-1 (5150-5250 MHz): Channels 36, 40, 44, 48 — Indoor only, no DFS
  • These channels avoid radar-related drops entirely
# Check available channels
/interface wifi info
# Use non-DFS channels (UNII-1)
/interface wifi channel add name=ch-5ghz-nodfs band=5ghz-ac width=80mhz frequency=5180

  • Maximum throughput — 4K/8K video, AR/VR, high-speed transfers
  • Ultra-low latency — Gaming, real-time applications
  • Congested environments — 1200 MHz of spectrum reduces contention
  • Future-proofing — As WiFi 6E device adoption increases
  • Limited device support — Only WiFi 6E-capable devices (2022+ flagship devices)
  • Shortest range — Highest frequency with poorest penetration
  • Regulatory complexity — Not all regions approved; some require AFC (Automatic Frequency Planning)
  • Backward incompatibility — Cannot serve legacy clients

RouterOS 7.x supports 6 GHz on select WiFi 6 hardware. Check capability before deployment:

/interface wifi info

WidthThroughputCoverageInterferenceBest For
20 MHzLowHighestLowIoT, long-range, congested
40 MHzMediumMediumMediumBalanced 2.4 GHz
80 MHzHighLowHighModern 5 GHz
160 MHzHighestLowestVery HighMaximum throughput

Forum users report these experiences:

  • Dense neighborhoods: Success with 20 MHz on 2.4 GHz and 40 MHz on 5 GHz
  • Stability issues: Often resolved by reducing from 80 MHz to 40 MHz or 20 MHz
  • Common problems solved by reducing width:
    • Periodic disconnections
    • High latency spikes
    • Neighbor interference
    • Unstable connections to distant clients
# 2.4 GHz: 20 MHz for stability
/interface wifi channel add name=ch-2ghz-20 band=2ghz-n width=20mhz frequency=2437
# 5 GHz: 80 MHz for balance
/interface wifi channel add name=ch-5ghz-80 band=5ghz-ac width=80mhz frequency=5180
# 5 GHz: 160 MHz for maximum throughput in clean environments
/interface wifi channel add name=ch-5ghz-160 band=5ghz-ac width=160mhz frequency=5180

Most deployments benefit from running both 2.4 GHz and 5 GHz simultaneously:

# Dual-band AP configuration
/interface wifi channel add name=ch-2ghz band=2ghz-n width=20mhz frequency=2437
/interface wifi channel add name=ch-5ghz band=5ghz-ac width=80mhz frequency=5180
/interface wifi security add name=sec-wpa3 authentication-types=wpa3-psk \
encryption=ccmp
# 2.4 GHz for IoT and legacy devices
/interface wifi add channel=ch-2ghz security=sec-wpa3 ssid=Office-IoT disabled=no
# 5 GHz for high-performance devices
/interface wifi add channel=ch-5ghz security=sec-wpa3 ssid=Office-Perf disabled=no

Verify both interfaces are active:

/interface wifi print
/interface wifi registration-table print

Enable band steering to push dual-band-capable clients to 5 GHz:

/capsman interface set numbers=0 configuration.sta-steering=band-between-ports

Many users prefer separate SSIDs to control which devices use which band:

  • IoT-SSID (2.4 GHz only) — Smart home devices, sensors
  • Main-SSID (5 GHz preferred) — Phones, laptops, tablets

Use channels 1, 6, and 11 only. These are the only truly non-overlapping channels.

Channel 1: 2412 MHz
Channel 6: 2437 MHz ← Most common choice
Channel 11: 2462 MHz

Warning: Never use adjacent channels (e.g., 3 and 4) — they overlap and cause interference.

WidthChannel Groups
20 MHzAny (36, 40, 44, 48…)
40 MHzPairs (36+40, 44+48, 52+56…)
80 MHzGroups (36+40+44+48)

Use frequency scan to identify least congested channels:

/interface wifi frequency-scan

  1. Enable band steering in configuration
  2. Reduce 2.4 GHz TX power to encourage 5 GHz adoption
  3. Use separate SSIDs with different names
  4. Update client device drivers
  1. Add more APs at lower power (don’t just increase power)
  2. Use 2.4 GHz for edge coverage only
  3. Check for DFS radar events blocking channels
  4. Verify antenna orientation on APs
  5. Consider adding a 5 GHz AP closer to the problem area

Forum users report that switching to 5 GHz resolves high jitter issues, especially in:

  • Warehouse environments
  • Areas with many competing WiFi networks
  • Locations with microwave ovens or other 2.4 GHz interferers


  • MikroTik Forum: Basic home network setup with multiple APs (thread 142248)
  • MikroTik Forum: 802.11r/k/v fast roaming with WifiWave2 (thread 169733)
  • MikroTik Forum: hAP ax3 random wireless disconnects (thread 176477)