Firmware 4.2.x is out as snapshot firmware

I have tested with 4.2.0 beta2 of AXT1800 and there is no recurrence of this problem. Do you have any other operations?

Adguard home (running)
Wireguard server (started)
Wireguard client (configured, standby)

I’ll test again (problem repeatable)

Edit: problem happened on ax1800 4.2 beta2, not axt1800

I misunderstood. My tests found that wireguard could connect, but could not access the Internet.
Thanks for your feedback.

2 Likes

I wasn’t specific about the device that has the problem, my mistake

I have fixed this issue in the commit below. This fix will be added to the snapshot firmware automatically tomorrow.

Due to the addition of an src_dev configuration, if you keep the configuration update, you will not see the BUG fixed unless you manually execute the following command

uci add_list parental_control.global.src_dev='br-lan'
uci add_list parental_control.global.src_dev='br-guest'
uci commit
/etc/init.d/parental_control restart
2 Likes

Just installed the latest snapshot (openwrt-mt2500-4.2.0-0105-1672880274.bin) on my new GL-MT2500.

I added 2 WireGuard configurations, and activated the WireGuard second configuration. Then proceeded to load the third WireGuard configuration, but the WireGuard client crashed, and now I see this blue screen. Interestingly, the second WireGuard configuration is still active, and works. But, no configurations are visible when I click the WireGuard Client menu. Please see attached screen print.

I want to know, does Flint’s 4.2.0 Beta 2 Firmware solve the 5Ghz WiFi problem?

I had same problem…

1 Like

I just tried it, going from 4.2 snapshot to 4.1.1 ( I checked the box to retain settings during the dowgrade)

Unfortunately, this did not work and essentially bricked my MT-2500, per attached screenprint.

I now have no access to the Dashboard, or the Luci interface. I do have access via SSH. Any ideas from this point, how to restore from SSH? Or, is there a direct link to the login for 4.1.1 that I can use?

Clear cache on browser or try incognito mode.
When do router upgrade do not save settings and use a fresh installation.
If the problem persista try uboot method to reinstall firmware.

1 Like

Thank you for the tip, I tried to clear the cache, incognito mode, and also used an entirely different browser, but that did not work. So, I reinstalled the firmware…
I hope nobody ever needs this, but here are the instructions to reinstall firmware in case you brick your router:

I was running the latest “Stable” version for the Flint router, version 4.1 or so I thought. Boy was I shocked when I noticed it was removed from stable because of a mistake!!! Now come on folks, this is a major screw up.On top of that, I ended up having a DNS leak using version 4.1. I tried upgrading to 4.2 beta but had to Uboot back to 3.14 stable, the real stable. Your quality assurance needs to get better here. How can someone even consider such products in a professional setting with errors like this.

1 Like

What issues have you experienced with the 4.2 snapshot?

Abysmal speeds compared to the latest 4.1 build.

1 Like

I have just installed today’s release and it seems to be working better than the one from a few days back. Two problems appear to have been resolved with the first being unable to start (connect) VPN client until router reboot and the second being unable to activate VPN cascade without a time out error appearing to have been resolved. Will keep on checking.

I just did a clean install of 4.2.0 Beta2. Seems to have improved the performance some.

Question in regards to the option “Services from GL Inet use VPN”. Should this option be turned OFF by default? I only use my Flint router as a VPN client. I want the most secure box possible and I do not use any of the plugins, extra features etc, just a router and a Wireguard VPN client.

Screenshot from 2023-01-08 18-50-54

Yes this should be default off.

So far so good with 4.2.x, I have however noticed (and this might have been present in earlier releases but I just didn’t notice so forgive me if this the case) that Adguard Home now has a login interface (http://192.168.8.1:3000/login.html) suggesting you can login to Adguard Home directly rather than having to go through the routers admin interface.

This might allow for the use of apps such as Adguard Home Remote for managing Adguard Home however, the routers login doesn’t work and the password reset steps detailed on the projects Github page are for Adguard Home instances users themselves have installed on other hardware so I doubt they’d apply.

Has anyone managed to configure Adguard Home so that you can login to its admin without needing to login to the router first?

How? I don’t have this.

Hmm, that’s a bit strange.

Now I know it’s there I can navigate straight to it without having to go through the routers admin interface first, not that I can login though! this does suggest sadly that its been unintentionally left in the latest snapshot… :slightly_frowning_face: