Community discussions

MikroTik App
  4. RouterOS
  5. General

IP Cloud Update Problem.

Locked
 
feiyangd
just joined
Topic Author
Posts: 1
Joined: Thu Apr 22, 2021 6:59 am

IP Cloud Update Problem.

Sat Apr 24, 2021 9:37 am

Hi all,

Ip cloud service seems to not work..
And diable and enable the ddns, reset configuration, reboot, reinstall the ROS VM, all have no effect to solve the problem.
Code: Select all
[admin@MikroTik] >  /ip cloud print
          ddns-enabled: yes
  ddns-update-interval: none
           update-time: yes
                status: updating...
Version:CHR 6.47.9 (long-term) on ESXI 6.7
Level:P-Unlimited (Trial)
WAN:PPPoE Dynamic IP


Does anyone have an idea how could I solve the problem?
Code: Select all
[admin@MikroTik] > export
# apr/24/2021 14:22:53 by RouterOS 6.47.9
# software id = 
#
#
#
/interface ethernet
set [ find default-name=ether1 ] disable-running-check=no name=LAN
set [ find default-name=ether2 ] disable-running-check=no name=WAN
/interface pppoe-client
add add-default-route=yes disabled=no interface=WAN name=pppoe-out1 password=****** user=*****
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip address
add address=192.168.8.3/24 interface=LAN network=192.168.8.0
/ip cloud
set ddns-enabled=yes update-time=yes
/ip dhcp-server network
add address=192.168.8.0/24 dns-server=192.168.8.3 gateway=192.168.8.3 netmask=24
/ip dns
set allow-remote-requests=yes servers=8.8.8.8,8.8.4.4
/ip dns static
add address=159.148.172.251 disabled=yes name=cloud2.mikrotik.com
/ip firewall address-list
add address=cloud.mikrotik.com list="MT Cloud"
add address=cloud2.mikrotik.com list="MT Cloud"
/ip firewall mangle
add action=log chain=output dst-address-list="MT Cloud"
add action=log chain=input src-address-list="MT Cloud"
/ip firewall nat
add action=masquerade chain=srcnat
/ip service
set telnet disabled=yes
set ftp disabled=yes
set ssh disabled=yes
set api disabled=yes
set api-ssl disabled=yes
/system clock
set time-zone-name=Asia/Shanghai
/system ntp client
set enabled=yes primary-ntp=193.182.111.143


[admin@MikroTik] > ping cloud.mikrotik.com
  SEQ HOST                                     SIZE TTL TIME  STATUS                                                                                                              
    0 159.148.147.229                            56  50 242ms
    1 159.148.147.229                            56  50 233ms
    2 159.148.147.229                            56  50 242ms
    3 159.148.147.229                            56  50 242ms
    sent=4 received=4 packet-loss=0% min-rtt=233ms avg-rtt=239ms max-rtt=242ms 

[admin@MikroTik] > ping cloud2.mikrotik.com
  SEQ HOST                                     SIZE TTL TIME  STATUS                                                                                                              
    0 159.148.172.251                                         timeout                                                                                                             
    1 159.148.172.251                                         timeout                                                                                                             
    2 159.148.172.251                            56  50 233ms
    sent=3 received=1 packet-loss=66% min-rtt=233ms avg-rtt=233ms max-rtt=233ms 


[admin@MikroTik] > tool sniffer quick ip-address=159.0.0.0/8 interface=pppoe-out1
INTERFACE                            TIME    NUM DIR SRC-MAC           DST-MAC           VLAN   SRC-ADDRESS                         DST-ADDRESS                         PROTOCOL   SIZE CPU FP 
pppoe-out1                          4.952      1 ->                                             113*.*.*:60283                 159.148.147.201:15252               ip:udp      323   1 no 
pppoe-out1                          5.209      2 <-                                             159.148.147.201:15252               113*.*.*:60283                 ip:udp       66   1 no 
pppoe-out1                          5.209      3 ->                                             113*.*.*:60283                 159.148.147.201:15252               ip:udp      323   1 no 
pppoe-out1                          5.468      4 <-                                             159.148.147.201:15252               113*.*.*5:60283               ip:udp       84   1 no 
pppoe-out1                          5.468      5 ->                                             113*.*.*:60283                 159.148.147.201:15252               ip:udp      360   1 no 
pppoe-out1                          5.716      6 <-                                             159.148.147.201:15252               113*.*.*:60283                 ip:udp       66   1 no 

[admin@MikroTik] >  / tool traceroute cloud2.mikrotik.com
 # ADDRESS                          LOSS SENT    LAST     AVG    BEST   WORST
 1 113.66.112.1                       0%    3   1.6ms    38.9     1.3   113.8
 2 219.135.167.125                    0%    3   1.9ms     1.8     1.7     1.9
 3 121.8.109.81                       0%    3   3.3ms     2.7     1.5     3.3
 4                                  100%    3 timeout
 5 202.97.12.5                      66..    3 timeout     4.1     4.1     4.1
 6 202.97.13.26                       0%    3 218.6ms     216   214.6   218.6
 7 81.173.18.22                       0%    3 211.5ms   211.3   210.3   212.1
 8 62.115.120.228                     0%    3   233ms   230.3     225     233
 9 62.115.114.249                     0%    3 236.2ms   232.2   228.1   236.2
10 62.115.136.79                      0%    2 225.1ms   229.2   225.1   233.2
11 213.248.84.33                      0%    2   248ms   247.8   247.5     248
12                                  100%    2 timeout
13                                  100%    2 timeout
14                                  100%    2 timeout
15 159.148.172.251                   50%    2 231.8ms   231.8   231.8   231.8
16 159.148.172.251                    0%    1 240.1ms   240.1   240.1   240.1

[admin@MikroTik] >  /ip cloud set ddns-enabled=no
[admin@MikroTik] >  /ip cloud set ddns-enabled=yes
[admin@MikroTik] >  /ip cloud force-update
[admin@MikroTik] >  /ip cloud print
          ddns-enabled: yes
  ddns-update-interval: none
           update-time: yes
                status: updating...
Top
 
rifhar
just joined
Posts: 2
Joined: Tue Mar 19, 2019 4:56 am

Re: IP Cloud Update Problem.

Tue May 18, 2021 5:22 am

I also experienced this kind of problem and it has been almost 2 months that the Routerboard cannot update the cloud, if the trace route the cloud will go directly to another place, ...
Top
 
User avatar
GreySer
just joined
Posts: 23
Joined: Thu Apr 21, 2016 9:38 am
Location: Cheboksary

Re: IP Cloud Update Problem.

Fri May 21, 2021 2:27 pm

Two month same problem on CHR. Support cannot help.
Top
 
User avatar
nichky
Forum Guru
Forum Guru
Posts: 1379
Joined: Tue Jun 23, 2015 2:35 pm

Re: IP Cloud Update Problem.

Sat May 22, 2021 12:44 pm

still is not clear for me:
use-local-addres
Top
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 12438
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:
Contact rextended

Re: IP Cloud Update Problem.

Sat May 22, 2021 1:16 pm

still is not clear for me:
use-local-addres
I see your signature about random.....
today I have no time, but if you "remember me" on the forum, if I forget this,
i make a function,
input can be one string of any lengt (max routeros length) composed by some symbolslike "^u-1@#.n€*$"
^ = uppercase / @ = lowercase / # = number / + = any of previous / $ = EASY symbol (! # $ % & * + = ? @) / ! any symbol (easy and the others) / * any character (from "space" 0x20 to ~ 0x7E)
(EASY symbol because on some keyboard / language symbols like ( ) < >, . \/ : ; -_ ^ " ' ` | [ ] { } ~ do not are present or are "hard" to write, or are misundestandable like " and '' and `` or hard detected if for example (space) is on the end, or can happen like " " you do not clearly read if is "(space)(space)" or "(space)" [ehehehe. 3 space really :))) ]
standard (from "space" 0x20 to ~ 0x7E) characters are leaved as-is, if > 0x7E or < 0x20 replaced evertime whith ?
and on output be a random password (the lenght is equal of length of string used):
escape code if wanted on final password exactly one of ^ @ # * $ symbols
Code: Select all
:local password $randpass "^u-1@#.n€*$"
:put $password
Iu-1r5.n?R!
Top
 
User avatar
nichky
Forum Guru
Forum Guru
Posts: 1379
Joined: Tue Jun 23, 2015 2:35 pm

Re: IP Cloud Update Problem.

Sat May 22, 2021 2:04 pm

im happy how random does. would you be able to give us an example about

use-local-addres
Top
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 12438
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:
Contact rextended

Re: IP Cloud Update Problem.

Sat May 22, 2021 2:11 pm

im happy how random does
>>>but all seems to be flawed.<<<
???


would you be able to give us an example about
use-local-addres
https://wiki.mikrotik.com/wiki/Manual:IP/Cloud#Advanced

You can use your private IP address like 192.168.1.1 instead of the detected ISP Public IP on WAN.
But next is useable only on local lan.
(device must use private IP, aka it not be one border device)
Top
 
User avatar
nichky
Forum Guru
Forum Guru
Posts: 1379
Joined: Tue Jun 23, 2015 2:35 pm

Re: IP Cloud Update Problem.

Sat May 22, 2021 2:24 pm

no,works well
Top
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 12438
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:
Contact rextended

Re: IP Cloud Update Problem.

Sat May 22, 2021 2:29 pm

no,works well
then update your signature ...
Top
 
User avatar
nichky
Forum Guru
Forum Guru
Posts: 1379
Joined: Tue Jun 23, 2015 2:35 pm

Re: IP Cloud Update Problem.

Sat May 22, 2021 3:30 pm

does it look better now?
Top
 
User avatar
sindy
Forum Guru
Forum Guru
Posts: 10842
Joined: Mon Dec 04, 2017 9:19 pm

Re: IP Cloud Update Problem.

Sat May 22, 2021 5:27 pm

would you be able to give us an example about use-local-address
If use-local-address=no (the default), the xxx.sn.mynetname.net resolves to the public IP from which the DDNS update request has arrived to the cloud server.
If use-local-address=yes, the xxx.sn.mynetname.net resolves to the WAN IP from which your routerboard has sent the DDNS update request, even if it is a private one and thus it will most likely be unreachable from the internet. It might theoretically be useful in specific cases when you'd have multiple WAN IPs on your routerboard, and you wanted xxx.sn.mynetname.net to resolve to one of them but were sending the update requests from the WAN holding the other one, which would require some mid-level magic with pref-src on routes and src-nat rules.

Loosely related: some stupid ISPs assign public IPs to clients, but NAT their traffic to other public IPs (I wouldn't believe that if I haven't seen that myself). And of course the IP assigned to the client is unreachable from the internet.
Top
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 12438
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:
Contact rextended

Re: IP Cloud Update Problem.

Sat May 22, 2021 5:31 pm

some stupid ISPs assign public IPs to clients, but NAT their traffic to other public IPs
wh... wh... whhh.... what the f???
Top
 
User avatar
sindy
Forum Guru
Forum Guru
Posts: 10842
Joined: Mon Dec 04, 2017 9:19 pm

Re: IP Cloud Update Problem.

Sat May 22, 2021 5:33 pm

wh... wh... whhh.... what the f???
Yes. Same feelings here. U.S., mobile operator, I don't remember exactly which one it was, so won't name any not to get sued :)
Top
 
vasmik
just joined
Posts: 7
Joined: Sat Mar 18, 2017 9:24 pm

Re: IP Cloud Update Problem.

Tue Sep 07, 2021 11:09 am

Does the services ip-cloud is working? i am facing an issue today
Top
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 12438
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:
Contact rextended

Re: IP Cloud Update Problem.

Tue Sep 07, 2021 6:48 pm

2021-09-07T15:37:37Z
Now is working again.
Top
Locked

Who is online

Users browsing this forum: anav, Bing [Bot], GoogleOther [Bot], k6ccc, silviub, triodetube and 41 guests
  4. RouterOS
  5. General