Skip to content

Routing Settings

The /routing/settings menu is much smaller than some older or unverified examples suggest. On verified RouterOS 7.15.3 CHR systems, this menu exposes a single configurable property: single-process.

Use /routing/settings to control whether the routing stack runs in a single process.

/routing/settings/print

Typical output:

single-process: no
PropertyTypeDefaultDescription
single-processyes | nonoRuns routing in a single process when enabled.

Enable single-process mode:

/routing/settings/set single-process=yes

Return to the default behavior:

/routing/settings/set single-process=no

Verify the current setting:

/routing/settings/print

The following items are not documented here because they were not present in the verified /routing/settings menu:

  • ECMP tuning such as ecmp-mode or l3-encoding
  • Redistribution controls such as redistribute-connected
  • Default per-protocol distances such as static-distance, ospf-distance, or bgp-distance
  • Route marking or distribution properties such as route-mark, route-distribute, or route-filter

If you need to place a static route into a non-main routing table, configure that on the route itself with routing-table=, not through /routing/settings.

On RouterOS v7, /ip/route/add does not accept routing-mark=. The routing-table= value must be the name of an existing table such as main or a table you created under /routing/table; an arbitrary string like custom-mark is not valid unless that table already exists.

/routing/table/add name=tenant-a
/ip/route/add dst-address=10.20.0.0/16 gateway=172.16.1.2 routing-table=tenant-a
  • Verified on RouterOS 7.15.3 CHR.
  • Properties sometimes described elsewhere under /routing/settings, such as ECMP, redistribution, route marks, or default administrative distances, were not present in the verified menu and are intentionally not documented here.
  • This page is intentionally limited to the verified single-process setting; it does not describe OSPF, BGP template, or routing-filter behavior.