New firmware version 4.7 being released for beta testing

OpenWRT underlying version is independent of the device. For example. my Marble has OpenWRT 19.07, but firmware version is 4.5. OpenWRT version depends of the chipset manufacturer mostly. I don't know if my Marble's OpenWRT will be updated with 4.7. But, whatever OpenWRT version has underlying, I only want that it performs well.

The version of OpenWRT you link is the fully open version. GL.Inet firmware is based on OpenWRT, but versions of it varies by device. But features are the same on all devices except when advertised.

I meant a new GL build for Flint 2 with APK support
https://openwrt.github.io/firmware-selector-openwrt-org/?version=24.10.0-rc2&target=mediatek%2Ffilogic&id=glinet_gl-mt6000

2 Likes

Oh, sorry. I thought that it was for all GL.Inet devices. Don't worry :slight_smile:

I've been holding off on upgrading from 23.05 to 24.10. Hoping we can get an updated beta once the 24.10 is stable from Openwrt.

Yes, it is.

2 Likes

"[psg] (Profile - psg - GL.iNet)

14h

Yes, but as soon as you config to WAN it starts expecting its own dhcp server running & router to be in place as the WAN interface wont run on the sane subnet as the LAN....
I WANT a flat network, ONE dhcp server....
Everything running LAN, NO WAN to be seen..."

Request from customer requesting above. Had similar issues getting bridge router working with flint 2 found a work around but not a great one.

but APK support has been moved back to SNAPSHOT?

When's the Brume 2 op24 version being released?

2 Likes

Just an FYI - Tried to update Beryl AX last night to the 12/4/2024 RC that was posted, using the router "Upgrade" option and that failed repeatedly. Eventually just downloaded the release manually from the firmware download page and did a local update, which worked.

2 Likes

I have the same issue (Flint 2). Local upgrade worked.
Tom

2 Likes

Same thing here. For USA I can see only 20 servers only from Seattle, for Canada also 20 from West Coast: Vancouver.
First I thought that it might be related to the time zone, but it's correct (EST).
Any suggestions? Firmware was installed without keeping the previous settings.

Hi,
I have an issue with this firmware.
On VPN Dashboard if I Modify Proxy Mode -> VPN Policy Based on the VLAN and select Private Enable VPN and Guest Disable VPN. Then on VPN Dashboard -> Global Options I Block Non-VPN Traffic then all the traffic from Guest network will be blocked.
I think here this option should be available based on which VLAN the VPN is Enabled.
If I enable VPN for Private VLAN then Block Non-VPN Traffic just for Private VLAN and not for both Guest and Private.

Or maybe add 2 switches for Block Non-VPN Traffic ? one for Private and one for Guest?

Or anyone know how can I sort it out?
Thanks

2 Likes

I gave up trying. I was doing NordVPN just as a trial so I was able to cancel

1 Like

I don't understand this to. I buy a new Flint v2 and its use same old v21. Spend money for old like sh... of dinosaurs fw. Even official owrt package support of opkg drop it under year ago for update, and even many enthusiasts is droped for this old fw.

The issue is that the router chipset manufacturers (Qualcomm, Mediatek, Siflower...) use a specific version of openWRT that they customize to get the most out of their network systems. Mediatek has used openWRT 21 on the Flint 2 chipset, and Qualcomm has used openWRT 19 on the Marble chipset, as two examples.

I tested op23.05.5 on Mango this week and seemed to have better results than stock gl.iNet FW.. at least in AP mode.

1 Like

Guys, just wanted to say that NordVPN wireguard not only works on the latest beta (2024-12-05) on my Beryl AX but also I copy-pasted that config, saved to a txt file and uploaded to the GL-MT300N-v2 Mango I have. I am now successfully connected via NordVPN wireguard on Mango! Can't wait for Mango to receive this update!

1 Like

Could you please do me a favour and check if for US and Canada you see any other servers in NordVPN wireguard, other than 20 from Seattle and 20 from Vancouver?
It seems that both @RichieC and me are facing this issue.
TIA.

Just checked, unfortunately still the case - only Seattle and Vancouver shown.

If you did your homework you would know, that there is an active development with OpenWrt 24.0. Instead, you have nothing better to do than trolling through this forum with false accusations. :man_facepalming:

1 Like

we also find this issue and resolve it now, please use latest version.

1 Like