Flint GL-AX1800 - 2 problems + upgrade on version 4.2.0 snapshot impossible

Hi,

  1. Unlike the SFT-1200, Flint does not have a MAC filtering option in the Luc interface. (firmware 3.214)
    Will it ever be fixed?

  2. The WireGuard server does not work for me on the 1800. I have a public static address without restrictions, disabled DMZ and UPnP.
    I turn on the WG server, configure the clients, but after connecting to 1800, the transfer does not work. (the client does not have access to the Internet)

My IP is fine, port 51820 open - proof:
I have a raspberry pi connected to Flint, a portainer with a wireguard server on it - when I turn it on, it works normally.

Where could be the problem?

Thanks

Pls upgrade to 4.2, which use open source wifi driver.

The two issues should have been resolved.

Thanks.

I will try it.

I will try
beta version

Can not…
I tried beta version - error
I tried snapshot - error

I cannot see what file you tried from the screenshot.

You should use the firmware from GL.iNet download center

Use the .tar file

I used same, from same url
4.2.0 snapshot
tar

You screenshot should at least contains the hash. Maybe you can just refresh the browser and try again.

I refreshed, no change
I also logged out and logged in, nothing
and also with another webbrowser - nothing = same error

I even tried rebooting the router - same result

If you are going from 3.x to 4.x you are supposed to use Uboot and a .IMG file

Don’t forget to update uboot

sorry, I dont know uboot
I need GUI interface

to explain:

i have MT1300, SFT1200 and AX1800
They all have the same GUI + Luci.
Uboot is something unknown to me

Yes an no the Beryl MT1300 uses NOR Flash 32MB and the Opal SFT1200 uses SPI NAND Flash 128MB the Flint AX1800 uses NAND Flash 128MB they are also on different kernels. Anyway the MT1300 and SFT1200 are updated by the GUI but AX1800 Needs uboot and it even states that on the firmware upgrade page.

Also Uboot should be updated

Uboot is simple if you follow the instructions.

1 Like

thanks, I see…I read that already

:frowning:

does this mean that I will buy a new Flint and do not have to update it normally through the GUI or automatically?

Well then I’ll return it, I don’t want to have problems

Just follow the instruction on the video linked in the referenced document above and you will not have any problems.

Ok guys…thanks so much…
I’ll try to do it over the weekend

1 Like

Just to be clear if you are going from 3.x to 4.x Update uboot first with the instructions from the link. You then want to reboot and check that the uboot firmware updated. Once that is done then update with the .IMG file ( I would use the Date Compiled: 2022-11-14 02:57:37 (UTC-05:00)SHA256: 6d3fcfde9f7b49aba32bce540ff698bcefc1849ae6bc8b9fc49682b123af9d56 This is a stable build 4.1.0. do a fresh install (do not keep settings) setup how you want and make a backup in LuCi of the config file and reboot. If you want to load a 4.2.0 beta or snapshot you can now do it from the GUI
Common problems with uboot are:
More then one device is connected to the wired connection of the router
You need to hold the power button/reset button before powering the router.
Use a private browser window when doing Uboot(this prevents cached pages)

1 Like

Ok k3m3l, but
Just to clarify - if I do all this according to the instructions, will I have a normal GUI for administration?
And then what next, if another update is needed?

You should see a different web page with uboot as logo, note that the end of the url must end with uboot like in the documentation because otherwise you are on the restore the firmware page, u-boot is basically your core bios where openwrt boots from.

To add: make sure before you upload anything that the image is 100% u-boot compatible and not just a firmware there might be links in the documentation or here else just ping me with a reply, because updating u-boot is usually not a standard procedure, this can hard brick ur device, so do so only when it has something broken in u-boot known in flint, you should see it as a procedure you only will do once and never hope to do it again.

1 Like

I am also facing some issues / differences on 4.1 and 4.2 beta:

  • when acting as wireguard server, doesnt respond to DNS request from inside WG tunnel. (WG not working when I set DNS = 10.0.0.1 (WG server IP) in the WG client conf. This worked fine in 3.x.
  • cant reach the WG server inside the tunnel via https, although I enabled HTTPS Remote Access (this should be for WAN) and also allowed 443 in Network → Firewall → Open ports on router. Did the same for DNS.
    this also worked fine in 3.x as far as I remember
  • also had some issues when tried downgrading back to 3.x - router crashed - so now I am back on 4.1 (had to use the process explained above)
    maybe I am missing something?

It will be 4.x GL.iNET firmware