{"id":102,"date":"2007-06-18T11:13:13","date_gmt":"2007-06-18T16:13:13","guid":{"rendered":"http:\/\/raffy.ch\/blog\/2007\/06\/18\/afterglow-example-visualizing-ip-tables-logs\/"},"modified":"2007-06-18T11:34:39","modified_gmt":"2007-06-18T16:34:39","slug":"afterglow-example-visualizing-ip-tables-logs","status":"publish","type":"post","link":"https:\/\/raffy.ch\/blog\/2007\/06\/18\/afterglow-example-visualizing-ip-tables-logs\/","title":{"rendered":"AfterGlow Example – Visualizing IP Tables Logs"},"content":{"rendered":"

I am sitting in Seville, at the First<\/a> conference, where I will be teaching a workshop on Wednesday. The topic is going to be insider threat visualization<\/a>. While sitting in some of the sessions here, I was playing with my iptables logs. Here is a command I am running to generate a graph from my iptables logs:
\ncat \/var\/log\/messages | grep \"BLOCK\" | perl -pe 's\/.*\\] (.*) (IN=[^ ]*).*(OUT=[^ ]*).*SRC=([^ ]* ).*DST=([^ ]* ).*PROTO=([^ ]* ).*?(SPT=[^ ]+ )?.*?(DPT=\\d* )?.*?(UID=\\d+)?.*?\/\\1,\\2,\\3,\\4,\\5,\\6,\\7,\\8,\\9\/' | awk -F, '{printf \"%s,%s,%s\\n\",$4,$5,$8}' | sed -e 's\/DPT=\/\/' -e 's\/ \/\/g' | afterglow.pl -e 1.3 -c iptables.properties -p 1 | neato -Tgif -o\/tmp\/test.gif; xloadimage \/tmp\/test.gif<\/code>
\nThis is fairly ugly. I am not going to clean it up. You get the idea. Now, what does the iptables.properties look? Well, if you thought the command above was ugly. The properties file is completely insane, but it shows you the power of using the “variable”<\/em> assignment:
\n variable=$ip=`ifconfig eth1 | grep inet`
\nvariable=$ip=~s\/.*?:(\\d+\\.\\d+\\.\\d+\\.\\d+).*\\n?\/\\1\/;
\nvariable=$subnet=$ip; $subnet=~s\/(.*)\\.\\d+\/\\1\/;
\nvariable=$bcast=$subnet.\".255\";
\n<\/code>color=\"invisible\" if (field() eq \"$bcast\")
\ncolor=\"invisible\" if ($fields[2] eq \"67\")
\ncolor=\"yellow\" if (field() eq \"$ip\")
\ncolor.source=\"greenyellow\" if ($fields[0]=~\/^192\\.168\\..*\/);
\ncolor.source=\"greenyellow\" if ($fields[0]=~\/^10\\..*\/);
\ncolor.source=\"greenyellow\" if ($fields[0]=~\/^172\\.16\\..*\/);
\ncolor.source=\"red\"
\ncolor.event=\"greenyellow\" if ($fields[1]=~\/^192\\.168\\..*\/)
\ncolor.event=\"greenyellow\" if ($fields[1]=~\/^10\\..*\/)
\ncolor.event=\"greenyellow\" if ($fields[1]=~\/^172\\.16\\..*\/)
\ncolor.event=\"red\"
\ncluster.target=\">1024\" if (($fields[2]>1024) && ($fields[1] ne \"$ip\"))
\ncluster.source=\"External\" if (field()!~\/^$subnet\/)
\ncluster.event=\"External\" if (field()!~\/^$subnet\/)
\ncolor.target=\"blue\" if ($fields[1] eq \"$ip\")
\ncolor.target=\"lightblue\"<\/code>
\nMind you, this was run on an Ubuntu Linux. You might have to change some of the commands and parsing of the output. Pretty neat, ey? Here is a sample output that this generated. My box is yellow. The question that I was trying to answer: Why is someone trying to conect to me on port 80?<\/p>\n

\"IPTables<\/a><\/p>\n

[tags]visualization, iptables, afterglow, security[\/tags]<\/p>\n","protected":false},"excerpt":{"rendered":"

I am sitting in Seville, at the First conference, where I will be teaching a workshop on Wednesday. The topic is going to be insider threat visualization. While sitting in some of the sessions here, I was playing with my iptables logs. Here is a command I am running to generate a graph from my […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,2],"tags":[],"class_list":["post-102","post","type-post","status-publish","format-standard","hentry","category-log-analysis","category-visualization"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t