I have upgraded my core routers CCR1036-12G-4S. Am running mpls,ospf and bgp within these routers. One ccr keeps rebooting after like 15-20 minutes.
the rest are ok. the router which keep rebooting is acting head of mpls traffic engineering tunnel and is pushing traffic via this tunnel. On tail side am not pushing traffic via the tunnel. Upload from client is following the normal path chosen by ospf. these routers are not rebooting
I remember we used to have similar problem in this router before mikrotik fixed mpls relating issue last year
Other routers are working fine. Downgraded this router to 41.4 and it is stable now

I confirm this issue is fixed in 6.43rc11. I tested for couple of hours and am not seeing crashes

still waiting for the bugfix only update

This vulnerability isn't much of a problem. The problem is administrators leaving their firewall services (API, Winbox, SSH, etc.) exposed to untrusted networks. It's better to apply firewall filters to the input chain that will protect against this and other future attacks.

On a pure Router it is better to not enable the Firewall AT ALL and have Fastpath enabled still. IPRestrict IPSERVICES in their setting (Disable services that you will not use) and IPRESTRICT USERS login from in their setting. We don't need any firewall for that basic security.

Returning to the increase of the parameter "Sector write since reboot" on 6.42.1, i have about 3k writes instead of about 700-800 on 6.43.rc3 after 12 hours uptime. Is it a bug or a feature?
RB951G-2HnD

I reported the problem to Mikrotik ([Ticket#2018042722002867]). In response I got:
"...Sector write value which shows NAND lifetime, but more precisely you can read in these articles: https://wiki.mikrotik.com/wiki/Manual:R ... bad_blocks, https://wiki.mikrotik.com/wiki/Manual:S ... Properties ..."

My actually values are:

Hi to all,
I updated RouterBoard 450 from 5.26 to 6.42.1 and now the routerboard doesn't boot. It reboot continously !
Can you help me?
Thanks

With 6.42.1 we noted the following issues:
a) Marking assured and related packet as fast track, after a while some SIP client is not able to receive the calls even if seems registered. The connection tracking table has the entry of the UDP packet, and it receive from the server SIP the call but seems that router NAT does not forward to internal host. I have removed the fast track rule (action fast track for packets that are assured and related in filter rule) and it solves the issue.
b) But after the fast track firewall rule disabled the UDP connections with dst-port 5060 are not marked as sip connection-type but as general UDP stream, applying on connection tracking table 3 minutes timeout instead of 60 minutes. I have not rebooted yet, since is a production router, I have planned reboot this night, hope can solve.

Please answer: switch crs317 dont forwards the qinq packets at wire-speed, why ?

Please answer: switch crs317 dont forwards the qinq packets at wire-speed, why ?

How do you check it? Was it working at wire-speed in previous versions?

I think ROS 6.42.1 i VERY buggy version Many,many things not working or working randomly. For instance - next NOT working: Intel i350 miniPCIe cards at x86, working "randomly" Queues. Today I have had NOT working Simple Queues at one x86 machine. I was looking for a problem long time, and..... after disable and enable all Queues - they starded working again. VERY, very strange problems...with ROS 6.42.1

Please answer: switch crs317 dont forwards the qinq packets at wire-speed, why ?

How do you check it? Was it working at wire-speed in previous versions?

You ask because you have such switch and everything works ? our switch crs317 never worked with qinq.
I will be glad to hear a confirmation that someone have working qinq on switch crs317.
But I think it is not.

our switch crs317 never worked with qinq.

Then please don't discuss it in this topic!!! This topic is only for issues specific for 6.42.1
Open a new topic in another section and fully explain you problem and configuration.

viewtopic.php?f=1&t=134316#p661270

Just updated my RB2011UiAS-RM to 6.42.1
After updating and rebooting I go back and check for updates, it shows 6.42 instead of 6.42.1, this does not happen on any of my other routers.


Capture.PNG

I have same problem on a RB2011UAS-2HnD!
Whatever kind of upgrade of ROS if Current 6.42.1 or RC version, the RB just seems to ignore that there is an update package downloaded in files and reboots to 6.42.

Has any1 else had this problem, and/or solved this?

Its kinda frustrating not getting it updated now since there actually is a voulnarability!

add more info
after playing with fast track and non fast track i confine i’m seeing the issue of packet marked sip and non sip wrongly.
After a reboot all work fine.

the issue we are seeing is the vpls interface associated to pppoe server are not listed. but i noted is going to be fixed since rc showing fixed dynamic interfaces

13:31:55 system,info router rebooted
13:31:56 system,error,critical router rebooted because some critical program crashed
----------------------------------------------------------------------------------------------------------------------
3 causes after upgrade to 6.42.1 ( CCR1036-8G-2S+ with 60-70 OVPN tunnels)
26-th of April, 4-th of May, 10-th of May

I am also experiencing a flood of supouts from previously content CPEs (SXT, 911) since installing 6.42.1 on April 24. Two examples:

I think ROS 6.42.1 i VERY buggy version Many,many things not working or working randomly. For instance - next NOT working: Intel i350 miniPCIe cards at x86, working "randomly" Queues. Today I have had NOT working Simple Queues at one x86 machine. I was looking for a problem long time, and..... after disable and enable all Queues - they starded working again. VERY, very strange problems...with ROS 6.42.1

Your report is believable, but the issue is not new to 6.42.1. For ten years I have been "solving" inexplicable queueing problems by exporting queues (both simple and tree), wiping out all queues, then reimporting. Someday I'm sure they will find this problem.

Hello!
Help me please! After updating SXT 5nDr2 from version 6.40.8 to version 6.42.1, the router dies! I have to restore the firmware via netinstall! After restoring the firmware to the initial version 5.26, the update on the Internet is up to 6.40.8, the router reboots and offers to update to 6.42.1 current if you click "update" the router downloads the update, reboots and does not turn on again! Tried it 2 times. What to do?

Hello!
Help me please! After updating SXT 5nDr2 from version 6.40.8 to version 6.42.1, the router dies! I have to restore the firmware via netinstall! After restoring the firmware to the initial version 5.26, the update on the Internet is up to 6.40.8, the router reboots and offers to update to 6.42.1 current if you click "update" the router downloads the update, reboots and does not turn on again! Tried it 2 times. What to do?

Have you tried netinstalling 6.42.1?

All good after upgrade on RB435G.
Keep checking for hickups.

Ive been testing 43RC11.. It addressed a huge number of issues posted in this thread. Good job Mikrotik.

It does not address the short sighted feature neutering of Netwatch tho. I still cannot send a alert or change a LED state based on a ping of a target. Because I use Netwatch for many things, I still cant use firmware past 41.5 because of this.

While im really impressed all the other bugs introduced in 42 have been so quickly addressed, I am upset Netwatch has not been addressed.

wireleswire link ~150m, after upgrade rate/signal loss.
are there any options I should tweak after upg ?

Ive been testing 43RC11.. It addressed a huge number of issues posted in this thread. Good job Mikrotik.

It does not address the short sighted feature neutering of Netwatch tho. I still cannot send a alert or change a LED state based on a ping of a target. Because I use Netwatch for many things, I still cant use firmware past 41.5 because of this.

While im really impressed all the other bugs introduced in 42 have been so quickly addressed, I am upset Netwatch has not been addressed.

Mikrotik at the very least needs to explain what is and what isn't supported after 6.42 in their Netwatch documentation. It's not that much to ask. I got the sense that calling a script which requires certain permissions doesn't work anymore. But if you put the entire script in the Netwatch code block instead of simply calling the script, does that work? I haven't upgraded from 6.41.4 so haven't tested this. Apologies if you've already given this a try.

Version 6.42.2 has been released in current channel:

viewtopic.php?f=21&t=134522

Everyone who complained about the Netwatch issue - Please see this topic viewtopic.php?f=2&t=134538