Change Details

Currently, routing behavior within the IntraNought network is inconsistent. Windriver can reach other machines through GRE tunnels, but return traffic is not always properly routed. This is due to the fact that several machines still rely on a static default gateway: ``` 172.27.27.1 ``` **Goal : ** - Ensure all IntraNought nodes participate in OSPF (via FRRouting) - Remove static default gateway (172.27.27.1) where applicable - Allow nodes to receive the default route dynamically via OSPF

In the current setup, some IntraNought nodes still rely on a static default gateway (172.27.27.1), which leads to inconsistent and asymmetric routing. To ensure correct behavior, the active (MASTER) router must advertise the default route via OSPF, while all IntraNought nodes dynamically learn and use this route. This guarantees that: - traffic always follows the active router, - routing remains consistent across the network, - failover (CARP) is properly reflected in routing.

CurrentlyIn the current setup, some IntraNought nodes still rely on a static default gateway (172.27.27.1), routing behavior within the IntraNought network is inconsistentwhich leads to inconsistent and asymmetric routing. Windriver can reach other machines through GRE tunnelsTo ensure correct behavior, but return traffic is not always properlythe active (MASTER) router must advertise the default routed. via OSPF, This is due to the fact that several machines still rely on a static default gateway: ``` 172.27.27.1 ```while all IntraNought nodes dynamically learn and use this route. **Goal : **This guarantees that: - Ensure all IntraNought nodes participate in OSPF (via FRRouting) - Remove static default gateway (172.27.27.1) where applicable- traffic always follows the active router, - Allow nodes to receive the default route dynamically via OSPF- routing remains consistent across the network, - failover (CARP) is properly reflected in routing.