WPA-EAP in GL.iNet Flint 3

Hardware Questions and Recommendations
1

Hello, not sure if this is the right place to ask.

I am trying to set up WPA-EAP (Enterprise) authentication using an existing RADIUS server on my GL.iNet Flint 3 router.

Given the Flint 3's default GUI does not support this feature, I am configuring it directly through the underlying OpenWrt LuCI interface.

Here's what I've tried:

  1. WPA3-EAP: The configuration reverts to default authentication settings immediately after saving in LuCI.
  2. WPA-EAP: The settings save correctly, but the new Wi-Fi interface remains disabled/inactive. Even after editing the /etc/config/wireless file via SSH to explicitly set option disabled '0', the interface will not activate.

Questions:

  1. Is WPA-EAP/RADIUS configuration truly functional and supported on the Flint 3, even when configured through OpenWrt LuCI and not the GL.iNet GUI?
  2. If WPA-EAP is not directly supported, are there any known workarounds or modifications I can apply to make it work?

Thanks

2

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

  1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
  2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
  3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

3

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.