<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress.com" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>ntop &amp;laquo; WordPress.com Tag Feed</title>
	<link>http://en.wordpress.com/tag/ntop/</link>
	<description>Feed of posts on WordPress.com tagged "ntop"</description>
	<pubDate>Thu, 24 Dec 2009 23:03:04 +0000</pubDate>

	<generator>http://en.wordpress.com/tags/</generator>
	<language>en</language>

<item>
<title><![CDATA[Snoop on your own network with ntop]]></title>
<link>http://jobenbissong.wordpress.com/2009/11/26/snoop-on-your-own-network-with-ntop/</link>
<pubDate>Thu, 26 Nov 2009 13:04:25 +0000</pubDate>
<dc:creator>Jo B</dc:creator>
<guid>http://jobenbissong.wordpress.com/2009/11/26/snoop-on-your-own-network-with-ntop/</guid>
<description><![CDATA[Ever wonder what is happening on your network? Particularly in terms of what traffic is passing in a]]></description>
<content:encoded><![CDATA[Ever wonder what is happening on your network? Particularly in terms of what traffic is passing in a]]></content:encoded>
</item>
<item>
<title><![CDATA[Network Traffic Monitoring with nTop]]></title>
<link>http://jasonk2600.wordpress.com/2009/11/21/network-traffic-monitoring-with-ntop/</link>
<pubDate>Sat, 21 Nov 2009 18:03:00 +0000</pubDate>
<dc:creator>jasonk2600</dc:creator>
<guid>http://jasonk2600.wordpress.com/2009/11/21/network-traffic-monitoring-with-ntop/</guid>
<description><![CDATA[Installation Configure and install nTop from the ports collection.&#160; NOTE:&#160; Be sure to acti]]></description>
<content:encoded><![CDATA[Installation Configure and install nTop from the ports collection.&#160; NOTE:&#160; Be sure to acti]]></content:encoded>
</item>
<item>
<title><![CDATA[ntop di opensuse 11.1]]></title>
<link>http://kembars.wordpress.com/2009/10/11/ntop-di-opensuse-11-1/</link>
<pubDate>Sun, 11 Oct 2009 04:20:59 +0000</pubDate>
<dc:creator>kembars</dc:creator>
<guid>http://kembars.wordpress.com/2009/10/11/ntop-di-opensuse-11-1/</guid>
<description><![CDATA[Salah satu network monitoring tools di linux yang instalasinya relatif simple yet powerful adalah ]]></description>
<content:encoded><![CDATA[Salah satu network monitoring tools di linux yang instalasinya relatif simple yet powerful adalah ]]></content:encoded>
</item>
<item>
<title><![CDATA[Linux Firewall How to abort (cut) specific connections]]></title>
<link>http://installatore.wordpress.com/2009/09/13/linux-firewall-how-to-abort-cut-specific-connections/</link>
<pubDate>Sun, 13 Sep 2009 11:03:01 +0000</pubDate>
<dc:creator>installatore</dc:creator>
<guid>http://installatore.wordpress.com/2009/09/13/linux-firewall-how-to-abort-cut-specific-connections/</guid>
<description><![CDATA[Alcune volte capita gestendo Firewall basati su distribuzioni Linux di dover killare eventuali conne]]></description>
<content:encoded><![CDATA[<div class='snap_preview'><p>Alcune volte capita gestendo Firewall basati su distribuzioni Linux di dover killare eventuali connessioni superfluee,o non autorizzate o più semplicemente terminare vpn lasciate aperte dagli impiegati piuttosto che terminare connessioni con alti consumi di banda nonchè peer-to-peer.Per fare ciò non possiamo affidarci al solito comando <strong>netstat </strong>dovremmo imparare a utilizzare altri due comandi disponibili in linux.</p>
<p>Il primo comando disponibile è il comando <strong>tcpkill</strong>.</p>
<p>La sintassi del comando è:</p>
<pre style="color:#000000;background-color:#f0f0f0;border:1px solid #c0c0c0;">tcpkill -i eth0 { expression }</pre>
<p>Per esempio per poter killare tutte le connessioni in uscita sulla porta 21 (ftp) potremmo usare il comando nella seguente maniera.</p>
<pre style="color:#000000;background-color:#f0f0f0;border:1px solid #c0c0c0;">tcpkill -i eth0 port 21</pre>
<p>Oppure bloccare completamente tutte le connessioni da e per un determinato host.</p>
<pre style="color:#000000;background-color:#f0f0f0;border:1px solid #c0c0c0;">tcpkill host 192.168.0.123</pre>
<p>Altrimenti bloccare tutti i pacchetti tra un determinato host e tutti gli altri pc in rete ad esclusione del nostro.</p>
<pre style="color:#000000;background-color:#f0f0f0;border:1px solid #c0c0c0;">tcpkill ip host 192.168.0.123 and not 192.168.0.15</pre>
<p>Il secondo è <strong>cutter</strong>.</p>
<p>Per esempio se volessimo terminare tutte le connessioni da un&#8217;host al resto del mondo.</p>
<pre style="color:#000000;background-color:#f0f0f0;border:1px solid #c0c0c0;">cutter 192.168.0.123</pre>
<p>Se invece ci interessa terminare solo le connessioni ssh.</p>
<pre style="color:#000000;background-color:#f0f0f0;border:1px solid #c0c0c0;">cutter 192.168.0.123 22</pre>
<p>Se vogliamo essere più specifici e bloccare tutte le connessioni ssh dal 192.168.0.123 al server remoto 123.123.123.123 la sintassi sarà la seguente.</p>
<pre style="color:#000000;background-color:#f0f0f0;border:1px solid #c0c0c0;">cutter 123.123.123.123 192.168.0.123 22</pre>
<p>Direi che questi 2 utilissimi comandi se usati in aggiunta ad iptraf o ad altri programmi di monitoring come ntop permettono anche l&#8217;automazione di eventuali operazioni ripetitive come la disconnessione do tutte le vpn alla fine del turno di lavoro.</p>
</div>]]></content:encoded>
</item>

</channel>
</rss>
