Going further,
under performance test results on example Mikrotik device page there is a specified configuration "25 ip filter rules".
How to read this?
Let's say I have 1000 forward rules on positions 2-999Traffic from 10.0.0.10
- to 10.0.20.31 will be affected by 1 rule?
- 10.0.123.145 will be affected by 4 rules?
<=> thus performance is only affected by "number of filters that traffic was tested against before matched"?
<=> thus any amount of filters that are virtually unreachable for traffic (matched before) will not affect performance (as long as there is enough memory they will be occupying while rotting![;)]( "Wink")
) (?)
+ question from original post - how exhausting is jumping without reason?
under performance test results on example Mikrotik device page there is a specified configuration "25 ip filter rules".
How to read this?
Let's say I have 1000 forward rules on positions 2-999
Code:
add action=accept chain=forward src-address=10.0.0.10 in-interface-list=trusted dst-address=10.0.20.31 out-interface-list=!WAN add action=accept chain=forward src-address=10.0.0.10 in-interface-list=trusted dst-address=10.0.20.34 out-interface-list=!WANadd action=accept chain=forward src-address=10.0.0.10 in-interface-list=trusted dst-address=10.0.111.123 out-interface-list=!WANadd action=accept chain=forward src-address=10.0.0.10 in-interface-list=trusted dst-address=10.0.123.145 out-interface-list=!WAN # and so on...- to 10.0.20.31 will be affected by 1 rule?
- 10.0.123.145 will be affected by 4 rules?
<=> thus performance is only affected by "number of filters that traffic was tested against before matched"?
<=> thus any amount of filters that are virtually unreachable for traffic (matched before) will not affect performance (as long as there is enough memory they will be occupying while rotting
) (?)+ question from original post - how exhausting is jumping without reason?
Statistics: Posted by ccky — Wed Dec 13, 2023 12:35 pm