Gargoyle Forum

Been running the 2025-10-24 build on my Netgear r7450 for a little over a day. Using it as a main gateway from my cable ISP and as a client+ap. Running nice and smooth, thank you Lantis!

Hi Lantis,
OpenWrt has migrated to 24.10.5. Do you consider to upgrade Gargoyle 1.15.x accordingly? Merry Xmas and thanks.

Yes I will take care of that over the next few weeks. There are some other changes submitted by Pythonic that I will also review.

I've got the current beta (build from October 24th, 2025) installed on my main router (Flint 2) now. Seems to be working just fine, but I had trouble installing it. I was coming from 1.15.x (aka 1.14.0), so retaining settings was not possible.
I therefore did install without preserving settings and the router booted to the factory reset state. Entering password and changing the same was no problem, but as soon as I changed the routers LAN IP address it would simply vanish. Would not establish a link with neither Linux nor Windows machines on ethernet, nor my Android tablet on wifi. Tried several times, and finally had a different network configuration where I was able to log in again. There was an error in the DHCP configuration, the start value being okay but the value for the end of the DHCP range was showing "NaN".
The only thing I did change was altering the address from default to 192.186.0.181 to move it to my home network IP range.

ektus wrote: ↑

Fri Jan 02, 2026 11:10 am

I've got the current beta (build from October 24th, 2025) installed on my main router (Flint 2) now. Seems to be working just fine, but I had trouble installing it. I was coming from 1.15.x (aka 1.14.0), so retaining settings was not possible.
I therefore did install without preserving settings and the router booted to the factory reset state. Entering password and changing the same was no problem, but as soon as I changed the routers LAN IP address it would simply vanish. Would not establish a link with neither Linux nor Windows machines on ethernet, nor my Android tablet on wifi. Tried several times, and finally had a different network configuration where I was able to log in again. There was an error in the DHCP configuration, the start value being okay but the value for the end of the DHCP range was showing "NaN".
The only thing I did change was altering the address from default to 192.186.0.181 to move it to my home network IP range.

So just to understand this, you’re setting this up as just a LAN client on your existing network? And therefore you would disable the DHCP server as step 2 (after changing the IP), but you don’t get the opportunity as the router becomes unreachable?

Just making sure I have the scenario right so I can think through a fix. I already know exactly why it’s failing.

So just to understand this, you’re setting this up as just a LAN client on your existing network? And therefore you would disable the DHCP server as step 2 (after changing the IP), but you don’t get the opportunity as the router becomes unreachable?

No, I didn't disable DHCP. And wouldn't have wanted to as this was to be becoming the main router.
1) Connect WAN port of router to home network (this was a spare)
2) Connect LAN port of Router to second ethernet interface of notebook
3) Upgrade router, including factory reset
4) Change password, reboot -> all okay
5) Change IP to be inside the home network (the same as was on the WAN port until now)
6) Remove connection to WAN port (so router ist standalone) and reboot
7) No connection to router, neither LAN nor Wifi if activated after step four. Wifi is visible, but doesn't connect.

I did eventually get in by connecting a LAN port to the house network. But that was a lot of try and error and a couple factory resets (long pressing the reset button). I briefly had two DHCP servers running, but that didn't lead to major network problems in the short period of time.

Next step was replacing the DHCP config with the current one from the 1.14.0 system, replacing the main router with the newly installed one and continuing the configuration (VPN server, lantis software repositories and some packages, the works).

The problem is your choice of IP.
192.168.0.181 is inside the DHCP range, which by default is x.x.x.100-x.x.x.249

When dnsmasq (which handles the DHCP Server role) starts it runs
ipcalc.sh "192.168.0.181/255.255.255.0" 100 150
Which returns So you need to adjust your DHCP range as a first step OR pick a new IP outside of the range.

My normal DHCP range is 200 to 254, I'm running out of addresses in the range below 100...

Good to know the reason, that'll hopefully lead to a much smoother update process the next time.

THANK YOU!

A new build has been released with OpenWrt 24.10.5 (+ a few commits) as the base.
This includes the fix for CVE-2025-14282 which should have no impact to 99% of users, but please check the linked documentation and ask questions if you are unsure.

Links in the first post and on the blog.

Thanks to both @aimacintyre and @lancethepants for their contributions.

This branch has now reached a reasonably stable point and will be merged into the master branch in the coming weeks.

Hey Lantis,

I did a build from your repo yesterday (Bump to latest OpenWrt 24.10 faed9d8). So far no issues, running good.

Cheers