After upgrade can't make to work EoIP over IPSec (IPIP over IPSec works but not without issue) and not working IPSec witch older firmware. What is even more disturbing it shows that established tunnel but no traffic pass and that same with EoIP over IPsec. Configuration was restored from backup, and i try everything but still nothing helps.
Ooo and another thing is that every change in ipsec is done, it not reset tunnel i must reset it manual :/

On hAP ac2 is similar problem. Unexpected reboots every 2h to 48h. I sent description of problem to Mikrotik support.

I have the same issue - one of my hAP ac2 is rebooting from time to time (looks like it usually reboots within 24 hours and then works properly till I reboot it manually - however this most likely is pure coincidence). My hAP ac2 also stuck/crashed without rebooting once (it resumed working after unplugging+replugging power).
For me the issue started after upgrade from 6.43.1 to 6.43.2. Router was working on 6.43.1 for around 48 hours without a single reboot. Then router was upgraded to 6.43.2 and after around 6 hours it rebooted for the first time.
Resource graphing is enabled on the router and memory usage was always below 17% (so memory leak should NOT be the cause of reboot, at least a memory leak that grows longer than 5 minutes).

Has MikroTik support replied to you?

As it looks like I have again mem leak reboots on hap ac with RouterOS 6.42.9. Just before reboot IPSEC failure show up in logs. 6.42.7 seemed to be ok, but 6.42.9 is again bad even on bugfix!

My experience on hAP ac2: very unstable, plenty of watchdog reboots (most of them due to ping timeouts, pinged address is linux server on LAN).
For me instability is regression from 6.42.9.

I take my words back. Instability is not a regression from 6.42.9, my hAP ac2 was not completely stable while running 6.42.7 (but much more stable than any of 6.43.x). Two days ago I downgraded to 6.42.9 and so far it's stable.

Some statistics:

• while running 6.43 for 7d21h it rebooted 13 times due to "watchdog cannot ping address W.X.Y.Z, reboting". So it had average uptime of 14.5 hours.
• while running 6.43.1 for 15d4h it rebooted 48 times, so it had average uptime of 7.6 hours
• while running 6.42.9 for 1d21h it never rebooted (current uptime 1d21h16m57s)

Every time I installed another version of ROS I also upgraded (or downgraded) firmware. Next I'll try to upgrade only ROS to determine if source of instability is ROS or firmware.

N.b.: my hAP ac2 doesn't seem to suffer of memory leaks, memory usage graph shows more or less steady usage of less that 1/4 of available RAM.

On hAP ac2 is similar problem. Unexpected reboots every 2h to 48h. I sent description of problem to Mikrotik support.

I have the same issue - one of my hAP ac2 is rebooting from time to time (looks like it usually reboots within 24 hours and then works properly till I reboot it manually - however this most likely is pure coincidence). My hAP ac2 also stuck/crashed without rebooting once (it resumed working after unplugging+replugging power).
For me the issue started after upgrade from 6.43.1 to 6.43.2. Router was working on 6.43.1 for around 48 hours without a single reboot. Then router was upgraded to 6.43.2 and after around 6 hours it rebooted for the first time.

Has MikroTik support replied to you?

It's the reply from Mikrotik support:

Right now I do not see where is the issue.
Try to turn of watchdog timer:
"/system watchdog set watchdog-timer=no"
And after device freeze, reboot or powercycle it and then manually create new supout.rif file. Send it to us.

After upgrading to 6.43.2 from 6.42.7 you can no longer have multiple IPsec peers to the same destination IP but with different source addresses. This worked fine on 6.42.7.

What's the reasoning behind this restriction?
I need multiple peers to the same destination but using different gateways (source addresses).

Please revert this change.

Appearently there is a memory leak since changelog 6.44beta17 (2018-Oct-04 09:42) states:

"*) bridge - fixed possible memory leak when VLAN filtering is used;"

I had VLAN filtering turned on... on my hap ac

The ones who monitored stable memory usage, did you have VLAN filtering on?
6.42.7 is still the best release for me so far and not 6.42.9.

Appearently there is a memory leak since changelog 6.44beta17 (2018-Oct-04 09:42) states:

"*) bridge - fixed possible memory leak when VLAN filtering is used;"

I had VLAN filtering turned on... on my hap ac

The ones who monitored stable memory usage, did you have VLAN filtering on?
6.42.7 is still the best release for me so far and not 6.42.9.

I have stable memory usage on my hAP AC and no VLAN filtering, but unexplained reboots approximately once a week.

As I noted memory usage on my hAP ac2 is stable and I don't have VLAN filtering enabled (I'm dealing with VLANs on switch chip).

After upgrading to 6.43.2 from 6.42.7 you can no longer have multiple IPsec peers to the same destination IP but with different source addresses.

This regression is said to be fixed in 6.44beta14. Please check the change log in the post here. And I'd expect this kind fix to be merged to 6.42.x later as well.

After upgrading to 6.43.2 from 6.42.7 you can no longer have multiple IPsec peers to the same destination IP but with different source addresses.

This regression is said to be fixed in 6.44beta14. Please check the change log in the post here. And I'd expect this kind fix to be merged to 6.42.x later as well.

Thanks. I totally missed that entry in the changelog.

Just upgraded RB951Ui-2nD from 6.42.7 to 6.43.2 and it's bricked. Netinstall does not see it.
I've upgraded it from winbox system -> packages -> download and install.

What could be a reason and is there any way to ressurect bricked device?

Just upgraded RB951Ui-2nD from 6.42.7 to 6.43.2 and it's bricked. Netinstall does not see it.
I've upgraded it from winbox system -> packages -> download and install.

What could be a reason and is there any way to ressurect bricked device?

Same here, repeated on 4 devices , copy paste .npk file, reboot...device DEAD, it make beep beep, but is not live, no winbox, no IP access, no wifi powered on ??
Something are bad with 6.43.2 ? Mikrotik ?

My experience on hAP ac2: very unstable, plenty of watchdog reboots (most of them due to ping timeouts, pinged address is linux server on LAN).
For me instability is regression from 6.42.9.

I take my words back. Instability is not a regression from 6.42.9, my hAP ac2 was not completely stable while running 6.42.7 (but much more stable than any of 6.43.x). Two days ago I downgraded to 6.42.9 and so far it's stable.

Some statistics:

• while running 6.43 for 7d21h it rebooted 13 times due to "watchdog cannot ping address W.X.Y.Z, reboting". So it had average uptime of 14.5 hours.
• while running 6.43.1 for 15d4h it rebooted 48 times, so it had average uptime of 7.6 hours
• while running 6.42.9 for 1d21h it never rebooted (current uptime 1d21h16m57s)

Every time I installed another version of ROS I also upgraded (or downgraded) firmware. Next I'll try to upgrade only ROS to determine if source of instability is ROS or firmware.

N.b.: my hAP ac2 doesn't seem to suffer of memory leaks, memory usage graph shows more or less steady usage of less that 1/4 of available RAM.

So I upgraded ROS to 6.43.2 while leaving firmware at 6.42.9 ... instability came back, in 2d10h it rebooted 8 times with average uptime of 7.3 hours. Memory usage (as charted by graphing tool) never raised above 40MB (out of 240MB), so this clearly is not the reason for reboots.

I hope MT will improve on stability of 6.43 branch ... or launch better (and more stable) 6.44 soon.

Just upgraded RB951Ui-2nD from 6.42.7 to 6.43.2 and it's bricked. Netinstall does not see it.
I've upgraded it from winbox system -> packages -> download and install.

What could be a reason and is there any way to ressurect bricked device?

Narian, what is the behavior of bricked device ? I have sveral with same problem.

1. After upgrade to 6.43.2 device are unreachable, boot up properly but not working.
2. I try to reset on default, and is passed, but same problem
3. Wifi are powered on with default SSID, after I try to connect to wifi stop working
4. LAN led are green even I disconnect LAN cable from that port
5. Netinstall not working

I've just upgraded my good old RB750G from 6.42.7 to 6.43.2 using check for updates and then download and install. The front LEDs of the router went out, as they usually do when it reboots, but they never came back. Winbox (latest version) couldn't connect to the router, no DHCP, no internet, nothing, the router was stuck. I've waited for about 5 minutes and decided to disconnect and reconnect the power cord. The router came back to life. I've checked the package list and version 6.43.2 was installed.

I've then upgraded the firmware using /system routerboard upgrade
After the firmware update a reboot is required so I've used system reboot and again the router was stuck.

I've waited a couple minutes and did the same disconnect and reconnect of the power cord to fix it.

There is a serious problem happening when rebooting the router using 6.43.2
I'm wondering if this has anything to do with it:

What's new in 6.43.2 (2018-Sep-18 12:12):
Changes in this release:
*) routerboot - fixed RouterOS booting on devices with particular NAND memory (introduced in v6.43);

Seeing as 6.44 will be a while can you please put any wireless patches from 6.44RC into the 6.43 branch? I have had CAPAC and HAPAC units stop registering clients on 6.43.2 until they were rebooted even though the interface was running.

*) wireless - improved stability for 802.11ac;

On mipsbe devices with AR8227 switch chipset (100 Mbps 5-port routers like hAP, hAP ac lite, hEX lite, hEX PoE lite, RB951Ui-2Hnd, OmniTik 5) it seems you can damage the routerboard after upgrading it to 6.43.2 and using no-default settings...

Anyone experienced physical Ethernet port problems after upgrade to 6.43.2? Port not linking or port showing false link without any cable connected (and looping traffic)?

Happened to me few days ago and to my friend yesterday:
Me: RB951Ui-2HnD. After upgrade - ports 2,3 stopped working. First they were just off (not reacting to the cable), then they started showing link (one - 10 Mbps, other one - 100 Mbps). Then port ether5 also stopped working (no reaction to link, showing inactive all the time). Additionally - I can use ether1, but when I add ether1 to the bridge (even if it's the only port in the bridge and regardless of hw-offload on or off) I have packet losses on the port.
My friend - 2 hAP ac lite devices. After upgrade - few Ethernet ports are just down (not showing link with cable connected), while others work (you can log in, etc.) with the same config.

The same architecture, the same chipset (AR8227), the same software version and problem after upgrade, both of us using "no-defaults" reset. Different devices with different configs on different continents. Is it possible, that the upgrade "destroyed" something physically? Or is it really just that strange coincidence only 2 of us had?

On mipsbe devices with AR8227 switch chipset (100 Mbps 5-port routers like hAP, hAP ac lite, hEX lite, hEX PoE lite, RB951Ui-2Hnd, OmniTik 5) it seems you can damage the routerboard after upgrading it to 6.43.2 and using no-default settings...

Anyone experienced physical Ethernet port problems after upgrade to 6.43.2? Port not linking or port showing false link without any cable connected (and looping traffic)?

Same situation, described below:

1. After upgrade to 6.43.2 device are unreachable, boot up properly but not working.
2. I try to reset on default, and is passed, but same problem
3. Wifi are powered on with default SSID, after I try to connect to wifi stop working
4. LAN led are green even I disconnect LAN cable from that port
5. Netinstall not working

Same situation, described below:

1. After upgrade to 6.43.2 device are unreachable, boot up properly but not working.
2. I try to reset on default, and is passed, but same problem
3. Wifi are powered on with default SSID, after I try to connect to wifi stop working
4. LAN led are green even I disconnect LAN cable from that port
5. Netinstall not working

Thank you, draguzet!
I reported it, Ticket#2018101022006114.
Can you, please, also share if you did firmware (RouterBoot) upgrade on it (System -> Routerboard -> Upgrade)? Or did it stay on older firmware? Also - what is the device model?
BTW - wifi is available, but "not working", the same for me. Reason is - the wifi is in the same bridge as the faulty ports, and is getting a broadcast storm (the ports are doing loop), and after connecting to wifi I'm getting the MNDP broadcast packets multiplied thousands times.
BTW2 - Netinstall not working also for me...

Same situation, described below:

1. After upgrade to 6.43.2 device are unreachable, boot up properly but not working.
2. I try to reset on default, and is passed, but same problem
3. Wifi are powered on with default SSID, after I try to connect to wifi stop working
4. LAN led are green even I disconnect LAN cable from that port
5. Netinstall not working

Thank you, draguzet!
I reported it, Ticket#2018101022006114.
Can you, please, also share if you did firmware (RouterBoot) upgrade on it (System -> Routerboard -> Upgrade)? Or did it stay on older firmware? Also - what is the device model?
BTW - wifi is available, but "not working", the same for me. Reason is - the wifi is in the same bridge as the faulty ports, and is getting a broadcast storm (the ports are doing loop), and after connecting to wifi I'm getting the MNDP broadcast packets multiplied thousands times.
BTW2 - Netinstall not working also for me...

It is on old Firmware, because first boot are not successful and I did not have a way to upgrade firmware (Routerboard - Upgrade).
Device models with problems are: RB951Ui-2HnD , RBDynaDishG-5HacDr3, RB921GS-5HPacD-19S, and for now we stop to upgrade !
I have successful Netinstall (on DynaDish for now) on following way:

1) Power your device off;
2) Power device on;
3) Press and hold the reset button (hold about 1m and relese reset button).
4) Device are detected on Netinstall, and DO NOT install 6.43.2 because same problem are present again !

Changes in this release:

*) routerboot - fixed RouterOS booting on devices with particular NAND memory (introduced in v6.43);

I suspect this fix to be incomplete, to say the least. Several of my wAP ac's in the field have become quite unstable, especially on reboots. Not sure if by .43.x or specifically .43.2 though.

We encountered an issue with the /routing bgp advertisements print detail where ... command which seems to crash/reboot our CCR1009-7G-1C-1S+s running on 6.43.1. We have two BGP full feeds with each approx. 720k IPv4 and 58k IPv6 routes, Cymru feed with 105k bogon prefixes and we redistribute a full feed to a single customer. Free Memory is at 840/1968MB, CPU usage average at 12%.

Generally stability of the BGP implementation and routing-related commands seems to have gotten much worse following the 6.43 release. Peering sessions terminate randomly, CMDs like /ip route print sporadically return false double results for the same dynamic route with same origin/path or even fail entirely, causing the terminal to freeze. With a (Cisco) peer we even encountered "AFI invalid address family" errors on the peers-side recently which all of a sudden disappeared again without any changes on the MT- nor Cisco-side.

Before opening a support ticket with MT, is anyone else seeing this (or similar) behaviour recently?

schadom - Please send supout file and problem description to support@mikrotik.com. Please provide precise command that you use in order to filter print command output.

I've just upgraded my good old RB750G from 6.42.7 to 6.43.2 using check for updates and then download and install. The front LEDs of the router went out, as they usually do when it reboots, but they never came back. Winbox (latest version) couldn't connect to the router, no DHCP, no internet, nothing, the router was stuck. I've waited for about 5 minutes and decided to disconnect and reconnect the power cord. The router came back to life. I've checked the package list and version 6.43.2 was installed.
----snip-----

What's new in 6.43.2 (2018-Sep-18 12:12):
Changes in this release:
*) routerboot - fixed RouterOS booting on devices with particular NAND memory (introduced in v6.43);

The same here. My RB750GL is gone. Bricked. LED is blinking as it should but Netinstall never gets anything from RB750GL.
That's third time in 7 years of working with various MT's but this time I just can't do a thing.

Any sugestion?

Br

Sasa

The same here. My RB750GL is gone. Bricked. LED is blinking as it should but Netinstall never gets anything from RB750GL.
That's third time in 7 years of working with various MT's but this time I just can't do a thing.
Any sugestion?

Try this:
1) Power your device off;
2) Power device on;
3) Press and hold the reset button (hold about 1m and relese reset button).
4) After board appears in Netinstall install version lower than 6.43.x !! (try different waiting time while holding reset button, 1 minute, 2 minute...)

I'm really strange when the Mikrotik will remove the 6.43.2 version and declare it unstable, since obviously the different boards are falling after the upgrade!

Connection between RB450GX4 and Winbox 3.18

Hi, guys: I just wanted to get help from this forum because my new device RB450GX4 has problem about connection to Winbox 3.18.
I need to close winbox for several times then it can be connected to RB450GX4... Very strange.

Have you guys with similar problem as mine ?

P.S.
The firmware in my RB450GX4 is mostly updated ~ 6.43.2.

Kris from Taiwan

Was it working good in previous versions? If not, please create separate topic with more details.

In queue export file and full backup export file has separate queue tree statements.

If i have queue tree with parent and childs then i have:
first parent statements
then queue types
and final the rest statements of tree, that childs. If i have only childs and no parents (except that global) the i have all statements together:

The same here. My RB750GL is gone. Bricked. LED is blinking as it should but Netinstall never gets anything from RB750GL.
That's third time in 7 years of working with various MT's but this time I just can't do a thing.
Any sugestion?

Try this:
1) Power your device off;
2) Power device on;
3) Press and hold the reset button (hold about 1m and relese reset button).
4) After board appears in Netinstall install version lower than 6.43.x !! (try different waiting time while holding reset button, 1 minute, 2 minute...)

I'm really strange when the Mikrotik will remove the 6.43.2 version and declare it unstable, since obviously the different boards are falling after the upgrade!

Done all of this. As I have few more devices for testing purpose it will wait for having some spare time to fiddle with this but it is annoying problem.
In 30 years this is my second completely bricked device. First was Buffalo router without header.

BTW, Mikrotik, are those 3 hidden spots with Rx, Tx, and GND marking real serial port or just ...

Br

Sasa

are those 3 hidden spots with Rx, Tx, and GND marking real serial port or just ...

TTL serial. Get a TTL serial to USB converter from aliexpress or similar, and you can connect it to a PC and watch the boot procedure.
(or even flash new firmware over serial when you are patient)

are those 3 hidden spots with Rx, Tx, and GND marking real serial port or just ...

TTL serial. Get a TTL serial to USB converter from aliexpress or similar, and you can connect it to a PC and watch the boot procedure.
(or even flash new firmware over serial when you are patient)

Speak about TTL serial to USB (and many serial to USB), beware that of them are using PL2303 series chipset and some of them are using fake PL2303 chipset, the latest driver and win10 driver will refuse to work with them. If you look for a Serial to USB cable better check if can work in win10 without manually install any driver.

p.s. I have one from UGreen which work in win10.

beware that of them are using PL2303 series chipset and some of them are using fake PL2303 chipset, the latest driver and win10 driver will refuse to work with them. If you look for a Serial to USB cable better check if can work in win10 without manually install any driver.

Could be, I never use Windows, and in Linux they all work without problem...

beware that of them are using PL2303 series chipset and some of them are using fake PL2303 chipset, the latest driver and win10 driver will refuse to work with them. If you look for a Serial to USB cable better check if can work in win10 without manually install any driver.

Could be, I never use Windows, and in Linux they all work without problem...

I have a fake PL2302 cable which damage my old wifi AP

are those 3 hidden spots with Rx, Tx, and GND marking real serial port or just ...

TTL serial. Get a TTL serial to USB converter from aliexpress or similar, and you can connect it to a PC and watch the boot procedure.
(or even flash new firmware over serial when you are patient)

Ah, nice suggestion but, all my laptops are Pro type and I have real serial ports on them
Serial port is not a problem on computer side. Question is, are those 3 spots on MT board real serial connections or just some
relics from past.

Br

Sasa

Ah, nice suggestion but, all my laptops are Pro type and I have real serial ports on them

The key here is that TTL serial and RS232 are somewhat different beasts- they differ at least in the voltage levels (while on the protocol level they must be compatible). You can easily damage TTL serial port by directly connecting it to a standard serial port on your laptop.

New version 6.43.4 has been released in stable RouterOS channel:

viewtopic.php?f=21&t=140560