Gargoyle Forum

A full boot log when the problem occurs should be fine, or if it occurs after saving the connection settings a logread there is ok. This is not normal behaviour, and even a late firewall should not really trigger it, as the scripts are triggered by the firewall itself. Saving connection information...

In case of usb modem usage, saving connection settings solving problem with web usage monitor.
Is it possible to fix this permanently or only workaround with late firewall restart should be used?

Lantis wrote:Then have you tried saving connection settings to try?

If you about bandwidth monitors - yes. Not help.
If you talking about modem and web usage case - will test and will let you know.

Interesting moment with Web usage. If you'ŗe on WAN - everything is working, but if you using USB modem as WAN, then first moment you set up everything (meaning switched to USB modem), web monitor working, but until reboot. If you rebooted device (meaning USB modem is a WAN from initial), web monito...

Yes. I'm on 19.07 In your Gargoyle git folder, run the following That error usually just requires you to restart the firewall, which can be triggered by saving your connection settings, or rebooting. But router reboot, for example, not solving this problem. I thought I wrote about bandwidth monitori...

If I would miss a commit, code on my side would not be the same with git, or? I tried to delete ramips_source folder and then build again. Tried "make clean" and nothing help. Could you instruct how could I fix this? I'll post errors when signature check is in config later. Another thing i...

Tried to build Gargoyle based on OpenWRT release 19.07 for ramips. Is it only for me these 2 rows in config causing build to fail: ... CONFIG_SIGNATURE_CHECK=y ... CONFIG_GCC_VERSION="7.5.0" ... By commenting first row and reverting second to "7.4.0" I was able to build again. PS...

OpenWRT 19.07 is released. Any adjustments expected or simply commit could be changed?

Maybe, but i don't know how the host will connect in this behaviour. It sounds like "undefined" behaviour. That's the thing. Connection happen only if either main router or repeater authentication is distinct. If both mixed - repeater not creating connection to main router. I already test...

Thank you. I will try and will let you know.
However, is it not the same as I would set wpa3/wpa2 authentication on repeater GUI?