Mikrotik How To

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)

Load Balance Mikrotik with PCC using PPPoe-Client connection - Mikrotik tutorial Load Balance Mikrotik with PCC using PPPoe-Client connection is used for bandwitdh optimalization,fail over, and bandwidth control usage.

First, make new mangle for mark connectio, packet and routing :

/ ip firewall mangle
add chain=input in-interface=internet1 action=mark-connection new-connection-mark=internet1_conn
add chain=input in-interface=internet2 action=mark-connection new-connection-mark=internet2_conn
add chain=output connection-mark=internet1_conn action=mark-routing new-routing-mark=to_internet1
add chain=output connection-mark=internet2_conn action=mark-routing new-routing-mark=to_internet2
add chain=prerouting dst-address-type=!local in-interface=Local per-connection-classifier=both-addresses:2/0 \
action=mark-connection new-connection-mark=internet1_conn passthrough=yes
add chain=prerouting dst-address-type=!local in-interface=Local per-connection-classifier=both-addresses:2/1 \
action=mark-connection new-connection-mark=internet2_conn passthrough=yes
add chain=prerouting connection-mark=internet1_conn in-interface=Local action=mark-routing new-routing-mark=to_internet1
add chain=prerouting connection-mark=internet2_conn in-interface=Local action=mark-routing new-routing-mark=to_internet2

Than set the default route and fail over gateway :
/ ip route
add dst-address=0.0.0.0/0 gateway=10.111.0.1 routing-mark=to_internet1 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=10.112.0.1 routing-mark=to_internet2 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=10.111.0.1 distance=1 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=10.112.0.1 distance=2 check-gateway=ping

Last, set the NAT for local connection:
/ ip firewall nat
add chain=srcnat out-interface=internet1 action=masquerade
add chain=srcnat out-interface=internet2 action=masquerade

That is simple script for Load Balance Mikrotik with PCC using PPPoe-Client connection.

Overview
Ethernet over IP (EoIP) Tunneling is a MikroTik RouterOS protocol that creates an Ethernet tunnel between two routers on top of an IP connection. The EoIP interface appears as an Ethernet interface. When the bridging function of the router is enabled, all Ethernet level traffic (all Ethernet protocols) will be bridged just as if there where a physical Ethernet interface and cable between the two routers (with bridging enabled). This protocol makes multiple network schemes possible.

Network setups with EoIP interfaces:

* Possibility to bridge LANs over the Internet
* Possibility to bridge LANs over encrypted tunnels
* Possibility to bridge LANs over 802.11b 'ad-hoc' wireless networks

Specifications
Packages required : None
License required : Basic (DEMO license is limited to 4 tunnels)
Home menu level : /interface eoip
Standards and Technologies : GRE (RFC1701)
Hardware usage: not significant
Related Documents
Software Package Installation and Upgrading
IP Addresses and Address Resolution Protocol (ARP)
Bridge Interfaces
PPTP (Point to Point Tunnel Protocol) Interface
Description
An EoIP interface should be configured on two routers that have the possibility for an IP level connection. The EoIP tunnel may run over an IPIP tunnel, a PPTP 128bit encrypted tunnel, a PPPoE connection, or any connection that transports IP.

Specific Properties:

* Each EoIP tunnel interface can connect with one remote router which has a corresponding interface configured with the same 'Tunnel ID'.
* The EoIP interface appears as an Ethernet interface under the interface list.
* This interface supports all features of and Ethernet interface. IP addresses and other tunnels may be run over the interface.
* The EoIP protocol encapsulates Ethernet frames in GRE (IP protocol number 47) packets (just like PPTP) and sends them to the remote side of the EoIP tunnel.
* Maximal count of EoIP tunnels is 65536.

EoIP Setup
Submenu leve : /interface eoip
Property Description
name (name; default: eoip-tunnelN)- interface name for reference
mtu (integer; default: 1500) - Maximum Transmission Unit. The default value provides maximal compatibility
arp (disabled | enabled | proxy-arp | reply-only; default: enabled) - Address Resolution Protocol
tunnel-id (integer; default: 0) - a unique tunnel identifier
remote-address - the IP address of the other side of the EoIP tunnel – must be a MikroTik router
Notes
tunnel-id is method of identifying tunnel. There should not be tunnels with the same tunnel-id on the same router. tunnel-id on both participient routers must be equal.

mtu should be set to 1500 to eliminate packet refragmentation inside the tunnel (that allows transparent bridging of ethernet-like networks, so that it would be possible to transport full-sized ethernet frame over the tunnrl).
Example
To add and enable an EoIP tunnel named to_mt2 to the 10.5.8.1 router, specifying tunnel-id of 1:

[admin@MikroTik] interface eoip> add name=to_mt2 remote-address=10.5.8.1 \
\... tunnel-id 1
[admin@MikroTik] interface eoip> print
Flags: X - disabled, R - running
0 X name="to_mt2" mtu=1500 arp=enabled remote-address=10.5.8.1 tunnel-id=1

[admin@MikroTik] interface eoip> enable 0
[admin@MikroTik] interface eoip> print
Flags: X - disabled, R - running
0 R name="to_mt2" mtu=1500 arp=enabled remote-address=10.5.8.1 tunnel-id=1

[admin@MikroTik] interface eoip>

EoIP Application Example
Let us assume we want to bridge two networks: 'Office LAN' and 'Remote LAN'. The networks are connected to an IP network through the routers [Our_GW] and [Remote]. The IP network can be a private intranet or the Internet. Both routers can communicate with each other through the IP network.

Our goal is to create a secure channel between the routers and bridge both networks through it. The network setup diagram is as follows:



To make a secure Ethernet bridge between two routers you should:

1. Create a PPTP tunnel between them. Our_GW will be the pptp server:

[admin@Our_GW] interface pptp-server> /ppp secret add name=joe service=pptp \
\... password=top_s3 local-address=10.0.0.1 remote-address=10.0.0.2
[admin@Our_GW] interface pptp-server> add name=from_remote user=joe
[admin@Our_GW] interface pptp-server> server set enable=yes
[admin@Our_GW] interface pptp-server> print
Flags: X - disabled, D - dynamic, R - running
# NAME USER MTU CLIENT-ADDRESS UPTIME ENC...
0 from_remote joe
[admin@Our_GW] interface pptp-server>

The Remote router will be the pptp client:

[admin@Remote] interface pptp-client> add name=pptp user=joe \
\... connect-to=192.168.1.1 password=top_s3 mtu=1500 mru=1500
[admin@Remote] interface pptp-client> enable pptp
[admin@Remote] interface pptp-client> print
Flags: X - disabled, R - running
0 R name="pptp" mtu=1500 mru=1500 connect-to=192.168.1.1 user="joe"
password="top_s2" profile=default add-default-route=no

[admin@Remote] interface pptp-client> monitor pptp
status: "connected"
uptime: 39m46s
encoding: "none"

[admin@Remote] interface pptp-client>

See the PPTP Interface Manual for more details on setting up encrypted channels.

2. Configure the EoIP tunnel by adding the eoip tunnel interfaces at both routers. Use the ip addresses of the pptp tunnel interfaces when specifying the argument values for the EoIP tunnel:

[admin@Our_GW] interface eoip> add name="eoip-remote" tunnel-id=0 \
\... remote-address=10.0.0.2
[admin@Our_GW] interface eoip> enable eoip-remote
[admin@Our_GW] interface eoip> print
Flags: X - disabled, R - running
0 name=eoip-remote mtu=1500 arp=enabled remote-address=10.0.0.2 tunnel-id=0
[admin@Our_GW] interface eoip>

[admin@Remote] interface eoip> add name="eoip" tunnel-id=0 \
\... remote-address=10.0.0.1
[admin@Remote] interface eoip> enable eoip-main
[admin@Remote] interface eoip> print
Flags: X - disabled, R - running
0 name=eoip mtu=1500 arp=enabled remote-address=10.0.0.1 tunnel-id=0

[Remote] interface eoip>

3. Enable bridging between the EoIP and Ethernet interfaces on both routers.

On the Our_GW:

[admin@Our_GW] interface bridge> add forward-protocols=ip,arp,other \
\... disabled=no
[admin@Our_GW] interface bridge> print
Flags: X - disabled, R - running
0 R name="bridge1" mtu=1500 arp=enabled mac-address=00:00:00:00:00:00
forward-protocols=ip,arp,other priority=1

[admin@Our_GW] interface bridge> port print
Flags: X - disabled
# INTERFACE BRIDGE
0 eoip-remote none
1 office-eth none
2 isp none

[admin@Our_GW] interface bridge> port set "0,1" bridge=bridge1

And the same for the Remote:

[admin@Remote] interface bridge> add forward-protocols=ip,arp,other \
\... disabled=no
[admin@Remote] interface bridge> print
Flags: X - disabled, R - running
0 R name="bridge1" mtu=1500 arp=enabled mac-address=00:00:00:00:00:00
forward-protocols=ip,arp,other priority=1

[admin@Remote] interface bridge> port print
Flags: X - disabled
# INTERFACE BRIDGE
0 ether none
1 adsl none
2 eoip-main none

[admin@Remote] interface bridge> port set "0,2" bridge=bridge1

4. Addresses from the same network can be used both in the Office LAN and in the Remote LAN

Mikrotik.com

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

Applies to RouterOS: 2.9, v3, v4

After you have installed the RouterOS software, or turned on the Router for the first time, there are various ways how to connect to it:

Method 1. Console Cable

If your device is a RouterBOARD, it doesn't have a monitor connector. You will have to either find a console cable (or Null modem cable) or see Method 2.

Plug one end of the serial cable into the console port (also known as a serial port or DB9 RS232C asynchronous serial port) of the RouterBOARD and the other end in your PC (which hopefully runs Windows or Linux). You can also use a USB-Serial adapter. Run a terminal program (HyperTerminal, or Putty on Windows) with the following parameters for All RouterBOARD models except 230:

115200bit/s, 8 data bits, 1 stop bit, no parity, flow control=none by default.

Mikrotīkls Ltd., known internationally as MikroTik, is a Latvian manufacturer of computer networking equipment. It sells wireless products and routers. The company was founded in 1995, with the intent to sell in the emerging wireless technology market. As of 2007, the company had more than 70 employees.RouterOS
The main product of MikroTik is a Linux-based operating system known as MikroTik RouterOS. It lets users turn a selected PC-based machine into a software router, allowing features such as firewall rules, VPN Server and Client, bandwidth shaper Quality of Service, wireless access point and other commonly used features for routing and connecting networks together. The system is also able to serve as a captive-portal based hotspot system. The operating system is licensed in escalating levels, each releasing more of the available RouterOS features as the level number rises. Licensing is fee based and escalates with the released features. There is a software called Winbox which provides a sophisticated GUI for the RouterOS operating system. The software also allows connections via FTP, telnet, and SSH. There is also an API which allows creating customised applications for management and monitoring.

Features
RouterOS supports many applications that can be used by medium size to large ISP, for example OSPF, BGP, VPLS/MPLS. All in one, RouterOS is a versatile system, and is very well supported by Mikrotik, both through a forum and a Wiki providing assorted and thematic examples of configurations.
The software provides support for virtually all the network interfaces that the Linux kernel 2.6.16 supports, excepting wireless, where the Atheros and Prism are the only supported chipsets, as of 3.x version. Mikrotik is also working on upgrades to the software which will enable full compatibility between the Mikrotik-specific services and newer networking developments such as IPv6 and MPLS[1]

RouterBOARD
The RouterOS, combined with their hardware product line, known as MikroTik RouterBOARD, is marketed at small to medium sized wireless Internet service providers, typically providing broadband wireless access in remote areas.

Developing IT markets

See also: Information and communication technologies for development
A recent project to build low-cost internet infrastructure in Mali chose MikroTik routers and operating systems because of the system's cost, flexibility, the fact that the system already had "a substantial user base in Mali", and had a user interface deemed "superior to other products".[2] MikroTik routers were also preferred for a WLAN project in Burkina Faso,[3] and MikroTik's proprietary Nstreme protocol performed better than IEEE 802.11 under the project's conditions.[4]
In 2008, it was decided that MikroTik routers would also be used exclusively by the Municipality of Piripiri, Piauí State, Brazil, to build the infrastructure for providing free internet access.[5] MikroTik routers are also popular in the Czech Republic, where they enjoy a good reputation.[6]
Under OLPC program, Uruguay deployed a Nation-wide wireless network in Schools. Probaby the largest Mikrotik deployment in a Country with a total population of 3 Million. Aproximatelly 200.000 Students received a small laptop which connected to Mikrotik Access Points.