My main concern is that if this is going to be the way forward I’m honestly either going to stay on 6.x for several more years and hope that the devs remove head from ground and make it usable or just find a new vendor.
At a remote site with no service and having to set up a new 6.x mtik and no docs on hand? You can most likely figure out how to set things up even if you’re going through the GUI.
Trying to do the same thing with v7? Good luck.
rc4 has been out for a while now. I fear that next is 7.1 (and not rc5). 
Or a v7.2beta1 
So, is the download server for dev release down?
Hoping I could get some help with Containers…I work for a SDN company where we are looking to install our endpoint software on Mikrotik routers as a containers. We typically use a compose file that executes the following code:
docker run
–rm
–name myTunneler1
–privileged
–network host
–device “/dev/net/tun:/dev/net/tun”
–volume “${PWD}:/ziti-edge-tunnel”
–volume “/var/run/dbus/system_bus_socket:/var/run/dbus/system_bus_socket”
–env NF_REG_NAME=myTunneler1
netfoundry/ziti-edge-tunnel:latest
We need to ingest an identity key called NF_REG_NAME=myendpoint.jwt — The file can be uploaded to the router or we could potentially preregister the identity and upload the resulting myendpoint.json to be mounted in /ziti-edge-tunnel.
@netfoundryskip, you would be better to make a new thread to discuss your issues rather than attempt to hijack the release announcement. your request is more likely to be seen this way vs putting it at the bottom of a very long thread.
unrelated: I predict for the next release we have v7.2RC1 or v7.2beta1 (testing) with move up to 5.10.x LTS kernel
Why do you think MT will jump from 7.1rc4 to 7.2beta1? The usual version path is beta → rc → release and I don’t see any reason to skip release version with 7.1 series. And I don’t think there’s a serious reason to jump from 5.6 (or whatever 7.1rc is using) to 5.10 … before MT irons out most (if not all) UI and driver issues still present.
We did see jump from 7.0beta to 7.1beta, but MT explained it was due to (change of) versioning rules …
Same here. Sadly…
SMB shares and users still self-created on ccr2004
Found on Reddit that some users receive rc5. Also waiting for at least a stable version cause my CCR2004-1G-12S+2XS still doesn’t have a production-ready firmware that can use all amount of RAM.
Trying to update a RB 850Gx2 (PPC) with the dev release, but winbox keeps saying “calculating download size” and hangs on that. While trying any other package option (long-term, stable, testing) they all download fluently. Something I’m missing here?
Might be related to the previous post that a new version might be coming shortly and they disabled rc4 for download already ?
If it’s stuck on calculating download size then you need to remove any extra packages that are installed.
It was a joke referring to bad software engineering practices from Mkt like introducing new features during a RC cycle. At this point they should just increment a number or pick a random one
None. It’s as it was by default. Never added any extras.
Hi, I’m interested in REST-API feature a lot, and this is a CCR1072 owner.
I have a trouble to execute just a simple request but it just hangs for 30 sec and got no response from the server.
Could you please give a test on a Tilera machine?
[Administrator@DESKTOP ~]$ curl -k -v -u admin: http://router.mydomain:48729/rest/ip/addresses
* STATE: INIT => CONNECT handle 0x80007eee8; line 1789 (connection #-5000)
* Added connection 0. The cache now contains 1 members
* STATE: CONNECT => RESOLVING handle 0x80007eee8; line 1835 (connection #0)
* family0 == v4, family1 == v6
* Trying 192.168.1.1:48729...
* STATE: RESOLVING => CONNECTING handle 0x80007eee8; line 1917 (connection #0)
* Connected to router.mydomain (192.168.1.1) port 48729 (#0)
* STATE: CONNECTING => PROTOCONNECT handle 0x80007eee8; line 1980 (connection #0)
* STATE: PROTOCONNECT => DO handle 0x80007eee8; line 2003 (connection #0)
* Server auth using Basic with user 'admin'
> GET /rest/ip/addresses HTTP/1.1
> Host: router.mydomain:48729
> Authorization: Basic YWRtaW46
> User-Agent: curl/7.79.1
> Accept: */*
>
* STATE: DO => DID handle 0x80007eee8; line 2077 (connection #0)
* STATE: DID => PERFORMING handle 0x80007eee8; line 2196 (connection #0)
* STATE: PERFORMING => DONE handle 0x80007eee8; line 2395 (connection #0)
* multi_done
* Empty reply from server
* The cache now contains 0 members
* Closing connection 0
curl: (52) Empty reply from server
You have to use HTTPS, see documentation for more info:
https://help.mikrotik.com/docs/display/ROS/REST+API
I have a tutorial on this on YouTube
Youtube tutorial is done by a random MT user. Answer above by @mrz is given by Mikrotik employee. So there are two questions: