Category Archives: alSUMBilling

New alSUMBilling.

Hello. new version of the alSUMBilling is out. https://sourceforge.net/projects/phpal/files/alSUMBilling/alsumbill20091208/ Changelog: 1) Fixed much probles. 2) added display traffic from/to IPs, thats isn’t in squidusers table With this version you no longer need userip table (created in ulog database) . usernames and IPs are reads from squidctr/squidusers table (you need to add IP for each user […]

Posted in alSUMBilling | Comments closed

alSUMBilling released!

First version of the alSUMBilling is online! http://phpal.sourceforge.net/alsumbilling

Posted in alSUMBilling | Comments closed

Langs moved to separated package

Right now folder with langs moved to separated package. This lang used in all Billings. http://sourceforge.net/project/showfiles.php?group_id=201020&package_id=311740

Also posted in alLANBilling, alSAMSBilling, site | Comments closed

New versions coming (Billings)

Right now i’m testing new project alSUMBilling. As you remember, this is complete solution for accouting all traffic (proxy+NAT)  in you bussines. This is alSAMSBilling + alLANBilling. alSUMBilling will be released after adding multilang and some fixes for another people (right now its configured only for my databases). Also new version of the alLANBilling and […]

Also posted in alLANBilling, alSAMSBilling | Comments closed

alLANBilling and alSUMBilling database optimization

Please delete old indexes before! I recomend to add this indexes to speedup processing: KEY `unix_secs` (`unix_secs`), KEY `dstusecs` (`dstaddr`,`unix_secs`), KEY `srcusecs` (`srcaddr`,`unix_secs`), KEY `output` (`output`,`unix_secs`) KEY `unix_secs` (`unix_secs`), KEY `dstusecs` (`dstaddr`,`unix_secs`), KEY `srcusecs` (`srcaddr`,`unix_secs`), KEY `output` (`output`,`unix_secs`)

Also posted in alLANBilling | Comments closed

Installing engine for alLANBilling

1) I hope that the NAT, routing, httpd, php, mysql,fprobe-ulog, flow-tools packages already installed 2) Add iptables rule to which all packages will be NAT-pass through ULOG This is only EXAMPLE: *filter :INPUT ACCEPT [0:0] :FORWARD DROP [0:0] :OUTPUT ACCEPT [0:0] :NETFLOW – [0:0] -A FORWARD -s 192.168.0.0/24 -d 123.123.123.123/32 -p tcp -m tcp –dport […]

Also posted in alLANBilling | Comments closed