Gargoyle Forum

People might be wondering why it's so quiet around here lately. I promise that i'm busier than ever implementing IPv6. It is still a few months away, and there will be bugs, but it is coming. I've just made a large milestone which is rewriting the bandwidth monitoring module. Blue line is the total ...

What method would you like to use so someone can assist you?
1. Remote web access (easy, not very secure)
2. OpenVPN (medium difficulty, much more secure)

If you have a dynamic IP you also need to setup DDNS.

Gargoyle does not support IPv6 yet (maybe in a month or two). Even then, support initially will only be for native IPv6, not transition technologies like 6to4. So you might be better manually configuring it if you really want to try it. https://openwrt.org/docs/guide-user/network/ipv6/barrier.breake...

You need to include: Ath9k, ath10k-ct, ath10k-firmware-988x-ct, iwinfo, hostapd-openssl At a minimum. There's more I'm sure I have forgotten. To have preconfigured wifi will require a patch or the use of custom files in OpenWrt build environment. https://openwrt.org/docs/guide-developer/build-system...

Those stats not showing up are usually accompanied by log entries along the lines of "device IMQ0 does not exist" Which indicates that the IMQ driver failed to start correctly. Usually saving QOS again causes it to restart and therefore attempt to reinsert the driver. I need to put some try, wait, f...

I've merged the two topics as they discuss the same bug.
As stated above, Gargoyle is not susceptible to the aforementioned issue by default.

Saving QOS again should fix the congestion control status being blank.

Curiously (and suspiciously) these bugs always show up near the dates when daylight savings kicks in or ends.

It is definitely related, or at least exacerbates the issue.

IPSet won't help unless you know the entire list of IPs used by youtube. Gargoyle doesn't really have any DNS level blocking built into the GUI. The app is probably making DNS calls and then resolving the IP rather than a web GET request. Everything would need to be setup manually, and there isn't r...

So testing the theory, it's working ok.
Now you can try adding back in the rules 1 at a time to try and cover the other use cases (e.g. the app).
I'm not sure what URLs the app uses internally.