24 docs tagged with "routing"

Understand the concept of OSPF areas and virtual links.

Bidirectional Forwarding Detection (BFD) is a low-latency protocol for detecting faults in network paths, operating independently of routing protocols. It uses UDP encapsulation with configurable ports and supports multihop sessions, but currently lacks echo mode and authentication. Configuration involves specifying interfaces, addresses, and VRFs in RouterOS CLI.

This page introduces BGP (Border Gateway Protocol) configuration in MikroTik RouterOS, covering basic setup and routing concepts for establishing external network connectivity using BGP.

Frequently asked questions.

Frequently asked questions.

The IGMP Proxy feature in RouterOS enables multicast routing by forwarding IGMP frames, offering a simpler alternative to PIM-SM for certain topologies. It supports basic multicast forwarding with minimal resource usage but lacks support for complex routing setups and loop detection.

IS-IS is an Interior Gateway Protocol used for distributing IP routing information within a single Autonomous System, operating as a link-state protocol that exchanges topology data between neighbors. It supports IPv4 and IPv6, uses TLV-based extensions, and requires configuration of area IDs, system IDs, and NSAP addresses for proper routing.

This page documents the transition from RouterOS v6 to v7, highlighting key changes such as increased routing table limits, new `/routing/table` and `/routing/rule` menus, improved route processing speed, and differences in policy routing. It includes examples for configuring custom routing tables, multi-WAN setups, and troubleshooting mangle rule conflicts.

Introduction on how neighbor relationships and adjacencies are formed.

BGP nexthop selection procedures on input and output.

OSPF (Open Shortest Path First) is a routing protocol used in MikroTik RouterOS to dynamically exchange route information and determine the best paths for data transmission within a network.

Introduction on how to establish BGP sessions.

Policy routing in RouterOS allows steering traffic based on criteria to specific gateways, using custom routing tables and rules. It supports dynamic routing decisions with firewall mangle marking or basic routing rule configurations for traffic control.

MikroTik RouterOS supports RIP version 2 for exchanging routing information within autonomous systems, selecting optimal paths based on hop count. Configuration is available under `/routing/rip`.

Route Distinguisher (RD) adds unique prefixes to customer addresses for VRF differentiation, while Route Targets control BGP routing information exchange between instances.

This section provides guides for RouterOS routing and networking protocols, covering routing decisions, policy routing, VRF, route filtering, and major protocols like BGP, OSPF, RIP, EVPN, MPLS, along with migration from RouterOS v6 to v7 for network design and troubleshooting.

Routing decision in MikroTik RouterOS involves selecting paths for packet transmission using FIB and RIB tables, managing connected networks, default routes, and hardware offloading for efficient packet forwarding.

RouterOS v7 enables multi-core routing by distributing tasks like FIB updates, BGP processing, and protocol handling across separate processes. Each sub-task uses private or shared memory, with BGP input/output affinity customizable via CLI. Memory usage and task status can be monitored using dedicated commands, enhancing performance on multi-core devices.

Basic understanding of shortest path calculation.

Overview of BGP protocol basics.

Overview of OSPF protocol basics.

This section provides guides for configuring and understanding unicast routing protocols including BGP, OSPF, RIP, IS-IS, BFD, RPKI, and EVPN in MikroTik RouterOS.

User guides offer detailed RouterOS configuration and design guidance, with specific sections available for routing and networking protocols.

RouterOS enables creating multiple Virtual Routing and Forwarding (VRF) instances for BGP-based MPLS VPNs, allowing separate routing tables and IP prefix isolation. VRF configurations are managed via the `/ip/vrf` menu, with routing table mappings created automatically. Each VRF supports up to 1024 instances and requires explicit service configuration for VRF-aware