Gargoyle 1.15.x BETA - 2025-03-31 - Based on OpenWrt 23.05

[pythonic]

Im using 1.15.X (Built 20241013-2237 git@347e0534) on my Asus rt-ac51u. I cant flash another firmware, its stuck, no matter what i try it wont flash anything else. I also tried using asus recovery tool but it wont accept the firmware..

Your device only has 64MB of RAM so it's possible that the failure to update may be due to insufficient temporary storage space during the flash process. The Gargoyle image is 10.6MB however the standard OpenWrt 23.05.5 image is less than 6MB so you may want to try installing that instead to see if that helps.

If @Lantis' advice isn't successful, you might try the techniques in the OpenWrt device page: the device is supposed to support TFTP installation. I note that there is a specific instruction to rename the image when using the Asus firmware restoration tool which may be significant in that case (the recommended version of that tool still seems to be downloadable at time of writing too).

[Lajkzy]

My bad, when i enter the commands, I realized I have an asus rt-ac58u.

[angus]

"BETA - 2025-03-31" Notable changes since 2024-11-13:
- Added a backend function to regenerate OpenVPN CRLs
- Removed various devices which only have 32MB of RAM
- Updated ksmbd-tools to 3.5.3 to fix an issue causing shared folders to not be visible
- Added initial support for 6GHz frequency scanning to Spectrum Analyser plugin

Hi Lantis,
Should we expect to have the Spectrum Analyzer included in released images? Thanks.

[Lantis]

I don’t believe it is installed by default on any devices due to its size. It’s not massive but it’s not small.
It can be installed from the plugin repo.

[fifonik]

I'm using GL-MT6000 and on version 1.15.X (Built 20240702-0231 git@ab461167) at this moment.
Is it considered to be safe to upgrade to the latest build preserving settings?
Do not want to spent a few hours re-configuring all the stuff %-)
Thanks.

[Lantis]

If you were already on one in the series yes it should be fine. There have not been any breaking changes so far.

[jarek7714]

Hi, any chance of a Gargoyle image for Google Wifi AC-1304?

[fifonik]

If you were already on one in the series yes it should be fine. There have not been any breaking changes so far.

Updated from the previous 1.15.x build to the latest one preserving settings this morning with no issues.
Unfortunately, I'm still unable to connect to the rourer using httpS.
Tried workaround mentioned here without success:
viewtopic.php?p=66487#p66487

Other than the issue, I'm pretty happy with the gargoyle 1.15.x on the gl6000 -- using it for about a year and only a coulple of times router stopped responding (probably because of weburl issue you mentioned).
Thanks a lot.

[Lantis]

If you were already on one in the series yes it should be fine. There have not been any breaking changes so far.

Updated from the previous 1.15.x build to the latest one preserving settings this morning with no issues.
Unfortunately, I'm still unable to connect to the rourer using httpS.
Tried workaround mentioned here without success:
viewtopic.php?p=66487#p66487

Other than the issue, I'm pretty happy with the gargoyle 1.15.x on the gl6000 -- using it for about a year and only a coulple of times router stopped responding (probably because of weburl issue you mentioned).
Thanks a lot.

Are you experiencing the same issue that was reported?
Given you preserved settings, I'm wondering if you preserved a badly formed certificate from before the fix.

However if you followed the "workaround", this should have resolved it. The missing instruction in that post is that you need to restart uhttpd (or the entire router).
To test the "fix", you could just delete the certificate and then Save Settings again on the access page. This should trigger a new cert to be generated.

If that doesn't work, let's figure it out and resolve it

[Lantis]

Hi, any chance of a Gargoyle image for Google Wifi AC-1304?

Hi, yes... and no. Mostly no I'm sorry.
That device is part of an ipq40xx subtarget called "chromium" which supports 1 single device, your device.
It is a bit wasteful to introduce a whole new subtarget just for a single device, so I'm not that keen to add it in sorry.

However, I will provide a test image and the build config such that you can build your own if you would like to. Give me some time to come back on this.