up vote 0 down vote favorite
1
share [g+] share [fb] 
 pkts bytes target     prot opt in     out     source               destination         
12770 2385K ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           quota: 2000000 bytes
0     0 DROP       all  --  any    any     anywhere             anywhere

How can this be? I've set limit to 2M, but it's now 2.385M and still accepting

Since 2010-07-23 15:07:47 commit "report initial quota value instead of current value to userspace" it became uncertain what the current value of quota is and I relied on bytes counter (when I reset the quota the counter is reset too). Why it fails?

link|improve this question
64% accept rate
feedback

2 Answers

up vote 0 down vote

Can you edit your post and include the output of iptables-save?

link|improve this answer
May be later, now I'm running kernel with reverted commit 49daf6a22622d4e1619aeaad5f9f0472bf89daff "xt_quota: report initial quota value instead of current value to userspace" and it does not reproduce. – Vi. Mar 10 '11 at 19:07
feedback
up vote 0 down vote accepted

Just revert this commit and enjoy quotas.

(Hovewer, I see inconsistent measurements sometimes; but in general in more works than not).

Considering netfilter quotas unreliable (both usual and with reverted commit).

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.