v7.1beta6 [development] is released!

[raimondsp]

What’s this mean for routeros though? (DX3000/2000 devices) Will we see hardware ipv6 routing so long as we either don’t configure any ipv6 firewall rules (ie, no way to get the route ‘out’ of the CPU) or if we do a VRF or something? Routing via CPU on these devices is abysmal, currently hanging a router-on-a-stick off them but I’d really like to ditch this process and get hardware offload onboard. NP16 is a fantastic device so this is a big ticket item for me and a lot of wisps.

For another network, I use IPv6 as an underlay so customers are isolated in a tunnel at the DMARC (can’t wait for vxlan over IP/evpn etc hopefully in hardware…SRv6 even better.). Similar question here in that I mostly want hardware IPv6 routing and a basic firewall for packets targeting the device just to be on the safe side. Generally packets will be encapsulated so no worries. Also, this is likely a DX8xxx series switch, probably CRS309 for those SFP+ ports. It’s not clear if you we’re saying that only the DX2/3 series can’t do fasttrack while the DX8x CAN.

Here is the documentation: L3 Hardware Offloading. Fasttrack hardware offloading is available only on DX8000 devices. On DX3000/DX2000, Fasttrack connections do not get offloaded and are processed by the CPU.

Summary:

• IPv4 hardware routing is available on all CRS3xx devices.
• IPv4 Fasttrack offloading is available only on DX8000 devices. DX3000/DX2000 hardware does not support it.
• IPv6 hardware routing is not available yet. It should be released later this year.
• Theoretically, the hardware of the DX8000 series support IPv6 Fasttrack offloading. However, IPv6 Fasttrack needs to be implemented on the software side first.