I need to have both 2.4g and 5g working. I have devices that are only 2.4g and some that are obviously faster on 5g.
I have tried to enable both on my OpenWRT One router but I can only seem to get one or the other enabled. It wouldn't seem logical for the team to put out a router with such a limit so I must be doing something wrong?
Can anyone who has got it working offer some advice on the correct config to get both bands working?
Interestingly, even though 2.4g is currently disabled, I can scan and see other devices. When I try to enable the radio, after about 25 seconds the devices returns to the login prompt, as if it rebooted.
As a broad/general statement, yes, OpenWrt works with both bands and can do it concurrently.
But, some hardware doesn't have the capability of concurrent operation (for example, the Raspberry Pi devices) due to limitations in the chipsets (hardware, not firmware/software). Other chipsets are not fully supported and thus 5G may not work, or may work with severe limitations (such as Broadcom).
Meanwhile, let’s see the rest of your configuration.
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
You are using Openwrt.One, of course it support 2.4G and 5G and working at the same time.
Describe more details and show the setup, and maybe screenshots to show how is your setup.
If just telling others is fast, something not working ...
it is difficult to see what's wrong.
Well, it would have been pretty stupid of me to gather a bunch of information until I confirmed that what I wanted was possible, wouldn't it? Now that someone has confirmed what I thought it should be, now I can gather what was requested. That makes more sense, no?
Finally had time to play with the router. Decided to go back to the stock 24.10.1 for testing and still getting the same issue as before. Here's the configs that have been requested.
I'm not going to post my firewall config for world+dog to see, and I don't see why that would have anything to do with the radio issue anyway. At this point I'm wondering if it's a hardware error.
When I try to enable the radio, I get the following in dmesg:
[Sat May 24 09:27:51 2025] br-lan: port 3(phy0-ap0) entered blocking state
[Sat May 24 09:27:51 2025] br-lan: port 3(phy0-ap0) entered disabled state
[Sat May 24 09:27:51 2025] mt798x-wmac 18000000.wifi phy0-ap0: entered allmulticast mode
[Sat May 24 09:27:51 2025] mt798x-wmac 18000000.wifi phy0-ap0: entered promiscuous mode
[Sat May 24 09:27:51 2025] br-lan: port 3(phy0-ap0) entered blocking state
[Sat May 24 09:27:51 2025] br-lan: port 3(phy0-ap0) entered forwarding state
[Sat May 24 09:27:51 2025] br-lan: port 3(phy0-ap0) entered disabled state
[Sat May 24 09:27:52 2025] br-lan: port 3(phy0-ap0) entered blocking state
[Sat May 24 09:27:52 2025] br-lan: port 3(phy0-ap0) entered forwarding state
Then the router reboots.
I'm using firmware OpenWrt 24.10.1 r28597-0425664679
Open to suggestions.
If I change that to 0 then my router just goes into a reboot cycle, effectively bricking it. I had to go into recovery which is how I ended up with the snapshot. It's what I had available.
I click on "Enable" next to "Wireless network is disabled"
root@OpenWrt:/etc/config# logread -f
Sat May 24 10:36:18 2025 daemon.notice netifd: radio0 (4029): WARNING: Variable 'data' does not exist or is not an array/object
Sat May 24 10:36:19 2025 daemon.notice hostapd: Set new config for phy phy0:
Sat May 24 10:36:19 2025 daemon.notice wpa_supplicant[1824]: Set new config for phy phy0
Sat May 24 10:36:19 2025 daemon.notice wpa_supplicant[1824]: Set new config for phy phy0
Sat May 24 10:36:19 2025 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Sat May 24 10:36:19 2025 daemon.notice hostapd: Restart interface for phy phy0
Sat May 24 10:36:19 2025 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=US ieee80211d=1 hw_mode=g supported_rates=60 90 120 180 240 360 480 540 basic_rates=60 120 240 beacon_int=100 stationary_ap=1 chanlist=1 #num_global_macaddr=7 #macaddr_base= ieee80211n=1 ht_coex=0 ht_capab=[LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935] ieee80211ax=1 he_su_beamformer=1 he_su_beamformee=1 he_mu_beamformer=1 he_bss_color=128 he_spr_sr_control=3 he_default_pe_duration=4 he_rts_threshold=1023 he_mu_edca_qos_info_param_count=0 he_mu_edca_qos_info_q_ack=0 he_mu_edca_qos_info_queue_request=0 he_mu_edca_qos_info_txop_request=0 he_mu_edca_ac_be_aifsn=8 he_mu_edca_ac_be_aci=0 he_mu_edca_ac_be_ecwmin=9 he_mu_edca_ac_be_ecwmax=10 he_mu_edca_ac_be_timer=255 he_mu_edca_ac_bk_aifsn=15 he_mu_edca_ac_bk_aci=1 he_mu_edca_ac_bk_ecwmin=9 he_mu_edca_ac_bk_ecwmax=10 he_mu_edca_ac_bk_timer=255 he_mu_edca_ac_vi_ecwmin=5 he_mu_edca_ac_v
Sat May 24 10:36:19 2025 kern.info kernel: [ 586.707000] br-lan: port 3(phy0-ap0) entered blocking state
Sat May 24 10:36:19 2025 kern.info kernel: [ 586.712590] br-lan: port 3(phy0-ap0) entered disabled state
Sat May 24 10:36:19 2025 kern.info kernel: [ 586.718262] mt798x-wmac 18000000.wifi phy0-ap0: entered allmulticast mode
Sat May 24 10:36:19 2025 kern.info kernel: [ 586.725277] mt798x-wmac 18000000.wifi phy0-ap0: entered promiscuous mode
Sat May 24 10:36:19 2025 kern.info kernel: [ 586.732292] br-lan: port 3(phy0-ap0) entered blocking state
Sat May 24 10:36:19 2025 kern.info kernel: [ 586.737888] br-lan: port 3(phy0-ap0) entered forwarding state
Sat May 24 10:36:19 2025 kern.info kernel: [ 586.743908] br-lan: port 3(phy0-ap0) entered disabled state
Sat May 24 10:36:19 2025 daemon.notice hostapd: phy0-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat May 24 10:36:19 2025 kern.info kernel: [ 586.896262] br-lan: port 3(phy0-ap0) entered blocking state
Sat May 24 10:36:19 2025 kern.info kernel: [ 586.901876] br-lan: port 3(phy0-ap0) entered forwarding state
Sat May 24 10:36:19 2025 daemon.notice netifd: Network device 'phy0-ap0' link is up
It then proceeds to reboot.
If I click Restart next to radio0 " MediaTek MT7981 802.11ax/b/g/n" the device remains inactive.
Some other interesting news. My wife said she was trying to watch something on TV last night and it would keep disconnecting from the wifi. I monitored the router and it seems to reboot itself every hour or so. Now that I can't explain. I think it's just going to go back and I'll revert to my old one which, although somewhat slow, actually works. Very disappointed.