Quota System

[ekkesa]

Hi,

Firstly I want to start by saying what an amazing system Eric has put together here - It is truely a good piece of software.

I am currently running your newest beta (1.3.9) on a Linksys WRT54GL and I am experiencing some issues witht the quota system.

Here are some of the issues I'm encountering:

1. Whenever I change a users quota, the system stops showing quotas for all users (Status --> Quota Usage), and I have to reboot. I'm not sure if the accounting of quota are still running. The chain (Chain egress_restrictions) are missing after a quota change.

2. Whenever I reboot, or the power goes down as it does often in South Africa, I seem to loose all the quotas that was assigned, including their usage so far.

3. If a edit a users quota, the usage goes back down to 0% - which is a bit annoying, but one could work around it. I believe this is an issue with the IPTables being cycled. Al the quotas also seem to go missing.

Is there anything I can check to try and sort this issue out?

Thankz

[tauki63]

Hi,

I wanted to ask the same questions which you already asked. It is a incedible piece of firmware but these problems pull it down. I hope eric could fix these bugs.

I am not sure whether other earlier releases have these bugs. If earlier bug are clean I am glad to use it.

However i would like the router page to show the usage before logging in to the router. Which first release that has it?

I am glad to use it if it has no bugs.

Does the preloaded gargoyle router has this problem?

I would like to buy one but it is not posted outside US.
I really hope it would be posted outside US especially Australia.
ONLY IF THESE BUGS DOES NOT OCCUR.

Thanks,
tauki

[ekkesa]

Hi,

I downgraded to version 1.2.4, and this is working like a charm now! Hope it helps.

This is really an incredible piece of software.

[Eric]

Sorry it took so long to respond to this (since the quota system is pretty much my top priority) -- there is an issue with this in 1.3.9, but it's since been fixed (for a while) in the repository and will work in the upcoming release. In fixing a race condition that pops up with PPPoE in the past release, it inadvertently caused this problem.

I'm glad the stable release is working well for you until then -- this is exactly why we have both a stable and experimental branch