<?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>PinQ &#124; st. Mudo &#187; MikroTik</title>
	<atom:link href="http://blog.nazmi.web.id/category/mikrotik/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nazmi.web.id</link>
	<description>Lembar Coretan Memori ku</description>
	<lastBuildDate>Thu, 24 Jun 2010 11:28:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Mikrotik Two gateways failover</title>
		<link>http://blog.nazmi.web.id/2007/07/19/two-gateways-failover/</link>
		<comments>http://blog.nazmi.web.id/2007/07/19/two-gateways-failover/#comments</comments>
		<pubDate>Thu, 19 Jul 2007 02:44:35 +0000</pubDate>
		<dc:creator>Irving</dc:creator>
				<category><![CDATA[MikroTik]]></category>

		<guid isPermaLink="false">http://blog.nazmi.web.id/19/07/2007/two-gateways-failover/</guid>
		<description><![CDATA[This example explains how to use multiple gateways with one taking over when first fails. It begins with adding the gateways. Set bigger distance value for the secondary one, and check-gateway for the first one:
/ip route add gateway=192.168.1.1 check-gateway=ping
/ip route add gateway=192.168.2.1 distance=2
That&#8217;s all, there are no more steps!
The first gateway will begin as it&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.defactowireless.com/images/mikrotik_round.jpg" alt="" hspace="10" vspace="10" width="75" height="80" align="right" />This example explains how to use multiple gateways with one taking over when first fails. It begins with adding the gateways. Set bigger <strong>distance</strong> value for the secondary one, and <strong>check-gateway</strong> for the first one:</p>
<pre>/ip route add gateway=192.168.1.1 check-gateway=ping
/ip route add gateway=192.168.2.1 distance=2</pre>
<p>That&#8217;s all, there are no more steps!</p>
<p>The first gateway will begin as it&#8217;s distance is smaller (default 0); the check-gateway will make sure it&#8217;s up; when the ping will fail, it will disable the first gateway and the second will take over; when first one comes up, it will return to it&#8217;s function.</p>
<p><em>from wiki dot mikrotik dot com</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nazmi.web.id/2007/07/19/two-gateways-failover/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to import Mikrotik router configuration</title>
		<link>http://blog.nazmi.web.id/2007/05/14/import-router-configuration/</link>
		<comments>http://blog.nazmi.web.id/2007/05/14/import-router-configuration/#comments</comments>
		<pubDate>Mon, 14 May 2007 07:01:45 +0000</pubDate>
		<dc:creator>Irving</dc:creator>
				<category><![CDATA[MikroTik]]></category>

		<guid isPermaLink="false">http://blog.nazmi.web.id/2007/05/14/import-router-configuration/</guid>
		<description><![CDATA[The Import Command
			 			Command name: /import

Description
The root level command /import [file_name] restores the exported information from the specified file. This is used to restore configuration or part of it after a /system reset event or anything that causes configuration data loss.
Note that it is impossible to import the whole router configuration using this feature. It [...]]]></description>
			<content:encoded><![CDATA[<h3>The Import Command</h3>
<p><a title=".61.4.1" name=".61.4.1"></a>			 			Command name: <strong><em>/import</em></strong><br />
<a title=".61.4.2" name=".61.4.2"></a></p>
<h3>Description</h3>
<p>The root level command <strong>/import [file_name]</strong> restores the exported information from the specified file. This is used to restore configuration or part of it after a <strong>/system reset</strong> event or anything that causes configuration data loss.<span id="more-48"></span></p>
<p><strong>Note</strong> that it is impossible to import the whole router configuration using this feature. It can only be used to import a part of configuration (for example, firewall rules) in order to spare you some typing.</p>
<p><a title=".61.4.3" name=".61.4.3"></a></p>
<h3>Command Description</h3>
<p><strong>file=[filename]</strong>  &#8211; loads the exported configuration from a file to router 		 		<a title=".61.4.4" name=".61.4.4"></a></p>
<h3>Example</h3>
<p>To load the saved export file use the following command:</p>
<p><em>[admin@MikroTik] &gt; import address.rsc<br />
Opening script file address.rsc<br />
Script file loaded successfully<br />
[admin@MikroTik] &gt;</em></p>
<p><em>(from mikrotik dot com)</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nazmi.web.id/2007/05/14/import-router-configuration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to export Mikrotik router configuration</title>
		<link>http://blog.nazmi.web.id/2007/05/14/export-router-configuration/</link>
		<comments>http://blog.nazmi.web.id/2007/05/14/export-router-configuration/#comments</comments>
		<pubDate>Mon, 14 May 2007 06:58:15 +0000</pubDate>
		<dc:creator>Irving</dc:creator>
				<category><![CDATA[MikroTik]]></category>

		<guid isPermaLink="false">http://blog.nazmi.web.id/2007/05/14/export-router-configuration/</guid>
		<description><![CDATA[The Export Command
 			Command name: /export

Description
The export command prints a script that can be used to restore configuration. The command can be invoked at any menu level, and it acts for that menu level and all menu levels below it. If the argument from is used, then it is possible to export only specified items. [...]]]></description>
			<content:encoded><![CDATA[<h3>The Export Command</h3>
<p><a title=".61.3.1" name=".61.3.1"></a> 			Command name: <strong><em>/export</em></strong><br />
<a title=".61.3.2" name=".61.3.2"></a></p>
<h3>Description</h3>
<p>The <strong>export</strong> command prints a script that can be used to restore configuration. The command can be invoked at any menu level, and it acts for that menu level and all menu levels below it. If the argument <strong>from</strong> is used, then it is possible to export only specified items. In this case <strong>export</strong> does not descend recursively through the command hierarchy. <strong>export</strong> also has the argument <strong>file</strong>, which allows you to save the script in a file on the router to retrieve it later via FTP.<span id="more-47"></span></p>
<p><a title=".61.3.3" name=".61.3.3"></a></p>
<h3>Command Description</h3>
<p><strong>file=[filename]</strong>  &#8211; saves the export to a file<strong>from=[number]</strong>  &#8211; specifies from which item to start to generate the export file 			 		 		<a title=".61.3.4" name=".61.3.4"></a></p>
<h3>Example</h3>
<p><em>[admin@MikroTik] &gt; ip address print<br />
Flags: X &#8211; disabled, I &#8211; invalid, D &#8211; dynamic<br />
#   ADDRESS            NETWORK         BROADCAST       INTERFACE<br />
0   10.1.0.172/24      10.1.0.0        10.1.0.255      bridge1<br />
1   10.5.1.1/24        10.5.1.0        10.5.1.255      ether1<br />
[admin@MikroTik] &gt; </em></p>
<p>To make an export file:</p>
<p><em>[admin@MikroTik] ip address&gt; export file=address<br />
[admin@MikroTik] ip address&gt;</em></p>
<p>To make an export file from only one item:</p>
<p><em>[admin@MikroTik] ip address&gt; export file=address1 from=1<br />
[admin@MikroTik] ip address&gt;</em></p>
<p>To see the files stored on the router:</p>
<p><em>[admin@MikroTik] &gt; file print<br />
# NAME                            TYPE         SIZE       CREATION-TIME<br />
0  address.rsc                     script       315        dec/23/2003 13:21:48<br />
1  address1.rsc                    script       201        dec/23/2003 13:22:57<br />
[admin@MikroTik] &gt;</em></p>
<p>To export the setting on the display use the same command without the <strong>file</strong> argument:</p>
<p><em>[admin@MikroTik] ip address&gt; export from=0,1<br />
# nov/13/2004 13:25:30 by RouterOS 2.9<br />
# software id = MGJ4-MAN<br />
#<br />
/ ip address<br />
add address=10.1.0.172/24 network=10.1.0.0 broadcast=10.1.0.255 \<br />
interface=bridge1 comment=&#8221;" disabled=no<br />
add address=10.5.1.1/24 network=10.5.1.0 broadcast=10.5.1.255 \<br />
interface=ether1 comment=&#8221;" disabled=no<br />
[admin@MikroTik] ip address&gt;</em></p>
<p><em> (from mikrotik dot com)</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nazmi.web.id/2007/05/14/export-router-configuration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Backup &amp; Restore MikroTik Configuration</title>
		<link>http://blog.nazmi.web.id/2007/05/14/backup-restore-mikrotik-configuration/</link>
		<comments>http://blog.nazmi.web.id/2007/05/14/backup-restore-mikrotik-configuration/#comments</comments>
		<pubDate>Mon, 14 May 2007 06:50:40 +0000</pubDate>
		<dc:creator>Irving</dc:creator>
				<category><![CDATA[MikroTik]]></category>

		<guid isPermaLink="false">http://blog.nazmi.web.id/2007/05/14/backup-restore-mikrotik-configuration/</guid>
		<description><![CDATA[System Backup
 			Submenu level: /system backup

Description
The save command is used to store the entire router configuration in a backup file. The file is shown in the /file submenu. It can be downloaded via ftp to keep it as a backup for your configuration.
To restore the system configuration, for example, after a /system reset, it is [...]]]></description>
			<content:encoded><![CDATA[<h3>System Backup</h3>
<p><a title=".61.2.1" name=".61.2.1"></a> 			Submenu level: <strong><em>/system backup</em></strong><br />
<a title=".61.2.2" name=".61.2.2"></a></p>
<h3>Description</h3>
<p>The <strong>save</strong> command is used to store the entire router configuration in a backup file. The file is shown in the <strong>/file</strong> submenu. It can be downloaded via ftp to keep it as a backup for your configuration.<span id="more-46"></span></p>
<p>To restore the system configuration, for example, after a <strong>/system reset</strong>, it is possible to upload that file via ftp and load that backup file using <strong>load</strong> command in <strong>/system backup</strong> submenu.</p>
<p><a title=".61.2.3" name=".61.2.3"></a></p>
<h3>Command Description</h3>
<p><strong>load name=[filename]</strong>  &#8211; Load configuration backup from a file</p>
<p><strong>save name=[filename]</strong>  &#8211; Save configuration backup to a file 			 		 		<a title=".61.2.4" name=".61.2.4"></a></p>
<h3>Example</h3>
<p>To save the router configuration to file <strong>test</strong>:</p>
<p><em>[admin@MikroTik] system backup&gt; save name=test<br />
Configuration backup saved<br />
[admin@MikroTik] system backup&gt;</em></p>
<p>To see the files stored on the router:</p>
<p><em> [admin@MikroTik] &gt; file print<br />
# NAME                           TYPE         SIZE       CREATION-TIME<br />
0 test.backup                    backup       12567      sep/08/2004 21:07:50<br />
[admin@MikroTik] &gt;</em></p>
<h3>Example</h3>
<p>To load the saved backup file <strong>test</strong>:</p>
<p><em>[admin@MikroTik] system backup&gt; load name=test<br />
Restore and reboot? [y/N]: y<br />
&#8230;</em></p>
<p><em>(from mikrotik dot com)</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nazmi.web.id/2007/05/14/backup-restore-mikrotik-configuration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Resetting Your Mikrotik RouterOS</title>
		<link>http://blog.nazmi.web.id/2007/05/14/resetting-your-mikrotik-routeros/</link>
		<comments>http://blog.nazmi.web.id/2007/05/14/resetting-your-mikrotik-routeros/#comments</comments>
		<pubDate>Mon, 14 May 2007 06:36:58 +0000</pubDate>
		<dc:creator>Irving</dc:creator>
				<category><![CDATA[MikroTik]]></category>

		<guid isPermaLink="false">http://blog.nazmi.web.id/2007/05/14/resetting-your-mikrotik-routeros/</guid>
		<description><![CDATA[Configuration Reset
 			Command name: /system reset

Description
The command clears all configuration of the router and sets it to the default including the login name and password (&#8217;admin&#8217; and no password), IP addresses and other configuration is erased, interfaces will become disabled. After the reset command router will reboot.

Command Description
reset  &#8211; erases router&#8217;s configuration 		  [...]]]></description>
			<content:encoded><![CDATA[<h3>Configuration Reset</h3>
<p><a title=".61.5.1" name=".61.5.1"></a> 			Command name: <strong><em>/system reset</em></strong><br />
<a title=".61.5.2" name=".61.5.2"></a></p>
<h3>Description</h3>
<p>The command clears all configuration of the router and sets it to the default including the login name and password (&#8217;admin&#8217; and no password), IP addresses and other configuration is erased, interfaces will become disabled. After the <strong>reset</strong> command router will reboot.</p>
<p><a title=".61.5.3" name=".61.5.3"></a></p>
<h3>Command Description</h3>
<p><strong>reset</strong>  &#8211; erases router&#8217;s configuration 		     <a title=".61.5.4" name=".61.5.4"></a><span id="more-45"></span></p>
<h3>Notes</h3>
<p><a title=".61.5.4.1" name=".61.5.4.1"></a>If the router has been installed using netinstall and had a script specified as the initial configuration, the reset command executes this script after purging the configuration. To stop it doing so, you will have to reinstall the router.</p>
<p><em>[admin@MikroTik] &gt; system reset<br />
Dangerous! Reset anyway? [y/N]: n<br />
action cancelled<br />
[admin@MikroTik] &gt;</em></p>
<p><em>(from mikrotik dot com) </em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nazmi.web.id/2007/05/14/resetting-your-mikrotik-routeros/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Transparent Traffic Shaper</title>
		<link>http://blog.nazmi.web.id/2007/04/19/transparent-traffic-shaper/</link>
		<comments>http://blog.nazmi.web.id/2007/04/19/transparent-traffic-shaper/#comments</comments>
		<pubDate>Thu, 19 Apr 2007 03:44:43 +0000</pubDate>
		<dc:creator>Irving</dc:creator>
				<category><![CDATA[MikroTik]]></category>

		<guid isPermaLink="false">http://blog.nazmi.web.id/2007/04/19/transparent-traffic-shaper/</guid>
		<description><![CDATA[Introduction
This example shows how to configure a transparent traffic shaper. The transparent traffic shaper is essentially a bridge that is able to differentiate and prioritize traffic that passes through it.
Consider the following network layout:

We will configure one queue limiting the total throughput to the client and three sub-queues that limit HTTP, P2P and all other [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Introduction</strong></p>
<p>This example shows how to configure a transparent traffic shaper. The transparent traffic shaper is essentially a bridge that is able to differentiate and prioritize traffic that passes through it.</p>
<p>Consider the following network layout:</p>
<p><a href="http://wiki.mikrotik.com/wiki/Image:Transparent-shaper.png" class="image" title="Transparent-shaper.png"><img src="http://wiki.mikrotik.com/images/3/33/Transparent-shaper.png" alt="Transparent-shaper.png" longdesc="/wiki/Image:Transparent-shaper.png" height="705" width="481" /></a></p>
<p>We will configure one queue limiting the total throughput to the client and three sub-queues that limit HTTP, P2P and all other traffic separately. HTTP traffic will have priority above all other traffic types.<span id="more-16"></span></p>
<p><strong>Quick Start for Impatient</strong></p>
<p>Configuration snippet from the MikroTik router:<br />
<em> / interface bridge<br />
add name=&#8221;bridge1&#8243;<br />
/ interface bridge port<br />
add interface=ether2 bridge=bridge1<br />
add interface=ether3 bridge=bridge1</em></p>
<p><em>/ ip firewall mangle<br />
add chain=prerouting protocol=tcp dst-port=80 action=mark-connection \<br />
new-connection-mark=http_conn passthrough=yes<br />
add chain=prerouting connection-mark=http_conn action=mark-packet \<br />
new-packet-mark=http passthrough=no<br />
add chain=prerouting p2p=all-p2p action=mark-connection \<br />
new-connection-mark=p2p_conn passthrough=yes<br />
add chain=prerouting connection-mark=p2p_conn action=mark-packet \<br />
new-packet-mark=p2p passthrough=no<br />
add chain=prerouting action=mark-connection new-connection-mark=other_conn \<br />
passthrough=yes<br />
add chain=prerouting connection-mark=other_conn action=mark-packet \<br />
new-packet-mark=other passthrough=no</em></p>
<p><em>/ queue simple<br />
add name=&#8221;main&#8221; target-addresses=10.0.0.12/32 max-limit=256000/512000<br />
add name=&#8221;http&#8221; parent=main packet-marks=http max-limit=240000/500000<br />
add name=&#8221;p2p&#8221; parent=main packet-marks=p2p max-limit=64000/64000<br />
add name=&#8221;other&#8221; parent=main packet-marks=other max-limit=128000/128000</em></p>
<p><strong>Explanation</strong><br />
Each piece of code is followed by the explanation of what it actually does.</p>
<p><strong>Bridge</strong></p>
<p><em>/ interface bridge<br />
add name=&#8221;bridge1&#8243;<br />
/ interface bridge port<br />
add interface=ether2 bridge=bridge1<br />
add interface=ether3 bridge=bridge1</em></p>
<p>We create a new bridge interface and assign two ethernet interfaces to it. Thus the prospective traffic shaper will be completely transparent to the client.</p>
<p><strong>Mangle</strong></p>
<p><em>/ ip firewall mangle<br />
add chain=prerouting protocol=tcp dst-port=80 action=mark-connection \<br />
new-connection-mark=http_conn passthrough=yes<br />
add chain=prerouting connection-mark=http_conn action=mark-packet \<br />
new-packet-mark=http passthrough=no</em></p>
<p>All traffic destined to TCP port 80 is likely to be HTTP traffic and therefore is being marked with the packet mark http. Note, that the first rule has passthrough=yes while the second one has passthrough=no. (You can obtain additional information about mangle at http://www.mikrotik.com/docs/ros/2.9/ip/mangle)</p>
<p><em>/ ip firewall mangle<br />
add chain=prerouting p2p=all-p2p action=mark-connection \<br />
new-connection-mark=p2p_conn passthrough=yes<br />
add chain=prerouting connection-mark=p2p_conn action=mark-packet \<br />
new-packet-mark=p2p passthrough=no<br />
add chain=prerouting action=mark-connection new-connection-mark=other_conn \<br />
passthrough=yes<br />
add chain=prerouting connection-mark=other_conn action=mark-packet \<br />
new-packet-mark=other passthrough=no</em></p>
<p>Same as above, P2P traffic is marked with the packet mark p2p and all other traffic is marked with the packet mark other.<br />
<strong><br />
Queues</strong></p>
<p><em>/ queue simple<br />
add name=&#8221;main&#8221; target-addresses=10.0.0.12/32 max-limit=256000/512000</em></p>
<p>We create a queue that limits all the traffic going to/from the client (specified by the target-address) to 256k/512k.</p>
<p><em>/ queue simple<br />
add name=&#8221;http&#8221; parent=main packet-marks=http max-limit=240000/500000<br />
add name=&#8221;p2p&#8221; parent=main packet-marks=p2p max-limit=64000/64000<br />
add name=&#8221;other&#8221; parent=main packet-marks=other max-limit=128000/128000</em></p>
<p>All sub-queues have the main queue as the parent, thus the aggregate data rate could not exceed limits specified in the main queue. Note, that http queue has higher priority than other queues, meaning that HTTP downloads are prioritized.</p>
<p><em>(&#8211;Eugene  Mikrotik wiki)</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nazmi.web.id/2007/04/19/transparent-traffic-shaper/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>How to make a Mikrotik HotSpot gateway</title>
		<link>http://blog.nazmi.web.id/2007/04/19/how-to-make-a-hotspot-gateway/</link>
		<comments>http://blog.nazmi.web.id/2007/04/19/how-to-make-a-hotspot-gateway/#comments</comments>
		<pubDate>Thu, 19 Apr 2007 03:35:58 +0000</pubDate>
		<dc:creator>Irving</dc:creator>
				<category><![CDATA[MikroTik]]></category>

		<guid isPermaLink="false">http://blog.nazmi.web.id/2007/04/19/how-to-make-a-hotspot-gateway/</guid>
		<description><![CDATA[The MikroTik HotSpot Gateway enables providing of public network access for clients using wireless or wired network connections. HotSpot Gateway should have at least two network interfaces:
1. HotSpot interface, which is used to connect HotSpot clients
2. LAN/WAN interface, which is used to access network resources.
The following picture shows wireless HotSpot setup

To setup simple HotSpot Gateway [...]]]></description>
			<content:encoded><![CDATA[<p>The MikroTik HotSpot Gateway enables providing of public network access for clients using wireless or wired network connections. HotSpot Gateway should have at least two network interfaces:</p>
<p>1. HotSpot interface, which is used to connect HotSpot clients</p>
<p>2. LAN/WAN interface, which is used to access network resources.</p>
<p>The following picture shows wireless HotSpot setup</p>
<pre><a href="http://wiki.mikrotik.com/wiki/Image:Hotspot1.jpg" class="image" title="hotspot1.jpg"><img src="http://wiki.mikrotik.com/images/2/2c/Hotspot1.jpg" alt="hotspot1.jpg" longdesc="/wiki/Image:Hotspot1.jpg" height="352" width="488" /></a></pre>
<p>To setup simple HotSpot Gateway follow the steps below:</p>
<p>1. Configure wireless interface on HotSpot Gateway:<span id="more-15"></span></p>
<p><em>[admin@HotSpot_Gateway]&gt; interface wireless set wlan1 ssid=HotSpot band=2.4ghz-b \ &#8230; mode=ap-bridge</em></p>
<p>2. Configure ip address for HotSpot interface:</p>
<p><em>[admin@HotSpot_Gateway] &gt; ip add add address=192.168.0.1/24 interface=wlan1</em></p>
<p>3. Configure ip address for WAN/LAN interface:</p>
<p><em>[admin@HotSpot_Gateway] &gt; ip add add address=10.5.8.250/24 interface=ether1</em></p>
<p>4. Add a route on HotSpot Gateway</p>
<p><em>[admin@HotSpot_Gateway] &gt; ip route add gateway=10.5.8.1</em></p>
<p>5. Configure Hotspot on wlan1 interface and add user admin with pasword test</p>
<p><em>[admin@MikroTik] &gt; ip hotspot setup</em><br />
<em>hotspot interface: wlan1<br />
local address of network: 192.168.0.1/24<br />
masquerade network: yes<br />
address pool of network: 192.168.0.2-192.168.0.254<br />
select certificate: none<br />
ip address of smtp server: 0.0.0.0<br />
dns servers: 10.5.8.2<br />
dns name: hs.example.net<br />
name of local hotspot user: admin<br />
password for the user: test</em></p>
<p>In order to access network resources HotSpot clients have to configure their wireless interfaces setting proper ssid, band and mode, and enabling dynamic host configuration (dhcp) on the wireless interface.</p>
<p><em>(mikrotik wiki)</em></p>
<pre></pre>
<pre></pre>
<pre></pre>
]]></content:encoded>
			<wfw:commentRss>http://blog.nazmi.web.id/2007/04/19/how-to-make-a-hotspot-gateway/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Setup  DHCP Server di Mikrotik</title>
		<link>http://blog.nazmi.web.id/2007/04/18/contoh-bikin-dhcp-server-di-mikrotik/</link>
		<comments>http://blog.nazmi.web.id/2007/04/18/contoh-bikin-dhcp-server-di-mikrotik/#comments</comments>
		<pubDate>Wed, 18 Apr 2007 12:50:47 +0000</pubDate>
		<dc:creator>Irving</dc:creator>
				<category><![CDATA[MikroTik]]></category>

		<guid isPermaLink="false">http://blog.nazmi.web.id/2007/04/18/contoh-bikin-dhcp-server-di-mikrotik/</guid>
		<description><![CDATA[1.Buat IP address pool
/ip pool add name=dhcp-pool ranges=172.16.0.10-172.16.0.20
2. Tambahkan DHCP Network dan gatewaynya yang akan didistribusikan ke client
Pada contoh ini networknya adalah 172.16.0.0/24 dan gatewaynya 172.16.0.1
/ip dhcp-server network add address=172.16.0.0/12 gateway=172.16.0.1

3. Tambahkan DHCP Server ( pada contoh ini dhcp diterapkan pada interface ether2 )
/ip dhcp-server add interface=ether2 address-pool=dhcp-pool
4. Jangan Lupa dibuat enable dulu dhcp servernya
/ip [...]]]></description>
			<content:encoded><![CDATA[<p><strong>1.Buat IP address pool</strong></p>
<p><em>/ip pool add name=dhcp-pool ranges=172.16.0.10-172.16.0.20</em></p>
<p><strong>2. Tambahkan DHCP Network dan gatewaynya yang akan didistribusikan ke client</strong></p>
<p>Pada contoh ini networknya adalah 172.16.0.0/24 dan gatewaynya 172.16.0.1</p>
<p><em>/ip dhcp-server network add address=172.16.0.0/12 gateway=172.16.0.1</em><br />
<span id="more-13"></span><br />
<strong>3. Tambahkan DHCP Server</strong> ( pada contoh ini dhcp diterapkan pada interface ether2 )</p>
<p><em>/ip dhcp-server add interface=ether2 address-pool=dhcp-pool</em></p>
<p><strong>4. Jangan Lupa dibuat enable dulu dhcp servernya</strong></p>
<p><em>/ip dhcp-server enable 0</em></p>
<p><strong>5. Tes Dari client</strong></p>
<p><em>(from internet)</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nazmi.web.id/2007/04/18/contoh-bikin-dhcp-server-di-mikrotik/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Redirect Mail traffic to a specified Mail Server</title>
		<link>http://blog.nazmi.web.id/2007/04/17/redirect-mail-traffic-to-a-specified-mail-server/</link>
		<comments>http://blog.nazmi.web.id/2007/04/17/redirect-mail-traffic-to-a-specified-mail-server/#comments</comments>
		<pubDate>Tue, 17 Apr 2007 04:07:54 +0000</pubDate>
		<dc:creator>Irving</dc:creator>
				<category><![CDATA[MikroTik]]></category>

		<guid isPermaLink="false">http://blog.nazmi.web.id/2007/04/17/redirect-mail-traffic-to-a-specified-mail-server/</guid>
		<description><![CDATA[This is if you want to redirect all traffic through your router to your own specified mail server. This is usefull if you have many clients from different locations connecting to your network at different times. (Note that if you are using Hotspot you can do this in the Hotspot settings instead)
ip firewall nat add [...]]]></description>
			<content:encoded><![CDATA[<p>This is if you want to redirect all traffic through your router to your own specified mail server. This is usefull if you have many clients from different locations connecting to your network at different times. (Note that if you are using Hotspot you can do this in the Hotspot settings instead)</p>
<p><em>ip firewall nat add chain=dstnat protocol=tcp dst-port=25 action=dst-nat to-addresses=10.0.0.1 to-ports=25 </em></p>
<p>This will redirect all smtp (port 25) traffic out the router to ip address 10.0.0.1</p>
<p><em>(mikrotik wiki)</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nazmi.web.id/2007/04/17/redirect-mail-traffic-to-a-specified-mail-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Setting Mikrotik Wireless Bridge</title>
		<link>http://blog.nazmi.web.id/2007/04/14/setting-mikrotik-wireless-bridge/</link>
		<comments>http://blog.nazmi.web.id/2007/04/14/setting-mikrotik-wireless-bridge/#comments</comments>
		<pubDate>Sat, 14 Apr 2007 02:56:02 +0000</pubDate>
		<dc:creator>Irving</dc:creator>
				<category><![CDATA[MikroTik]]></category>

		<guid isPermaLink="false">http://blog.nazmi.web.id/2007/04/14/setting-mikrotik-wireless-bridge/</guid>
		<description><![CDATA[Sering kali, kita ingin menggunakan Mikrotik Wireless untuk solusi point to point  dengan mode jaringan bridge (bukan routing). Namun, Mikrotik RouterOS sendiri  didesain bekerja dengan sangat baik pada mode routing. Kita perlu melakukan beberapa  hal supaya link wireless kita bisa bekerja untuk mode bridge.Mode bridge memungkinkan network yang satu tergabung dengan network [...]]]></description>
			<content:encoded><![CDATA[<p>Sering kali, kita ingin menggunakan Mikrotik Wireless untuk solusi point to point  dengan mode jaringan bridge (bukan routing). Namun, Mikrotik RouterOS sendiri  didesain bekerja dengan sangat baik pada mode routing. Kita perlu melakukan beberapa  hal supaya link wireless kita bisa bekerja untuk mode bridge.Mode bridge memungkinkan network yang satu tergabung dengan network di sisi satunya  secara transparan, tanpa perlu melalui routing, sehingga mesin yang ada di network  yang satu bisa memiliki IP Address yang berada dalam 1 subnet yang sama dengan  sisi lainnya.</p>
<p>Namun, jika jaringan wireless kita sudah cukup besar, mode bridge ini akan membuat  traffic wireless meningkat, mengingat akan ada banyak traffic broadcast dari network  yang satu ke network lainnya. Untuk jaringan yang sudah cukup besar, saya menyarankan  penggunaan mode routing.</p>
<p>Berikut ini adalah diagram network yang akan kita set.<br />
<img src="http://www.mikrotik.co.id/images/artikel/wireless-bridge-01-new.jpg" height="88" width="435" /><br />
<span id="more-11"></span><br />
<img src="http://www.mikrotik.co.id/images/line.gif" height="18" width="438" /></p>
<p><strong>Konfigurasi Pada Access Point</strong></p>
<p>1. Buatlah sebuah interface bridge yang baru, berilah nama bridge1</p>
<p><img src="http://www.mikrotik.co.id/images/artikel/wireless-bridge-02.jpg" height="248" width="435" /></p>
<p>2. Masukkan ethernet ke dalam interface bridge</p>
<p><img src="http://www.mikrotik.co.id/images/artikel/wireless-bridge-03.jpg" height="245" width="435" /></p>
<p>3.  Masukkan IP Address pada interface bridge1</p>
<p><img src="http://www.mikrotik.co.id/images/artikel/wireless-bridge-04.jpg" height="209" width="435" /></p>
<p>4. Selanjutnya adalah setting wireless interface. Kliklah pada menu Wireless  (1), pilihlah tab interface (2) lalu double click pada nama interface wireless  yang akan digunakan (3). Pilihlah mode AP-bridge (4), tentukanlah ssid (5), band  2.4GHz-B/G (6), dan frekuensi yang akan digunakan (7). Jangan lupa mengaktifkan  default authenticated (8) dan default forward (9). Lalu aktifkankanlah interface  wireless (10) dan klik OK (11).</p>
<p><img src="http://www.mikrotik.co.id/images/artikel/wireless-bridge-05.jpg" height="528" width="435" /></p>
<p>5. Berikutnya adalah konfigurasi WDS pada wireless interface yang digunakan.  Bukalah kembali konfigurasi wireless seperti langkah di atas, pilihlah tab WDS  (1). Tentukanlah WDS Mode dynamic (2) dan pilihlah bridge interface untuk WDS  ini (3). Lalu tekan tombol OK.</p>
<p><img src="http://www.mikrotik.co.id/images/artikel/wireless-bridge-06.jpg" height="414" width="415" /></p>
<p>6. Langkah selanjutnya adalah menambahkan virtual interface WDS. Tambahkan interface  WDS baru seperti pada gambar, lalu pilihlah interface wireless yang kita gunakan  untuk WDS ini. Lalu tekan OK.</p>
<p><img src="http://www.mikrotik.co.id/images/artikel/wireless-bridge-07.jpg" height="312" width="435" /></p>
<p>7. Jika WDS telah ditambahkan, maka akan tampak interface WDS baru seperti pada  gambar di bawah.</p>
<p><img src="http://www.mikrotik.co.id/images/artikel/wireless-bridge-08.jpg" height="156" width="435" /><br />
<img src="http://www.mikrotik.co.id/images/line.gif" height="18" width="438" /></p>
<p><strong>Konfigurasi pada Wireless Station</strong></p>
<p>Konfigurasi pada wireless station hampir sama dengan langkah-langkah di atas,  kecuali pada langkah memasukkan IP Address dan konfigurasi wirelessnya. Pada konfigurasi  station, mode yang digunakan adalah <em>station-wds</em>, frekuensi tidak perlu ditentukan, namun harus menentukan scan-list di mana  frekuensi pada access point masuk dalam scan list ini. Misalnya pada access point  kita menentukan frekuensi 2412, maka tuliskanlah scan-list 2400-2500.<br />
<img src="http://www.mikrotik.co.id/images/artikel/wireless-bridge-09.jpg" height="525" width="435" /></p>
<p><img src="http://www.mikrotik.co.id/images/line.gif" height="18" width="438" /><br />
<strong>Pengecekan link</strong></p>
<p>Jika link wireless yang kita buat sudah bekerja dengan baik, maka pada menu wireless,  akan muncul status R (lihat gambar di bawah).</p>
<p><img src="http://www.mikrotik.co.id/images/artikel/wireless-bridge-10.jpg" height="179" width="435" /><br />
Selain itu, mac-address dari wireless yang terkoneksi juga bisa dilihat pada  jendela registration (lihat gambar di bawah).</p>
<p><img src="http://www.mikrotik.co.id/images/artikel/wireless-bridge-11.jpg" height="179" width="435" /></p>
<p><strong><img src="http://www.mikrotik.co.id/images/line.gif" height="18" width="438" /><br />
</strong></p>
<p><strong>Konfigurasi keamanan jaringan wireless</strong></p>
<p>Pada Mikrotik, cara paling mudah untuk menjaga keamanan jaringan adalah dengan  mendaftarkan mac-address wireless pasangan pada access list. Hal ini harus dilakukan  pada sisi access point maupun pada sisi client. Jika penginputan access-list telah  dilakukan, maka matikanlah fitur <em>default authenticated </em>pada wireless, maka wireless lain yang mac addressnya tidak terdaftar tidak akan  bisa terkoneksi ke jaringan kita.</p>
<p>Jika kita menginginkan fitur keamanan yang lebih baik, kita juga bisa menggunakan  enkripsi baik WEP maupun WPA.</p>
<p><em>(www.mikrotik.co.id)</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nazmi.web.id/2007/04/14/setting-mikrotik-wireless-bridge/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

