GL-AXT1800; possible hardware fault with recent order (GL29575)

I ordered a pair of GL-AXT1800 along with an GL-M2 (Development Board). I've posted about the M2 separately.

Since receiving them (circa 2024-09-17), despite much trial+error to figure out what might be wrong with relevant configuration (all sans InterWeb access), I've been unable to achieve any functionality with the 2.4GHz 802.11 radio.

I followed the included setup instructions. The unit hasn't (at least while it's been in my possession) been dropped or otherwise mistreated.

I even tried performing a clean (discarding all configuration) firmware upgrade (to v4.6.4), but this yielded the same (null) results.

I changed the relevant (UCI) configuration to specify my country-code (JE), both before firmware-upgrade and after (but did briefly test post-upgrade before changing any configuration).

The other of the pair of AXT1800 which I ordered, having tested it thoroughly for comparison, appears to function as expected, even straight out of the box, and still after changing the radios' country-code to match my location. It's only the first unit which is troublesome.

The pair of GL-MT3000 which I've ordered previously, have also been trouble-free, and do not exhibit this problem; it's only with this one AXT1800.

Thus, I'm suspecting some kind of hardware fault, at this point. If this turns out to be the case, I'd like to return the faulty items for fully-functional replacements.
However, part of why I'm posting publicly is because I'm willing to (within reason) run whatever tests folks here might suggest, to at least accurately diagnose the problem.

Other possibly relevant context which I can think of: the 5GHz radio on the unit in question functions as expected.
The 2.4GHz radio was tested in multiple modes (master, client/station), and never yielded anything useful; even when another transceiver was placed very close to the unit's antennas (to test if it was some kind of extreme attenuation problem). In either case, the other transceiver couldn't detect 802.11 beacons when the AXT1800's 2.4GHz radio was in master-mode, and the AXT1800 couldn't detect any 802.11 beacons (of other transceivers, when they were in master-mode, even when their antennas were very close) when the AXT1800 was in client/station mode.
All the while, the 5GHz radio functioned as expected (both transmitting and detecting beacons).

While I'm new to GLĀ·iNet's products (and somewhat OpenWrt), and mobile/cellular networking, I'm not new to general system administration (though, have limited experience with OpenWrt & BusyBox) or (non-cellular) networking.

Complications: I have very sporadic InterWeb access (scrounging a connection, very temporarily, at the moment), and thus I'll only be able to respond every couple of weeks (less over the December holidays, of course).
I'd appreciate if moderators/admins could permit this thread to remain open (as opposed to auto-closed due to inactivity) as a result.

For those who have read this far, I appreciate your attention; thankyou.
Suggestions of what else to try, most welcome. I'll respond when I'm able to.

  1. please upgrade to the latest firmware v4.6.8 for the AXT1800, and without 'keep settings'.

    GL.iNet download center
  2. SSH to the router, and execute this command:
    iwinfo
    ubus call network.wireless status
  3. PM me the syslog.
1 Like

FYI: I am working on this. Apologies for the delay; life distracts me with other complications.

Plan: Given what was suggested in the related thread about the GL-M2, I intend to perform a firmware update/upgrade cleanly, without preserving configuration. That, then, will provide a recent-version, without any configuration changes (or non-stock opkg packages) to test against.

I'll report back with the results, in due time. Bear with me.

Please take your time to do the compare test and also many thanks for your tests.

If the first AXT1800 still occurs the same issue in v4.6.8 (flash the firmware v4.6.8 in uboot), please contact [email protected], cite this thread and offer the purchase order number.

Thankyou, @bruce.

As mentioned in the other thread, I've been dealing with a medical crisis, and some other matters. My apologies for such a long delay. I haven't forgotten about this thread, though.

I'm hoping that, by November, I'll have more time to work on this properly, and post some test-results. I've set reminders, on both threads, to nag me to get it done.

Thankyou for your patience, and continued good support/service.

I noticed that firmware v4.8 has been released, which I'll install (cleanly), and re-test. I'll report the results.

Ah, must it be using Uboot, specifically? Not the HTTP-UI?
Please confirm.

So far, I've been using the ā€œonline upgradeā€ facility within the standard/regular HTTP-UI.

I thought that Uboot was only for disaster-recovery, when the system won't boot normally.

I'm inclined to try using the (safer) normal upgrade process first. If the results are still the same, then (riskier) Uboot could be tried in future.

Thankyou. I appreciate that a return would be accepted, despite the amount of time since purchase :+1::100:. This, too, encourages me to be a repeat-customer in future, to request a replacement (not a refund), and to recommend GLĀ·iNet to others (I know several tech-savvy people who travel often).

First, I'll upgrade the firmware and run the commands (eg iwinfo & ubus call network.wireless status) that you requested/advised. If only to help diagnose the cause of the problem (for R&D) with confidence.
Better to be sure that it really is a hardware fault, before shipping a box all the way back :slightly_smiling_face:.

Yes, you can upgrade the latest firmware through GL GUI (please do not keep settings), the current firmware has been updated to v4.8.2 stable.

If no luck, please contact [email protected] by email, and our colleagues will provide the corresponding after-sales policy.