Page MenuHomeVyOS Platform
Create Task
Maniphest T3061

OSPF v2 - Filtered route is added to the routing table as inactive
Resolved (N/A)PublicBUG
Actions

Description

When a route is filtered using route-map (like set protocols ospf route-map 'default-route'), the route appears in the OSPF database (as expected) but also in the routing table as "inactive". Example for 0.0.0.0/0 (which was filtered):
O 0.0.0.0/0 [110/10] via 192.168.1.244, eth0 inactive, 00:07:41

As a result, other routing rules that depend on the existence of that route in the routing table might lead to incorrect results.
Example:
The router with the inactive 0.0.0.0/0 will still redistribute a default route via "set protocols ospf default-information originate". This should not be the case as 0.0.0.0/0 should not be in the routing table!

Details

Difficulty level
Unknown (require assessment)
Version
1.2.6-S1
Why the issue appeared?
Issues in third-party code
Is it a breaking change?
Unspecified (possibly destroys the router)

Event Timeline

mplanquart created this task.Nov 12 2020, 1:53 PM
Viacheslav added a subscriber: Viacheslav.EditedNov 12 2020, 1:58 PM

This is expected behavior, so routes not installed in the routing table.

pasik added a subscriber: pasik.Nov 12 2020, 2:24 PM
Viacheslav added a comment.Nov 12 2020, 4:56 PM

Imagine if you use for example BGP and don't have a default route or set it to blackhole.
Then you originate the default route for a neighbor.
Why it should not announce the default route to the neighbor?

mplanquart added a comment.Nov 12 2020, 6:33 PM

The issue here is that "set protocols ospf default-information originate" propagates a default route even if there is an inactive route for 0.0.0.0/0. It should only propagate if "always" is used. So, maybe the inactive route is not in the routing table (in the routing sense) but it seems to be taken into consideration for redistribution.

Note that Cisco and Brocade routers (the other one I used) behave as I expected (so differently than VyOS).

Thanks.

Viacheslav changed Why the issue appeared? from Will be filled on close to Issues in third-party code.May 13 2021, 9:28 PM
dmbaturin closed this task as Resolved N/A.Jan 9 2024, 6:37 PM