I have two mikrotik devices, a CRS305 in one location with an OpenVPN server running in ethernet mode, and a hEX in a different location being an OpenVPN client. Both devices are upgraded to 7.15.2/3 What happens is that I set up the hEX client, it connects, and I can access resources. I close the U...

I've created a short script that helps parse this broken JSON, but a real fix is still needed from Mikrotik. Typescript/Javascript: async getBinaryBrokenJSON(url: string, upload: {[key: string]: string | string[] }) : Promise<Buffer> { var response = await fetch(url, { method: 'POST', body: JSON.str...

You've apparently got the minimalist " ntpsec " version of these tools installed. I had in mind the more mainstream ntp.org ones, which give more readable output. Ah, looks like the "mainstream" ones are deprecated, so Debian replaced them with ntpsec. Either way, both tools are...

I was attempting to read a backup file, and realized that the REST endpoint in 7.15.2 produces invalid JSON: $ curl -X POST -u admin:${PASSWORD} -H "content-type: application/json" https://${YOUR_IP}/rest/file/read --data '{"file":"my-test.backup","chunk-size"...

NTP is a UDP protocol; nmap's default TCP port scan is correct to show it closed. Whoops, I knew that but forgot to have nmap do that. 123/udp open ntp While there is a UDP port-scanning option , I'd prefer a tool like ntpdate -q for testing availability. Your own choice of ntpq should also work, t...

I'm stumped. I've found lots of forums posts about this, such as https://forum.mikrotik.com/viewtopic.php?t=203727 or https://forum.mikrotik.com/viewtopic.php?p=794718 but none have helped me. Earlier this afternoon, I just got my new CRS305. I am not using it as a router, just a fancy switch, as su...