Setting route-queue-limit-high=0 disables route indexing when there are any routes in the processing queue - the most efficient CPU usage but the longest delay before hardware offloading. Lowering this value leads to faster route processing but increases the lag between a route's appearance in RouterOS and hardware memory. The switch driver stops route indexing when route-queue-size (see #monitor) exceeds this value. Route-queue-limit-high ( number Default: 512 ) Disabling icmp-reply-on-error silently drops the packets on the hardware level in case of an error. Enabling icmp-reply-on-error helps with network diagnostics but may open potential vulnerabilities for DDoS attacks.

Since the hardware cannot send ICMP messages, the packet must be redirected to the CPU to send an ICMP reply in case of an error (e.g., 'Time Exceeded', 'Fragmentation required', etc.). Icmp-reply-on-error ( yes | no Default: yes ) Since IPv6 routes occupy a lot of HW memory, enable it only if IPv6 traffic speed is significant enough to benefit from hardware routing. Not all switch chips support FastTrack HW Offloading (see hw-supports-fasttrack).Įnables or disables IPv6 Hardware Offloading. Keep it enabled unless HW TCAM memory reservation is required, e.g., for dynamic switch ACL rules creation. Autorestart does not work for system failures, such as OOM (Out Of Memory).įasttrack-hw ( yes | no Default: yes (if supported) )Įnables or disables FastTrack HW Offloading. Otherwise, if an error occurs, l3-hw-offloading gets disabled, and the error code is displayed in the switch settings and #monitor. Automatically restarts the l3hw driver in case of an error.

Routeros version 7