Component: route
303 changelog entries across 125 version(s)
Releases by channel (stacked)
- fixed "Route Target" byte order;
- fixed unreachable routed networks on VRFs;
- fixed route rule upgrade;
- fixed situation when routes with unequal distances got treated as ECMP routes;
- improvements on VRF isolation;
- improved stability and other minor fixes;
- improved stability when connected route is modified;
- improved stability when connected route is modified;
- improved stability when connected route is modified;
- routing rules improvements;
- improved stability when 6to4 interface is configured with disabled IPv6 package;
- improved stability when 6to4 interface is configured with disabled IPv6 package;
- fixed source address selection of outgoing packets;
- added rpki-check;
- bgp improvements;
- do not allow modifying/deleting "main" table;
- fixed incorrectly interpreted prefix states received from RTR;
- fixed IPv6 ECMP connected routes;
- fixed IPv6 policy routing;
- routing rules improvements;
- improved stability when 6to4 interface is configured with disabled IPv6 package;
- improved system stability after reboot with large amount of VLAN interfaces with PPPoE servers attached;
- improved system stability after reboot with large amount of VLAN interfaces with PPPoE servers attached;
- fixed area range summary route installation in VRF;
- fixed area range summary route installation in VRF;
- fixed DHCP/PPP “add-default-route” “distance” minimal value to 1;
- improved reliability on routing table update;
- fixed potential route crash on routing table update;
- improved reliability on routing table update;
- fixed memory leak when route cache is disabled;
- added suppport for more than 8 bits of options;
- fixed ospf by handling ipv6 encoded prefixes with stray bits;
- do not show duplicate gateway on connected route;
- fixed filter by routing table;
- fixed crash on removing route that was aggregated;
- using ldp could cause connected routes with invalid interface nexthop;
- fixed crash that could be triggered by change in nexthop address resolution;
- some imported VPNv4 routes were not using MPLS labels;
- imported VPNv4 routes were not always updated or removed when the original route changed;
- fix dst-prefix filtering did not return routes when routes with different routing-mark were present;