Skip to content

Band Selection Guide

BandFrequencyTypical RangeMax Speed (WiFi 6)InterferenceBest For
2.4 GHz2400-2500 MHz50-70m indoor600 MbpsHighLegacy devices, IoT, long range
5 GHz5150-5850 MHz30-40m indoor4.8 GbpsLowHigh throughput, modern devices
6 GHz5925-7125 MHz20-30m indoor9.6 GbpsMinimalUltra-high throughput, dense environments

The 2.4 GHz band remains essential for:

  • IoT and smart home devices - Most IoT devices (smart bulbs, sensors, switches) only support 2.4 GHz
  • Legacy device support - Older smartphones, laptops, and tablets may not support 5 GHz
  • Longer range coverage - Better penetration through walls and obstacles
  • Outdoor deployments - Extended range for yard, patio, or warehouse coverage

Advantages:

  • Longer wavelength penetrates walls and obstacles better
  • Works with more devices (100% WiFi compatibility)
  • Better range, especially outdoors
  • Lower cost hardware
  • Less congestion in most areas (vs 5 GHz in urban areas)

Disadvantages:

  • Limited channels (only 3 non-overlapping)
  • Heavily congested in urban environments
  • Slower maximum speeds
  • More susceptible to interference (microwaves, Bluetooth, cordless phones)

Only three non-overlapping channels exist in 2.4 GHz:

ChannelCenter FrequencyPrimary Use
12412 MHzCoverage area A
62437 MHzCoverage area B
112462 MHzCoverage area C

Critical: Never use channels 2-5 or 7-10 for primary APs. These overlap with channels 1, 6, and 11 and cause more interference than using adjacent channels.

# Legacy wireless package
/interface wireless channel add name=2.4GHz-20MHz band=2ghz-b/g/n frequency=2437 channel-width=20mhz
# WiFi package
/interface wifi channel add name=2.4GHz band=2ghz-b/g/n/ax frequency=2437 channel-width=20mhz

For IoT-heavy networks:

# Separate IoT network
/interface wifi security add name=IoT-Security authentication-types=wpa2-psk passphrase=IoTPass123!
/interface wifi datapath add name=IoT-DP bridge=bridge-iot vlan-id=100
/interface wifi configuration add name=IoT-AP \
ssid=SmartHome \
security=IoT-Security \
datapath=IoT-DP \
country=UnitedStates

IoT Recommendations:

  • Use separate SSID/VLAN for IoT devices
  • Disable 5 GHz on IoT-only networks
  • Use WPA2-PSK (most IoT devices don’t support WPA3)
  • Consider disabling client isolation for device-to-device communication

The 5 GHz band is recommended for:

  • High-throughput applications - 4K streaming, large file transfers, video conferencing
  • Modern devices - Any device from 2015+ typically supports 5 GHz
  • Dense environments - More available channels reduces interference
  • Business networks - Better performance for employee and guest networks

Advantages:

  • Many more non-overlapping channels (25+)
  • Much faster maximum speeds (up to 4.8 Gbps with WiFi 6)
  • Less interference from non-WiFi devices
  • Better performance in dense environments

Disadvantages:

  • Shorter range (reduced by ~30% vs 2.4 GHz)
  • Worse penetration through walls
  • Not supported by some legacy devices
  • DFS restrictions in some regions
UNII BandChannelsFrequencyDFS RequiredMax Power
UNII-136, 40, 44, 485150-5250 MHzNo23 dBm
UNII-252, 56, 60, 645250-5330 MHzYes23 dBm
UNII-2 Extended100-1445470-5720 MHzYes23 dBm
UNII-3149-1655725-5850 MHzNo30 dBm

Non-DFS (No radar avoidance needed):

  • 36 (5180 MHz) - Primary recommendation
  • 40 (5200 MHz)
  • 44 (5220 MHz)
  • 48 (5240 MHz)
  • 149 (5745 MHz)
  • 153 (5765 MHz)
  • 157 (5785 MHz)
  • 161 (5805 MHz)
WidthThroughputInterference RiskBest Environment
20 MHzModerateLowDense, legacy devices
40 MHzHighMediumStandard deployments
80 MHzVery HighHighOpen environments
160 MHzMaximumVery HighClean spectrum available

Recommendation: Use 80 MHz as default for 5 GHz. Reserve 160 MHz for specific high-throughput needs.

# WiFi package - 80 MHz channel
/interface wifi channel add name=5GHz-80MHz \
band=5ghz-a/n/ac/ax \
frequency=5180,5200,5220,5240 \
channel-width=80mhz
# Legacy wireless package
/interface wireless channel add name=5GHz-80MHz \
band=5ghz-a/n/ac \
frequency=5180 \
channel-width=80mhz

DFS channels (52-64, 100-144) can be affected by:

  • Radar detection - Immediate channel switch required
  • 30-minute blocking - After radar detection, channel is blocked for 30 minutes
  • Weather radar - Can trigger DFS on adjacent channels

For reliable 5 GHz operation, prefer non-DFS channels (36-48, 149-165).

For comprehensive information on DFS behavior, deployment strategies, and workarounds, see DFS Channels.

Most deployments should use both 2.4 GHz and 5 GHz on the same SSID for seamless client experience.

# Create single configuration for both bands
/interface wifi configuration add name=DualBand-AP \
ssid=Office-Network \
security=corp-sec \
datapath=corp-dp \
country=UnitedStates
# Apply to both radios
/interface wifi set [find name="wifi1"] configuration=DualBand-AP
/interface wifi set [find name="wifi2"] configuration=DualBand-AP

For specialized deployments:

# High-performance 5 GHz only
/interface wifi configuration add name=5GHz-Performance \
ssid=Office-5G-Only \
security=corp-sec \
channel=5GHz-80MHz
# IoT/legacy 2.4 GHz only
/interface wifi configuration add name=2.4GHz-IoT \
ssid=Office-IoT \
security=IoT-sec \
channel=2.4GHz
Device TypeRecommended BandChannel WidthNotes
Streaming (4K)5 GHz80 MHzHigh throughput needed
Smartphones5 GHz (auto)80 MHzMost modern phones support it
Smart TV5 GHz40-80 MHzWired preferred if possible
IoT Devices2.4 GHz20 MHzLegacy compatibility
Guests5 GHz40 MHzSecurity isolation
ScenarioRecommendation
Open floor plan5 GHz with 80 MHz, APs every 30m
Dense client count5 GHz with 20/40 MHz, more APs
Conference roomsDedicated 5 GHz SSID
IoT/smart buildingSeparate 2.4 GHz SSID + VLAN
Roaming usersEnable band steering
ScenarioRecommendation
Yard/coverage2.4 GHz, lower channels (1/6/11)
Warehouse (line-of-sight)60 GHz (W60G) for fixed links
Outdoor point-to-point5 GHz with 40 MHz, high-gain antennas
Loading dock2.4 GHz for legacy scanners

For apartments, dormitories, or dense office:

  1. Use 5 GHz exclusively - Higher capacity
  2. Reduce channel width - 20 or 40 MHz to reduce interference
  3. Increase AP count - Lower transmit power, more APs
  4. Use lower UNII-1 channels - 36-48 avoid DFS
  5. Implement minimum RSSI - Prevent weak client associations
# Minimum signal strength to accept clients
/interface wifi access-list
add action=accept signal-range=-70..120
add action=reject signal-range=-120..-71

Band steering encourages dual-band clients to use 5 GHz for better performance.

/interface wifi configuration set [find] \
band-steering=yes

Note: Some devices may experience issues with aggressive band steering. Test thoroughly with all device types.

  1. Non-overlapping channels - Ensure APs don’t share channels within coverage overlap
  2. Reduce power - Lower tx-power to reduce co-channel interference:
/interface wifi set [find] tx-power=17
  1. Adjacent channel spacing - Space channels by 4+ channels in 5 GHz
For each AP:
1. Scan environment for existing WiFi
2. Identify least congested non-DFS channels
3. Assign channel with maximum separation from neighbors
4. For 2.4 GHz: Use 1, 6, or 11 only
5. For 5 GHz: Prefer 36, 40, 44, 48 (non-DFS)
Application2.4 GHz Target5 GHz Target
VoIP/Video-60 dBm-65 dBm
Streaming-65 dBm-70 dBm
Web Browsing-70 dBm-75 dBm
Basic Connectivity-80 dBm-80 dBm
  1. Check client capability - Older devices may not support 5 GHz
  2. Verify AP 5 GHz is enabled - Confirm radio is not disabled
  3. Reduce 5 GHz power - If 2.4 GHz signal is much stronger
  4. Enable band steering - Push clients to 5 GHz
  1. Check channel width - Reduce from 160 MHz to 80 MHz
  2. Verify DFS isn’t triggering - Check logs for radar detection
  3. Scan for interference - Other APs may be on same channel
  4. Check AP density - Too many APs can cause self-interference
  1. Confirm 2.4 GHz only - Most IoT devices don’t support 5 GHz
  2. Check security type - IoT often requires WPA2-PSK
  3. Verify SSID visibility - Some IoT devices have issues with hidden SSIDs
  4. Check client isolation - May block device-to-device communication