v6.43.14 [long-term] is released!

Announcements
1

RouterOS version 6.43.14 has been released in public “long-term” channel!

Before an upgrade:

  1. Remember to make backup/export files before an upgrade and save them on another storage device;
  2. Make sure the device will not lose power during upgrade process;
  3. Device has enough free storage space for all RouterOS packages to be downloaded.

What’s new in 6.43.14 (2019-Apr-02 09:12):

MAJOR CHANGES IN v6.43.14:

!) ipv6 - fixed soft lockup when forwarding IPv6 packets;
!) ipv6 - fixed soft lockup when processing large IPv6 Neighbor table;

Changes in this release:

*) ipv6 - adjust IPv6 route cache max size based on total RAM memory;

To upgrade, click “Check for updates” at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after some problem has appeared on device

Please keep this forum topic strictly related to this specific RouterOS release.

2

Just gonna leave a link to the MikroTik blog post here, so people can read about what this patch fixes.
Here: https://blog.mikrotik.com/software/cve-2018-19298-cve-2018-19299-ipv6-resource-exhaustion.html

3

Very please - do it backport to 6.40.x! It is last (very) stable version with old bridge.

4

after upgrading to 6.43.14, our ipv6 on pppoe has stopped working on devices with more than 1000x pppoe online, equipment with less than 1000x pppoe online, it works.
when downgrading to version 6.42.12 back to normal operation.

https://prnt.sc/n7h3xl

5

I did several tests and the problem still persists.

6

Did you test with 6.43.13?

7

yes, all above 6.42.12, presented problems in the delivery of ipv6 on pppoe.
especially when restarting the router, better after deleting all the bindings of the dhcpv6 server.

8

Upgrade from 6.42.9 on CCR1009.

IPv4 DHCP server in winbox empty (and not working, of course), export from CLI empty too (and stuck terminal).
Every CPU about 20-30 % load.
In log: snmp, warning timeout while waiting for program 23

----edit:
problem is in leases. I use this configuration:

/ip dhcp-server
add disabled=no interface=bridge2 lease-time=1d10m name=mgmtDhcp
add add-arp=yes disabled=no interface=vlan51 lease-script=":if ( \$leaseBound = 1 ) do={\r\
    \n  /ip firewall address-list add list=sysClient51 address=\"\$leaseActIP\";\r\
    \n} else={\r\
    \n  /ip firewall address-list remove [find list=sysClient51 address=\"\$leaseActIP\"] \r\
    \n};\r\
    \n" lease-time=6h10m name=clients51
/ip dhcp-server alert
add disabled=no interface=vlan51
/ip dhcp-server lease
add address=10.168.28.107 comment=gpon mac-address=78:8A:20:B9:B7:02 server=mgmtDhcp
add address=10.168.236.10 comment="4046" mac-address=70:3A:CB:6C:46:8F server=clients51
add address=10.168.236.11 comment="3914" mac-address=E8:DE:27:38:19:32 server=clients51
add address=10.168.236.12 comment="0420" mac-address=84:16:F9:E2:4E:D8 server=clients51
add address=10.168.236.13 comment="4634" mac-address=D4:6E:0E:55:9B:24 server=clients51
add address=10.168.236.14 comment="4645" mac-address=84:16:F9:E1:BA:8A server=clients51
add address=10.168.236.15 comment="4682" mac-address=84:16:F9:E4:F9:58 server=clients51
add address=10.168.236.16 comment="4125" mac-address=C4:E9:84:31:C2:AA server=clients51
add address=10.168.236.18 comment="4788" mac-address=C0:25:E9:07:18:B2 server=clients51
add address=10.168.236.19 comment="4925" mac-address=C4:71:54:30:4D:04 server=clients51
add address=10.168.236.20 comment="4775" mac-address=D4:6E:0E:E6:72:18 server=clients51
add address=10.168.236.17 comment="T000" mac-address=04:18:D6:E6:B5:46 server=clients51
/ip dhcp-server network
add address=10.168.28.104/29 dns-server=10.168.1.1,10.168.29.1 gateway=10.168.28.105 ntp-server=10.168.28.105
add address=10.168.236.0/24 dns-server=10.168.1.1,10.168.29.1 gateway=10.168.236.1 ntp-server=10.168.1.1,10.168.29.1

Solution is remove all static leases, upgrade ROS and then import leases back.
Problem is in step between 6.42.12 and 6.43 (I tried it).

9

I had the same upgrading from 6.42.12 on a CCR1009.

Not only that, but IPv6 (pd-pool) on PPPoE not working either. It depends on DHCPv6.

Downgraded back to 6.42.12, remove DHCPv4 server and details, upgraded, created it again. That resolved the problem. Details in ticket #2019040522003959

An upgrade should not render the entire DHCP package useless.

/M

10

The issue is the DHCP package. IPv6 in PPPoE depends on DHCPv6, which is affected, if you had anything DHCP set up in 6.42.x or before. As Ludvik pointed out. It might be as simple as removing the leases. But it’s definatly a bug.

/M

11

if I remove dhcpv6-server bindings resolves, but every I reboot I have to remove the bindins from ipv6.

12

post deleted. my mistake. sorry.

13

Hi,
I have 4 RouterBOARD DynaDish G-5HacD r3, and when I update to 6.43.14 I can’t run bandwidth test to this RouterBOARD.
I checked if Btest Server is enable and I have no firewall rules just bridge.
The error when try run a test is “Can’t connect”

Any help?

14

DHCP issue confirmed on 1036-8G-2S+

No issues on 1009-7G-1C-1S+

Tried to pull a SUP file on the 1036’s but it hung at 1%.

Hundreds of leases on those 1036’s… this is not going to be fun.

MT, what’s going on here?

15

No IPV6 on PPPOE clients after upgrade to 6.43.14 and 6.44.2.
Sad…

16

I’m running 6.44.2 on a RBD52G, my internet connection is over PPPoE … and IPv6 works just fine.

17

My problem is on the server side.

18

Does DHCP work at all ? Can you do a configuration export or does it hang ?

IPv6 on PPPoE would be affected by the DHCP problem above, as it relies on DHCPv6 pushing the IPv6 details over PPPoE.

/M

19

It hangs!

20

Same problem so as anyone else. DHCP screwed. I have had no response on ticket #2019040522003959 either yet.

/M