If the Mikrotik box is behind a NAT router, then the /ip cloud service is useless, because it registers the LAN IP address of the Mikrotik, instead of the true external IP address.
Please can the /ip cloud feature can be enhanced with an option to register the true external IP address, as sensed by the IP Cloud server, instead of the LAN IP address of the Mikrotik WAN interface.
If you login to your NAT router then surely you can forward the winbox port to your internal device?
Use the ddns script. It works reliably.
You miss the point completely. It is the NAT router that has a public IP address that is dynamically allocated by the ISP, so I am seeking a solution for locating the public IP address of the NAT router, in order to access the Mikrotik. Of course the Mikrotik is in the router’s DMZ, so there is no problem reaching the Mikrotik once the NAT router has been located.
Ah, my mistake
In this case I guess you would need to use the DDNS script or another method to get your external IP Address as I think it would easily cause messes with people behind ISP NAT where you are unable to punch through it or where if you took your router somewhere your password could easily be nicked by a bad actor.
If they add an option to have them detect it then that would be great however I think there are many downsides to the likely outcome of it and I am not sure you will get the change you desire in this feature.
Regards
Alexander
Isn’t the cloud notification happening in an “on event” fashion. e.g. change of the IP assigned to the WAN interface?
If this is the case, the whole cloud stuff is useless, since your WAN IP in the DMZ won’t change, thus no public IP change events will be generated/notified.
IMHO the router hosting the public interface needs to solve dynamic DNS issues, not one from your DMZ or LAN.
No, IP is updated every minute, regardless of changes. Next version will allow you to choose between public IP and local IP.
Tnx. for the clarification normis.
Still I think it’s a good concept that every network device should be self-sufficient to resolve its access requirements, including dynamic DNS registrations.
In this way there are no dependencies between the two, and GW access will be available even if the DMZ/LAN device responsible with the registration fails.
Thank you!!
is there anyway to force update ip cloud after power loss for my 951Ui-2HnD ??
It does this automatically, every 60s, or you can use the “force-update” command in console
Normis, and what if we use multiple WAN connecties?
Does this also work with the new version of The Mikrotik cloudservices?
it will resolve to one of your global IP addresses. If your firewall is configured properly, you will be able to connect to one of the WAN interfaces and establish a connection the router.
Or what is the problem?
I had v6.18 installed and after changing public ip ip cloud didnt changed it. I had to come on place and do force-update manually. Why?
I upgraded to v6.19, hope it solved this problem.
I have a suggestion for IP Cloud, make an checkbox ( Use my external IP) which will make that MT will check IP using remote service, that can for example connect to mt servers and check your outgoing ip (outside IP) and assign to this domain.
It already does that. It is using external ip address for the hostname.
It was not like this in first version it appeared, so just make sure you are using the latest routeros version.
I use multiple wan how do I direct this out a specific wan. ? is there an ip range I can use and set a /ip route rule for? My problem is my main isp uses nat and proxy before it gets to my router but my other isps don’t So I need to manage from wan2 or wan 3.
is there a script i need to run becuase of it being host name and not IPs?
you can use policy routing, to determine which gateway will be used for which connections.
http://wiki.mikrotik.com/wiki/Testwiki/IP_routing#Policy_routing_implementation_example
I Have problem with access my RB I activate the cloud service and I get my DNS name but when I am try to log from winbox it says wrong username or password
you are logging into a different router maybe? are you sure your DDNS address resolves to correct IP? If there is NAT, is it correctly configured for redirection ?