mtik3
mtik3
Manual:IP/Firewall/Mangle
< Manual:IP| Firewall
Revision as of 05:58, 26 April 2022 by Olga (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Contents
Summary
Properties
Stats
Menu specific commands
Basic examples
Change MSS
Marking packets
Summary
Sub-menu: /ip firewall mangle
Mangle is a kind of 'marker' that marks packets for future processing with special marks. Many
other facilities in RouterOS make use of these marks, e.g. queue trees, NAT, routing. They identify
a packet based on its mark and process it accordingly. The mangle marks exist only within the
router, they are not transmitted across the network.
Additionally, the mangle facility is used to modify some fields in the IP header, like TOS (DSCP)
and TTL fields.
Properties
Property Description
action (action name; Default: accept) Action to take if packet is matched by the rule:
https://wiki.mikrotik.com/index.php?title=Manual:IP/Firewall/Mangle&oldid=34539 1/12
12/14/24, 2:16 AM Manual:IP/Firewall/Mangle - MikroTik Wiki
https://wiki.mikrotik.com/index.php?title=Manual:IP/Firewall/Mangle&oldid=34539 2/12
12/14/24, 2:16 AM Manual:IP/Firewall/Mangle - MikroTik Wiki
chain (name; Default: ) Specifies to which chain the 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 (upload and download) has been
transfered through the relevant connection
connection-limit (integer,netmask; Matches connections per address or address block
Default: ) after given value is reached.
connection-mark (no-mark | string; Matches packets marked via mangle facility with
Default: ) particular connection mark. If no-mark is set, rule will
match any unmarked connection.
https://wiki.mikrotik.com/index.php?title=Manual:IP/Firewall/Mangle&oldid=34539 3/12
12/14/24, 2:16 AM Manual:IP/Firewall/Mangle - MikroTik Wiki
connection-nat-state (srcnat | dstnat; Can match connections that are srcnatted, dstnatted
Default: ) or both. 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 allows the
Default: ) capture of traffic based on the present speed of the
connection. Read more >>
connection-state (estabilished | invalid | Interprets the connection tracking analysis data for a
new | related; Default: ) particular packet:
connection-type (ftp | h323 | irc | pptp | Matches packets from related connections based on
quake3 | sip | tftp; Default: ) 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; Matches packets where destination is equal to
Default: ) specified IP or falls into specified IP range.
dst-address-list (name; Default: ) Matches destination address of a packet against
user-defined address list
https://wiki.mikrotik.com/index.php?title=Manual:IP/Firewall/Mangle&oldid=34539 4/12
12/14/24, 2:16 AM Manual:IP/Firewall/Mangle - MikroTik Wiki
https://wiki.mikrotik.com/index.php?title=Manual:IP/Firewall/Mangle&oldid=34539 5/12
12/14/24, 2:16 AM Manual:IP/Firewall/Mangle - MikroTik Wiki
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; Matches the policy used by IpSec. Value is written in
Default: ) 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.
https://wiki.mikrotik.com/index.php?title=Manual:IP/Firewall/Mangle&oldid=34539 6/12
12/14/24, 2:16 AM Manual:IP/Firewall/Mangle - 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 until a given pps limit is exceeded.
Parameters are written in following format:
count[/time],burst.
log-prefix (string; Default: ) Adds specified text at the beginning of every log
message. Applicable if action=log
new-connection-mark (string; Default: )
new-dscp (integer: 0..63; Default: ) Sets a new DSCP value for a packet.
new-mss (integer; Default: ) Sets a new MSS for a packet. clamp-to-pmtu option
dynamically sets the MSS size acordingly to the Path
MTU.
new-packet-mark (string; Default: )
https://wiki.mikrotik.com/index.php?title=Manual:IP/Firewall/Mangle&oldid=34539 7/12
12/14/24, 2:16 AM Manual:IP/Firewall/Mangle - MikroTik Wiki
new-priority(integer | from-dscp | from- Sets a new priority for a packet. This can be the
dscp-high-3-bits | from-ingress; Default: ) VLAN, WMM, DSCP or MPLS EXP priority Read
more >>. This property can also be used to set an
internal priority.
new-routing-mark (string; Default: )
new-ttl (decrement | increment |
set:integer; Default: )
nth (integer,integer; Default: ) Matches every nth packet. Read more (https://wiki.mi
krotik.com/wiki/NTH_load_balancing_with_masquera
de)
out-bridge-port (name; Default: ) Actual interface the packet is leaving the router, if
outgoing interface is bridge
out-interface (; Default: ) Interface the packet is leaving the router
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
Default: ) bytes.
passthrough (yes|no; Default: yes) whether to let the packet to pass further (like action
passthrough) into firewall or not (property only valid
some actions).
per-connection-classifier PCC matcher allows division of traffic into equal
(ValuesToHash:Denominator/Remainder; streams with ability to keep packets with specific set
Default: ) 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: Matches particular IP protocol specified by protocol
tcp) 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
random (integer: 1..99; Default: ) Matches packets randomly with given probability.
https://wiki.mikrotik.com/index.php?title=Manual:IP/Firewall/Mangle&oldid=34539 8/12
12/14/24, 2:16 AM Manual:IP/Firewall/Mangle - MikroTik Wiki
src-port (integer[-integer]: 0..65535; List of source ports and ranges of source ports.
Default: ) Applicable only if protocol is TCP or UDP.
src-mac-address (MAC address; Default: ) Matches source MAC address of the packet
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
https://wiki.mikrotik.com/index.php?title=Manual:IP/Firewall/Mangle&oldid=34539 9/12
12/14/24, 2:16 AM Manual:IP/Firewall/Mangle - MikroTik Wiki
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/index.php?title=Manual:IP/Firewall/Mangle&oldid=34539 10/12
12/14/24, 2:16 AM Manual:IP/Firewall/Mangle - MikroTik Wiki
Basic examples
Change MSS
It is a well known fact that VPN links have smaller packet size due to encapsulation overhead. A
large packet with MSS that exceeds the MSS of the VPN link should be fragmented prior to sending
it via that kind of connection. However, if the packet has DF flag set, it cannot be fragmented and
should be discarded. On links that have broken path MTU discovery (PMTUD) it may lead to a
number of problems, including problems with FTP and HTTP data transfer and e-mail services.
In case of link with broken PMTUD, a decrease of the MSS of the packets coming through the VPN
link solves the problem. The following example demonstrates how to decrease the MSS value via
mangle:
Marking packets
Marking each packet is quite resource expensive especially if rule has to match against many
parameters from IP header or address list containing hundreds of entries.
mark all tcp packets except tcp/80 and match these packets against first address list
mark all udp packets and match them against second address list.
Setup looks quite simple and probably will work without problems in small networks. Now
multiply count of rules by 10, add few hundred entries in address list, run 100Mbit of traffic over
this router and you will see how rapidly CPU usage is increasing. The reason for such behavior is
that each rule reads IP header of every packet and tries to match collected data against parameters
specified in firewall rule.
Fortunately if connection tracking is enabled, we can use connection marks to optimize our setup.
https://wiki.mikrotik.com/index.php?title=Manual:IP/Firewall/Mangle&oldid=34539 11/12
12/14/24, 2:16 AM Manual:IP/Firewall/Mangle - MikroTik Wiki
new-connection-mark=second
add chain=forward connection-mark=second action=mark-packet new-packet-mark=second passthrough=no
Now first rule will try to match data from IP header only from first packet of new connection and
add connection mark. Next rule will no longer check IP header for each packet, it will just compare
connection marks resulting in lower CPU consumption. Additionally passthrough=no was added
that helps to reduce CPU consumption even more.
https://wiki.mikrotik.com/index.php?title=Manual:IP/Firewall/Mangle&oldid=34539 12/12