BUG: Local FTP transfers are included in the bandwidth usage

[interfasys]

I've just noticed that all transfers made between local IPs are included in the bandwidth usage calculation.
This is a big problems for people that spread their static content over several sites/IPs, but it's also unfair and could get a user banned for the wrong reasons.

 

[scsi]

Its definitely not a bug at all. It just reads usage from the log file. How do you expect it to know the ip is local? If something like that was added or changed it would have to be a feature.

 

[interfasys]

Errr...DA has the whole list of IPs at different levels. It can perfectly ignore traffic coming from local IPs for the usage calculations.

Even if the traffic comes from a different user, it's hardly justifiable to charge for bandwidth that wasn't metered by the router/provider/data centre.

 

[DirectAdmin Support]

Hello,

Just to confirm, you're referring to incoming connections from "local" boxes, eg:
198.168.x.x
10.x.x.x

Right now, the logging format doesn't record where connections come from.
We can change it from:

LogFormat               userlog "%u %b %m"

to be:

LogFormat               userlog "%u %b %m %a"

and then we'll figure out the "skipping" in a later version of DA.

http://www.directadmin.com/features.php?id=1154

John

 

[interfasys]

Hello John,
No, I meant public IPs that are hosted on the same box, although it is also a good idea not to log traffic coming from private IPs as you're suggesting.

Here is an example:
IPs on the box
66.55.44.33
66.55.44.32
66.55.44.31


When website A replicates its content to site B using FTP, there will be a connection made between 66.55.44.33 and 66.55.44.31. It will not count as external traffic at the provider and should not be included in the bandwidth usage for that user.

Cheers,

Olivier

 

[nobaloney]

John's suggestion for the first step is still appropriate.

Configuring the second step is going to be a bit more complex, though.

Jeff