Do not install this or any older firmware on ER-12device as this will brickit for good.
ER-12 is officially supported starting from 1.10.4and 2.0.0-alpha.1firmwares.
Note:The ER-X/ER-X-SFP/EP-R6has more limited storage, and in some cases, an upgrade may fail due to not enough space. If this happens, remove the old backup image first (using "delete system image" command, seeherefor more details) before doing an upgrade.
More details can be found in the release notes below. Please give it a try if you are interested in the new features/changes to help us test them so that we can get the release out sooner! Thanks very much!
Changes since v1.10.1
Offloading- AddCLIcommands to disable flow-table flushing in offloading enginewhen routing table changes:
set system offload ipv4 disable-flow-flushing-upon-fib-changes
set system offload ipv6 disable-flow-flushing-upon-fib-changes
Discussed here Prior to 1.10.3 firmware flow-table in offloading engine was always flushed when route was updated in linux routing table. Flow flushing ensured that offloading engine got routing updates instantly but it wasted a lot of CPU time and decreased performance if routing table was constantly updated for (instance in Full BGP, big OSPF or flapping PPPoE interface scenarios) In 1.10.3 firmware by default disable-flow-flushing-upon-fib-changes is not set which means that flow table in offloading engine is always flushed upon routing table changes same way as it used to be in previous firmware. If you have Full-BGP table or large OSPF network they you are advised to setdisable-flow-flushing-upon-fib-changes this will ensure less CPU-load and increase max throughput. Important note formulti-WAN environments- if nexthopinterface of default-gateway changes anddisable-flow-flushing-upon-fib-changesis set then it will take up toflow-lifetimeseconds before all existing offloaded flows switch to new nexthop interface (up to 12 seconds by default).
Offloading- AddCLI command to modify flow-lifetime in offloading engine (expressed in seconds):
set system offload flow-lifetime 24
Prior to 1.10.3 firmware flow-lifetime parameter was hardcoded and was notsynchronized between different ER platforms: 12 seconds on ER-Lite/ER-Poe, 6 seconds on ER/ER-pro/ER-4/ER-6 and 3 seconds on ER-Infinity. In 1.10.3 firmware default value of flow-lifetimeis set to 12 seconds for all ER platformsand now it can be modified. By modifyingflow-lifetimeparameter you control how much traffic skips from offloading engine intolinuxnetwork stack. If you increaseflow-lifetime then: a) Offloaded IP flows will expire less frequently and lesspackets will be forwarded to linux b) CPU load will decreaseand max throughput will increase c) if disable-flow-flushing-upon-fib-changes parameter is set then it will take moretime for offloading engine to detect changes in routing table If you decreaseflow-lifetime then: a) Offloaded IP flows will expire morefrequently and more packets will be forwarded to linux b) CPU load will increaseand max throughput will decrease c) if disable-flow-flushing-upon-fib-changes parameter is set then it will take lesstime for offloading engine to detect changes in routing table
Offloading - addCLIcommand to show flows in offloading engine:
show ubnt offload flows
Offloading- addCLIcommand to show offloading engine statistics: