N/A - Feature not yet available
OK - Initial tests successful
NOK - initial tests not successful
Highlight Colors:
- Yellow - partially working
- Green - Working
- Red - Not working at the moment
Feature | Beta7 |
---|---|
Convert route rules after upgrade from v6.x | N/A |
IPv4 Route Rules | OK |
IPv6 Router Rules | NOK |
ECMP flags | OK |
dst@table | OK |
gateway@table | OK |
gateway%interface | OK |
recursive route over ipv6 LL address | OK |
3 level recursive gateway with ECMP | OK |
IPV6 ECMP | OK |
IPv6 connected ECMP | N/A |
Addresses from same subnet to multiple interfaces | NOK |
Show time when route was last updated | N/A |
Check Gateway | Ping OK, ARP NOK (works as ping), BFD NOK (not implemented) |
Scope and target scope | OK |
IPv4 Mangle routing-mark | OK |
IPv6 Mangle routing-mark | NOK (Added but does not work at the moment) |
Packet SRC address | NOK (wrong src is picked for locally originated pacekets) |
Routing-table parameter for ping and telnet | NOK |
Show if route is harware accelerated | N/A |
Custom route selection policy | N/A |
IPv4 with IPv6 nexthops and RFC5549 | N/A |
Routing Instance | OK |
VRF | OK |
Some kind of mechanism to import/export routes from one vrf to another within same router | N/A |
Convert OSPF config from v6 to v7 after upgrade | N/A |
OSPF neigbors in in NSSA Area | Cannot establish adjacency (ROS-12206) |
OSPF in boadcast network | Does not work with more than 2 neighbors (ROS-12201) |
OSPF with routing filters | OK |
OSPF Virtual Link | OK |
BGP and OSPF SNMP monitoring | N/A |
Convert BGP config from v6 to v7 after upgrade | N/A |
BGP Templates and dynamic peers | OK |
BGP connect listen on network | OK |
BGP guess remote.as | OK |
Show from which peer route received | OK ( /routing/route/print detail --> belongs-to) |
BGP Address Families | Currently only IPv4, IPv6 |
BGP input.accept-* | Does not work right after peer established, need to resend routes |
eBGP nexthop self | OK |
BFD | N/A |
Input Filter | OK |
Output Filter | OK |
BGP Local addess auto selection | OK |
BGP route reflect | OK |
BGP route server | OK |
BGP Roles https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-open-policy/?include_text=1 | OK |
BGP peer-cache uptime in "established" state | N/A |
BGP Flow Spec | Flow spec attributes are forwarded |
BGP Selection | OK |
BGP Selection (Multipath) | N/A |
BGP Confederation | N/A |
BGP Aggregation | N/A |
BGP ORF | N/A |
Discard prefix RTBH rfc 6666 | N/A |
AS-wide Unique BGP Identifier RFC 6286 | N/A |
MPLS | N/A |
RPKI session | OK |
RPKI possibility to view received info of specific prefix | N/A |
RPKI show connection status | N/A |
Convert routing filters after upgrade from v6.x | N/A |
Routing filter chain drop by default without rules | OK |
Routing filter prefix match | OK |
Routing filter protocol match | Missing other protocols like modem DHCP etc (these routes are not matched by "static") |
Routing filter append communities | OK |
Routing filter append large community | OK |
Routing filter set weight | "sub, add" does not work if attribute has default unset value, if attribute is not set then default value should be assumed. |
Routing filter set local pref | "sub, add" does not work if attribute has default unset value, default value should be 100 if not set. |
Routing filter set MED | "sub,add" should assume default value. |
Routing filter set origin | OK |
Routing filter set igp metric from OSPF cost | Can be set with set-num-prop=bgp-igp-metric<add>ospf-ext-metric or ospf-metric, but what to do if it is not possible to guess which metric to use? |
Routing filter match prefix with address list | OK |
Routing filter match community/large community lists | OK |
Routing filter add prefix to address list | N/A |
Routing filter validate prefix with RPKI | OK |