Gargoyle Forum

Yes, it has the same security patches as 21.02.1

Any differences/commits since 1.13.X (Built 20220115-0541 git@54463e40)?

Fixed a problem with ipv6 on mvebu routers and with Tor

Many thanks to all the contributors for their hard work!

The firmware is stable and very user friendly, it keeps getting better and better with each release.

Thanks for all your hard work, been a fan on gargoyle firmware since 10 or more years.

Sorry to bring the same topic i stated on another post, but still having trouble with gargoyle 1.13.x versions on Archer C7 V2 router.

The problem is when i assign static IP (IPV4) address on the DHCP option, i am not sure if the problem is related to ipv6 or a bug in this specific router. But when I assign static IP most devices can't connect (couldn't get ip address) and a few devices that are able to connect they are assigned an IP that doesn't match router settings and has no internet connection (my dhcp range 192.168.0.100-192.168.0.200) and those few devices are assigned in range 169.254.xxx.xxx, and I don't know where that IP is coming from.

I already Tried disabling ipv6 option on dhcp settings, and disable enforce DHCP assignments. The only way i can connect a device to the router is to assign a static IP on the device itself.

If enforce DHCP is disabled, all devices should get an internet connection whether they get your intended address or not.
Can you open another topic and post your connection settings and DHCP settings?
Also are you sure you only have a single DHCP server running?

169.254 addresses are what windows assigns when it can’t get an IP

Happy to report EdgeRouterX which had a prior botched flash with Ubiquiti software is alive and kicking and operates perfectly with Gargoyle's latest firmware.

Is an upgrade from the previous release OK (I see one person mentioned doing it)? One thing that gives me pause is that it's a major OpenWRT version leap behind-the-scenes.

1.12.x, not recommended due to major openwrt revision jump and introduction of IPv6 specific capabilities.

1.13.x to 1.13.0, generally ok, but your mileage may vary.

OK, thanks

Given the OpenVPN changes and industry limits on TLS cert lengths (825 days), do the ones generated here fall under that limitation now? I know when I was generating some for another project recently, easyrsa automatically chose 825.

I think the limit had been around 1185 days before that, but I know the ones generated here in earlier versions extended nearly a couple decades somehow!