Network Address Translation is an Internet standard that allows hosts on local area networks to use one set of IP addresses for internal communications and another set of IP addresses for external communications. A LAN that uses NAT is referred as natted network. For NAT to function, there should be a NAT gateway in each natted network. The NAT gateway (NAT router) performs IP address rewriting on the way a packet travel from/to LAN.
Network Address Translation is an Internet standard that allows hosts on local area networks to use one set of IP addresses for internal communications and another set of IP addresses for external communications. A LAN that uses NAT is referred as natted network. For NAT to function, there should be a NAT gateway in each natted network. The NAT gateway (NAT router) performs IP address rewriting on the way a packet travel from/to LAN.
Line 26:
Line 28:
</p>
</p>
<h2>Properties</h2>
===Masquerade===
Firewall NAT <code>action=masquerade</code> is unique subversion of <code>action=srcnat</code>, it was designed for specific use in situations when public IP can randomly change, for example DHCP-server changes it, or PPPoE tunnel after disconnect gets different IP, in short - when public IP is dynamic.
Every time interface disconnects and/or its IP address changes, router will clear all masqueraded connection tracking entries that send packet out that interface, this way improving system recovery time after public ip address change.
Unfortunately this can lead to some issues when <code>action=masquerade</code> is used in setups with unstable connections/links that get routed over different link when primary is down. In such scenario following things can happen:
* on disconnect, all related connection tracking entries are purged;
* next packet from every purged (previously masqueraded) connection will come into firewall as <code>connection-state=new</code>, and, if primary interface is not back, packet will be routed out via alternative route (if you have any) thus creating new connection;
* primary link comes back, routing is restored over primary link, so packets that belong to existing connections are sent over primary interface without being masqueraded leaking local IPs to a public network.
You can workaround this by creating <b>blackhole</b> route as alternative to route that might disappear on disconnect).
When <code>action=srcnat</code> is used instead, connection tracking entries remain and connections can simply resume.
==Properties==
<table class="styled_table">
<table class="styled_table">
Line 43:
Line 59:
<li> <var>jump</var> - jump to the user defined chain specified by the value of <code>jump-target</code> parameter
<li> <var>jump</var> - jump to the user defined chain specified by the value of <code>jump-target</code> parameter
<li> <var>log</var> - add a message to the system log containing following data: in-interface, out-interface, src-mac, protocol, src-ip:port->dst-ip:port and length of the packet. After packet is matched it is passed to next rule in the list, similar as <code>passthrough</code>
<li> <var>log</var> - add a message to the system log containing following data: in-interface, out-interface, src-mac, protocol, src-ip:port->dst-ip:port and length of the packet. After packet is matched it is passed to next rule in the list, similar as <code>passthrough</code>
<li> <var>masquerade</var> - replace source address of an IP packet to IP determined by routing facility.
<li> <var>masquerade</var> - replaces source port of an IP packet to one specified by <code>to-ports</code> parameter and replace source address of an IP packet to IP determined by routing facility. <code>[[#Masquerade | Read more >>]]</code>
<li> <var>netmap</var> - creates a static 1:1 mapping of one set of IP addresses to another one. Often used to distribute public IP addresses to hosts on private networks
<li> <var>netmap</var> - creates a static 1:1 mapping of one set of IP addresses to another one. Often used to distribute public IP addresses to hosts on private networks
<li> <var>passthrough</var> - ignore this rule and go to next one (useful for statistics).
<li> <var>passthrough</var> - if packet is matched by the rule, increase counter and go to next rule (useful for statistics).
<li> <var>redirect</var> - replaces destination port of an IP packet to one specified by <code>to-ports</code> parameter
<li> <var>redirect</var> - replaces destination port of an IP packet to one specified by <code>to-ports</code> parameter and destination address to one of the router's local addresses
<li> <var>return</var> - passes control back to the chain from where the jump took place
<li> <var>return</var> - passes control back to the chain from where the jump took place
<li> <var>same</var> - gives a particular client the same source/destination IP address from supplied range for each connection. This is most frequently used for services that expect the same client address for multiple connections from the same client
<li> <var>same</var> - gives a particular client the same source/destination IP address from supplied range for each connection. This is most frequently used for services that expect the same client address for multiple connections from the same client
<td>Time interval after which the address will be removed from the address list specified by <code>address-list</code> parameter. Used in conjunction with <code>add-dst-to-address-list</code> or <code>add-src-to-address-list</code> actions<br />
<td>Time interval after which the address will be removed from the address list specified by <code>address-list</code> parameter. Used in conjunction with <code>add-dst-to-address-list</code> or <code>add-src-to-address-list</code> actions<br />
Value of <code>00:00:00</code> will leave the address in the address list forever</td>
<ul class="bullets">
<li>Value of <var>none-dynamic</var> (<code>00:00:00</code>) will leave the address in the address list till reboot
<li>Value of <var>none-static</var> will leave the address in the address list forever and will be included in configuration export/backup
<td>Connection Rate is a firewall matcher that allow to capture traffic based on present speed of the connection. [[Connection_Rate | Read more>>]]</td>
<td>Connection Rate is a firewall matcher that allow to capture traffic based on present speed of the connection. <code>[[Connection_Rate | Read more>>]]</code></td>
</tr>
<tr>
<td><var><b>connection-state</b></var> (<em>estabilished | invalid | new | related</em>; Default: <b></b>)</td>
<td>Interprets the connection tracking analysis data for a particular packet:
<ul class="bullets">
<li> <var>established</var> - a packet which belongs to an existing connection
<li> <var>invalid</var> - a packet which could not be identified for some reason
<li> <var>new</var> - a packet which begins a new connection
<li> <var>related</var> - a packet which is related to, but not part of an existing connection, such as ICMP errors or a packet which begins FTP data connection
<td>Matches packets from related connections based on information from their connection tracking helpers. A relevant connection helper must be enabled under [[IP/Services | /ip firewall service-port]]</td>
<td>Matches packets from related connections based on information from their connection tracking helpers. A relevant connection helper must be enabled under [[IP/Services#Service_Ports | /ip firewall service-port]]</td>
<td>Matches packets if given pps limit is exceeded. As opposed to the <var>limit</var> matcher, every destination IP address / destination port has it's own limit. Parameters are written in following format: <code>count,time,burst,mode,expire</code>.
<td>Matches packets until a given pps limit is exceeded. As opposed to the <var>limit</var> matcher, every destination IP address / destination port has it's own limit. Parameters are written in following format: <code>count[/time],burst,mode[/expire]</code>.
<ul class="bullets">
<ul class="bullets">
<li><b>count</b> - maximum average packet rate measured in packets per <code>time</code> interval
<li><b>count</b> - maximum average packet rate measured in packets per <code>time</code> interval
<li><b>time</b> - specifies the time interval in which the packet rate is measured
<li><b>time</b> - specifies the time interval in which the packet rate is measured (optional)
<li><b>burst</b> - number of packets which are not counted by packet rate
<li><b>burst</b> - number of packets which are not counted by packet rate
<li><b>mode</b> - the classifier for packet rate limiting
<li><b>mode</b> - the classifier for packet rate limiting
<li><b>expire</b> - specifies interval after which recored ip address /port will be deleted
<li><b>expire</b> - specifies interval after which recored ip address /port will be deleted (optional)
<td>Matches the policy used by IpSec. Value is written in following format: <code><b>direction, policy</b></code>. Direction is Used to select whether to match the policy used for decapsulation or the policy that will be used for encapsulation.
<ul>
<li><var>in</var> - valid in the PREROUTING, INPUT and FORWARD chains</li>
<li><var>out</var> - valid in the POSTROUTING, OUTPUT and FORWARD chains</li>
</ul>
<ul>
<li><var>ipsec</var> - matches if the packet is subject to IpSec processing;</li>
<li><var>none</var> - matches packet that is not subject to IpSec processing (for example, IpSec transport packet).</li>
</ul>
<p>For example, if router receives Ipsec encapsulated Gre packet, then rule <code>ipsec-policy=in,ipsec</code> will match Gre packet, but rule <code>ipsec-policy=in,none</code> will match ESP packet.</p></td>
<td>PCC matcher allows to divide traffic into equal streams with ability to keep packets with specific set of options in one particular stream. [[PCC | Read more >>]]</td>
<td>PCC matcher allows to divide traffic into equal streams with ability to keep packets with specific set of options in one particular stream. <code>[[PCC | Read more >>]]</code></td>
<td>Attempts to detect TCP and UDP scans. Parameters are in following format <code>WeightThreshold, DelayThreshold, LopPortWeight, HighPortWeight</code>
<td>Attempts to detect TCP and UDP scans. Parameters are in following format <code>WeightThreshold, DelayThreshold, LowPortWeight, HighPortWeight</code>
<ul class="bullets">
<ul class="bullets">
<li> <b>WeightThreshold</b> - total weight of the latest TCP/UDP packets with different destination ports coming from the same host to be treated as port scan sequence
<li> <b>WeightThreshold</b> - total weight of the latest TCP/UDP packets with different destination ports coming from the same host to be treated as port scan sequence
<li> <b>DelayThreshold</b> - delay for the packets with different destination ports coming from the same host to be treated as possible port scan subsequence
<li> <b>DelayThreshold</b> - delay for the packets with different destination ports coming from the same host to be treated as possible port scan subsequence
<li> <b>LowPortWeight</b> - weight of the packets with privileged (<=1024) destination port
<li> <b>LowPortWeight</b> - weight of the packets with privileged (<1024) destination port
<li> <b>HighPortWeight</b> - weight of the packet with non-priviliged destination port
<li> <b>HighPortWeight</b> - weight of the packet with non-priviliged destination port
</ul>
</ul>
Line 291:
Line 323:
</tr>
</tr>
<tr>
<tr>
<td><var><b>tcp-flags</b></var> (<em>ack | cwr | ece | fin | psh | rst | syn | urg</em>; Default: <b></b>)</td>
<td>Replace original port with specified one. Applicable if action is dst-nat, redirect, netmap, same, src-nat</td>
<td>Replace original port with specified one. Applicable if action is dst-nat, redirect, masquerade, netmap, same, src-nat</td>
</tr>
</tr>
<tr>
<tr>
Line 398:
Line 415:
</table>
</table>
<h2>Basic examples</h2>
==Basic examples==
<h3>Source NAT</h3>
<h3>Source NAT</h3>
<h4>Masquerade</h4>
<p>
<p>
If you want to "hide" the private LAN 192.168.0.0/24 "behind" one address 10.5.8.109 given to you by the ISP, you should use the source network address translation (masquerading) feature of the MikroTik router. The masquerading will change the source IP address and port of the packets originated from the network 192.168.0.0/24 to the address 10.5.8.109 of the router when the packet is routed through it.
If you want to "hide" the private LAN 192.168.0.0/24 "behind" one address 10.5.8.109 given to you by the ISP, you should use the source network address translation (masquerading) feature of the MikroTik router. The masquerading will change the source IP address and port of the packets originated from the network 192.168.0.0/24 to the address 10.5.8.109 of the router when the packet is routed through it.
Line 411:
Line 430:
All outgoing connections from the network 192.168.0.0/24 will have source address 10.5.8.109 of the router and source port above 1024. No access from the Internet will be possible to the Local addresses. If you want to allow connections to the server on the local network, you should use destination Network Address Translation (NAT).
All outgoing connections from the network 192.168.0.0/24 will have source address 10.5.8.109 of the router and source port above 1024. No access from the Internet will be possible to the Local addresses. If you want to allow connections to the server on the local network, you should use destination Network Address Translation (NAT).
</p>
</p>
<h4>Source nat to specific address</h4>
If you have multiple public IP addresses, source nat can be changed to specific IP, for example, one local subnet can be hidden behind first IP and second local subnet is masqueraded behind second IP.
If you want to link Public IP 10.5.8.200 address to Local one 192.168.0.109, you should use destination address translation feature of the MikroTik router. Also if you want allow Local server to talk with outside with given Public IP you should use source address translation, too.
If you want to link Public IP 10.5.8.200 address to Local one 192.168.0.109, you should use destination address translation feature of the MikroTik router. Also if you want allow Local server to initiate connections to outside with given Public IP you should use source address translation, too.
</p>
</p>
<p>
<p>
Line 426:
Line 456:
to-addresses=192.168.0.109
to-addresses=192.168.0.109
</pre>
</pre>
Add rule allowing the internal server to talk to the outer networks having its source address translated to 10.5.8.200:
Add rule allowing the internal server to initate connections to the outer networks having its source address translated to 10.5.8.200:
<p>If you would like to direct requests for a certain port to an internal machine (sometimes called opening a port, port mapping), you can do it like this:</p>
This rule translates to: ''when an incoming connection requests TCP port 1234, use the DST-NAT action and redirect it to local address 192.168.1.1 and the port 1234''
<h4>Port forwarding to internal FTP server</h4>
[[File:ftp-passive.png]]
<p>
As you can see from illustration above FTP uses more than one connection, but only command channel should be forwarded by Destination nat. Data channel is considered as related connection and should be accepted with "accept related" rule if you have strict firewall. Note that for related connections to be properly detected FTP helper has to be enabled.
<p>Note that active FTP might not work if client is behind dumb firewall or NATed router, because data channel is initiated by the server and cannot directly access the client.</p>
[[File:ftp-active-fail.png]]
<p>If client is behind Mikrotik router, then make sure that FTP helper is enabled</p>
If you want to link Public IP subnet 11.11.11.0/24 to local one 2.2.2.0/24, you should use destination address translation and source address translation features with action=netmap.
If you want to link Public IP subnet 11.11.11.0/24 to local one 2.2.2.0/24, you should use destination address translation and source address translation features with action=netmap.
<p>If you would like to direct requests for a certain port to an internal machine (sometimes called opening a port, port mapping), you can do it like this:</p>
<h3>Carrier-Grade NAT (CGNAT) or NAT444</h3>
<p>To combat IPv4 address exhaustion, new RFC 6598 was deployed. The idea is to use shared 100.64.0.0/10 address space inside carrier's network and performing NAT on carrier's edge router to sigle public IP or public IP range.</p>
<p>Because of nature of such setup it is also called NAT444, as opposed to a NAT44 network for a 'normal' NAT environment, three different IPv4 address spaces are involved.</p>
[[file:cgnat.png]]
CGNAT configuration on RouterOS does not differ from any other regular source NAT configuration:
* public_if - interface on providers edge router connected to internet
The advantage of NAT444 is obvious, less public IPv4 addresses used. But this technique comes with mayor drawbacks:
* The service provider router performing CGNAT needs to maintain a state table for all the address translations: this requires a lot of memory and CPU resources.
* Console gaming problems. Some games fail when two subscribers using the same outside public IPv4 address try to connect to each other.
* Tracking of users for legal reasons means extra logging, as multiple households go behind one public address.
* Anything requiring incoming connections is broken. While this already was the case with regular NAT, end users could usually still set up port forwarding on their NAT router. CGNAT makes this impossible. This means no web servers can be hosted here, and IP Phones cannot receive incoming calls by default either.
* Some web servers only allow a maximum number of connections from the same public IP address, as a means to counter DoS attacks like SYN floods. Using CGNAT this limit is reached more often and some services may be of poor quality.
* 6to4 requires globally reachable addresses and will not work in networks that employ addresses with limited topological span.
More on things that can break can be read in this article [http://chrisgrundemann.com/index.php/2011/nat444-cgn-lsn-breaks/]
Packets with Shared Address Space source or destination addresses MUST NOT be forwarded across Service Provider boundaries. Service Providers MUST filter such packets on ingress links.
In RouterOS this can be easily done with firewall filters on edge routers:
Service providers may be required to do logging of MAPed addresses, in large CGN deployed network that may be a problem.
Fortunately RFC 7422 suggests a way to manage CGN translations in such a way as to significantly reduce the amount of logging required while providing traceability for abuse response.
RFC states that instead of logging each connection, CGNs could deterministically map customer private addresses (received on the customer-facing interface of the CGN, a.k.a., internal side) to public addresses extended with port ranges.
In RouterOS described algorithm can be done with few script functions.
After pasting above script in the terminal function "addNatRules" is available. If we take our example, we need to map 6 shared network addresses to be mapped to 2.2.2.2 and each address uses range of 100 ports starting from 2000. So we run our function:
This rule translates to: ''when an incoming connection requests TCP port 1234, use the DST-NAT action and redirect it to local address 192.168.1.1 and the port 1234''
Network Address Translation is an Internet standard that allows hosts on local area networks to use one set of IP addresses for internal communications and another set of IP addresses for external communications. A LAN that uses NAT is referred as natted network. For NAT to function, there should be a NAT gateway in each natted network. The NAT gateway (NAT router) performs IP address rewriting on the way a packet travel from/to LAN.
There are two types of NAT:
source NAT or srcnat. This type of NAT is performed on packets that are originated from a natted network. A NAT router replaces the private source address of an IP packet with a new public IP address as it travels through the router. A reverse operation is applied to the reply packets travelling in the other direction.
destination NAT or dstnat. This type of NAT is performed on packets that are destined to the natted network. It is most comonly used to make hosts on a private network to be acceesible from the Internet. A NAT router performing dstnat replaces the destination IP address of an IP packet as it travel through the router towards a private network.
Hosts behind a NAT-enabled router do not have true end-to-end connectivity. Therefore some Internet protocols might not work in scenarios with NAT. Services that require the initiation of TCP connection from outside the private network or stateless protocols such as UDP, can be disrupted. Moreover, some protocols are inherently incompatible with NAT, a bold example is AH protocol from the IPsec suite.
To overcome these limitations RouterOS includes a number of so-called NAT helpers, that enable NAT traversal for various protocols.
Masquerade
Firewall NAT action=masquerade is unique subversion of action=srcnat, it was designed for specific use in situations when public IP can randomly change, for example DHCP-server changes it, or PPPoE tunnel after disconnect gets different IP, in short - when public IP is dynamic.
Every time interface disconnects and/or its IP address changes, router will clear all masqueraded connection tracking entries that send packet out that interface, this way improving system recovery time after public ip address change.
Unfortunately this can lead to some issues when action=masquerade is used in setups with unstable connections/links that get routed over different link when primary is down. In such scenario following things can happen:
on disconnect, all related connection tracking entries are purged;
next packet from every purged (previously masqueraded) connection will come into firewall as connection-state=new, and, if primary interface is not back, packet will be routed out via alternative route (if you have any) thus creating new connection;
primary link comes back, routing is restored over primary link, so packets that belong to existing connections are sent over primary interface without being masqueraded leaking local IPs to a public network.
You can workaround this by creating blackhole route as alternative to route that might disappear on disconnect).
When action=srcnat is used instead, connection tracking entries remain and connections can simply resume.
Properties
Property
Description
action (action name; Default: accept)
Action to take if packet is matched by the rule:
accept - accept the packet. Packet is not passed to next NAT rule.
add-dst-to-address-list - add destination address to Address list specified by address-list parameter
add-src-to-address-list - add source address to Address list specified by address-list parameter
dst-nat - replaces destination address and/or port of an IP packet to values specified by to-addresses and to-ports parameters
jump - jump to the user defined chain specified by the value of jump-target parameter
log - add a message to the system log containing following data: in-interface, out-interface, src-mac, protocol, src-ip:port->dst-ip:port and length of the packet. After packet is matched it is passed to next rule in the list, similar as passthrough
masquerade - replaces source port of an IP packet to one specified by to-ports parameter and replace source address of an IP packet to IP determined by routing facility. Read more >>
netmap - creates a static 1:1 mapping of one set of IP addresses to another one. Often used to distribute public IP addresses to hosts on private networks
passthrough - if packet is matched by the rule, increase counter and go to next rule (useful for statistics).
redirect - replaces destination port of an IP packet to one specified by to-ports parameter and destination address to one of the router's local addresses
return - passes control back to the chain from where the jump took place
same - gives a particular client the same source/destination IP address from supplied range for each connection. This is most frequently used for services that expect the same client address for multiple connections from the same client
src-nat - replaces source address of an IP packet to values specified by to-addresses and to-ports parameters
address-list (string; Default: )
Name of the address list to be used. Applicable if action is add-dst-to-address-list or add-src-to-address-list
Time interval after which the address will be removed from the address list specified by address-list parameter. Used in conjunction with add-dst-to-address-list or add-src-to-address-list actions
Value of none-dynamic (00:00:00) will leave the address in the address list till reboot
Value of none-static will leave the address in the address list forever and will be included in configuration export/backup
chain (name; Default: )
Specifies to which chain rule will be added. If the input does not match the name of an already defined chain, a new chain will be created.
comment (string; Default: )
Descriptive comment for the rule.
connection-bytes (integer-integer; Default: )
Matches packets only if a given amount of bytes has been transfered through the particular connection. 0 - means infinity, for example connection-bytes=2000000-0 means that the rule matches if more than 2MB has been transfered through the relevant connection
connection-limit (integer,netmaks; Default: )
Matches connections per address or address block after given value is reached.
connection-mark (no-mark | string; Default: )
Matches packets marked via mangle facility with particular connection mark. If no-mark is set, rule will match any unmarked connection.
Matches packets from related connections based on information from their connection tracking helpers. A relevant connection helper must be enabled under /ip firewall service-port
content (string; Default: )
Match packets that contain specified text
dscp (integer: 0..63; Default: )
Matches DSCP IP header field.
dst-address (IP/netmask | IP range; Default: )
Matches packets which destination is equal to specified IP or falls into specified IP range.
dst-address-list (name; Default: )
Matches destination address of a packet against user-defined address list
dst-address-type (unicast | local | broadcast | multicast; Default: )
Matches destination address type:
unicast - IP address used for point to point transmission
local - if dst-address is assigned to one of router's interfaces
broadcast - packet is sent to all devices in subnet
multicast - packet is forwarded to defined group of devices
Matches packets until a given pps limit is exceeded. As opposed to the limit matcher, every destination IP address / destination port has it's own limit. Parameters are written in following format: count[/time],burst,mode[/expire].
count - maximum average packet rate measured in packets per time interval
time - specifies the time interval in which the packet rate is measured (optional)
burst - number of packets which are not counted by packet rate
mode - the classifier for packet rate limiting
expire - specifies interval after which recored ip address /port will be deleted (optional)
dst-port (integer[-integer]: 0..65535; Default: )
List of destination port numbers or port number ranges
fragment (yes|no; Default: )
Matches fragmented packets. First (starting) fragment does not count. If connection tracking is enabled there will be no fragments as system automatically assembles every packet
from-client - matches packets that are coming from the HotSpot client
http - matches HTTP requests sent to the HotSpot server
local-dst - matches packets that are destined to the HotSpot server
to-client - matches packets that are sent to the HotSpot client
icmp-options (integer:integer; Default: )
Matches ICMP type:code fileds
in-bridge-port (name; Default: )
Actual interface the packet has entered the router, if incoming interface is bridge
in-interface (name; Default: )
Interface the packet has entered the router
ingress-priority (integer: 0..63; Default: )
Matches ingress priority of the packet. Priority may be derived from VLAN, WMM or MPLS EXP bit. Read more>>
ipsec-policy (in | out, ipsec | none; Default: )
Matches the policy used by IpSec. Value is written in following format: direction, policy. Direction is Used to select whether to match the policy used for decapsulation or the policy that will be used for encapsulation.
in - valid in the PREROUTING, INPUT and FORWARD chains
out - valid in the POSTROUTING, OUTPUT and FORWARD chains
ipsec - matches if the packet is subject to IpSec processing;
none - matches packet that is not subject to IpSec processing (for example, IpSec transport packet).
For example, if router receives Ipsec encapsulated Gre packet, then rule ipsec-policy=in,ipsec will match Gre packet, but rule ipsec-policy=in,none will match ESP packet.
any - match packet with at least one of the ipv4 options
loose-source-routing - match packets with loose source routing option. This option is used to route the internet datagram based on information supplied by the source
no-record-route - match packets with no record route option. This option is used to route the internet datagram based on information supplied by the source
no-router-alert - match packets with no router alter option
no-source-routing - match packets with no source routing option
no-timestamp - match packets with no timestamp option
record-route - match packets with record route option
router-alert - match packets with router alter option
strict-source-routing - match packets with strict source routing option
timestamp - match packets with timestamp
jump-target (name; Default: )
Name of the target chain to jump to. Applicable only if action=jump
PCC matcher allows to divide traffic into equal streams with ability to keep packets with specific set of options in one particular stream. Read more >>
port (integer[-integer]: 0..65535; Default: )
Matches if any (source or destination) port matches the specified list of ports or port ranges. Applicable only if protocol is TCP or UDP
protocol (name or protocol ID; Default: tcp)
Matches particular IP protocol specified by protocol name or number
psd (integer,time,integer,integer; Default: )
Attempts to detect TCP and UDP scans. Parameters are in following format WeightThreshold, DelayThreshold, LowPortWeight, HighPortWeight
WeightThreshold - total weight of the latest TCP/UDP packets with different destination ports coming from the same host to be treated as port scan sequence
DelayThreshold - delay for the packets with different destination ports coming from the same host to be treated as possible port scan subsequence
LowPortWeight - weight of the packets with privileged (<1024) destination port
HighPortWeight - weight of the packet with non-priviliged destination port
random (integer: 1..99; Default: )
Matches packets randomly with given probability.
routing-mark (string; Default: )
Matches packets marked by mangle facility with particular routing mark
same-not-by-dst (yes | no; Default: )
Specifies whether to take into account or not destination IP address when selecting a new source IP address. Applicable if action=same
src-address (Ip/Netmaks, Ip range; Default: )
Matches packets which source is equal to specified IP or falls into specified IP range.
src-address-list (name; Default: )
Matches source address of a packet against user-defined address list
src-address-type (unicast | local | broadcast | multicast; Default: )
Matches source address type:
unicast - IP address used for point to point transmission
local - if address is assigned to one of router's interfaces
broadcast - packet is sent to all devices in subnet
multicast - packet is forwarded to defined group of devices
src-port (integer[-integer]: 0..65535; Default: )
List of source ports and ranges of source ports. Applicable only if protocol is TCP or UDP.
If you want to "hide" the private LAN 192.168.0.0/24 "behind" one address 10.5.8.109 given to you by the ISP, you should use the source network address translation (masquerading) feature of the MikroTik router. The masquerading will change the source IP address and port of the packets originated from the network 192.168.0.0/24 to the address 10.5.8.109 of the router when the packet is routed through it.
To use masquerading, a source NAT rule with action 'masquerade' should be added to the firewall configuration:
All outgoing connections from the network 192.168.0.0/24 will have source address 10.5.8.109 of the router and source port above 1024. No access from the Internet will be possible to the Local addresses. If you want to allow connections to the server on the local network, you should use destination Network Address Translation (NAT).
Source nat to specific address
If you have multiple public IP addresses, source nat can be changed to specific IP, for example, one local subnet can be hidden behind first IP and second local subnet is masqueraded behind second IP.
If you want to link Public IP 10.5.8.200 address to Local one 192.168.0.109, you should use destination address translation feature of the MikroTik router. Also if you want allow Local server to initiate connections to outside with given Public IP you should use source address translation, too.
If you would like to direct requests for a certain port to an internal machine (sometimes called opening a port, port mapping), you can do it like this:
This rule translates to: when an incoming connection requests TCP port 1234, use the DST-NAT action and redirect it to local address 192.168.1.1 and the port 1234
Port forwarding to internal FTP server
As you can see from illustration above FTP uses more than one connection, but only command channel should be forwarded by Destination nat. Data channel is considered as related connection and should be accepted with "accept related" rule if you have strict firewall. Note that for related connections to be properly detected FTP helper has to be enabled.
Note that active FTP might not work if client is behind dumb firewall or NATed router, because data channel is initiated by the server and cannot directly access the client.
If client is behind Mikrotik router, then make sure that FTP helper is enabled
If you want to link Public IP subnet 11.11.11.0/24 to local one 2.2.2.0/24, you should use destination address translation and source address translation features with action=netmap.
To combat IPv4 address exhaustion, new RFC 6598 was deployed. The idea is to use shared 100.64.0.0/10 address space inside carrier's network and performing NAT on carrier's edge router to sigle public IP or public IP range.
Because of nature of such setup it is also called NAT444, as opposed to a NAT44 network for a 'normal' NAT environment, three different IPv4 address spaces are involved.
CGNAT configuration on RouterOS does not differ from any other regular source NAT configuration:
public_if - interface on providers edge router connected to internet
The advantage of NAT444 is obvious, less public IPv4 addresses used. But this technique comes with mayor drawbacks:
The service provider router performing CGNAT needs to maintain a state table for all the address translations: this requires a lot of memory and CPU resources.
Console gaming problems. Some games fail when two subscribers using the same outside public IPv4 address try to connect to each other.
Tracking of users for legal reasons means extra logging, as multiple households go behind one public address.
Anything requiring incoming connections is broken. While this already was the case with regular NAT, end users could usually still set up port forwarding on their NAT router. CGNAT makes this impossible. This means no web servers can be hosted here, and IP Phones cannot receive incoming calls by default either.
Some web servers only allow a maximum number of connections from the same public IP address, as a means to counter DoS attacks like SYN floods. Using CGNAT this limit is reached more often and some services may be of poor quality.
6to4 requires globally reachable addresses and will not work in networks that employ addresses with limited topological span.
More on things that can break can be read in this article [1]
Packets with Shared Address Space source or destination addresses MUST NOT be forwarded across Service Provider boundaries. Service Providers MUST filter such packets on ingress links.
In RouterOS this can be easily done with firewall filters on edge routers:
Service providers may be required to do logging of MAPed addresses, in large CGN deployed network that may be a problem.
Fortunately RFC 7422 suggests a way to manage CGN translations in such a way as to significantly reduce the amount of logging required while providing traceability for abuse response.
RFC states that instead of logging each connection, CGNs could deterministically map customer private addresses (received on the customer-facing interface of the CGN, a.k.a., internal side) to public addresses extended with port ranges.
In RouterOS described algorithm can be done with few script functions.
Lets take an example:
Inside IP
Outside IP/Port range
100.64.1.1
2.2.2.2:2000-2099
100.64.1.2
2.2.2.2:2100-2199
100.64.1.3
2.2.2.2:2200-2299
100.64.1.4
2.2.2.2:2300-2399
100.64.1.5
2.2.2.2:2400-2499
100.64.1.6
2.2.2.2:2500-2599
Instead of writing NAT mappings by hand we could write a function which adds such rules automatically.
After pasting above script in the terminal function "addNatRules" is available. If we take our example, we need to map 6 shared network addresses to be mapped to 2.2.2.2 and each address uses range of 100 ports starting from 2000. So we run our function:
