Flint 4 BE-14000 Discussion Thread

Thanks for posting this, it’s very useful.

I’m not miles apart from your use case so, I wonder if the risk of going to the V4.11 beta is low for me. I use a 1Gb/s SFP module to connect to my broadband service. The router has WiFi disabled, I use AdGuard Home and Tailscale and that’s about it, other than reserving IP addresses for all my networked devices and IPv6.

I don’t want to start from scratch on the config so, I’d want to perform an upgrade, and maintain settings. How much of a risk that presents is anyone’s guess I’d expect.

Because you use Tailscale and want to preserve the existing configuration, I would not consider the 4.11 beta a low-risk upgrade. The beta thread already documents a Tailscale/IP Masquerade firewall-ordering issue, as well as configuration-preservation problems in some setups.

If rebuilding the configuration is unacceptable, remain on stable 4.9.2 for now. If you choose to test the beta, first export a LuCI backup, record critical settings separately, download the stable recovery firmware, and be prepared to factory-reset and configure manually—restoring an older backup onto a substantially different firmware branch may reintroduce incompatible settings.

This reply was generated by AI. Please verify its accuracy.

GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.

I am loving the the FLINT 4 and MESH (F4 as well). Now is the time to try and break things... lol..

I have docker and a container on the node already which is working well, and now I want to expand the containers but am becoming limited by my uneducated SSH commands and knowledge etc.

I would like to add the Jason Cox Powerwall-Dashboard and need some assistance please.
This is the link to what I am trying to do:-

All is good, I have installed Git and Git-HTTP from Plug-ins and then I have SSH'd into the NODE ok and then I run the install command (sorry I am a monkey see, monkey do person) :-

git clone https://github.com/jasonacox/Powerwall-Dashboard.git

And this seemed to install OK.

The next step is I need to setup a few parameters and I enter this command:-

cd Powerwall-Dashboard

That works and I CD to the Directory and with the LS command I can see all the files in that directory - so far so good and then I need to run the setup with the command

./setup.sh

And here is my problem that I do not know how to resolve.....

After running the setup I get this message:-

Powerwall Dashboard (v5.3.0) - SETUP

ERROR: Running this as root will cause permission issues.

Please ensure your local user is in the docker group and run without sudo.
sudo usermod -aG docker $USER
./setup.sh

root@FLINT_4_Node:~/Powerwall-Dashboard#

And here endeth my install and my knowledge on the next step to get this setup working.

It seems I need to login to the F4 node as a user - can I get some guidance on how to do this or how to continue with the setup.

I do have the same script (?) / install running on a RasPI 5 docker container but as I have the u-beaut Flint 4 I would like to use it to the max and remove the Pi 5 / docker from the network.

Thanks :grin:

The installer is stopping intentionally because Flint 4’s normal SSH session runs as root, while setup.sh requires a conventional non-root Linux user with access to Docker. Do not bypass the check or run the displayed sudo usermod command yet—OpenWrt may not provide sudo/usermod, and its user and Docker-socket setup differs from the Linux distributions targeted by this project.

Please run these non-destructive checks on the node and share only their output:

grep '^docker:' /etc/group
ls -ln /var/run/docker.sock
command -v adduser
command -v usermod
docker compose version

They will show whether this firmware has the necessary user-management tools, Docker group/socket permissions, and Compose support. That determines whether a non-root account can be configured safely or whether the project’s documented manual-install method—or continuing to host it on the Raspberry Pi—is the practical option. Powerwall-Dashboard is a third-party project and this installation on Flint 4 is not officially supported by GL.iNet; any guidance is best-effort, and GL.iNet Technical Support may not be able to troubleshoot or maintain it. Do not post Tesla credentials or tokens.

This reply was generated by AI. Please verify its accuracy.

GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.

As much as I do not like having to interact with an AI bot, below is the result of the no-destructive tests:-

root@FLINT_4_Node:~# grep '^docker:' /etc/group
docker:x:32769:docker,root
root@FLINT_4_Node:~# ls -ln /var/run/docker.sock
srw-rw---- 1 0 32769 0 Sep 27 11:55 /var/run/docker.sock
root@FLINT_4_Node:~# command -v adduser
/usr/sbin/adduser
root@FLINT_4_Node:~# command -v usermod
/usr/sbin/usermod
root@FLINT_4_Node:~# docker compose version
Docker Compose version v5.1.4

I’m trying to update my Flint 4 to 4.11.0 beta 3; I currently have 4.11.0 beta 1 installed.
The process seems to be going smoothly, but once the router restarts, beta 1 is still installed.
Has anyone else had the same problem?

First verify the complete firmware version and build date under System → Upgrade; the “beta1” label alone may not reliably distinguish builds. If both are unchanged, please state whether you used Online Upgrade or uploaded a local file, and provide the exact firmware filename (but do not upload the firmware itself). This will distinguish an incorrect image/channel from an upgrade or boot failure.

Before retrying, confirm that the image is specifically for GL-BE14000 and compare its SHA-256 checksum with the download-page value if one is provided. Back up the configuration first, but do not factory-reset yet. Since beta firmware may contain upgrade and configuration-migration issues, avoid repeatedly flashing until the image and method are confirmed.

This reply was generated by AI. Please verify its accuracy.

GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.

I had the same issue.

In the end, I decided to flash the new firmware via U-Boot and reconfigure everything.

You will loose your data this way.

I had the same problem, I had to try three or four times before the upgrade worked (the last time I shut down Adguard home and DPI, then made a restart before upgrading), I also had a problem with the Flint 4’s password after upgrade, it was gone, and I could not login to the portal without a password, but loggin in with SSH worked, and as soon as i had logged in with SSH the Flint 4 told me how to set a password.

:slight_smile: / Hans

I tried it as you described: I turned off AdGuard, disabled network quality, and DPI isn’t active, but I haven’t sorted it out yet...
To be honest, I can’t be bothered to go through the whole configuration process again...

If reconfiguring from scratch is not acceptable, do not use U-Boot recovery or factory-reset the router merely to install beta 3. Since the normal upgrade is not applying, remain on beta 1 for now and avoid repeated flashing until GL.iNet staff confirm whether this beta image has an upgrade-path issue or provide a corrected build.

Keep a current configuration backup, but note that restoring a backup across beta builds may also restore incompatible settings.

This reply was generated by AI. Please verify its accuracy.

GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.

Nope I updated mine OK and is showing beta 3.

It worked OK first time on both the main and NODE routers - AdGuard was still enabled at the time of upgrade.

Could I ask those that are using v4.11 beta 3 what issues you’re seeing?

I’ve read the main v4.11 beta thread and I only came across a single issue reported on the Flint 4, I believe.

Even here, other than the process of upgrading being a little flakey, I don’t see any real issues reported?!

There is not yet enough Flint 4 beta 3 feedback to treat the absence of reports as evidence that it is issue-free. In the reports available so far, the main Flint 4-specific problem is the unreliable upgrade from beta 1 to beta 3; one user also reported losing the Admin Panel password after upgrading. Other users completed the upgrade successfully. The Hardware Flow Offloading crash reported elsewhere was on beta 1, so it should not be assumed to affect beta 3 without a new test.

Anyone reporting beta 3 results should include the complete build date and test the features relevant to their setup—especially Mesh stability, VPN throughput, Network Acceleration, AdGuard Home, DPI/Network Quality, IPv6, Docker, and configuration retention. Current reports can be followed in the SDK v4.11 beta thread.

This reply was generated by AI. Please verify its accuracy.

GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.

I have 2x different copper SFPs that do not work in 4.11.0 beta 1 or 4.11.0 beta 3.

The same SFPs work fine in 4.9.1 and 4.9.2.

The SFP devices are reported in the dmesg log the exact same as in 4.9.x but in 4.11.0 builds the gl-inet web ui always say they are not inserted.

Beyond that I had attempted to upgrade 4.9.1 to 4.11.0 beta 1 with keep settings which failed. After upload the router did not reboot, the gl-inet web ui became inaccessible the Luci web ui remain available. On router reboot 4.9.1 remained and was again fully functional.

The upgrade succeeded, excluding the above sfp issue, when I selected to not keep settings.

I haven't noticed other issues with either 4.11.0 beta yet.

Because both modules work on 4.9.1/4.9.2 but fail after a clean 4.11 installation, retained configuration is unlikely to explain the SFP issue. This is strong evidence of a 4.11 beta regression, although it is not yet clear whether the failure is limited to the GL.iNet interface/status service or also affects the underlying link setup.

Please provide the exact manufacturer/model and supported speeds of both modules, the complete beta 3 build date, and a short redacted dmesg excerpt covering module insertion. These details will show whether modules on the Flint 4 compatibility list are affected and give staff a focused reproduction case. Your failed “keep settings” upgrade also matches the upgrade-path problem reported by other users.

This reply was generated by AI. Please verify its accuracy.

GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.

Here is the dmesg when the SFP is inserted:

root@GL-BE14000:~# dmesg -c > /dev/null
root@GL-BE14000:~# dmesg
[ 1003.895622] sfp sfp: SM: enter empty:detached:down event tx_clear
[ 1003.901734] sfp sfp: SM: exit empty:detached:down
[ 1003.906651] sfp sfp: SM: enter empty:detached:down event insert
[ 1003.912597] sfp sfp: SM: exit probe:detached:down
[ 1003.917313] sfp sfp: SM: enter probe:detached:down event los_low
[ 1003.923336] sfp sfp: SM: exit probe:detached:down
[ 1004.232013] sfp sfp: SM: enter probe:detached:down event timeout
[ 1004.274032] sfp sfp: module CISCO-METHODE SP7041-TEB rev A1 sn MTC29XXXXXX dc 25040401
[ 1004.283403] yt92xx: SFP notify br_nominal=13 ext=0x01 dac=0 copper=1 -> speed=2
[ 1004.329597] yt92xx: P4 SFP apply 1G/2.5G-autoneg path (copper SGMII)
[ 1004.374641] yt92xx: P4 SFP apply 1G/2.5G-autoneg path (copper SGMII)
[ 1004.381000] sfp sfp: SM: exit waitdev:detached:down

This log confirms that beta 3 reads the module EEPROM and identifies it as a copper SGMII module, then selects the 1G/2.5G autonegotiation path. However, the SFP state remains waitdev:detached:down, so this is not merely an incorrect Admin Panel status—the module is detected, but the firmware does not attach it to the network device/link path.

Please share the output of these commands, along with the second module’s exact model:

ubus call system board
ip -d link show

This will identify the precise beta 3 build and whether the expected SFP network interface exists. Please also edit or redact the module serial number (sn ...) from the public log if possible.

This reply was generated by AI. Please verify its accuracy.

GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.

4.9.2 dmesg is similar “waitdev:detached:down” but is fully functional. Dmesg output from 4.9.2 on SFP insertion:

[ 261.644539] sfp sfp@0: SM: enter empty:detached:down event insert
[ 261.650641] sfp sfp@0: SM: exit probe:detached:down
[ 261.655518] sfp sfp@0: SM: enter probe:detached:down event tx_clear
[ 261.661810] sfp sfp@0: SM: exit probe:detached:down
[ 261.666731] sfp sfp@0: SM: enter probe:detached:down event los_low
[ 261.672919] sfp sfp@0: SM: exit probe:detached:down
[ 261.955277] sfp sfp@0: SM: enter probe:detached:down event timeout
[ 261.997158] sfp sfp@0: module CISCO-METHODE SP7041-TEB rev A1 sn MTC291XXXXXX dc 25040401
[ 262.006651] yt92xx: SFP notify br_nominal=13 ext=0x01 dac=0 -> speed=2
[ 262.092344] yt92xx: P4 SFP apply 1G/2.5G-autoneg path
[ 262.176598] yt92xx: P4 SFP apply 1G/2.5G-autoneg path
[ 262.181646] sfp sfp@0: SM: exit waitdev:detached:down

ubus call system board output as requested:

root@GL-BE14000:~# ubus call system board
{
"kernel": "6.12.94",
"hostname": "GL-BE14000",
"system": "ARMv8 Processor rev 0",
"model": "GL.iNet GL-BE14000",
"board_name": "glinet,gl-be14000",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "25.12-SNAPSHOT",
"firmware_url": "https://downloads.openwrt.org/",
"revision": "r32295+912-c25265953b",
"target": "mediatek/filogic",
"description": "OpenWrt 25.12-SNAPSHOT r32295+912-c25265953b",
"builddate": "1790748850"
}
}
root@GL-BE14000:~#

ip -d link show output is long and includes numerous bits of sensitive information I do not wish to attempt to clean and post to a public forum.

The 4.9.2 comparison corrects the earlier interpretation: waitdev:detached:down is not sufficient evidence that the module failed to attach, because the working firmware reaches the same SFP state. The meaningful evidence is that the same module works on 4.9.2 but not after clean installations of 4.11 beta 1 and beta 3. The ubus output identifies beta 3’s OpenWrt base as 25.12-SNAPSHOT with kernel 6.12.94.

There is no need to post the full ip -d link show output publicly. For a focused reproduction report, please provide only the complete GL.iNet firmware version/build shown under System → Upgrade and the exact model of the second module. Any full interface output can instead be sent privately to a GL.iNet technical support member.

This reply was generated by AI. Please verify its accuracy.

GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.