To Debug nat: debug ip nat

Clear NAT mappings: clear ip nat translation *

Definitions for the Document: Public IP. An Internet routable IP address. Static IP address: An Ip that does not change. This can either be a private or a public IP address. Private IP address. A non public routable IP address.  [...]]]> Purpose: This document encompasses the procedure on configuring a 1:1 nat on a mikrotik CPE.

Definitions for the Document:
Public IP. An Internet routable IP address.
Static IP address: An Ip that does not change. This can either be a private or a public IP address.
Private IP address. A non public routable IP address.  This includes. 10.0.0.0/8, 172.16.0.0/12,192.168.0.0/16, 169.254.0.0/16
In the following example we are assuming the following:
35.35.42.7   is our Public IP
192.168.3.125 is our Static DHCP IP we will set in step 2.
Our CPE is in station mode.
We are running a DHCP server on ether1 Interface which our customer is plugged into.  The DHCP scope is 192.168.3.0/25
There are 3 Basic steps involved.

1.Bind Public IP to wlan interface
2.Make endpoint a Static client
3.Configure 2 NAT rules.

1.The Public Ip needs to be bound to the WLAN interface.  If the network is handing out Public IPs already this step is already done.

2.You will need to make the device where the 1:1 nat ends at a static DHCP client. This means it is receiving an Ip from DHCP, but it will never change.  This is a very important step. The Customer LAN side does not have to be DHCP. It can be static as long as the appropriate info is setup.  I find running DHCP on the LAN side makes life easier.

Go to IP-DHCP Server. Click on the leases tab.  Find the device you wish the 1:1 nat to end at.  Highlight it and click “make static”.  If there is more than 1 device in this list you will have to verify with the customer which device they need the 1:1 nat to.  There are a couple of ways to verify this.

1.Have the customer confirm the MAC address of the router or PC.
2.Remove all the leases from the leases tab by highlighting them and clicking the minus button.  Have the customer reboot the router or PC.

3.You will configure 2 nat rules. One tells the device what to do with outbound traffic and the other tells it what to do with inbound traffic.

/ip firewall nat add chain=dstnat dst-address=35.35.42.7\
to-ports=0-65535 protocol=tcp action=netmap to-addresses=192.168.3.125

/ip firewall nat add chain=srcnat src-address=192.168.3.125 \
to-ports=0-65535 protocol=tcp  action=netmap to-addresses=35.35.42.7

Our lab setup consists of the following hardware: -2 RouterBoard [...]]]> The goal of this exercise is to show how to setup OSPF between two routerboards to enable communication between two separate IP networks. In this case we want the 2 PC’s, which are on separate DHCP networks to be able to communicate with each other via dynamic routing.

Our lab setup consists of the following hardware:
-2 RouterBoard 450’s connected together via Ethernet on ether1.
-A PC attached to port 2 of each Rb450

The configuration consists of :

Router1
Ether1 IP: 10.10.10.1/30
Ether2 IP:192.168.3.1/24
DHCP running on Ether2 handing out DHCP in the range of 192.168.3.10-192.168.3.254

Router2
Ether1 IP: 10.10.10.2/30
Ether2 IP: 192.168.4.1/24
DHCP running on Ether2 handing out DHCP in the range of 192.168.4.10-192.168.4.254

Stay tuned for the video coming soon.

Display routes with inconsistent originating ASes show ip bgp inconsistent-as

Display all BGP paths show ip bgp paths

Display stats of all BGP connections: show ip bgp summary