Well some sort of control and completely brand agnostic solution... Not to say there are hundreds of more important features requests than IP Cloud or Kids Control viewtopic.php?f=1&t=45934 to tackle first and clearly most of them cannot be replaced by a less than 10 lines script or by an existing component supporting an established standard !Free dyndns per device. What more can u ask
While you're doing this DNS stuff, is there any chance that conditional-forwarders might be added into the RouterOS DNS resolver? i.e. relay any requests for company.local to 192.168.1.1, for a branch office scenario?While you find some feature not so useful to yourself and relentlessly bash them - consider that there are other features made by RouterOS developer team that you are using. This one particular - IP-Cloud - is touted by you as very unsafe and understandably so - MikroTik hasn't disclosed information - but from time to time your posts look like just bashing.Actually this would put the mikrotik in the middleman role. It has to be considered as unsafe. I understand that some people do not care about it, but I rather build my own management network instead of rely on services that I cannot control and that can do whatever I do not know what above what they promote.
Ona brighter note - there are new features in testing, new features in the development and one feature that just came out of testing and is included in new RC - IPv6 support.
this is what "IPv6 support" entails -
*) DNS requests via IPV6
*) IP-Cloud services (DDNS update, timezone) via IPv6
*) AAAA support for *.ns.mynetname.net domains
For now - there is only AAAA OR A entry support. Due to nature of RouterOS - if you have a dual-stack router and want the IP-Cloud address to be IPv6 you have to force it via /ip dns static entry - add cloud2.mikrotik.com with these IPv6 addresses 20a2:610:7501:4000::251 and 2a02:610:7501:1000::201
coming to the router near you soon:Code: Select all
$ host <serial>.sn.mynetname.net <serial>.sn.mynetname.net has address 192.168.88.1 <serial>.sn.mynetname.net has IPv6 address 2001:db8:1337:beef::ada
I hear mumbles of CHR being available from 6.43 so there could quite possibly be x86 implementation.I am also looking forward to have support in x86Will it be available for x86 router soon?
The serial number consists of 12 hexadecimal characters.Currently is easy to make a brute force search for mikrotik devices using the cloud service as the names follow an simple pattern and is just an DNS query.