That is exactly what we are all hoping for. Unfortunately the silence from Mikrotik does not fill me with confidence that they even understand how bad this problem could turn out.Let's hope MikroTik can have a build ready with a fix before the full details of this go public...
I believe that thread refers to CVE-2018-19298 which is a similar incident. The later one (CVE-2018-19299) is far more sinister.Something similar (if not the same)had been already discussedin this forum.
Code:Select all
local board
if ([:pick [:sys ro g mod] 0 11] = "RouterBOARD") do={
set board [:pick [:sys ro g mod] 12 [:len [:sys ro g mod]]]
} else={
set board [:pick [:sys ro g mod] 2 [:len [:sys ro g mod]]]
}
That is definitely the truth!Or there has to be a lot of people who want some feature. And even that doesn't always work.
Yes, we now have WAN and LAN on separate SFP+. Not seeing any improvement so far unfortunately.Looks good!
Did you also separate the input and output over the 2 different SFP+ or is it still using a VLAN setup?
I've always run netinstall on a local network. It doesn't break dhcp in my experience.It may well be that ignoring this recommendation and putting both of them on a live network may break things.
As I understand it, if you want a shell on Mikrotik, wait for the code mentioned in vault7 to be released. That seems to do exactly what you want!
+1 good Idea, on the Shell access, and couldnt agree more on the DNS server issue.
Hi....20/40mhzCe or 20/40mhzeC
I think that is about 3 steps down the line. I need to get a working configuration first!
Yes, I took the screenshot after I had rebooted the router and the sessions had loaded fully, hence why they have only been up for a few minutes.you are speaking about crash every 2 weeks but on your picture we can see that session are up for 13 minutes !