Editing Talk:Traffic accounting with iptables
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 2: | Line 2: | ||
I added a warning about the cron period. Our iptables bytecounters overflowed within an hour when we had constant download at 60Mbps. We calculated (based on the maxiumum value we had seen accounted and the 100Mbps network connection) that we should run the cron every 15 mins. Should consider even more frequently if using a Gbit connection.[[User:Robferrer|Robferrer]] 07:08, 14 May 2008 (EDT) | I added a warning about the cron period. Our iptables bytecounters overflowed within an hour when we had constant download at 60Mbps. We calculated (based on the maxiumum value we had seen accounted and the 100Mbps network connection) that we should run the cron every 15 mins. Should consider even more frequently if using a Gbit connection.[[User:Robferrer|Robferrer]] 07:08, 14 May 2008 (EDT) | ||
| − | |||
This guide is very flawed for 99% of VPS hosts who offer more than 1 IP address with a vps account. --[[User:Vpsspeed|Vpsspeed]] 14:34, 13 June 2009 (UTC) | This guide is very flawed for 99% of VPS hosts who offer more than 1 IP address with a vps account. --[[User:Vpsspeed|Vpsspeed]] 14:34, 13 June 2009 (UTC) | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
