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.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Nov 12 2020
Nov 12 2020
mplanquart added a comment to T3061: OSPF v2 - Filtered route is added to the routing table as inactive.
Jul 18 2018
Jul 18 2018
mplanquart renamed T748: OSPFv3 - IPv6 OSPF not working properly after the neighbor pushing ::/0 is disconnected from OSPFv3 - IPv6 OSPF not properly after the neighbor pushing ::/0 is disconnected (even though one neighbor is still alive) to OSPFv3 - IPv6 OSPF not working properly after the neighbor pushing ::/0 is disconnected .
mplanquart renamed T748: OSPFv3 - IPv6 OSPF not working properly after the neighbor pushing ::/0 is disconnected from OSPFv3 - IPv6 Routing table entries of a disconnected neighbor are not cleared/replaced by the entries of the other neighbor to OSPFv3 - IPv6 OSPF not properly after the neighbor pushing ::/0 is disconnected (even though one neighbor is still alive).
Jul 17 2018
Jul 17 2018