GL-MT6000 Flint 2 Access Point mode Guest/IoT network not giving IP

[srdjan]

Hi, I’m running Flint 2 in Access Point mode, latest firmware. I could not see Guest/IoT network settings, so I went to “Advanced” (LuCI). Things there look fine to me, I have enabled IoT on one of the WiFi radios. When I try to connect, it says connected, but no IP is given.

1. Any idea why?
2. In general, what would be the way to debug this sort of issues?

Help much appreciated. Thanks.

[charles2]

Hi,

When the Flint 2 is operating in Access Point Mode, NAT and DHCP are disabled, and the device mainly works as a Layer 2 access point/switch. Client IP addresses therefore need to be provided by the upstream router. Simply re-enabling the IoT or Guest SSID in LuCI only enables the wireless interface itself. It does not automatically restore a separate subnet or DHCP service for that network.

If you would like to keep separate IoT and Guest networks while using the Flint 2 as an AP, the upstream router needs to support VLANs and provide the gateway/DHCP service for each VLAN. The Flint 2 can then be configured as a VLAN-aware AP, with the corresponding IoT/Guest Wi-Fi interfaces mapped to their VLANs.

You can refer to the following examples:
Flint 2 + AP Mode + upstream VLAN/DHCP

Flint 2 as "dumb" VLAN (W)AP + OPNsense router

Hi, I recently got a Flint 2 router, and I wanted to put it behind an OPNsense router to use it as a dumb WAP. Furthermore, I wanted to divide my network as follows: Step 1: Wireless access point for trusted devices and all Ethernet ports for trusted devices Step 2: Wireless access point for untrusted devices and one Ethernet port for untrusted devices Since I want my OPNsense router to manage everything, I thought I would need to use VLANs. Step 1 worked, but Step 2 failed. When trying to c…

Multiple SSIDs + VLAN configuration example

Flint 3 (GL-BE9300) as AP behind pfSense: multiple SSIDs -> VLAN + Random BSSID

Hi Well, overall your requirements are feasible. However, the configuration will be quite complex, and it requires you to have sufficient knowledge of networking concepts as well as a solid understanding of LuCI/UCI. Below is a configuration example. Since the steps for Work and IoT are repetitive, only Main / Guest / IoT are used as examples here. Topology is as follows: [image] Configuration steps: Start from a factory-default BE9300 v4.8.3 configuration Configure its WAN port as …

Thank you for your support and understanding.

[srdjan]

Thanks for that. Conceptually I understand how it’s supposed to work, but I could not make any network changes in LuCI. I tried in both AP and Router mode, when going to Advanced Settings (LuCI) → Network, a message is displayed that the configuration is migrated. After that I was not able to save any changes (made some small irrelevant changes), but they were all reverted as per OpenWRT policy when connection is lost.

I’ll wait for 4.10 with updated OpenWRT version.

[charles2]

Hi,

Thank you for the clarification.

What specific prompt appears when you access LuCI? If possible, could you please provide a screenshot.
When you click “Save & Apply,” do the changes fail to apply and then show a 90-second countdown before the configuration is reverted or recovered?

If you prefer to wait and try again after firmware v4.10 is available, that is also fine. If you encounter the same issue or other issue then, please feel free to contact us and we will continue to look into it with you.

Thank you for your understanding and support.