Gargoyle Forum

I may at some later point (busy week). If you have any hint where to look at, let me know. I do know that the early enabling I did last spring for 2023.0x was fine in this regard.

Tried https://github.com/lantis1008/gargoyle/ ... enwrt_2305 today on a WRT32X (just had to patch the config to switch to libustream-mbedtls). It booted, basic networking was fine but WIFI remained broken. Known issue at this state of development?

https://github.com/torvalds/linux/commi ... efd0fab14c (hit 5.11)

As there is that issue with mvebu devices and OpenWRT 22.03 while the current 19.07 is clearly aging, I've tweaked gargoyle master to build with openwrt master, at least for mvebu devices. See https://github.com/jan-kiszka/gargoyle/commits/openwrt-23.04-hacks for the needed changes. The result seems...

I was about to use backup/restore for playing with a self-built master version when I realized this deficit: Can you elaborate on the incompatibility of the OpenVPN settings under /etc/openvpn/, even when doing just minor updates, but also across major ones? TIA.

Yes, Gargoyle itself is safe. See also https://forum.openwrt.org/viewtopic.php?id=62794.

Problem persists with 1.8.0, as it did with 1.7.1 (didn't test 1.7.2).

Is there a ticketing system to track issues a bit better?

The DLNA forwarding bug as described in http://www.gargoyle-router.com/phpbb/vi ... 47&p=26981 persists with 1.7.1 - just in case it was supposed to be addressed. Thanks in advance for looking into it!

Hi, I had to add echo '0' > '/sys/devices/virtual/net/br-lan/bridge/multicast_snooping' to /etc/rc.local in order to make a LAN-attached DLNA server visible again for WLAN clients. That used to work out-of-the-box with earlier versions. Something seems to have changed in 1.7.0. Known issue with some...

Issue and workaround confirmed here as well. This used to work in previous releases without such a rule, just checked the saved config.