We only can do it for ARM systems, no plans for MIPS now.
Licence costs, how I see it.+1 mipsbe (lot of deployed devices)
but really... what's the reason of zerotier not available for mipsbe (or other archs)?
I'm not following this closely, but did anyone from MikroTik ever in any way suggest or confirm that they are paying anything to ZeroTier for including it in RouterOS? Because it would seem weird. ZeroTier is running commercial service, more clients supporting it is good for them. Surely some MikroTik customers appreciate it too, and that in turn is good for MikroTik if they can offer it. So to me it looks like mutually beneficial cooperation, but definitely not overwhelmingly in MikroTik's favour, to justify paying for it.
I am sorry for my EnglishCan you explain how do you setup that configuration? Or maybe make a diagram or something?... I'm interested on that setup..
LTE input I gave 192.168.4.1 as Router. Raspberry zero 192.168.4.221
for Zerotier settings
I'd love to know what the blocker is for mipsbe hardware
Another +1, ZT is really useful with LTE (which often have CGNAT). And most of Mikrotik's LTE devices are MIPSBE. I can see not offering something exotic like TILE... But MIPSBE is where ZT seems noticeably missing.I'd love to know what the blocker is for mipsbe hardware
Agreed. If MIPSBE was a legacy platform, I'd understand implicitly, but they just released the CRS504 on that platform. There are several CRS3xx models on it as well, including "Our fastest switch for the most demanding setups" and the "Switch of the future".
The option to tie two remote switches together with ZeroTier is a brain-dead natural move, particularly when they're both behind NAT.
Having an SXT myself, I can tell you this: it's underpowered to add anything else next to minor routing towards CAP and Cap Lite, some DHCP and if needed capsman.I would really like to use Zerotier on my SXT. Any chance this will be possible some time in the future?
there is some CRS 3xx references which uses MiPS CPU:What CRS?
MikroTik has added ZeroTier to RouterOS v7.1rc2 as a separate package for the ARM/ARM64 architecture
of course i dont think a good practice to use a switch as a VPN gateway, but for secure remote management of the switch itself it will be nice
You can run Zerotier in a Docker container on CHR.Still no timeline for supporting other architectures? I bought a Hap ac3 just to try it out and it works great! But I'm literally waiting for you guys to support x86/CHR before purchasing any more licenses!
Flash is only 16Mb.In my hEX, I have free 200.6 MiB. There is the sufficient room for 32M.In my hEX S I have free 1892 KiB, where is sufficent room for 32M???
Why is it "foolish" to use the microsd? The Dude package already runs on the microsd, is that foolish?But even assuming that once "optimized", compiled and compressed, are 3M the package, the system already occupies 15M...
And it is completely useless and foolish to name the external memory, which you know perfectly well that it will never contain packets loaded at system startup, even for safety.
You are the foolish, the microsd it hosts only the database,Why is it "foolish" to use the microsd? The Dude package already runs on the microsd, is that foolish?
It seems like you're losing the argument if you're resorting to attacking the other person. Yes, the dude db is on the microsd, which is worse because it's a read-write load vs a read-only load in storing executables--microsd flash tends to be less durable than onboard flash. Also, I don't need to run the dude on my hEX.You are the foolish, the microsd it hosts only the database,Why is it "foolish" to use the microsd? The Dude package already runs on the microsd, is that foolish?
don't be a know-it-all, that you risk saying bullshit.
The executable code is in the nand along with routeros ...
And the dude is ~1,2M, no space at all for zerotier....
I am not "losing" the subject at all, also because the facts speak for themselves: there is no space.
All these requests for Zerotier on mips are perfectly useless if the RouterBOARD does not have at least 32M of space on the NAND.
I don't care if I'm right or not…language problem
what else could I do?
That was a lot more civil and calm explanation.To be precise, if I didn't explain myself well,
I argue, without giving further examples,
that simply by inserting support for zerotier, there would be no space left,
and in future versions you might be forced not to update (to continue using zerotier ),
because only the RouterOS package takes up almost everything and there is no room left for anything else.
As has already happened on smips...
What I meant is that I am neither interested to have right or not on the subject,So…you're conceding that your argument is both wrong and ineffectively presented?
Please consider the effective used space after installation, not only the compressed package.Look at what exists now. Size of main package (7.4) is 12.5 MB (arm), 11.3 MB (mipsbe) and 10.7 MB (mmips), with AFAIK same functionality. Size of zerotier package for arm is a bit over 0.7 MB, and I don't see any reason why if should be significantly more for other architectures if other stuff isn't. So size alone is not an argument against mipsbe/mmips version. As it looks now, it has good chance to last longer (when main package keeps growing) on these than on 16 MB arm devices.
Very interesting. Sadly metarouter is not supported by newest devices.Hey just for anyone still interested in this, it looks to be possible by adding an OpenWRT MetaRouter, OpenWRT has a MIPS Zerotier package.