Don’t count on or wait for official releases.
Releases happen when I think of it and when I can get in touch with Eric and he has time. So there are no schedules and no guarantees.
But the code is changing much more frequently and I provide downloads regularly.
Version 1.14.0: Based on OpenWrt 22.03
Moderator: Moderators
Re: Version 1.14.0: Based on OpenWrt 22.03
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Please be respectful when posting. I do this in my free time on a volunteer basis.
Re: Version 1.14.0: Based on OpenWrt 22.03
Hi Lantis, I've updated my router to the latest build. https login works fine now. But am finding it rebooting quite a lot, ranges from 5 hours to 3 days.
Am using 1.15.X (Built 20241113-1230 git@b0c923bf) on TP-Link Archer A6 v3.
Am using 1.15.X (Built 20241113-1230 git@b0c923bf) on TP-Link Archer A6 v3.
Re: Version 1.14.0: Based on OpenWrt 22.03
More info will be required to have any chance of figuring out what this is (and probably best reported in a separate thread rather than cluttering this one).
Apart from an outline of your configuration (particularly the functions enabled) it would be helpful if you could configure logging to a remote host in case a critical error is logged.
Something else that might help would be to log into the router via ssh and run top continuously (without using the web UI). This is to look for excessive CPU or memory usage; the last top screen displayed when the reboot happens might give a clue.
Other things you could try would be to "upgrade" to OpenWrt 23.05.5 (don't attempt to preserve configuration though) which is very close to the base on which the recent Gargoyle 1.15 builds are based; if the reboots still happen that would be indicative of an issue not specific to Gargoyle. You could then try a OpenWrt 24.10 release candidate (just released, or about to be released) to see whether the behaviour changes.
I'm aware of a potential issue with a different target architecture (not currently supported by Gargoyle) that might look like this but had thought it to be target architecture specific.