My second GL-AX1800 arrived today. I see that the 20% pricing glitch has been corrected meanwhile.
I already bricked and debricked the device 3 times. https://docs.gl-inet.com/router/en/3/tutorials/debrick/ was helpful. On the first time, I simply ran sysupgrade from the command line via SSH. On the second and third time (upgrading from openwrt-ax1800-4.6.8-1017-1729176012.img), I used the web interface, and got the same thing. I was unable to enable any failsafe mode either.
The symptoms that I am seeing is that the LED stays solid blue and the router canât be accessed via any wired Ethernet port. There is no DHCP server responding on the LAN ports nor any DHCP requests being sent to the WAN port. I suspect that something was broken between 9f76070e2de5c28830ede70c31fb81278f1c7183 (May 27) and todayâs snapshot. Iâll try to install an older sysupgrade firmware snapshot.
Edit: I figured out my mistake. My self-built firmware worked, but so did the factory.bin from the firmware-selector as well. In the manufacturerâs web interface for an upgrade from a local image, both factory.bin images were identified as "SNAPSHOT", while the "sysupgrade" image was identified as "unknown".
Yes, I got it working to the extent I needed for now. I followed https://openwrt.org/docs/guide-user/network/wifi/wifiextenders/bridgedap, disabling the DHCP client and server. I made the WAN port part of the LAN bridge, although I could as well have connected the main router via one of the LAN ports. I configured it via SSH, because for some reason, LuCI does not run at all with yesterdayâs snapshot firmware from the firmware-selector.
Curiously, the WiFi of a 2016 laptop achieved about 20 Mb/s according to speedtest.net. With a 5-year-old flagship mobile phone I initially got only 10 Mb/s; on some runs it exceeded 100 Mb/s. The devices were located upstairs 1 to 2 meters from the second router. I used identical WLAN configuration for both routers, which I realize could have caused severe interference. Today I repeated the experiment with only the router in the basement running, and the devices located upstairs. The throughput was similarly bad (but still OK for our general use). Via wired Ethernet through the 2 routers, the performance was as expected, throttled by my ISP to a bit over 200 Mb/s.
I did not experiment with https://openwrt.org/docs/guide-user/network/wifi/roaming yet. I think that for starters, I must use non-overlapping wifi channels. Iâd also like to experiment with VLANs and VLAN specific WiFi SSIDs at some point.
could someone who owns an AX/T/1800 run the Wireguard performance test on it, and post the results in A Wireguard comparison DB ? test setup is described in the 1st post.
I experimented with IEEE 802.11r WiFi roaming this weekend. I was impressed how smoothly it worked. I configured non-overlapping radio channels for both 2.4 GHz and 5 GHz WLAN bands and enabled 802.11r and FT over DS.
I got the best results with a setup where there was a few meters of overlap between the main router in the basement and the second router in a garden shed, which were connected to each other by gigabit Ethernet. The handover would take place near the house door. Initially I had set up the second access point indoors upstairs, but I had trouble forcing any handover, because each router would easily cover the entire house on their own.
With the two laptops that I tested (Lenovo ThinkPad X220 from the early 2010s, and a 2016 laptop with Skylake and Intel 8260), the handover was very smooth, with less than 100ms of delay. I tested this by opening an SSH session from the laptop to one of the routers and executing ping -A 192.168.1.x (the address of the laptop) on it. The SSH session survived during the handover, and the round-trip time reported by ping typically was less than 2 ms, and even during the handover it was less than 100 ms.
On an Android phone, the connection would be interrupted for up to 10 seconds during the handover. A WiFi based Signal voice call was disturbed but not disconnected during the handover. It is possible that I had configured a mismatching mobility domain between the two routers; I did not double check this before tearing down the experiment.
One low-end Android phone from 2016 would fail to authenticate with WiFi as long as 802.11r on the 2.4 GHz interface was enabled.
I've been using WiFi roaming between the GL-iNet AX1800 and a couple of B1300s for a couple of years. The advice I had heard was to use adjacent radio channels as that helps devices to notice a stronger alternative. Modern Android will actively switch to a better network. I also enable usteer and had previously used Dawn. Configuration for usteer is not well documented and I'm not sure how well it works in practice. It's also a good idea to lower the transmit strength of access points as that makes it less likely that they get used from a high distance. I find handover to be much quicker than 10 seconds. I barely notice interruption at all. There are a few other things to enable like 802.11k and replace wpad-basic-mbedtls with wpad-mbedtls.
I've also successfully used VLANs on the AX1800 for a long time. The configuration for that changed when moving to the newer release - after configuring Bridge VLAN Filtering, it is important to change items such as "lan" under interfaces to use br-lan.1 or whatever the appropriate VLAN is instead of just br-lan.
I updated to a fresh snapshot as recently as last Thursday and that's been working fine.
I do not know what I am doing wrong, but I cannot get any of these images to run on my AXT1800.
I had to uboot back to factory firmware. I wanted to see if 5G was any more stable with newer firmware. This thing works fine except it causes havoc for one Chromebook just does not like to connect or stay connected.
I went here: Router Firmware Selector
and tried the factory.ubi and the factory.bin and it would not boot up. I tried DHCP, then static 192.168.1.1, and 192.168.8.1 and was never able to get a web page.
Is there a trick?
I appreciate all the responses. Sorry for the late reply.
I was not so clear on my initial post. I tried all that. Waiting for it to provide a DHCP to my cable connected computer. I tried static addresses just to see what was up.
I tried the factory.bin and the ubi. I do not think it reboots, or if it does, it never advertises as DHCP server. This is is from a single desktop connected to it by a single cord on a lan port.
I set the computer static address as 192.168.1.2 and flash via the uboot debrick method. I can re-flash a factory GLiNET image, but no basic image for clean openwrt. Once the image is flashed, I reset the computer to use dhcp and wait. It never gets an address. No amount of disconnect/reconnect of the eth cable does anything.
If I use the GLiNET interface, can I flash an image there? When I try, it complains that it does not match or something. Which image file should I use if I try this method?
This is an AXT1800 and I grab the AXT imageâŚ
openwrt-qualcommax-ipq60xx-glinet_gl-axt1800-squashfs-factory.bin
What I am trying to âfixâ is that many of the 5G connections take forever to connect or stop or never get a DHCP address when connected to this thing. The 2.4G seems fine, but all that is connected there are IoT things. I have a Flint MT6000 as the main router and have this as a repeater. Not too happy with it, actually, as I have tried devices right next to it and they do not connect on 5G.
In the manufacturerâs web interface for an upgrade from a local image, both factory.bin images were identified as "SNAPSHOT", while the "sysupgrade" image was identified as "unknown".
I simply uploaded an image to the web interface of the stock firmwareâs firmware upgrade function. The "both factory.bin" refers to an image built by myself, or downloaded via the OpenWrt firmware selector.
For upgrading from one OpenWrt snapshot to another, I usually upload the "sysupgrade" image via SSH to /tmp and then execute sysupgrade -c -u followed by the image file name. In this way, the settings would be preserved. The key thing is that the "sysupgrade" works when you already are running OpenWrt, but not when upgrading from the stock firwmare to OpenWrt. You will need the factory.bin format for that.
retrying. I a may be getting somewhere but I am still stumped.I downloaded the âfactoryâ images and get:
If I try to use the stock firmware upload dialog, I get âfirmware is not compatible with the deviceâ. The device shows in the normal firmware as:
Model: GL Technologies, Inc. AXT1800
Architecture: ARMv8 Processor rev 4
OpenWrt Version: OpenWrt 23.05-SNAPSHOT
So, I can get nothing useful when I use the GLiNET firmware upload.
When I go to luci and then upload the âfactory.binâ, I get an error incompatible, but when I try the âsysupgradeâ image:
I get what looks like it is right:
I hit continue and it never comes back. I waited 10 full minutes. Nothing. I have it set to collect a dhcp on a cable just from the computer to the router. It never gets an IP address. Tried turning the interface off then back on, never gets an IP. I am guessing it should get something on 192.168.1.x, but nothing ever shows up.
I know I should not need to, but when I try setting my computer to 192.168.1.20 and the gateway to 192.168.1.1, I cannot ping it this way, either.
I then go back and uboot the GLiNet image and go back to stock. Problem is I cannot connect to it on 5Ghz on it for some reason with stock firmware. That is why I want to flash a bare bones openwrt and see if 5Ghz will work.
I was able to finally make some headway. I used uboot to upload the factory.ubi image. It eventually starts the DHCP and I get an IP address. But when I try to add luci, I get all kinds of errors. Did a bit of googling and learned I needed to disable ipv6 from /etc/config/network to be able to install luci. I now have it set up and going. What a rigamarole.
I've been using numerous AXT1800's on snapshot for many months, regularly reflashing to whatever is the latest snapshot.
I ALWAYS use the uboot Web-Ui and I always use the factory.bin image.
This works every time, from an old snapshot to new or even GL firmware to new snapshot.
I very often use the firmware selector to make a custom image (I am doing package development work and need to do testing).
I have never had any problems of any sort other than the beacon_int bug* that is common to ALL devices using the ath11k driver. I currently have two AXT1800s on my test network.
*FYI: If you change the option beacon_int from the default 100 to anything else, the wireless vifs either fail to come up or are very flaky. This is not unique to the AX(T)1800, it is a bug in ath11k.
Thanks. Well, I was able to bring up the snapshot w/o luci by burning the *.ubi image pretty easily once I understood what was going on. Donât know what the problem was, but uboot puked every time I tried the factory.img. It never came up with dhcp giving out an address. It only worked with the .ubi image. Once I disabled ipv6 on the wan, I was able to install luci and get it all set up. It did solve my problem. At least now I am able to use the 5G radio to extend my network. That was really the only thing I was trying to âfixâ. Thanks to all for the help!
After purchase in 2022, putting it into the box until resurrection for Solidus1983 firmware in 2023 and relying on snapshots until now there finally is 25.12.0-rc1. Big thanks to the devs.
When i have the original GL.Inet (beta 4.8.3, OpenWrt 23.05-SNAPSHOT) running on the GL.Inet AX1800 (Flint).
And i open Not the GL.Inet webinterface, but Luci.
And in Luci i goto -system - flash firmware
And at "Flash new firmware image" i select the downloaded Sysupgrade *.bin file from OpenWRt firmware selector 25.12.0-rc1 (not the snapshot).
Does the GL.Inet AX1800 then upgrade from 23.05 to 25.12 with keeping settings (that are configured on 23.05 with GL.Inet web interface, but backed up with Luci on that GL.Inet 23.05 ?
This because GL.Inet 3.8.4 (23.05 snapshot) beta .tar file is 65.5 MB big, and the OpenWRT 25.12 .bin is 12.6 MB.
So GL.Inet has way more software in it's firmware. I'm afraid that i get a unstable device when i upgrade as described above.
