Connecting To The Router
Connecting To The Router
Connecting To The Router
More information about the current default configuration can be found in the Quick Guide
document that came with your device. The quick guide document will include information about
which ports should be used to connect for the first time and how to plug in your devices.
This document describes how to set up the device from the ground up, so we will ask you to clear
away all defaults.
When connecting the first time to the router with the default username admin and no password,
you will be asked to reset or keep the default configuration (even if the default config has only an IP
address). Since this article assumes that there is no configuration on the router you should remove it
by pressing "r" on the keyboard when prompted or click on the "Remove configuration" button in
WinBox.
Connect Routers ether1 port to the WAN cable and connect your PC to ether2. Now open WinBox
and look for your router in neighbor discovery. See detailed example in Winbox article.
If you see the router in the list, click on MAC address and click Connect.
The simplest way to make sure you have absolutely clean router is to run
/system reset-configuration no-defaults=yes skip-backup=yes
Or from WinBox (Fig. 1-1):
Configuring IP Access
Since MAC connection is not very stable, the first thing we need to do is to set up a router so that IP
connectivity is available:
Now connected PC should be able to get a dynamic IP address. Close the Winbox and reconnect to
the router using IP address (192.168.88.1)
Dynamic Public IP
Dynamic address configuration is the simplest one. You just need to set up a DHCP client on the
public interface. DHCP client will receive information from an internet service provider (ISP) and set
up an IP address, DNS, NTP servers, and default route for you.
/ip dhcp-client add disabled=no interface=ether1
After adding the client you should see the assigned address and status should be bound
[admin@MikroTik] /ip dhcp-client> print
Flags: X - disabled, I - invalid
# INTERFACE USE ADD-DEFAULT-ROUTE STATUS ADDRESS
0 ether1 yes yes bound 1.2.3.100/24
Static Public IP
In the case of static address configuration, your ISP gives you parameters, for example:
IP: 1.2.3.100/24
Gateway: 1.2.3.1
DNS: 8.8.8.8
These are three basic parameters that you need to get the internet connection working
To set this in RouterOS we will manually add an IP address, add a default route with a provided
gateway, and set up a DNS server
/ip address add address=1.2.3.100/24 interface=ether1
/ip route add gateway=1.2.3.1
/ip dns set servers=8.8.8.8
PPPoE Connection
PPPoE connection also gives you a dynamic IP address and can configure dynamically DNS and
default gateway. Typically service provider (ISP) gives you a username and password for the
connection
/interface pppoe-client
add disabled=no interface=ether1 user=me password=123 \
add-default-route=yes use-peer-dns=yes
Winbox/Webfig actions:
Verify Connectivity
After successful configuration, you should be able to access the internet from the router.
Verify IP connectivity by pinging known IP address (google DNS server for example)
[admin@MikroTik] > /ping 8.8.8.8
HOST SIZE TTL TIME STATUS
8.8.8.8 56 47 21ms
8.8.8.8 56 47 21ms
Minimum 12 characters;
Include numbers, Symbols, Capital and lower case letters;
Is not a Dictionary Word or Combination of Dictionary Words;
/user set 0 password="!={Ba3N!40TуX+GvKBzjTLIUcx/,"
We strongly suggest using a second method or Winbox interface to apply a new password for your
router, just to keep it safe from other unauthorized access.
[admin@MikroTik] > / password
old password:
new password: ******
retype new password: ******
Make sure you remember the password! If you forget it, there is no recovery. You will need to
reinstall the router!
You can also add more users with full or limited router access in /user menu
The best practice is to add a new user with a strong password and disable or remove the
default admin user.
/user add name=myname password=mypassword group=full
/user remove admin
Note: login to the router with new credentials to check that the username/password is working.
MAC Connectivity Access
By default mac server runs on all interfaces, so we will disable default all entry and add a local
interface to disallow MAC connectivity from the WAN port.
[admin@MikroTik] /tool mac-server> print
Flags: X - disabled, * - default
# INTERFACE
0 * all
/tool mac-server
disable 0;
add interface=local;
Neighbor Discovery
MikroTik Neighbor discovery protocol is used to show and recognize other MikroTik routers in the
network, disable neighbor discovery on public interfaces:
/ip neighbor discovery-settings set discover-interface-list=local
IP Connectivity Access
Besides the fact that the firewall protects your router from unauthorized access from outer networks,
it is possible to restrict username access for the specific IP address
/user set 0 allowed-address=x.x.x.x/yy
The first two rules accept packets from already established connections, so we assume those are OK
to not overload the CPU. The third rule drops any packet which connection tracking thinks is invalid.
After that, we set up typical accept rules for specific protocols.
If you are using Winbox/Webfig for configuration, here is an example of how to add an
established/related rule:
Administrative Services
Although the firewall protects the router from the public interface, you may still want to disable
RouterOS services.
Additionally, each service can be secured by allowed IP address or address range(the address service
will reply to), although more preferred method is to block unwanted access in firewall because the
firewall will not even allow to open socket
/ip service set winbox address=192.168.88.0/24
Other Services
A bandwidth server is used to test throughput between two MikroTik routers. Disable it in the
production environment.
/tool bandwidth-server set enabled=no
A router might have DNS cache enabled, which decreases resolving time for DNS requests from
clients to remote servers. In case DNS cache is not required on your router or another router is used
for such purposes, disable it.
/ip dns set allow-remote-requests=no
Some RouterBOARDs have an LCD module for informational purposes, set pin
or disable it.
/lcd set enabled=no
It is good practice to disable all unused interfaces on your router, in order to decrease unauthorized
access to your router.
/interface print
/interface set x disabled=yes
RouterOS utilizes stronger crypto for SSH, most newer programs use it, to turn on SSH strong crypto:
/ip ssh set strong-crypto=yes
Following services are disabled by default, nevertheless, it is better to make sure that none of then
were enabled accidentally:
/ip proxy set enabled=no
/ip socks set enabled=no
/ip upnp set enabled=no
/ip cloud set ddns-enabled=no update-time=no
NAT Configuration
At this point, PC is not yet able to access the Internet, because locally used addresses are not
routable over the Internet. Remote hosts simply do not know how to correctly reply to your local
address.
The solution for this problem is to change the source address for outgoing packets to routers public
IP. This can be done with the NAT rule:
/ip firewall nat
add chain=srcnat out-interface=ether1 action=masquerade
In case if a public interface is a pppoe, then the in-interface should be set to "pppoe-out".
Another benefit of such a setup is that NATed clients behind the router are not directly connected to
the Internet, that way additional protection against attacks from outside mostly is not required.
Port Forwarding
Some client devices may need direct access to the internet over specific ports. For example, a client
with an IP address 192.168.88.254 must be accessible by Remote desktop protocol (RDP).
After a quick search on Google, we find out that RDP runs on TCP port 3389. Now we can add a
destination NAT rule to redirect RDP to the client's PC.
/ip firewall nat
add chain=dstnat protocol=tcp port=3389 in-interface=ether1 \
action=dst-nat to-address=192.168.88.254
If you have set up strict firewall rules then RDP protocol must be allowed in the firewall filter forward
chain.
Setting up Wireless
For ease of use bridged wireless setup will be made so that your wired hosts are in the same Ethernet
broadcast domain as wireless clients.
The important part is to make sure that our wireless is protected, so the first step is the security
profile.
Now when the security profile is ready we can enable the wireless interface and set the desired
parameters
/interface wireless
enable wlan1;
set wlan1 band=2ghz-b/g/n channel-width=20/40mhz-Ce distance=indoors \
mode=ap-bridge ssid=MikroTik-006360 wireless-protocol=802.11 \
security-profile=myProfile frequency-mode=regulatory-domain \
set country=latvia antenna-gain=3
To do the same from Winbox/Webfig:
Open Wireless window, select wlan1 interface, and click on the enable button;
Double click on the wireless interface to open the configuration dialog;
In the configuration dialog click on the Wireless tab and click the Advanced mode button
on the right side. When you click on the button additional configuration parameters will appear and
the description of the button will change to Simple mode;
Choose parameters as shown in the screenshot, except for the country settings and SSID. You
may want to also choose a different frequency and antenna gain;
Next, click on the HT tab and make sure both chains are selected;
Click on the OK button to apply settings.
The last step is to add a wireless interface to a local bridge, otherwise connected clients will not get
an IP address:
/interface bridge port
add interface=wlan1 bridge=local
Now wireless should be able to connect to your access point, get an IP address, and access the
internet.
A ruleset is similar to input chain rules (accept established/related and drop invalid), except the first
rule with action=fasttrack-connection. This rule allows established and related connections to bypass the
firewall and significantly reduce CPU usage.
Another difference is the last rule which drops all new connection attempts from the WAN port to
our LAN network (unless DstNat is used). Without this rule, if an attacker knows or guesses your local
subnet, he/she can establish connections directly to local hosts and cause a security threat.
For more detailed examples on how to build firewalls will be discussed in the firewall section, or
check directly Building Your First Firewall article.
First, we need to add a NAT rule to redirect HTTP to our proxy. We will use RouterOS built-in proxy
server running on port 8080.
/ip firewall nat
add chain=dst-nat protocol=tcp dst-port=80 src-address=192.168.88.0/24 \
action=redirect to-ports=8080
In the "Web Proxy Access" dialog click on "+" to add a new Web-proxy rule
Enter Dst hostname that you want to block, in this case, "www.facebook.com", choose the
action "deny"
Then click on the "Ok" button to apply changes.
Repeat the same to add other rules.
Troubleshooting
RouterOS has built-in various troubleshooting tools, like ping, traceroute, torch, packet sniffer,
bandwidth test, etc.
We already used the ping tool in this article to verify internet connectivity.