Hi all
I recently deployed gargoyle on x86 and have noted that when I deploy individuals with quota restriction then quotas dont work. Nothing is displayed. If I use individuals without quota combined, it works. This is my main requirement. I have observed that when I create restriction using all hosts except, this does not work too. I tried working around this by creating restriction with all hosts and then adding exception that too does not work. Iam running gargoyle v1.14.0
individuals without quota issues on x86
Moderator: Moderators
Re: individuals without quota issues on x86
Hi zizebra,
Thanks for the detailed report — the specifics (individual quotas, "all hosts except", and the all-hosts-plus-exception workaround) were really helpful, because they let me reproduce exactly what you described rather than guess.
The key thing: you're on v1.14.0, which is quite an old release. The whole firewall backend has been rewritten since then — 1.14.x used iptables, and the 1.15.x line (based on newer OpenWrt) was rebuilt on nftables/fw4. A lot of quota +
restriction interaction issues from the iptables era simply don't exist in the rewritten backend.
I checked all three of the things you hit, on a current 1.15.x build, in a test environment:
1. A per-individual quota on a host that also has a restriction — the quota still counts and displays. (In your v1.14.0 it showed nothing; on the current build it keeps accounting normally.)
2. A restriction set to "all hosts except X" — X keeps internet access and everyone else is blocked, as intended.
3. A restriction on "all hosts" plus an exception for X — same result: X is allowed, everyone else blocked.
All three worked correctly, and I've added automated tests for them so they stay working.
So the short version: this looks like it's already resolved in the current line, and the fix is to move to a newer build rather than anything you're doing wrong in your config.
Two caveats worth being upfront about:
- The current 1.15.x builds are on a much newer OpenWrt base, so don't try to keep your v1.14.0 settings across the upgrade — back them up, flash clean, and reconfigure. Config formats have changed and stale settings cause odd breakage.
If you do move to a current build and still see the quota-with-restriction problem, please shout — at that point it'd be a live bug on the current code and I'd want to dig into your exact config. But based on what you've described,
upgrading should sort all three out.
Thanks for the detailed report — the specifics (individual quotas, "all hosts except", and the all-hosts-plus-exception workaround) were really helpful, because they let me reproduce exactly what you described rather than guess.
The key thing: you're on v1.14.0, which is quite an old release. The whole firewall backend has been rewritten since then — 1.14.x used iptables, and the 1.15.x line (based on newer OpenWrt) was rebuilt on nftables/fw4. A lot of quota +
restriction interaction issues from the iptables era simply don't exist in the rewritten backend.
I checked all three of the things you hit, on a current 1.15.x build, in a test environment:
1. A per-individual quota on a host that also has a restriction — the quota still counts and displays. (In your v1.14.0 it showed nothing; on the current build it keeps accounting normally.)
2. A restriction set to "all hosts except X" — X keeps internet access and everyone else is blocked, as intended.
3. A restriction on "all hosts" plus an exception for X — same result: X is allowed, everyone else blocked.
All three worked correctly, and I've added automated tests for them so they stay working.
So the short version: this looks like it's already resolved in the current line, and the fix is to move to a newer build rather than anything you're doing wrong in your config.
Two caveats worth being upfront about:
- The current 1.15.x builds are on a much newer OpenWrt base, so don't try to keep your v1.14.0 settings across the upgrade — back them up, flash clean, and reconfigure. Config formats have changed and stale settings cause odd breakage.
If you do move to a current build and still see the quota-with-restriction problem, please shout — at that point it'd be a live bug on the current code and I'd want to dig into your exact config. But based on what you've described,
upgrading should sort all three out.
Re: individuals without quota issues on x86
Many thanks for the quick response. I did see the post provided and suggestion for version 1.15 however I didn't see it on the download section. The highest version i see for x86 is 1.14. The install is relatively new, I can install new version without problems as my existing setup is actively serving the home.
Re: individuals without quota issues on x86
I have located the version 1.15.0 and installed it. Every is working as intended. Ia. Grateful. Thank you