<?xml version="1.0" encoding="UTF-8"?>
<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/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>human.network.web.id &#187; mangle</title>
	<atom:link href="http://human.network.web.id/tag/mangle/feed/" rel="self" type="application/rss+xml" />
	<link>http://human.network.web.id</link>
	<description>forward packet..forward paket..repeat until powered off</description>
	<lastBuildDate>Tue, 17 Jan 2012 05:42:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Mikrotik: membuat hotspot baypass traffic IIX</title>
		<link>http://human.network.web.id/2008/07/24/hotspot-baypass-iix/</link>
		<comments>http://human.network.web.id/2008/07/24/hotspot-baypass-iix/#comments</comments>
		<pubDate>Thu, 24 Jul 2008 08:48:53 +0000</pubDate>
		<dc:creator>human</dc:creator>
				<category><![CDATA[Mikrotik]]></category>
		<category><![CDATA[baypass]]></category>
		<category><![CDATA[default]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[human.network]]></category>
		<category><![CDATA[iix]]></category>
		<category><![CDATA[lokal]]></category>
		<category><![CDATA[mangle]]></category>
		<category><![CDATA[marking]]></category>
		<category><![CDATA[mikrotik]]></category>
		<category><![CDATA[simple queue]]></category>

		<guid isPermaLink="false">http://human.network.web.id/?p=136</guid>
		<description><![CDATA[Karena pertanyaan dari mas andy (andy_m3m@yahoo.co.id) di topik hotspot sebelumnya. Saya buatkan post sendiri untuk masalah ini. Di tempat saya, saya sudah mengaplikasikan ini sekitar 2~3 bulan yang lalu. Pada saat itu memang kebutuhan saya untuk melimit internasional agar terbagi rata, tetapi untuk ke IIX tidak di limit. Rupa-nya tidak hanya saya yang berniat dengan [...]]]></description>
		<wfw:commentRss>http://human.network.web.id/2008/07/24/hotspot-baypass-iix/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
		<item>
		<title>Squid zph and Mikrotik</title>
		<link>http://human.network.web.id/2008/07/03/squid-zph-and-mikrotik/</link>
		<comments>http://human.network.web.id/2008/07/03/squid-zph-and-mikrotik/#comments</comments>
		<pubDate>Thu, 03 Jul 2008 12:41:38 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[proxy]]></category>
		<category><![CDATA[baypass]]></category>
		<category><![CDATA[default]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[HIT]]></category>
		<category><![CDATA[hotspot]]></category>
		<category><![CDATA[htb]]></category>
		<category><![CDATA[interface]]></category>
		<category><![CDATA[limit]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[mail]]></category>
		<category><![CDATA[mangle]]></category>
		<category><![CDATA[marking]]></category>
		<category><![CDATA[mikrotik]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[Penalty]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[queue]]></category>
		<category><![CDATA[router]]></category>
		<category><![CDATA[simple]]></category>
		<category><![CDATA[squid]]></category>
		<category><![CDATA[tcp]]></category>
		<category><![CDATA[tos]]></category>
		<category><![CDATA[vi]]></category>
		<category><![CDATA[youtube]]></category>
		<category><![CDATA[Zero]]></category>
		<category><![CDATA[zph]]></category>

		<guid isPermaLink="false">http://human.network.web.id/?p=114</guid>
		<description><![CDATA[Bonus tambahan dari squid 2.7-stable3 adalah fungsi zph yang sudah terintegrasi. ZPH sendiri adalah Zero Penalty Hit, penjelasan-nya bisa dibaca di http://zph.bratcheda.org/ Pada 2.7 sudah masuk dalam core engine squid. Sebelum versi 2.7 harus melakukan patch. Tutorial di bawah ini saya memakai squid dari caching youtube. Ide dari pemakaian ZPH ini adalah ketika memutar video [...]]]></description>
		<wfw:commentRss>http://human.network.web.id/2008/07/03/squid-zph-and-mikrotik/feed/</wfw:commentRss>
		<slash:comments>60</slash:comments>
		</item>
		<item>
		<title>Bypass traceroute traffic</title>
		<link>http://human.network.web.id/2008/01/24/bypass-traceroute-traffic/</link>
		<comments>http://human.network.web.id/2008/01/24/bypass-traceroute-traffic/#comments</comments>
		<pubDate>Thu, 24 Jan 2008 02:43:59 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Mikrotik]]></category>
		<category><![CDATA[baypass]]></category>
		<category><![CDATA[default]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[icmp]]></category>
		<category><![CDATA[interface]]></category>
		<category><![CDATA[limit]]></category>
		<category><![CDATA[mangle]]></category>
		<category><![CDATA[mikrotik]]></category>
		<category><![CDATA[port]]></category>
		<category><![CDATA[queue]]></category>
		<category><![CDATA[simple]]></category>
		<category><![CDATA[tcp]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[traceroute]]></category>
		<category><![CDATA[udp]]></category>

		<guid isPermaLink="false">http://human.network.web.id/2008/01/24/bypass-traceroute-traffic/</guid>
		<description><![CDATA[Pada mesin modern, aplikasi traceroute biasa mempergunakan protokol UDP dari pada ICMP. Oleh karena itu bila admin sudah membaypass icmp, maka yang di dapat ping time akan stabil pada saat utilitas traffic full. Tapi pada saat kondisi yang sama bila dilakukan traceroute, hasilnya berbeda signifikan. Setelah menganalisa paket traceroute dengan tcpdump dan panduan dari wiki, [...]]]></description>
		<wfw:commentRss>http://human.network.web.id/2008/01/24/bypass-traceroute-traffic/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Burst for each TCP connection</title>
		<link>http://human.network.web.id/2008/01/11/burst-for-each-tcp-connection/</link>
		<comments>http://human.network.web.id/2008/01/11/burst-for-each-tcp-connection/#comments</comments>
		<pubDate>Fri, 11 Jan 2008 16:36:59 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Mikrotik]]></category>
		<category><![CDATA[default]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[forward]]></category>
		<category><![CDATA[ip mangle]]></category>
		<category><![CDATA[limit]]></category>
		<category><![CDATA[mangle]]></category>
		<category><![CDATA[marking]]></category>
		<category><![CDATA[mbits]]></category>
		<category><![CDATA[mikrotik]]></category>
		<category><![CDATA[pcq]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[queue]]></category>
		<category><![CDATA[queue tree]]></category>
		<category><![CDATA[tcp]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[TTL]]></category>
		<category><![CDATA[user]]></category>
		<category><![CDATA[vi]]></category>

		<guid isPermaLink="false">http://human.network.web.id/2008/01/11/burst-for-each-tcp-connection/</guid>
		<description><![CDATA[Diambil dari http://forum.mikrotik.com/viewtopic.php?t=12870 This is little how-to create manual burst using queue tree. As it is bandwidth control using queue tree first we need to mangle traffic first i mangle all connections, then i mark first 2Mbytes then i mark the rest of packets /ip firewall mangle add chain=forward protocol=tcp \ action=mark-connection \ new-connection-mark=new_conn passthrough=yes [...]]]></description>
		<wfw:commentRss>http://human.network.web.id/2008/01/11/burst-for-each-tcp-connection/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to convert a MT box in an Anti Spam server with v2.9</title>
		<link>http://human.network.web.id/2008/01/11/how-to-convert-a-mt-box-in-an-anti-spam-server-with-v29/</link>
		<comments>http://human.network.web.id/2008/01/11/how-to-convert-a-mt-box-in-an-anti-spam-server-with-v29/#comments</comments>
		<pubDate>Fri, 11 Jan 2008 16:15:42 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Mikrotik]]></category>
		<category><![CDATA[ACCEPT]]></category>
		<category><![CDATA[antispam]]></category>
		<category><![CDATA[check]]></category>
		<category><![CDATA[dnsbl]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[HIT]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[icmp]]></category>
		<category><![CDATA[icon]]></category>
		<category><![CDATA[lease]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[live]]></category>
		<category><![CDATA[mail]]></category>
		<category><![CDATA[mangle]]></category>
		<category><![CDATA[mikrotik]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[nth]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[port]]></category>
		<category><![CDATA[postfix]]></category>
		<category><![CDATA[smtp]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[tcp]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[TTL]]></category>
		<category><![CDATA[tx]]></category>
		<category><![CDATA[vi]]></category>
		<category><![CDATA[xp]]></category>

		<guid isPermaLink="false">http://human.network.web.id/2008/01/11/how-to-convert-a-mt-box-in-an-anti-spam-server-with-v29/</guid>
		<description><![CDATA[Diambil dari http://forum.mikrotik.com/viewtopic.php?t=15721 Hi there, for months I have the idea how to transform one Mikrotik OS in an Anti Spam server. After more than 20 days applying few scripts, firewall rules and address list, I have achieved reduce from 45.000 mails per day to only 11.000/12.000 without many complaints from my customers. Before continuing, [...]]]></description>
		<wfw:commentRss>http://human.network.web.id/2008/01/11/how-to-convert-a-mt-box-in-an-anti-spam-server-with-v29/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Bypass icmp via htb.init</title>
		<link>http://human.network.web.id/2008/01/11/bypass-icmp-via-htb/</link>
		<comments>http://human.network.web.id/2008/01/11/bypass-icmp-via-htb/#comments</comments>
		<pubDate>Fri, 11 Jan 2008 14:13:14 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[baypass]]></category>
		<category><![CDATA[default]]></category>
		<category><![CDATA[eth0]]></category>
		<category><![CDATA[eth1]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[htb]]></category>
		<category><![CDATA[icmp]]></category>
		<category><![CDATA[mangle]]></category>
		<category><![CDATA[noc]]></category>
		<category><![CDATA[semarang]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[vi]]></category>

		<guid isPermaLink="false">http://human.network.web.id/2008/01/11/bypass-icmp-via-htb/</guid>
		<description><![CDATA[Kalau pakai script htb.init biasa kita bisa membaypass icmp supaya ping time kecil. Selama ini saya berpikir untuk membaypass harus pakai teknik mangle di firewall. Ternyata hal itu tidak sepenuhnya benar. Setelah di ajari oleh master-nya noc isp di semarang baru tahu saya, kalau itu bisa tanpa mangle. Procedurenya : buka file htb.init di /var/cache [...]]]></description>
		<wfw:commentRss>http://human.network.web.id/2008/01/11/bypass-icmp-via-htb/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to prevent NATed access</title>
		<link>http://human.network.web.id/2008/01/08/how-to-prevent-nated-access/</link>
		<comments>http://human.network.web.id/2008/01/08/how-to-prevent-nated-access/#comments</comments>
		<pubDate>Tue, 08 Jan 2008 04:22:27 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Mikrotik]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[forward]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[icmp]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[live]]></category>
		<category><![CDATA[mail]]></category>
		<category><![CDATA[mangle]]></category>
		<category><![CDATA[mikrotik]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[router]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[TTL]]></category>
		<category><![CDATA[user]]></category>
		<category><![CDATA[vi]]></category>
		<category><![CDATA[Zero]]></category>

		<guid isPermaLink="false">http://human.network.web.id/2008/01/08/how-to-prevent-nated-access/</guid>
		<description><![CDATA[Sesuai dengan judul diatas, inti dari kasus ini adalah penyedia jasa tidak ingin BW yang diberikan kepada user di sharing lagi mempergunakan nat-router. Ilmu baru buat saya, dengan memberikan TTL=1 ?, mmmm aneh sekali. Hasil dari googling di wikipedia di dapat informasi sebagai berikut : The TTL field is set by the sender of the [...]]]></description>
		<wfw:commentRss>http://human.network.web.id/2008/01/08/how-to-prevent-nated-access/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

