Manual IP Firewall Filter - MikroTik Wiki
Manual IP Firewall Filter - MikroTik Wiki
Manual:IP/Firewall/Filter
From MikroTik Wiki
< Manual:IP | Firewall
Contents Applies
to
RouterOS: v3, v4+
1 Summary
2 Chains
3 Properties
4 Stats
5 Menu specific commands
6 Basic examples
6.1 Router protection
6.2 Customer protection
6.3 Brute force protection
Summary
Sub-menu: /ip firewall filter
The firewall implements packet filtering and thereby provides security functions that are used to manage data
flow to, from and through the router. Along with the Network Address Translation it serves as a tool for
preventing unauthorized access to directly attached networks and the router itself as well as a filter for outgoing
traffic.
Network firewalls keep outside threats away from sensitive data available inside the network. Whenever
different networks are joined together, there is always a threat that someone from outside of your network will
break into your LAN. Such break-ins may result in private data being stolen and distributed, valuable data
being altered or destroyed, or entire hard drives being erased. Firewalls are used as a means of preventing or
minimizing the security risks inherent in connecting to other networks. Properly configured firewall plays a key
role in efficient and secure network infrastrure deployment.
MikroTik RouterOS has very powerful firewall implementation with features including:
packet size
packet arrival time
and much more!
Chains
The firewall operates by means of firewall rules. Each rule consists of two parts - the matcher which matches
traffic flow against given conditions and the action which defines what to do with the matched packet.
Firewall filtering rules are grouped together in chains. It allows a packet to be matched against one common
criterion in one chain, and then passed over for processing against some other common criteria to another
chain. For example a packet should be matched against the IP address:port pair. Of course, it could be achieved
by adding as many rules with IP address:port match as required to the forward chain, but a better way could be
to add one rule that matches traffic from a particular IP address, e.g.: /ip firewall filter add src-
address=1.1.1.2/32 jump-target="mychain" and in case of successfull match passes control over the IP packet
to some other chain, id est mychain in this example. Then rules that perform matching against separate ports
can be added to mychain chain without specifying the IP addresses.
input - used to process packets entering the router through one of the interfaces with the destination IP
address which is one of the router's addresses. Packets passing through the router are not processed
against the rules of the input chain
forward - used to process packets passing through the router
output - used to process packets originated from the router and leaving it through one of the interfaces.
Packets passing through the router are not processed against the rules of the output chain
When processing a chain, rules are taken from the chain in the order they are listed there from top to bottom. If
a packet matches the criteria of the rule, then the specified action is performed on it, and no more rules are
processed in that chain (the exception is the passthrough action). If a packet has not matched any rule within
the built-in chain, then it is accepted.
Properties
Property Description
action (action name; Default: accept) Action to take if packet is matched by the rule:
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
address-list-timeout (time; Default: Time interval after which the address will be removed from the
00:00:00) 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 00:00:00 will leave the address in the address list
forever
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; Matches packets only if a given amount of bytes has been
Default: ) 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,netmask; Matches connections per address or address block up to and
Default: ) including given value. Should be used together with connection-
state=new and/or with tcp-flags=syn because matcher is very
resource intensive.
connection-mark (no-mark | string; Matches packets marked via mangle facility with particular
Default: ) connection mark. If no-mark is set, rule will match any
unmarked connection.
connection-nat-state (srcnat | dstnat; Can match connections that are srcnatted, dstnatted or both.
Default: ) Note that connection-state=related connections connection-nat-
state is determined by direction of the first packet. and if
connection tracking needs to use dst-nat to deliver this
connection to same hosts as main connection it will be in
connection-nat-state=dstnat even if there are no dst-nat rules at
all.
connection-rate (Integer 0..4294967295; Connection Rate is a firewall matcher that allow to capture
Default: ) traffic based on present speed of the connection. Read more >>
connection-state (estabilished | invalid | Interprets the connection tracking analysis data for a particular
new | related | untracked; Default: ) packet:
connection-type (ftp | h323 | irc | pptp | Matches packets from related connections based on information
quake3 | sip | tftp; Default: ) 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; Matches packets which destination is equal to specified IP or
Default: ) 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 | Matches destination address type:
broadcast | multicast; Default: )
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
dst-limit (integer[/time],integer,dst- Matches packets until a given rate is exceeded. Rate is defined
address | dst-port | src-address[/time]; as packets per time interval. As opposed to the limit matcher,
Default: ) every flow has it's own limit. Flow is defined by mode
parameter. Parameters are written in following format:
count[/time],burst,mode[/expire].
dst-port (integer[-integer]: 0..65535; List of destination port numbers or port number ranges
Default: )
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
hotspot (auth | from-client | http | local-
dst | to-client; Default: )
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. Works only if use-ip-firewall is enabled in
bridge settings.
in-bridge-port-list (name; Default: ) Set of interfaces defined in interface list. Works the same as
in-bridge-port
in-interface (name; Default: ) Interface the packet has entered the router
in-interface-list (name; Default: ) Set of interfaces defined in interface list. Works the same as
in-interface
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; Matches the policy used by IpSec. Value is written in following
Default: ) 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.
https://wiki.mikrotik.com/wiki/Manual:IP/Firewall/Filter 5/11
28/08/2018 Manual:IP/Firewall/Filter - MikroTik Wiki
jump-target (name; Default: ) Name of the target chain to jump to. Applicable only if
action=jump
layer7-protocol (name; Default: ) Layer7 filter name defined in layer7 protocol menu.
limit (integer,time,integer; Default: ) Matches packets up to a limited rate (packet rate or bit rate).
Rule using this matcher will match until this limit is reached.
Parameters are written in following format:
count[/time],burst:mode.
log-prefix (string; Default: ) Adds specified text at the beginning of every log message.
Applicable if action=log
nth (integer,integer; Default: ) Matches every nth packet. Read more >>
out-bridge-port (name; Default: ) Actual interface the packet is leaving the router, if outgoing
interface is bridge. Works only if use-ip-firewall is enabled in
bridge settings.
out-bridge-port-list (name; Default: ) Set of interfaces defined in interface list. Works the same as
out-bridge-port
p2p (all-p2p | bit-torrent | blubster | Matches packets from various peer-to-peer (P2P) protocols.
direct-connect | edonkey | fasttrack | Does not work on encrypted p2p packets.
gnutella | soulseek | warez | winmx;
Default: )
packet-mark (no-mark | string; Default: ) Matches packets marked via mangle facility with particular
packet mark. If no-mark is set, rule will match any unmarked
packet.
packet-size (integer[-integer]:0..65535; Matches packets of specified size or size range in bytes.
Default: )
per-connection-classifier PCC matcher allows to divide traffic into equal streams with
(ValuesToHash:Denominator/Remainder; ability to keep packets with specific set of options in one
https://wiki.mikrotik.com/wiki/Manual:IP/Firewall/Filter 6/11
28/08/2018 Manual:IP/Firewall/Filter - MikroTik Wiki
random (integer: 1..99; Default: ) Matches packets randomly with given probability.
reject-with (icmp-admin-prohibited | Specifies ICMP error to be sent back if packet is rejected.
icmp-net-prohibited | icmp-protocol- Applicable if action=reject
unreachable | icmp-host-prohibited |
icmp-network-unreachable | tcp-reset |
icmp-host-unreachable | icmp-port-
unreachable; Default: icmp-network-
unreachable)
routing-mark (string; Default: ) Matches packets marked by mangle facility with particular
routing mark
src-address (Ip/Netmaks, Ip range; Matches packets which source is equal to specified IP or falls
Default: ) 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:
src-port (integer[-integer]: 0..65535; List of source ports and ranges of source ports. Applicable only
Default: ) if protocol is TCP or UDP.
src-mac-address (MAC address; Default: Matches source MAC address of the packet
https://wiki.mikrotik.com/wiki/Manual:IP/Firewall/Filter 7/11
28/08/2018 Manual:IP/Firewall/Filter - MikroTik Wiki
)
tcp-flags (ack | cwr | ece | fin | psh | rst | Matches specified TCP flags
syn | urg; Default: )
ack - acknowledging data
cwr - congestion window reduced
ece - ECN-echo flag (explicit congestion notification)
fin - close connection
psh - push function
rst - drop connection
syn - new connection
urg - urgent data
Stats
/ip firewall filter print stats will show additional read-only properties
Property Description
bytes (integer) Total amount of bytes matched by the rule
packets (integer) Total amount of packets matched by the rule
By default print is equivalent to print static and shows only static rules.
https://wiki.mikrotik.com/wiki/Manual:IP/Firewall/Filter 8/11
28/08/2018 Manual:IP/Firewall/Filter - MikroTik Wiki
Basic examples
Router protection
Lets say our private network is 192.168.0.0/24 and public (WAN) interface is ether1. We will set up firewall to
allow connections to router itself only from our local network and drop the rest. Also we will allow ICMP
protocol on any interface so that anyone can ping your router from internet.
Customer protection
To protect the customer's network, we should check all traffic which goes through router and block unwanted.
For icmp, tcp, udp traffic we will create chains, where will be droped all unwanted packets:
Bruteforce_login_prevention_(FTP_&_SSH)
https://wiki.mikrotik.com/wiki/Manual:IP/Firewall/Filter 10/11
28/08/2018 Manual:IP/Firewall/Filter - MikroTik Wiki
https://wiki.mikrotik.com/wiki/Manual:IP/Firewall/Filter 11/11