That's good to know, thanks! Yeah, I'm trying to solve a problem on my Flint 2 with it not letting a VPN connected device (wireguard) connect to an internal web service on the WAN interface's IP address - like I get with NAT loopback from the LAN interface - it keeps trying to connect to the router's https port.
I asked over in the openWRT forums, and got a lot of pushback because it's "not official openWRT" and the current openWRT releases use nftables rather than iptables (which is what the glinet builds use - based on 21.02).
I've asked about the issue in these forums but haven't had an answer, so I thought "well, I'll ask if anyone upstream has any ideas", and wow, do I regret asking for help there. 28 messages back and forth about how "you should just install our firmware" and "it's not really openWRT because they modified the older code to work on the hardware before it was fully supported") I remember that community being a lot friendlier in the past.
Even still, I do like the firmware, and maybe when I have some time, I'll look at moving to the openwrt build. I'll have to set everything up again, which is a shame, because apart from this one little thing, I do really like the GL UI for setting things up easily, and then using luci to set up the things that the stock can't do easily (or at all). Hopefully I won't have to do the same with my Beryl travel router as well, and can just use its built-in wireguard VPN client as-is.
But it does seem that it would benefit gl.inet to be closer to the official builds, possibly to even build their UI on top of the stock firmware so it's got a broader support base.