Mikrotik How To

It has thirteen individual gigabit Ethernet ports, two 5-port switch groups, and includes Ethernet bypass capability. 2GB of SODIMM RAM are included, there is one microSD card slot, a beeper and a serial port. The RB1100AH comes preinstalled in a 1U aluminium rackmount case, assembled and ready to deploy.


CPU PowerPC P2020 dual core 1066MHz network CPU with IPsec accelerator Memory SODIMM DDR Slot, 2GB installed (RouterOS will use only up to 1.5GB) Boot loader RouterBOOT, 1Mbit Flash chip Data storage Onboard NAND memory chip, one microSD card slot Ethernet Thirteen 10/100/1000 Mbit/s Gigabit Ethernet with Auto-MDI/X Ethernet Includes switch to enable Ethernet bypass mode in two ports miniPCI none Serial port One DB9 RS232C asynchronous serial port.

Extras Reset switch, beeper, voltage and temperature sensors Power options Built-in power supply (IEC C14 standard connector 110/220V), PoE (12- 24V on port 13) Fan Built in fans, and Fan headers Dimensions 1U case: 44 x 176 x 442 mm, 1275g. Board only: 365g Operating System MikroTik RouterOS, Level 6 license.

R52nM dual band miniPCI card (300mW 2.4Ghz & 5Ghz)  Support in 802.11a/b/g/n with MMCX connectors gift you excellent perfomance for your wireless backbone.
Dual band IEEE 802.11a/b/g/n standard
• Output Power of up to 23dBm
• Support for up to 2x2 MIMO with spatial multiplexing
• Four times the throughput of 802.11a/g
• Atheros AR9220, chipset
• High Performance (up to 300Mbps physical data rates and 200Mbps of actual user throughput) with Low Power Consumption
• Two MMCX antenna connectors
• Modulations:
OFDM: BPSK, QPSK, 16 QAM, 64QAM
DSSS: DBPSK, DQPSK, CCK
• Operating temperatures: -50ºC to 60ºC
• Power consumption MAX 1.95W
• ESD protection +/- 12kV

http://www.balticnetworks.com/mikrotik-r52nm-802-11a-b-g-n-300mw-minipci-card-with-(mmcx-.connectors.html).

Wireless retransmission is when the card sends out a frame and you don't receive back the acknowledgment (ACK), you send out the frame once more till you get back the acknowledgment. Wireless retransmits can increase the latency and also lower the throughput of the wireless link.

To check if the wireless connection has wireless retransmissions you need to compare two fields in the wireless registration table: frames and hw-frames. If the hw-frames value is bigger than frames value then it means that the wireless link is making retransmissions. If the difference is not so big, it can be ignored, but if the hw-frames count it two, three or four times or even bigger than the frames count then you need to troubleshoot this wireless connection.

(wm).

7.5 dBi antenna
400 Mhz proc
32 MB RAM
MSRP $119

Webfig Skins

They talk about webfig skins. This gives you the ability to customize the webfig interface. The only downside is that you don’t have the option to make the base page load straight to webfig when you browse to the router. It still loads to the generic Mikrotik screen which gives you the menu options for webfix/winbox/etc.

Wireless Options Simplified

They’ve merged ht-extension-channels into the channel-width option.

SXT Reflector

They highlight a 3rd party reflector that you mount the SXT on that narrows the beam with down by 20 dBi…25 down to 5. They are saying it buys you an extra 7KM.
Nothing really blowing my skirt up, but at least more product is hitting the market.




(gsw).

Mikrotik Wireless Point To Point Setup - When you are looking at a point to point (P2P) wireless link you will hear people mention “line of sight”. As in, if I stand at one point can I see where the other antenna will be mounted. I once thought “as long as I can see the other antenna, I’m good…right?” Not exactly. There is this tiny thing called the Fresnel zone.
Wikipedia will give you the complete scoop, so I will paraphrase The Fzone is the shape of the wireless signal between two radios.

What most people don’t realize is that the wireless Fzone between two radios is shaped like a football. It is actually fatter in the middle and tapers down towards the ends. What this means is that if you have a large obstruction in the middle of your Fzone, you will get degraded signal. Degraded signal means lower throughput and possibly no connection at all! So, how does one figure all this mess out?
Find point A’s elevation, point B’s elevation and the elevation of point M, which is the halfway point between A and B. A great place to find this info is here. This is Daft Logics altitude finder. It will give you the altitude for a point on a google map.
Lets say that site A is 100′, B is 200′ and M is 120′.

What we want to do is take the site with the lowest elevation and make it 0 by subtracting itself:
Site A now: 100 – 100 = 0
Then subtract Site A’s original value from the other sites:
Site B now: 200 – 100 = 100
Site M now: 120 – 100 = 20
Site A = 0, site B = 100 and site M = 20.

Then find the distance between point A and B “as the crow flies”, aka a straight line. You can again use Daft Logic for this.
We will say that our distance is 10 miles.
Now visit an Fzone calculator like this one. Put in your distance and frequency and it will give you the height of the Fzone at midpoint. I’m saying my distance is 10 miles and my frequency is 5800. This gives me an Fzone height of 46′ at 5 miles (the halfway point).
So using all of this information I know that my Fzone midpoint will be 50′ at 5 miles(site A elevation + site B elevation / 2). This is the center of the Fzone at 5 miles, and we know that from our Fzone calc that the Fzone is 46′. If we divide that in half, we get 23′. So now we take our 50′ midpoint for the Fzone, subtract 23′ and last subtract the mid point M’s elevation which is 20 and we end up with 7′.

It looks like the earth isn’t hitting our Fzone, but if anything stands higher than 7′ at that mid point, it will start to eat into our Fzone. What can we do? We can raise up our antennas to increase our distance from earth.

(gsw) .

This is my first post about the Mikrotik Product.  I will be putting up several examples in the coming weeks and months, so if you don’t see what you are looking for, be sure to contact me directly.  Leaving a comment is fine, but not likely to be “answered” unless it is a clarification for the specific article.
This article is intended to be a short guide to help you configure a Mikrotik router to behave in a way that is similar to a soho router with a wireless connection upstream.  This configuration is perfect for a WISP that is using devices like the RouterBoard 411 (priced at about $59), along with a CM9 or similar radio (about $40), associated power supply, outdoor enclosure/antenna, etc.  The total cost of a flexible device like this is about $150-160, including everything needed to install at a customer’s house or business.

This particular configuration features a DHCP server for the LAN clients, wireless upstream and a NAT function that will allow you, the WISP, to only require a single IP for the customer.  For the impatient, you can scroll to the bottom for a CUT/PASTE complete script without further ado.  For those that WANT further ado, read on…
Step one with a newly opened RouterBoard product is to log into the board.  Other articles explain that process, so I won’t take time to do it here.
Now, on with the explanation:
# Get rid of any static routes
/ip route remove [find]

This removes any routes that may have been added by the vendor you purchased your router from.  There are a few that may set this up.
#turn on all interfaces and delay for 3 seconds
/interface enable [find]
:delay 3
This bit of code will enable all interfaces on the router (including the wlan card, which is not “on” by default).  The “:delay 3″ line causes a pause in the processing of the script.  This allows time for the system to load the drivers for the wlan card.
# Set SSID and band
/ interface wireless
set wlan1 mode=station ssid="SET_ME" band=2.4ghz-b/g disabled=no
This is where you will configure the parameters for the operation of the wlan card.  In this example, we set the card to operate as a 2.4GHz client in either “b” or “g” mode.  Your network may be different, so set this accordingly.  You can determine the supported bands with the following command:
/interface wireless info print
The CM9 card, for example, supports the following bands:
2ghz-b, 5ghz, 2ghz-g, 5ghz-10mhz, 5ghz-5mhz, 2ghz-10mhz, 2ghz-5mhz
#Next, we set the identity:
#Set customer name here -- no spaces or crazy characters please
/system identity
set name="client_NAME"

This is the name that will show up in the top of Winbox and as part of the prompt in terminal mode.  You will, also, see this name in the “neighbor list” of other local routers (“/ip neighbor print”).  Setting this makes it pretty easy to see which device is which when connecting to multiple routers.
# Set the wireless card to get an IP via DHCP
/ ip dhcp-client
add interface=wlan1 add-default-route=yes use-peer-dns=yes \
use-peer-ntp=yes comment="This interface talks to the tower" disabled=no

If you provide your customers with an IP address via DHCP server at the AP, then this is the code you will use to set up the client side.  If you assign your customer a static IP address, then you can add that IP below and leave this portion of the configuration out.
# This should be the IP inside the network...
# Doesn't need to be changed unless the network demands it (private network)
/ ip address
add address=192.168.7.1/24 interface=ether1 \
comment="This is the customer's gateway" disabled=no

We are assigning the CUSTOMER LAN address here.  If they are using a different range of addresses (static assignments), then you may need to alter this address and the DHCP server below.  Also, you can add the “outside interface” (wlan card) IP address assignment here if that is the way your network functions.  You just have to duplicate the last 2 lines and set the “interface” to “wlan1″ and set the address appropriately.  Also, you will have to add the default route as follows:
/ip route add gateway=10.10.10.1
Just be sure that you set the gateway appropriately for your network.
# Configuration for the DHCP server for the LAN
/ ip pool
add name="dhcp_pool1" ranges=192.168.7.100-192.168.7.200
/ ip dhcp-server
add name="dhcp1" interface=ether1 lease-time=1d address-pool=dhcp_pool1 \
bootp-support=static authoritative=yes disabled=no
/ ip dhcp-server network
add address=192.168.7.0/24 gateway=192.168.7.1 dns-server=4.2.2.3

This code does several things, but as a whole, it sets up a DHCP server on the LAN side of the network.  If you changed the LAN IP above, you will need to make adjustments in this section of the configuration.  Note that the “dns-server” setting here is the server that is sent to the LAN clients.
# You can change the DNS to be what you want
/ ip dns
set primary-dns=4.2.2.2 secondary-dns=4.2.2.3 \
allow-remote-requests=yes cache-size=2048KiB cache-max-ttl=1w

Strictly speaking, the DNS servers here are not necessary, but are advised.  Just ensure that you use working DNS servers here.  One reason you may want to set these is if you want to create a caching dns server for the LAN clients.  If you want to do this, you can set the “dns-server” parameter above to point to the 192.168.7.1 (ether1 IP) address.  Note the option above that says “allow-remote-requests=yes“.  That is not a default setting (it’s off by default), so be sure that you turn it on if you want the caching dns server to work.
/ ip firewall nat
add chain=srcnat out-interface=wlan1 src-address=192.168.7.0/24 \
action=masquerade disabled=no
This section only has to be changed if you made changes to the LAN IP address above.  This is the code that sets up the router to masquerade (NAT) traffic out the wlan port.
That’s all there is to it! Below you will find the full script ready for you to hack to fit your network.  Just copy this code to the clipboard (highlight it, then hit CTRL-C), then paste it into notepad (or other favorite text editor), make appropriate changes and save it somewhere that is convenient for you.  To use it on a router, you simply connect to the NEW router, open a “New Terminal”, RIGHT-CLICK in the window and select paste.  That’s all there is to it!  Here’s the script in it’s entirety:
# Get rid of any static routes
/ip route remove [find]
#turn on all interfaces and delay for 3 seconds
/interface enable [find]
:delay 3
# Set SSID and band
/ interface wireless
set wlan1 mode=station ssid="SET_ME" band=2.4ghz-b/g disabled=no
#Set customer name here -- no spaces or crazy characters please
/system identity
set name="client_NAME"
# Set the wireless card to get an IP via DHCP
/ ip dhcp-client
add interface=wlan1 add-default-route=yes use-peer-dns=yes \
use-peer-ntp=yes comment="This interface talks to the tower" disabled=no
# This should be the IP inside the network...
# Doesn't need to be changed unless the network demands it (private network)
/ ip address
add address=192.168.7.1/24 interface=ether1 \
comment="This is the customer's gateway" disabled=no
# Configuration for the DHCP server for the LAN
/ ip pool
add name="dhcp_pool1" ranges=192.168.7.100-192.168.7.200
/ ip dhcp-server
add name="dhcp1" interface=ether1 lease-time=1d address-pool=dhcp_pool1 \
bootp-support=static authoritative=yes disabled=no
/ ip dhcp-server network
add address=192.168.7.0/24 gateway=192.168.7.1 dns-server=4.2.2.3
# You can change the DNS to be what you want
/ ip dns
set primary-dns=68.109.202.25 secondary-dns=10.21.11.1 \
allow-remote-requests=yes cache-size=2048KiB cache-max-ttl=1w
/ ip firewall nat
add chain=srcnat out-interface=wlan1 src-address=192.168.7.0/24 \
action=masquerade disabled=no

Source : http://blog.butchevans.com/2008/06/how-to-configure-a-mikrotik-router-to-replace-cpe-router/

We tested a pair of RB600A devices, each populated with the new R52n card, that were each connected to a pair of antennas. Running a bandwidth test from a RouterBOARD 1000 on each end, we achieved up to 30000pps and 194.3Mbps throughput. The applications are limitless. With new laptops supporting 802.11n by default, you can increase your local network capacity four times of the previously possible speeds.








RB600A with R52n
Result units                                       Mbps       Pps

Routing w/ Conntrack                        183     15000

Routing wo/ Conntrack                      195     16000

Advanced Mikrotik Hotspot Setup - You can also go a step further and play with some other available options, as this only skims the surface of the hotspot capabilities.


1. To disable communication between wireless clients (recommended), disable the default forward option on the wireless interface.

interface wireless set wlan1 default-forward=disabled
2. To set up a wallet garden (pages people can access without authenticating), use the following command:

ip hotspot walled-garden add dst-host=www.website.com
3. To limit client bandwidth type the following, replacing profilename with the current hotspot profile in use and speed with the rate limit in bits per second:

ip hotspot profile set profilename rate-limit=”speed“
4. You can customise the login and status pages by editing the files in the hotspot directory of the Mikrotik box. You can access these via FTP.

Tunning Wireless Interface To Increase Throughput - To increase the troughput of the mikrotik wireless link, i have did this way.

Enter interface wireless to tune.

Data Rates Tab:

- Select configure. start with smalest values in Supported Rates A/G, in this case 6Mbps.

You should understand that for 802.11 devices there is really limited amount of information (or "feedback" from the environment) that devices can use to tune their behavior:

• signal strength, which could be used to figure out best transmit rate knowing receiver sensitivity. Sill this is not reliable taking into account that sensitivity for different receivers varies (e.g. changes over time), path conditions are not symmetric (and device can only measure signal strength it receives), etc.
• by receiving/not receiving acknowledgment for frame sent.

DBii-F20 wireless minipci card work at 2,4GHz, output power 500 mWatt have Rx sensivity until -97 dbm. Include pigtail MMCX to N-Female.

Transmitter Characteristics (Tx)

This tutorial mikrotik is about Routing Information Protocol (RIP). Routing Information Protocol (RIP) is a dynamic routing protocol used in local and wide area networks. As such it is classified as an interior gateway protocol (IGP). It uses the distance-vector routing algorithm. It was first defined in RFC 1058 (1988). The protocol has since been extended several times, resulting in RIP Version 2 (RFC 2453). Both versions are still in use today, however, they are considered to have been made technically obsolete by more advanced techniques such as Open Shortest Path First (OSPF) and the OSI protocol IS-IS. RIP has also been adapted for use in IPv6 networks, a standard known as RIPng (RIP next generation), published in RFC 2080 (1997).

This Routing Information Protocol (RIP) on Mikrotik is used for wireless connection.

RIP Configuration :

1. add ip address at wlan that has been established
e.g, : 192.168.75.1/30
2. RIP Setting
routing > rip > interface
add if there is none, set interface to wlan, authentication = md5
authenticatio key = coli (any)
check on se setting:
redistribute static routes
redistribute connected routes
or as needed.

routing > rip > neighbour
add adress 192.168.75.2 << ip addrres at other side wlan.

At other site mikrotik, do the same thing. The different just abbout neighbour ip addrress, asign the ip address from the other wlan (crisscrossed)

Just share about wireless configuration with eoip tunnel.

konfigurasi di ap

buat interface eoip nama bebas
isi remote address, misal 172.16.1.1
tunel id : ( bebas pokonya angka, asal sama dengan eoip tunel ID di mikrotik satunya)



add ip addras di interface wlan
misal 172.16.1.2/30

buat interface bridge
add port bridge ether1 dan eoip-tunel interface

konfigurasi di client

buat interface eoip nama bebas
isi remote address, misal 172.16.1.2
tunel id : ( bebas pokonya angka, asal sama dengan eoip tunel ID di mikrotik satunya)

add ip addras di interface wlan
misal 172.16.1.1/30

buat interface bridge

port bridge : ether1 dan eoip