Difference between revisions of “Manual:IP/Cloud”


  (21 intermediate revisions by the same user not shown) Line 1: Line 1: − {{Versions|v6.27+}} +

{{Versions| v6.+}}

    −

{{Note|Currently running as public beta. Server availability could vary, and syntax could change}}

+   +

 

  +

{{Note | Currently running as public beta. Server availability could vary, and syntax could change}}

     

= Summary =

 

= Summary =

Line 18: Line 20:      

{{Warning | Be aware that if router has multiple public IP addresses and/or multiple internet gateways, the exact IP used for the update may not be as expected!}}

 

{{Warning | Be aware that if router has multiple public IP addresses and/or multiple internet gateways, the exact IP used for the update may not be as expected!}}

  +  

= Operation details =

 

= Operation details =

     

* Checks for outgoing IP address change: every 60 seconds  

 

* Checks for outgoing IP address change: every 60 seconds  

* Waits for the MikroTik’s cloud server’s response: 15 seconds  

+

* Waits for the MikroTik’s server’s response: 15 seconds  

 

* DDNS record TTL: 60 seconds  

 

* DDNS record TTL: 60 seconds  

 

* Cloud time update: after reboott and during every DDNS update (when router’s WAN IP address changes or after the <code>force-update</code> command is used)

 

* Cloud time update: after reboott and during every DDNS update (when router’s WAN IP address changes or after the <code>force-update</code> command is used)

 

* Time-zone-autodetect: The time zone is detected depending on the router’s public IP address and our commercial database

 

* Time-zone-autodetect: The time zone is detected depending on the router’s public IP address and our commercial database

    −

After the device has sent it’s IP address to the MikroTik’s cloud server, it will stay on the server permanently. DNS name (/ip cloud ddns-name) will resolve to last sent IP address. When user sets <code>/ip cloud set ddns-enabled=no</code>, then the device will send a message to MikroTik’s cloud server to disable the DNS name for this device.

+

After the device has sent IP address to the MikroTik’s server, it will stay on the server permanently. DNS name (/ip cloud ddns-name) will resolve to last sent IP address. When user sets <code>/ip cloud set ddns-enabled=no</code>, then the device will send a message to MikroTik’s server to disable the DNS name for this device.

    −

When <code>/ip cloud set ddns-enabled=yes</code> is set, then the device will send encrypted packets to MikroTik’s cloud server using port ”’UDP/15252”’. For devices using RouterOS v6.43 and newer the encrypted [[ Manual:IP/Cloud | IP/Cloud]] packets are going to be sent to ”’cloud2.mikrotik.com”’. For devices using older RouterOS versions (prior to v6.43), encrypted [[ Manual:IP/Cloud | IP/Cloud]] are going to be sent to ”’cloud.mikrotik.com”’.

+

When <code>/ip cloud set ddns-enabled=yes</code> is set, then the device will send encrypted packets to MikroTik’s server using port ”’UDP/15252”’. For devices using RouterOS v6.43 and newer the encrypted IP/Cloud packets are going to be sent to ”’cloud2.mikrotik.com”’. For devices using older RouterOS versions (prior to v6.43), encrypted IP/Cloud are going to be sent to ”’cloud.mikrotik.com”’.

     

Since RouterOS v6.43 if your device is able to reach ”’cloud2.mikrotik.com”’ using IPv6, then ”’AAAA”’ record is going to be created for your public IPv6 address. If your device is only able to reach ”’cloud2.mikrotik.com”’ using IPv4, then only ”’A”’ record is going to be created for your public IPv4 address.

 

Since RouterOS v6.43 if your device is able to reach ”’cloud2.mikrotik.com”’ using IPv6, then ”’AAAA”’ record is going to be created for your public IPv6 address. If your device is only able to reach ”’cloud2.mikrotik.com”’ using IPv4, then only ”’A”’ record is going to be created for your public IPv4 address.

    −

{{ Note | IP Cloud requires a working license on Cloud Hosted Router (CHR). }}

+

{{ Note | IPCloud requires a working license on Cloud Hosted Router (CHR). }}

     

== Example ==

 

== Example ==

Line 52: Line 55:      

<pre>

 

<pre>

[admin@MikroTik] > ip cloud set update-time=yes  

+

[admin@MikroTik] > ip cloud set update-time=yes  

 

</pre>

 

</pre>

    Line 58: Line 61:      

<pre>

 

<pre>

[admin@MikroTik] > system clock set time-zone-autodetect=yes  

+

[admin@MikroTik] > system clock set time-zone-autodetect=yes  

  +   +

 

  +   +

 

  +   +  

</pre>

 

</pre>

  +   +      

= Properties =

 

= Properties =

Line 70: Line 81:  

}}

 

}}

    −

{{Mr-arg-ro-table

+

{{Mr-arg-table

 

|arg=ddns-enabled

 

|arg=ddns-enabled

 

|type=yes {{!}} no

 

|type=yes {{!}} no

 

|default=no

 

|default=no

|desc=If set to yesthen router will send an encrypted message to the MikroTik cloud server. Server will then decrypt the message and verify that sender is an authentic Mikrotik router. If all is OK then server will create a DDNS record for this router and send response to the router. Every minute the cloud service on the router will check if WAN IP address  

+

|desc=If set to yesthen will send an encrypted message to the MikroTikserver. will then decrypt the message and verify that sender is an authentic . If all is OKthen server will create a DDNS record for this and send response to the . Every minute the service on the router will check if WAN IP address  

matches the one sent to server and will send encrypted update to cloud server if IP address changes.  

+

matches the one sent to server and will send encrypted update to cloud server if IP address changes.  

 

}}

 

}}

    −

{{Mr-arg-ro-table

+

{{Mr-arg-table

|arg=force-update

  −

|type=command

  −

|desc=When executed, ddns update to cloud server will be sent immediately, even if router’s IP address is not changed.

  −

 

  −

Note: if ”/ip cloud update-time” is set to “auto” then router clock will be updated to cloud server time (if no ntp or sntp client is enabled).

  −

}}

  −

 

  −

{{Mr-arg-ro-table

   

|arg=update-time

 

|arg=update-time

 

|type=yes {{!}} no

 

|type=yes {{!}} no

 

|default=no

 

|default=no

|desc=If set to yesthen router clock will be set to time, provided by cloud server IF there is no SNTP or NTP service enabled. If set to nothen cloud service will never update router clock. If update-time = yes, Clock will be updated even when /ip cloud ddns-enabled = no  

+

|desc=If set to yesthen router clock will be set to time, provided by cloud server IFthere is no SNTPenabled. If set to nothen service will never update clock. If update-timeyes, Clock will be updated even when ddns-enabledno

 

}}

 

}}

     

{{Mr-arg-ro-table

 

{{Mr-arg-ro-table

 

|arg=public-address

 

|arg=public-address

|type=string

+

|type=

|desc=Read only, shows router IPv4 address that was sent to cloud server and assigned to DNS name (see /ip cloud dns-name). This field is visible only after at least one ddns-request was successfully completed.  

+

|desc=IPv4 address that was sent to cloud server and assigned to DNS name (see /

  +   +

 

  +   +   +   +

cloud dns-name). This field is visible only after at least one ddns-request was successfully completed.  

 

}}

 

}}

     

{{Mr-arg-ro-table

 

{{Mr-arg-ro-table

 

|arg=warning  

 

|arg=warning  

|type=string

+

|type=string

|desc=Read only, shows a warning message if IP address sent by router differs from IP address in UDP packet header as visible by cloud server. Typically this happens if router is behind NAT. Example: “DDNS server received request from IP 123.123.123.123 but your local IP was 192.168.88.23; DDNS service might not work”  

+

|desc=a warning message if IP address sent by differs from IP address in UDP packet header as visible by server. Typically this happens if is behind NAT. Example: “DDNS server received request from IP 123.123.123.123 but your local IP was 192.168.88.23; DDNS service might not work”  

 

}}

 

}}

     

{{Mr-arg-ro-table

 

{{Mr-arg-ro-table

 

|arg=dns-name

 

|arg=dns-name

|type=string

+

|type=

|desc=Read only, shows DNS name assigned to the router. Name consists of 12 character serial number appended by ”.sn.mynetname.net”. This field is visible only after at least one ddns-request is successfully completed.  

+

|desc=DNS name assigned to the . Name consists of 12 character serial number appended by ”.sn.mynetname.net”. This field is visible only after at least one ddns-request is successfully completed.  

 

}}

 

}}

     

{{Mr-arg-ro-table-end

 

{{Mr-arg-ro-table-end

 

|arg=status

 

|arg=status

|type=status

+

|type=

|desc=Read only, contains text string that describes current dns-service state. The messages are self explanatory

+

|desc=text string that describes current dns-service state. The messages are self explanatory

    −

*”’updating…”’

+

* ”’updating…”’

*”’updated”’

+

* ”’updated”’

*”’Error: no Internet connection”’

+

* ”’Error: no Internet connection”’

*”’Error: request timed out”’

+

* ”’Error: request timed out”’

*”’Error: REJECTED. Contact MikroTik support”’

+

* ”’Error: REJECTED. Contact MikroTik support”’

*”’Error: internal error”’ – should not happen. One possible cause is if router runs out of memory

+

* ”’Error: internal error”’ – should not happen. One possible cause is if router runs out of memory

  +     −

}}

       

== Advanced ==

 

== Advanced ==

Line 134: Line 143:  

}}

 

}}

    −

{{Mr-arg-rotable

+

{{Mr-arg–

 

|arg=use-local-address

 

|arg=use-local-address

 

|type=yes {{!}} no

 

|type=yes {{!}} no

 

|default=no

 

|default=no

|desc=By default, the DNS name will be assigned to the detected public address (from the UDP packet header). If you wish to send your “local” or “internal” IP address, set this to yes

+

|desc=By default, the DNS name will be assigned to the detected public address (from the UDP packet header). If you wish to send your “local” or “internal” IP address, set this to yes

 

}}

 

}}

  +   +   +   +   +

Since RouterOS v6.14 MikroTik offers a Dynamic DNS name service for RouterBOARD devices. This means that your device can automatically get a working domain name, this is useful if your IP address changes often, and you want to always know how to connect to your router.

After the device has sent its IP address to the MikroTik’s Cloud server, it will stay on the server permanently. DNS name (/ip cloud ddns-name) will resolve to last sent IP address. When user sets /ip cloud set ddns-enabled=no, then the device will send a message to MikroTik’s Cloud server to disable the DNS name for this device.

When /ip cloud set ddns-enabled=yes is set, then the device will send encrypted packets to MikroTik’s Cloud server using port UDP/15252. For devices using RouterOS v6.43 and newer the encrypted IP/Cloud packets are going to be sent to cloud2.mikrotik.com. For devices using older RouterOS versions (prior to v6.43), encrypted IP/Cloud are going to be sent to cloud.mikrotik.com.

Since RouterOS v6.43 if your device is able to reach cloud2.mikrotik.com using IPv6, then AAAA record is going to be created for your public IPv6 address. If your device is only able to reach cloud2.mikrotik.com using IPv4, then only A record is going to be created for your public IPv4 address.



Source link

Administrador AcessoWi-Fi.com – Gerente UnicoHost Soluções Web – Engenheiro de Redes

Julio Rossoni

Administrador AcessoWi-Fi.com - Gerente UnicoHost Soluções Web - Engenheiro de Redes

This site uses Akismet to reduce spam. Learn how your comment data is processed.