New EdgeRouter firmware v2.0.3 英文官方网站已经发布

Note: The ER-X/ER-X-SFP/EP-R6 has 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, see here for 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!

Note 2: Version v2.0.2 was not released because we identified major flaw during internal beta testing.
ER-X v2.0.3固件下载地址
其他产品v2.0.3固件下载地址

Enhancements and bug fixes:

[!Offloading] - Fix regression in v2.0.1 that caused random reboots of ER-X/ER-X-SFP and EP-R6 routers when hwnat offloading was enabled. Discussed here -> here and here
[!Offloading] - Fix regression in v2.0.1 that caused random filesystem corruption and failure to boot of ER-X/ER-X-SFP and EP-R6 routers when hwnat offloading was enabled. Discussed here, here, here…
[WebGUI] - Fix regression in v2.0.0 when ping in WebGUI did not work. Discussed here
[WebGUI] - Fix bad eth9 interface in Basic Setup Wizard on ER-X and ER-4. Discussed here
[WebGUI] - Add checkbox to toggle IPv6 functionality from WebGUI
[WebGUI] - Fix bug that caused WebGUI/UNMS to become inactive if aggressive network scanners opens lots of unauthorized sessions
[QoS] - Fix bug in v2.0.1 that caused Qdisc to be configured on all ER-X interfaces. Discussed here
[Firewall] - Fix bad firewall rules when MSS clamping is configured. Discussed here
[Firewall] - Fix regression in v2.0.0 that caused firewall section to disappear if rule had TCP_UDP protocol assigned to ■■■■ port. Discussed here
[FlowAccounting] - Fix netflow daemon crash if WAN interface is down for more than 1 minute. Discussed here
[Interface] - Fix bug when rx/tx counters of switch-port interfaces were not updated on ER-X/ER-X-SFP and EP-R6 models.
[Interface] - Fix regression in v2.0.0 when statically configured IPv6 addresses on ER-8-XG were missing after reboot
[OpenVPN] - Fix regression in v2.0.0 when client-specific options were ignored.Discussed here
[Bonding] - Fix bug when bonding did not pass traffic if switch-port interfaces are used on ER-12. Discussed here and here
[QoS] - Now transit packets will automatically bypass offloading if netflow or qos or suspend are configured
[IPv6] - Fix IPv6 bug when address auto-configuration for VLAN interfaces did not work when enabled.
[IPv6] - Fix regression in v2.0.0 when radvd did not work correctly when multiple router-advert were configured. Discussed here
[MDNS] - Fix bug when mdns service did not start if VTI interface was configured. Discussed here
[Routing] - Fix bug when 0.0.0.0/0 static route sometimes was not restored when nexthop address became reachable
[CLI] - Fix Perl error message when running “clear dhcp lease ip …” CLI command. Discussed here
[TechSupport] - Fix bug when tech-support file was truncated if flow-accounting was configured
[TechSupport] - Add output of journalctl to tech-support file
[TechSupport] - Add runtime state of flow-accounting to tech-support file
[UNMS] - add support for configuring QoS and suspended clients via UNMS
Known issues:

Throughput degradation by 5-10% when comparing with v1.10.9 firmware with older kernel
! IPsec and VLAN offloading on ER-X/ER-X-SFP and EP-R6 does not work
LoadBalancing sometimes fails to recover after switching to failover interface
Sometimes statistics in WebGUI is “freezing” and page refresh is needed in order to weke it up
Sometimes DPI is reporting wrong rx/tx counters

实测可以开启硬件加速,200m宽带单线程可以轻松到30m/s的下载速度。

我这边200M,最大下载能冲到40m/s!

目前已经开启硬件加速7个小时,相当稳定。v2.0.0和v2.0.1版本开启硬件加速系统随机出错问题已经解决了。同时ipv6重新拨号获取时间由原来的2分半钟到1分钟左右。

  • 与使用旧内核的 v1.10.9 固件相比,吞吐量降低5-10%
  • ER-X / ER-X-SFPEP-R6 上的IPsec和VLAN卸载不起作用
  • 切换到故障切换接口后,LoadBalancing有时无法恢复
  • 有时WebGUI中的统计信息是“冻结”,并且需要页面刷新才能完成
  • 有时DPI会报告错误的rx / tx计数器

我的开启offload hwnat没有问题,已经平稳运行20小时,这个版本有个问题就是进入CLI命令有点慢,大约要2~3分钟左右。

1赞

过一段时间再升,现在都不敢乱升级,以前升级了个2.0.1折腾死了

买了ER-X都暂时还没有用,这下担心了。固件换来换去,有死机的有不能NAT的,到底ER-X是否稳定?网络系统的各个环节稳定使用是关键,这个折腾的让人信心不足。

配置好了不动就是稳定的,你天天修修改改再升级咋样都是不稳定的,基于上述原因设备的稳定性在于使用者的意愿和选择:stuck_out_tongue_winking_eye:

升级到 2.0.3 忽然有一天死机后,无论如何重启都无法连接上 er-x 最后重置好了。

v2.0.3版本上,$$无法使用。

暂时停留在v1.9版本,看来新固件还不够稳定。

停留在了1.10.9版本,这个版本相对稳定,转发效率比2.0.3高,也是19年的版本。

因为某些原因在新的内核上重建了所有东西…
整体系统上内核因为直接更新到了Debian 9…所以软件库的选择面一下子大了。。
至少我的$$是直接从APT上拉下来的不需要自己搞这些了。。
web开时间稍微长一点就会frozen…其他都还好。。

这个版本稳定性怎样?

升级2.0.3使用一个月 刚开始20天一切正常,后来10天平均一天死机1`2次 必须重启路由。目前降回1.10.9看看情况

看来还是呆在10.9比较妥当。

继续 10.9比较ok啊!

# show version | grep -E Version\|Up\|model
Version:      v2.0.3
HW model:     EdgeRouter X 5-Port
Uptime:       18:17:59 up 24 days, 14 min,  1 user,  load average: 1.03, 1.07, 1.04

还好吧,感觉应该还算稳定,因为只有200M的家庭宽带,没有上hwnat offload,其他用上的功能:

  • smart queue,限制WAN口的上行,降低满负荷的时候的ping值
  • 两个openvpn,一个是client,一个是server
  • PPPOE拨号一个
  • 一些比较基本的防火墙规则
  • 一个Linux Bridge,同时也有vlan-aware的switch,三个VLAN,各有DHCP server
  • xx上网

遇到的问题,就是启动的时候,有时PPPOE一直重拨,但一直获取不到IP,需要手工断线重连