Difference between revisions of "Talk:Traffic accounting with iptables"
(→adult movie preview: new section) |
(Removed some spam links and useless non related sentences) |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 10: | Line 10: | ||
::: A dirty solution would be to put all IP addresses for that server in a file, and change /usr/local/sbin/vz-all-running-ip to cat said file. | ::: A dirty solution would be to put all IP addresses for that server in a file, and change /usr/local/sbin/vz-all-running-ip to cat said file. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 14:44, 8 June 2015
IPTables bytecounter overflow[edit]
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.Robferrer 07:08, 14 May 2008 (EDT)
More than one IP per container[edit]
This guide is very flawed for 99% of VPS hosts who offer more than 1 IP address with a vps account. --Vpsspeed 14:34, 13 June 2009 (UTC)
- Hey, this is wiki, meaning that if you find a problem in the text you can fix it yourself. --Kir 10:22, 16 June 2009 (UTC)
- We're in the middle of writing an in-house VPS control panel. I'll see if we can get a copy of our bandwidth monitoring script on here in a few weeks time when its ready! --Vpsspeed 10:20, 7 July 2009 (UTC)
- A dirty solution would be to put all IP addresses for that server in a file, and change /usr/local/sbin/vz-all-running-ip to cat said file.
