WiFi and subnet configuration help - MT6000 Flint2

[Mr_Inc]

Hi,

I had posted in this thread but I think I may be hijacking the OP's thread (although he never received a reply).

To simplify my requirement, I need to achieve one of three things which I have been unable to achieve either in the GL GUI or the Luci GUI. Any one of the requirements will help me, but I cannot figure how to achieve any one of the three.

1. If I were to use the default '2.4Ghz Guest WiFi' in the GL GUI to attach my IOT devices to, how do I change the subnet on this SSID given that it shares the same subnet configuration with the 5Ghz Wifi Guest network through the 'GUEST' interface on radios ra1 and rax1 (see image below, which also shows the 'br-guest' association. This 'bridge' does not appear on the Luci Network - Interfaces- Devices tab.)
   

   

2. If I were to use the default '2.4Ghz WiFi' in the GL GUI to attach my IOT devices to, how do I change the subnet on this SSID because it currently shares the same subnet from from the 'LAN' interface which uses the 'br-LAN bridge' device for both the 2.4Ghz and 5Ghz as does the main LAN subnet (default 192.168.0.0/24 but which I have change to 192.168.10.1 for the router and 192.168.50.1 for the GUEST interface) See below.
   

   
   
   
   
   
   
   
   
   Note: that although the LAN interface shows the br-lan in the Device field, the GUEST interface shows unspecified as the device with no radio references at all.

3. Create a brand new SSID for 2.4Ghz Wifi with a new IOT subnet (192.168.30.0/24) with access to WAN only - and I am quite OK with disabling the standard 2.4GHz wifi which is delivered OOTB linked to the the LAN interface.

As I wrote earlier, detailed instructions how to achieve just one of the above will be greatly appreciated!
Thanks.

[bruce]

1. GL GUI -> Network -> Guest network, here can change the subnet IP. The 'br-guest' is hard code.
   

   

2. It's not sense and cannot feasible, unless manually custom add a route rule.

3. Add a new SSID for IoT WiFi for MT6000, on the SSH:

# /etc/config/network
uci add network device # =cfg1b0f15
uci set network.@device[-1].type='bridge'
uci set network.@device[-1].name='br-iot'
uci set network.iot=interface
uci set network.iot.proto='static'
uci set network.iot.device='br-iot'
uci set network.iot.ipaddr='192.168.11.1'
uci set network.iot.netmask='255.255.255.0'

# /etc/config/dhcp
uci set dhcp.iot=dhcp
uci set dhcp.iot.interface='iot'
uci set dhcp.iot.start='100'
uci set dhcp.iot.limit='150'
uci set dhcp.iot.leasetime='12h'
uci add_list dhcp.iot.ra_flags='none'

# /etc/config/firewall
uci add firewall zone # =cfg26dc81
uci set firewall.@zone[-1].name='iot'
uci set firewall.@zone[-1].input='ACCEPT'
uci set firewall.@zone[-1].output='ACCEPT'
uci set firewall.@zone[-1].forward='REJECT'
uci add_list firewall.@zone[-1].network='iot'
uci add firewall forwarding # =cfg27ad58
uci set firewall.@forwarding[-1].src='iot'
uci set firewall.@forwarding[-1].dest='wan'



# /etc/config/wireless
uci del wireless.mt798612.disabled
uci set wireless.wifinet4=wifi-iface
uci set wireless.wifinet4.device='mt798612'
uci set wireless.wifinet4.mode='ap'
uci set wireless.wifinet4.ssid='GL Router-IoT-5G'
uci set wireless.wifinet4.encryption='psk2'
uci set wireless.wifinet4.key='goodlife'
uci set wireless.wifinet4.network='iot'
uci set wireless.wifinet4.ifname='rax2'
uci del wireless.mt798611.disabled
uci set wireless.wifinet5=wifi-iface
uci set wireless.wifinet5.device='mt798611'
uci set wireless.wifinet5.mode='ap'
uci set wireless.wifinet5.ssid='GL Router-IoT-2.4G'
uci set wireless.wifinet5.encryption='psk2'
uci set wireless.wifinet5.key='goodlife'
uci set wireless.wifinet5.network='iot'
uci set wireless.wifinet5.ifname='ra2'

uci commit



reboot

[Mr_Inc]

Thanks Bruce.

1. I do understand how to change the 'Guest' subnet, but I asked about the 2.4 Ghz SSID only. Not the 5Ghz. This is what I had in mind.
   
   

If this were possible, I could just put my IOT devices on the 2.4Ghz Guest SSID.
However, I think your answer to my #2 item would suggest the above is also impossible to achieve.

2. I also concluded the same when I could not associate a new bridge with the WiFi.

3. Although it is a pity that to add a new WiFi SSID one has to revert to CLI to achieve that, it nonetheless does show how flexible the router can be given the strength of the underlying OS in OpenWRT. I will give your suggestion a try to see if it works for me!

Thanks for the prompt reply. I appreciate it.

[Mr_Inc]

Hi @bruce

Wow, that worked really really well! Thank you! Would you suggest I save those CLI commands to a .sh file to execute should a future upgrade affect these?

At the risk of sounding ungrateful, is there a way to change the WiFi names on the Tabs in the GUI (say to include IOT or similar)?

Thanks. Again.

EDIT.
How difficult would it be to ensure the Internet page shows the 6 WiFi stations as reference? It's showing the three x 5G but only the one x 2.4G.

[bruce]

Because these are the custom-added WiFi radio, some icon elements of the GL GUI are not yet fully supported.

Later, the GL firmware will support 3 WiFi radios by default.

Now you can change anything, SSID, password, etc. But recommended config them in the Luci, Network -> Interface 'br-iot' and Network -> Wireless 'GL Router-IoT-xG'

It will reserve there unless you reset the firmware. Yes, if you reset the firmware, all configurations will be restored to factory settings, so you just need to re-add it.

[eb3f73]

@bruce, your prior post no longer works for me. After running your commands and restarting networking, logread -f produces frequent and endless messages like the following:

Sat Jan 11 14:10:42 2025 kern.err kernel: [ 8551.997654] 7986@C13L1,MlmeEnqueueForRecv() 6180: orig_wdev(band/channel)=(1/36),msg_recv_wdev(band/channel)=(0/6)
Sat Jan 11 14:10:42 2025 kern.err kernel: [ 8552.015942] 7986@C13L1,MlmeEnqueueForRecv() 6180: orig_wdev(band/channel)=(1/36),msg_recv_wdev(band/channel)=(0/6)
Sat Jan 11 14:10:42 2025 kern.err kernel: [ 8552.064489] 7986@C13L1,MlmeEnqueueForRecv() 6180: orig_wdev(band/channel)=(1/36),msg_recv_wdev(band/channel)=(0/6)
Sat Jan 11 14:10:42 2025 kern.err kernel: [ 8552.077669] 7986@C13L1,MlmeEnqueueForRecv() 6180: orig_wdev(band/channel)=(1/36),msg_recv_wdev(band/channel)=(0/6)
Sat Jan 11 14:10:42 2025 kern.err kernel: [ 8552.121248] 7986@C13L1,MlmeEnqueueForRecv() 6180: orig_wdev(band/channel)=(1/36),msg_recv_wdev(band/channel)=(0/6)
Sat Jan 11 14:10:42 2025 kern.err kernel: [ 8552.175038] 7986@C13L1,MlmeEnqueueForRecv() 6180: orig_wdev(band/channel)=(1/36),msg_recv_wdev(band/channel)=(0/6)

Is there an update? This is really frustrating. I'm regretting investing in any GL-iNet products at this point (one MT6000, one AXT1800, and one A1300). Despite your products being OpenWRT-based, I can't get them to work with anything I need (VLANs, multiple WiFis, etc.) that OpenWRT supports on my other routers (Asus, Linksys, etc.).

[kinga77]

Hi @bruce I'm interested in your solution proposed (point 3: add configuration via ssh), but it seem to be very frustrating...
After, in the another post you say: "Later, the GL firmware will support 3 WiFi radios by default."...
When this firmware will be delivered?
I think it is very useful to manage more than one WiFi ssid from GUI. Any ETA?

Thank You!