Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

/routing/filter/community-list

PropertyDescription
comment (string; Default: )
communities (list of communities; Default: )

List of communities expressed either as well-known name or in the following format: "as:number", where each section can be integer [0..65535].

Accepted well known names:

accept-own     graceful-shutdown  no-advertise         no-llgr         route-filter-6      
accept-own-nh  internet           no-export            no-peer         route-filter-xlate-4
blackhole      llgr-stale         local-as  route-filter-4  route-filter-xlate-6

disabled (yes | no)
name (integer [string; Default: )Reference name.
regexp (string)Regexp matcher to match communities. The community set with only the regexp parameter cannot be used to append communities.

/routing/filter/community-ext-list

PropertyDescription
comment (string; Default: )
communities (list of ext communities; Default: )

List of extended communities expressed as raw integer value or in the typed format: "type:value", where type can be:

  • rt - route-target
  • soo -  site of origin

Value depends on the type, for more info on RT and SoO values ask google.

disabled (yes | no)
name (integer [string; Default: )Reference name.
regexp (string)Regexp matcher to match communities. The community set with only the regexp parameter cannot be used to append communities.

/routing/filter/community-large-list

PropertyDescription
comment (string; Default: )
communities (list of large communities; Default: )

List of large communities expressed in following format: "admin:value1:value2", where each section can be integer [0..4294967295].

disabled (yes | no)
name (integer [string; Default: )Reference name.
regexp (string)Regexp matcher to match communities. The community set with only the regexp parameter cannot be used to append communities.


Route Selection

Route selection rules allow controlling how output routes are selected from available candidate routes. By default, (if no selection rules are set) output always picks the best route.

...

Selection rules in RouterOS are configured from /routing/filter/select-rule menu.

Select rules can also call routing filters where routes get selected based on filter rules. For example, to mimic default output selection we can set up the following rule sets:

Code Block
languageros
/routing filter rule 
add chain=get_active rule="if (active) {accept}"

/routing filter select-rule
add chain=my_select_chain do-where=get_active


Property Reference

/routing/filter/chain

...