v6.39rc [release candidate] is released

Announcements
221

Three reasons:

  1. None of the protocols in the p2p filter are used today. Limeware? Kazaa? Really … ?
  2. This matcher also caught non-p2p traffic and interrupted normal communcations
  3. You can duplicate the functionality with l7 filters. In fact, p2p filter is the same as L7 filter, but L7 has more customisation
222

Thank you for explanation.

223

CHR v6.39rc45 update error, the interfaces are missing.
console error- info failed: std failure: timeout (13)
system reboots at 16% when trying to run supout.

restored from backup (6.39rc41) and retried the package update, same results.

224

RB493G - THE SAME - BRICKED! after update to 6.39rc45.
Its… loading and …reboots … loading and …reboots … loading and …reboots … loading and …reboots
Only Netinstall to 6.38.3 - helped.
So - version 6.39rc45 have a BIG BUG!

225

:wink:

  1. Most of the actual P2P protocol use https / ssl / tls = no readable packets
  2. MikroTik staff do not waste time to identifyng all p2p protocol, but is better to think about 17GHz, 24GHz, 60GHz, 802.11ad, MU-MIMO 5GHz (802.11ac Wave 2), powerline (homeplug) etc. :wink:
226

v6.39rc45

CCR1009-8G-S-S+ - Bricked
951G-2HnD - Working




227

Rb2011 and hap ac bricked also

228

RB1100aHX2 BRICKED, man, this is a RC, not an alpha, can’t even think how this happend.

Trying to downgrade to earlier version, unfortunately at this time i’m 250 miles away from the RB, so only can connect through layer2 (MAC) and i’m lossing the connection every X seconds and I can’t upload de 11MB system file.

229

The trouble is, MikroTik’s naming is not exactly what many people expect. Personally I’d call their “RC” beta if I’d like to be nice, or alpha if I want to be safe.

230

you are searching for troubles messing with RC while being 250 miles away…

231

RB411, RB2011, RB962 - upgraded to RC45.

232

I have 433,433ah, Chr, crs125, base no 2, upgrade to. 45 ok.
But I get 450g that I lost access after updating,
I think is some configuration, that cause the crash and not related to hardware


Enviado de meu XT1580 usando Tapatalk

233

Just checked, I got a 450g updated normal to 45,so this crash is very specific.

Enviado de meu XT1580 usando Tapatalk

234

By any chance, did you have PCQ simple queues on the affected 450G?

235

No,
I only use simple queue, default settings

One different from both 450
is that on crashed one I have ipv6 packages disabled, and working one it is enabled


Enviado de meu XT1580 usando Tapatalk

236

Seems that we have managed to reproduce this crash which was introduced in last rc release. We will try to fix it as soon as possible and release new version with fix included.

237

Can you tell what is causing?


Enviado de meu XT1580 usando Tapatalk

238

Yeap, I’ll prefer to name them like that.


Lesson learned with Mikrotik.

239

“Lesson learned …”
There are three branches: bugfix, current and RC (read it as beta/alpha/test version)
It should be obvious that production system should not go further than “current” despite the name of device manufacturer.

240

I was having issues with the DHCP offered lease without success, that is why I took the risk.

Fortunately, I just recovered the router with remote hands support. Connected directly I was able to upload the system file through the MAC address winbox connection, just downgrade and we are back in business.