{{Warning|This manual is moved to https://help.mikrotik.com/docs/display/ROS/IP+Settings}}
__TOC__
__TOC__
Line 49:
Line 51:
|type=time interval
|type=time interval
|default=30s
|default=30s
|desc=ARP timeout on all interfaces that use ARP. Can use postfix ms, s, m, h, d for milliseconds, seconds, minutes, hours or days. if no postfix is set then seconds (s) is used.
|desc=Sets Linux <b>base_reachable_time</b> (base_reachable_time_ms) on all interfaces that use ARP. Initial validity of ARP entry is picked from interval [timeout/2..3*timeout/2] (default from 15s to 45s) after neighbor was found. Can use postfix ms, s, m, h, d for milliseconds, seconds, minutes, hours or days. if no postfix is set then seconds (s) is used. Parameter <b>DOES NOT</b> represent a time when ARP entry is removed from ARP cache, ARP cache entries can be stored in the cache for up to 10minutes if reference in route cache is created.
}}
}}
Line 82:
Line 84:
* loose - Loose mode as defined in RFC3704 Loose Reverse Path. Each incoming packet's source address is also tested against the FIB and if the source address is not reachable via any interface the packet check will fail.
* loose - Loose mode as defined in RFC3704 Loose Reverse Path. Each incoming packet's source address is also tested against the FIB and if the source address is not reachable via any interface the packet check will fail.
Current recommended practice in RFC3704 is to enable strict mode to prevent IP spoofing from DDos attacks. If using asymmetric routing or other complicated routing or VRRP, then loose mode is recommended.
Current recommended practice in RFC3704 is to enable strict mode to prevent IP spoofing from DDoS attacks. If using asymmetric routing or other complicated routing or VRRP, then loose mode is recommended.{{Warning | strict mode does not work with routing tables}}
}}
}}
Line 110:
Line 112:
{{Mr-arg-table
{{Mr-arg-table
|arg=max-neighbor-entries
|arg=max-neighbor-entries
|type=integer [0..4294967295]
|type=integer [0..2147483647]
|default=
|default=
|desc= Maximum number of allowed neighbors in ARP table.
|desc= Maximum number of allowed neighbors in ARP table.
Line 119:
Line 121:
|type=yes {{!}} no
|type=yes {{!}} no
|default=yes
|default=yes
|desc= Disable or enable Linux route cache.
|desc= Disable or enable Linux route cache. Note that by disabling route cache, it will also disable fast path.
Sets Linux base_reachable_time (base_reachable_time_ms) on all interfaces that use ARP. Initial validity of ARP entry is picked from interval [timeout/2..3*timeout/2] (default from 15s to 45s) after neighbor was found. Can use postfix ms, s, m, h, d for milliseconds, seconds, minutes, hours or days. if no postfix is set then seconds (s) is used. Parameter DOES NOT represent a time when ARP entry is removed from ARP cache, ARP cache entries can be stored in the cache for up to 10minutes if reference in route cache is created.
Limit the maximum rates for sending ICMP packets whose type matches icmp-rate-mask to specific targets. 0 to disable any limiting, otherwise the minimum space between responses in milliseconds.
Enable/disable packet forwarding between interfaces. Resets all configuration parameters to defaults according to RFC1812 for routers.
rp-filter (loose | no | strict; Default: no)
Disables enables source validation.
no - No source validation.
strict - Strict mode as defined in RFC3704 Strict Reverse Path. Each incoming packet is tested against the FIB and if the interface is not the best reverse path the packet check will fail. By default failed packets are discarded.
loose - Loose mode as defined in RFC3704 Loose Reverse Path. Each incoming packet's source address is also tested against the FIB and if the source address is not reachable via any interface the packet check will fail.
Current recommended practice in RFC3704 is to enable strict mode to prevent IP spoofing from DDoS attacks. If using asymmetric routing or other complicated routing or VRRP, then loose mode is recommended.
Warning: strict mode does not work with routing tables
secure-redirects (yes | no; Default: yes)
Accept ICMP redirect messages only for gateways, listed in default gateway list.
send-redirects (yes | no; Default: yes)
Whether to send ICMP redirects. Recommended to be enabled on routers.
tcp-syncookies (yes | no; Default: no)
Send out syncookies when the syn backlog queue of a socket overflows. This is to prevent against the common 'SYN flood attack'.
syncookies seriously violate TCP protocol, do not allow o use TCP extensions, can result in serious degradation of some services (f.e. SMTP relaying), visible not by you, but your clients and relays, contacting you.
