Page MenuHomeDevCentral

Installation and configuration of FRRouting
Open, NormalPublic

Description

Based on the T2208 (Quagga), this task aims to migrate to FRRouting.

FRRouting will replace Quagga as the routing suite to manage dynamic routing (we will use OSPF integrated in FRRouting).


Steps on routers :

  • 1. Install FRRouting on router-002 and router-003 D4055
  • 2. Activate the service D4055
  • 3. Create the FRR configuration with OSPF added D4093

FRRouting should also be installes on Ysul and Windriver :

  • 1. Install FRRouting D4093
  • 2. Activate the service D4093
  • 3. Create the FRR configuration with OSPF added D4093

References :

https://en.wikipedia.org/wiki/FRRouting
https://docs.opnsense.org/manual/dynamic_routing.html
https://docs.frrouting.org/en/latest/ospfd.html
https://docs.frrouting.org/en/latest/vtysh.html
https://man.freebsd.org/cgi/man.cgi?query=vtysh&sektion=1&manpath=freebsd-ports
https://community.cisco.com/t5/networking-knowledge-base/understanding-passive-interface-default-command-in-ospf/ta-p/3120648
https://packetpushers.net/blog/understanding-ospf-router-id-rid-assignment

Event Timeline

yousra triaged this task as Normal priority.Thu, Apr 9, 08:38
yousra created this task.
yousra updated the task description. (Show Details)
yousra updated the task description. (Show Details)
yousra updated the task description. (Show Details)

command : sudo vtysh

router-002# show ip ospf route
============ OSPF network routing table ============
N    172.27.27.0/27        [10] area: 0.0.0.0
                           directly attached to vmx0

============ OSPF router routing table =============

============ OSPF external routing table ===========


router-002#

commande : router-002# show ip ospf interface

gre1 is up
  ifindex 4, MTU 1476 bytes, BW 0 Mbit <UP,POINTOPOINT,RUNNING,MULTICAST>
  This interface is UNNUMBERED, Area 0.0.0.0
  MTU mismatch detection: enabled
  Router ID 2.2.2.2, Network Type POINTOPOINT, Cost: 10
  Transmit Delay is 1 sec, State Point-To-Point, Priority 1
  No backup designated router on this network
  Multicast group memberships: OSPFAllRouters
  Timer intervals configured, Hello 10s, Dead 40s, Wait 40s, Retransmit 5
    Hello due in 7.934s
  Neighbor Count is 0, Adjacent neighbor count is 0
  Graceful Restart hello delay: 10s
  LSA retransmissions: 0
gre2 is up
  ifindex 7, MTU 1476 bytes, BW 0 Mbit <UP,POINTOPOINT,RUNNING,MULTICAST>
  This interface is UNNUMBERED, Area 0.0.0.0
  MTU mismatch detection: enabled
  Router ID 2.2.2.2, Network Type POINTOPOINT, Cost: 10
  Transmit Delay is 1 sec, State Point-To-Point, Priority 1
  No backup designated router on this network
  Multicast group memberships: OSPFAllRouters
  Timer intervals configured, Hello 10s, Dead 40s, Wait 40s, Retransmit 5
    Hello due in 0.519s
  Neighbor Count is 0, Adjacent neighbor count is 0
  Graceful Restart hello delay: 10s
  LSA retransmissions: 0
vmx0 is up
  ifindex 1, MTU 1500 bytes, BW 10000 Mbit <UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
  Internet Address 172.27.27.11/27, Broadcast 172.27.27.31, Area 0.0.0.0
  MTU mismatch detection: enabled
  Router ID 2.2.2.2, Network Type BROADCAST, Cost: 10
  Transmit Delay is 1 sec, State DR, Priority 1
  Designated Router (ID) 2.2.2.2 Interface Address 172.27.27.11/27
  No backup designated router on this network
  Multicast group memberships: <None>
  Timer intervals configured, Hello 10s, Dead 40s, Wait 40s, Retransmit 5
    No Hellos (Passive interface)
  Neighbor Count is 0, Adjacent neighbor count is 0
  Graceful Restart hello delay: 10s
  LSA retransmissions: 0

The vtysh command-line tool is used to interact with FRRouting and display routing information.

The OSPF routing table shows the IntraNought network (172.27.27.0/27), which will be shared with Windriver and Ysul.

The OSPF interface configuration shows that OSPF is enabled on both vmx0 and gre1, gre2.

yousra updated the task description. (Show Details)
yousra updated the task description. (Show Details)
yousra updated the task description. (Show Details)

ysul.nasqueron.org# show ip ospf neighbor

Neighbor ID     Pri State           Up Time         Dead Time Address         Interface                        RXmtL RqstL DBsmL
2.2.2.2           1 Full/-          1h30m05s          32.570s 172.27.27.250   gre1:172.27.27.31                    0     0     0

ysul.nasqueron.org# show ip ospf route

============ OSPF network routing table ============
N    172.27.27.0/27        [20] area: 0.0.0.0
                           via 172.27.27.250, gre1

============ OSPF router routing table =============

============ OSPF external routing table ===========

netstat -rn

172.27.27.0/27     172.27.27.250      UG1            gre1

An OSPF adjacency is successfully established between ysul and router-002 through the GRE tunnel. This allows dynamic route exchange, as shown by the learned 172.27.27.0/27 network via OSPF.

ysul.nasqueron.org# show ip ospf neighbor

Neighbor ID     Pri State           Up Time         Dead Time Address         Interface                        RXmtL RqstL DBsmL
2.2.2.2           1 Init/-          14m09s            32.374s 172.27.27.250   gre1:172.27.27.31                    0     0     0
3.3.3.3           1 Full/-          17.178s           31.923s 172.27.27.254   gre1:172.27.27.31                    0     0     0

ysul.nasqueron.org# show ip ospf route

============ OSPF network routing table ============
N    172.27.27.0/27        [20] area: 0.0.0.0
                           via 172.27.27.254, gre1

============ OSPF router routing table =============

============ OSPF external routing table ===========

netstat -rn

172.27.27.0/27     172.27.27.254      UG1            gre1

In this context, Ysul maintains a GRE tunnel toward the VIP, which now reaches router-003. As a result, a FULL OSPF adjacency is successfully established with router-003, allowing Ysul to learn and install the correct route to the internal network (172.27.27.0/27).

Router-002, however, still appears in the OSPF neighbor table in INIT state. This is because, although the tunnel has been reconfigured on Ysul, it remains active on router-002. Consequently, router-002 continues to send OSPF Hello packets that are still received by Ysul through the GRE interface toward the VIP.

Since GRE is stateless, packets can be sent even if the return path is no longer valid.

So basically the communication between Ysul and router-002 is no longer bidirectional, it is why the OSPF adjacency cannot be established. As a result, no routing information is exchanged and router-002 is not used for forwarding traffic. This behavior is acceptable in this context, as it does not impact routing.