Traffic summary using iptables: Difference between revisions
No edit summary |
No edit summary |
||
Line 71: | Line 71: | ||
= Cron entry = |
= Cron entry = |
||
I've added this to crontab (crontab -e) |
|||
<pre> |
<pre> |
||
59 * * * * /usr/local/sbin/grabTraffic.pl |
|||
</pre> |
|||
= Database create options = |
= Database create options = |
||
For those wanting it; I've made a unique key formed by year+month+day+hour+source. It's highly inefficient, but I'm dealing with a relatively low amount of data on my end (checking 3 hosts, so for a year I'll have a max of 3 hosts * 24 hours * 365 days ~= 25000 entries). |
For those wanting it; I've made a unique key formed by year+month+day+hour+source. It's highly inefficient, but I'm dealing with a relatively low amount of data on my end (checking 3 hosts, so for a year I'll have a max of 3 hosts * 24 hours * 365 days ~= 25000 entries). |
||
<pre> |
<pre> |
||
CREATE TABLE `traffic` ( |
|||
`id` int(11) NOT NULL AUTO_INCREMENT, |
|||
`year` smallint(4) DEFAULT NULL, |
|||
`month` smallint(2) DEFAULT NULL, |
|||
`day` smallint(2) DEFAULT NULL, |
|||
`hour` smallint(2) DEFAULT NULL, |
|||
`source` varchar(20) DEFAULT NULL, |
|||
`traffic` bigint(20) DEFAULT NULL, |
|||
PRIMARY KEY (`id`), |
|||
UNIQUE KEY `datecheck` (`year`,`month`,`day`,`hour`,`source`) |
|||
) ENGINE=MyISAM AUTO_INCREMENT=13 DEFAULT CHARSET=latin1 |
|||
</pre> |
|||
= Example iptables output to test if it's working = |
|||
For ingoing traffic, issue: |
|||
<pre> |
|||
root@gateway:~# iptables -L TRAFFIC_ACCT_IN -n -v -x |
|||
Chain TRAFFIC_ACCT_IN (1 references) |
|||
pkts bytes target prot opt in out source destination |
|||
968985 56959759 all -- * * 0.0.0.0/0 192.168.0.210 |
|||
78 4328 all -- * * 0.0.0.0/0 192.168.0.220 |
|||
55144 80428099 all -- * * 0.0.0.0/0 192.168.0.240 |
|||
</pre> |
</pre> |
||
For outgoing, do: |
|||
<pre> |
|||
root@gateway:~# iptables -L TRAFFIC_ACCT_OUT -n -v -x |
|||
Chain TRAFFIC_ACCT_OUT (1 references) |
|||
pkts bytes target prot opt in out source destination |
|||
12713 4252586 all -- * * 192.168.0.210 0.0.0.0/0 |
|||
26 1440 all -- * * 192.168.0.220 0.0.0.0/0 |
|||
928 53851 all -- * * 192.168.0.240 0.0.0.0/0 |
|||
</pre> |
|||
If you need to flush the counter for any of those, just use the -Z option followed by the chain-name: |
|||
<pre> |
|||
iptables -Z TRAFFIC_ACCT_OUT |
|||
</pre> |
</pre> |
Revision as of 17:18, 12 March 2011
Overview
Using iptables and a simple perl script to analyze data traffic.
Iptables setup
I've added two new chains; in- and outgoing traffic inside forwarding rules. I've added these to my firewall startup script:
It is pretty self-explanatory.
### Static variables IPT=/sbin/iptables ### Static machines WEB=192.168.0.210 MAIL=192.168.0.220 MIRROR=192.168.0.240 ### Create logging of traffic (assuming eth0 is the wan interface and/or the one doing the forwarding) $IPT -N TRAFFIC_ACCT_IN $IPT -N TRAFFIC_ACCT_OUT $IPT -I FORWARD -i eth0 -j TRAFFIC_ACCT_IN $IPT -I FORWARD -o eth0 -j TRAFFIC_ACCT_OUT $IPT -A TRAFFIC_ACCT_IN --dst ${WEB} $IPT -A TRAFFIC_ACCT_IN --dst ${MAIL} $IPT -A TRAFFIC_ACCT_IN --dst ${MIRROR} $IPT -A TRAFFIC_ACCT_OUT --src ${WEB} $IPT -A TRAFFIC_ACCT_OUT --src ${MAIL} $IPT -A TRAFFIC_ACCT_OUT --src ${MIRROR}
Perl script to grab data
I'm putting the data from iptables into a local mysql database. From there I further analyze.
It's a simple two-stage process; 1. Get the data from the newly created chains; 2. Put into db and reset counter.
Mine is based around getting data every hour, so I've made a cron entry for that
Perl script:
#!/usr/bin/perl use strict; use DBI; ## Setup database connection my $dsn = 'dbi:mysql:<dbname>:<ip or localhost>:3306'; my $user = '<username>'; my $pass = '<password>'; my $dbh = DBI->connect($dsn, $user, $pass) or die "Horrible!!\n$DBI::errstr\n"; my ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time); $mon++; $year += 1900; ## Only grab outgoing data my @aData = `/sbin/iptables -L TRAFFIC_ACCT_OUT -n -v -x | awk '\$1 ~ /^[0-9]+\$/ { printf \"%s, %d \\n\", \$7, \$2 }'`; foreach (@aData) { chomp; my @aSplitter = split(/, /, $_); my $sExtraSQL = "ON DUPLICATE KEY UPDATE traffic = ".$dbh->quote($aSplitter[1]); my $sSQL = "INSERT INTO traffic (source, year, month, day, hour, traffic) VALUES (?, ?, ?, ?, ?, ?) $sExtraSQL\n"; my $sth = $dbh->prepare($sSQL); $sth->execute($aSplitter[0], $year, $mon, $mday, $hour, $aSplitter[1]); } my $bResetIptableCounter = `/sbin/iptables -Z TRAFFIC_ACCT_OUT`;
The code is extremely straightforward and no checks really. If I miss out of one hours traffic, it's no biggie, so haven't put much work into that part.
Cron entry
I've added this to crontab (crontab -e)
59 * * * * /usr/local/sbin/grabTraffic.pl
Database create options
For those wanting it; I've made a unique key formed by year+month+day+hour+source. It's highly inefficient, but I'm dealing with a relatively low amount of data on my end (checking 3 hosts, so for a year I'll have a max of 3 hosts * 24 hours * 365 days ~= 25000 entries).
CREATE TABLE `traffic` ( `id` int(11) NOT NULL AUTO_INCREMENT, `year` smallint(4) DEFAULT NULL, `month` smallint(2) DEFAULT NULL, `day` smallint(2) DEFAULT NULL, `hour` smallint(2) DEFAULT NULL, `source` varchar(20) DEFAULT NULL, `traffic` bigint(20) DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `datecheck` (`year`,`month`,`day`,`hour`,`source`) ) ENGINE=MyISAM AUTO_INCREMENT=13 DEFAULT CHARSET=latin1
Example iptables output to test if it's working
For ingoing traffic, issue:
root@gateway:~# iptables -L TRAFFIC_ACCT_IN -n -v -x Chain TRAFFIC_ACCT_IN (1 references) pkts bytes target prot opt in out source destination 968985 56959759 all -- * * 0.0.0.0/0 192.168.0.210 78 4328 all -- * * 0.0.0.0/0 192.168.0.220 55144 80428099 all -- * * 0.0.0.0/0 192.168.0.240
For outgoing, do:
root@gateway:~# iptables -L TRAFFIC_ACCT_OUT -n -v -x Chain TRAFFIC_ACCT_OUT (1 references) pkts bytes target prot opt in out source destination 12713 4252586 all -- * * 192.168.0.210 0.0.0.0/0 26 1440 all -- * * 192.168.0.220 0.0.0.0/0 928 53851 all -- * * 192.168.0.240 0.0.0.0/0
If you need to flush the counter for any of those, just use the -Z option followed by the chain-name:
iptables -Z TRAFFIC_ACCT_OUT