You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even though the kernel does all the accounting, having many iptables rules can slow down a home router, especially if its already nearing its NAT throughput limit.
The text was updated successfully, but these errors were encountered:
I don't think this should be an issue of your application. Just note it in the readme. All monitoring solutions which don't use (most likely proprietary) NAT acceleration ICs and drivers will need to rely on the CPU being fast enough to count while NATing packets using iptables. This is just a matter of processing power I think. There is nothing you can do.
Maybe the kernel also drops counting in favor of keeping throughput high? So possibly related to #37 ?
I left this as a bug because it could be partially mitigated by changing construction of the iptables rules. If the rules were laid out in consideration of how the kernel processes them, we could reduce the number of rule evaluations required per packet per device.
Even though the kernel does all the accounting, having many iptables rules can slow down a home router, especially if its already nearing its NAT throughput limit.
The text was updated successfully, but these errors were encountered: