Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Feature

v7.0Beta7

v7.1Beta1v7.1Beta2v7.1Beta3v7.1Beta4v7.1Beta7
Winbox
BGP support





OSPF support





RIP support





Router ID support





Routing filter support












Generic
/31 address supportN/A




Convert route rules after upgrade from v6.xN/A

OK

Static IPv6 upgrade from ROS v6

NOKOK

IPv4 Route RulesOK




IPv6 Route RulesNOKOK



ECMP flagsOK




dst@tableOK




gateway@tableOK




gateway%interfaceOK




recursive route over ipv6 LL addressOK




3 level recursive gateway with ECMP OK




IPV6 ECMPOK




IPv6 connected ECMP

N/A

OK



Addresses from same subnet to multiple interfacesNOK




Show time when route was last updatedN/A




Check GatewayPing OK, ARP NOK (works as ping), BFD NOK (not implemented)




Scope and target scopeOK




IPv4 Mangle routing-markOK




IPv6 Mangle routing-markNOK (Added but does not work at the moment)OK



Packet SRC address

NOK (wrong src is picked for locally originated packets)


Does not work correctly with /32 addresses


Routing-table parameter for ping and telnetNOK




Show if route is hardware acceleratedN/A

Shows if route is candidate for HW acceleration

Custom route selection policy N/A




IPv4 with IPv6 nexthops and RFC5549N/A
OK









Routing InstanceOK


Renamed to Router-ID
VRFNeeds more testing




Some kind of mechanism to import/export routes from one vrf to another within same routerN/A




BFDN/A











OSPF
Convert OSPF config from v6 to v7 after upgradeN/A




OSPF neighbours in in NSSA AreaCannot establish adjacency




OSPF in broadcast networkDoes not work with more than 2 neighbours

OK

OSPF with routing filtersOK




OSPF Virtual LinkOK




BGP and OSPF SNMP monitoringN/A











BGP
Convert BGP config from v6 to v7 after upgradeN/A

OK

BGP Templates and dynamic peersOK




BGP connect listen on networkOK




BGP guess remote.asOK




Show from which peer route receivedOK ( /routing/route/print detail --> belongs-to)




BGP Address FamiliesCurrently only IPv4, IPv6




BGP input.accept-*Does not work right after peer established, need to resend routes




eBGP nexthop selfOK




Input FilterOK




Output FilterOK




BGP Local address auto selectionOK




BGP route reflectOK




BGP route serverOK




BGP Roles
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-open-policy/?include_text=1
OK




BGP peer-cache uptime in "established" stateN/A











BGP Flow SpecFlow spec attributes are forwarded




BGP SelectionOK











BGP Selection (Multipath)N/A




BGP ConfederationOK




BGP AggregationN/A




BGP ORFN/A




Discard prefix RTBH  rfc RFC 6666N/A




AS-wide Unique BGP Identifier RFC 6286N/A




Exported PDU PCAP saver




Ok
Exported PDU PCAP loader












MPLS
Static label mappingN/A




Static mapping upgrade from v6





LDP IPv4 mappingN/A



Ok
LDP IPv6 mappingN/A




LDP signaled VPLSN/A




LDP config upgrade from v6N/A




TEN/A




TE Config upgrade from v6N/A




VPLS Encap to TEN/A




BGP signaled VPLSN/A




VPLS config upgrade from v6N/A




Fast rerouteN/A




MPLS ECMPN/A




One label per VRFN/A











RPKI sessionOK




RPKI possibility to view received info of specific prefixN/AOK



RPKI show connection statusN/A



Ok







Filters
Convert routing filters after upgrade from v6.xN/A




Routing filter chain drop by default without rulesOK




Routing filter prefix match

OK






Routing filter protocol matchMissing other protocols like modem DHCP etc (these routes are not matched by "static")




Routing filter append communitiesOK




Routing filter append large communityOK




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 originOK




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 listOK




Routing filter match community/large community listsOK




Routing filter add prefix to address listN/A




Routing filter validate prefix with RPKIOK




...