Tried the last two snapshot-files ax1800-squashfs-nand-factory.ubi but after reboot GL-inet's 4.10 stable firmware is still there. I must be missing something.
If your using GL-iNets stock firmware you can just use the pin hole reset trick to get into uboot.
Change your Client PC to a static IP such as 192.168.1.66 submask 255.255.255.0 then head to http://192.168.1.1 and flash the factory image from there.
Hi!
I am interested getting the GL-AXT1800 but really want mesh functionality, which the standard firmware does not support. I suppose using the latest openwrt would make it work. I'l keep my eyes on this thread as i do want the original wireguard speed.
Hey I had a question and also I just wanted to say thank you! I was able to OpenWrt on my GL-iNet AX1800 Flint using the ubi image and uboot.
The question I have is about updating, should I change the opkg repo sources?
Right now when I run opkg update it seems to update using the source address (linked in this thread where I got the ubi) and I wasn't sure if I'm supposed to keep it set to that (idk maybe its specific to the device) or change it?
I wanted to ask before changing anything. There is also this error when updating:
Collected errors:
* opkg_download: Failed to download https://flint.solidus1983.duckdns.org/snapshots/r21530/targets/ipq60xx/generic/kmods/5.15.83-1-3f1053257cef558c1091c7eac414bc74/Packages.gz, wget returned 8.
Just wanted to chime in here for the mentioned issues that I managed to solve in my project.
wpad with mesh preinstalled and working @borgqueenx
Repos are updated with full packages support using official OpenWRT repo and kmod repo from official GL.iNet.
USB2/3 working well @hipo
You can use SmoothWAN and ignore the VPN part if needed, I struggled with avoiding conflicts with GL.iNet back-end automation and checks, the image does not include any of that (equivalent to vanilla OpenWRT)
Includes HTTPS Web UI and other additions/fixes if you check the changelog in releases.
Feel free to use stuff from the build for a vanilla solidus1983 !
Tip avoid the new kernel as of this date, it's missing a lot of features such as 802.11s and misconfigured USB power management. Wireguard-backport module in old vs latest kernel shows no performance differences.
Note when using WireGuard or any other VPN, disable speedifyconf, engardeconf, and tinyvpnconf from startup menu, then reboot.
When using custom NTP settings, add service network restart in local startup script since the snapshot is based on older 21.02.X revisions. (common WG issue)
No worries! I'm just happy I'm able to install OpenWrt on this router in the first place.
So I tried running opkg update again and got "wget returned 8" for the kmods package list (all the other lists update without issue).
Running opkg update:
Downloading https://flint.solidus1983.duckdns.org/snapshots/r21530/targets/ipq60xx/generic/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_core
Downloading https://flint.solidus1983.duckdns.org/snapshots/r21530/packages/aarch64_cortex-a53/base/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_base
Downloading https://flint.solidus1983.duckdns.org/snapshots/r21530/targets/ipq60xx/generic/kmods/5.15.83-1-3f1053257cef558c1091c7eac414bc74/Packages.gz
*** Failed to download the package list from https://flint.solidus1983.duckdns.org/snapshots/r21530/targets/ipq60xx/generic/kmods/5.15.83-1-3f1053257cef558c1091c7eac414bc74/Packages.gz
Downloading https://flint.solidus1983.duckdns.org/snapshots/r21530/packages/aarch64_cortex-a53/luci/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_luci
Downloading https://flint.solidus1983.duckdns.org/snapshots/r21530/packages/aarch64_cortex-a53/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_packages
Downloading https://flint.solidus1983.duckdns.org/snapshots/r21530/packages/aarch64_cortex-a53/routing/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_routing
Downloading https://flint.solidus1983.duckdns.org/snapshots/r21530/packages/aarch64_cortex-a53/telephony/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_telephony
Collected errors:
* opkg_download: Failed to download https://flint.solidus1983.duckdns.org/snapshots/r21530/targets/ipq60xx/generic/kmods/5.15.83-1-3f1053257cef558c1091c7eac414bc74/Packages.gz, wget returned 8.
Is it possibly just an issue with my network or network provider? I wasn't sure initially if there was something I was supposed to change or wasn't doing. Either way, I'd be happy to try the new build.
That being said I had something weird happen when I was setting up simple-adblock that I'm not sure about and don't know if whatever happened would carry over. Would this be equivalent to reinstalling? (I just want to know what I would want to backup/save)
[TL/DR: I couldn't swap from iptable to nftables after sysupgrade, dnsmasq stopped working with my vpn afterwards, re-flashing without attempting to swap from iptables to nftables didn't resolve the issue, and I had to get the network back up and running so I rolled back to the previous version.]
So I gave this a shot, I think around 13 hours ago (I tried I swear). The sysupgrade went over just fine no issues. However, there were warnings about iptables and nftables coexisting. I tried replacing iptables with nftables and dnsmasq stopped working shortly afterwards.
Not sure were to go from there, I used the pin-reset trick, flashed it with the previous ubi image, then tried updating without saving settings (I was hoping it would replace iptables during the update). That did not work. Reset it to ubi image, uploaded an archive of my settings, checked keep settings, and flashed the sysupgrade again. That sort of worked (the flashing part), but DHCP didn't.
Fortunately, I managed to convince my pc I knew how to find the gateway and got back in. Unfortunately, the router had dns but my pc still didn't.
So I reset dnsmasq. Argued with rtnetlink some more. Got a dhcp address and still no DNS on my pc. Something about the update prevents me from using a wireguard tunnel on my pc (if I want DNS anyway).
Finally, used the pin reset trick again, flashed the previous ubi image again, and after some odd but short lived issues I had dns again.
Hi, been trying to test your last two (February) builds - thanks...
My GL-iNet AXT-1800 currently has the GL-iNet software on it - the latest beta build (4.2.0 beta3n Date Compiled: 2023-02-14).
I've tried using uboot to load either of the recent Feb builds, but using the .ubi file, all that happens is the GL-iNet software reloads...
I tried loading an old December version of your software via uboot, which loads fine and then I tried loading the new (Feb) versions from the web console (using the .bin sysupgrade file of course) but that failed and the router locked up and I had to reload the GL-iNet software again via uboot.
hi there,
I dont know what i may be doing wrong but I have tried flashing all ubi files through uboot using the recommended procedure however it keeps taking me back to stock glinet. What could I be doing wrong?
Thank you in advance