CLI is not working on 3 Synology NAS
Hello all,
I am disappointed by the behavior of my 3 Syno NAS. Each one is on different location and IP and they have all the same behavior.
CLI stay blocked on "activating". I tried so many things, firewall configs, reboots and so more but nothing change.
One time a NAS has managed to connect and be visible on the reporting page but after 2 requests stopped to work.
I don't understand what's happening. i am paying this service who works properly on my Android devices but look not able to work with CLI on Syno devices. Please advise.
Below, the result the diag tool.
sh-4.4# nextdns status
running
sh-4.4# nextdns log
Mar 28 21:41:32 Andromeda systemd[1]: Started NextDNS DNS53 to DoH proxy..
Mar 28 21:41:32 Andromeda systemd[1]: Starting NextDNS DNS53 to DoH proxy....
Mar 28 21:41:33 Andromeda nextdns[4453]: Starting NextDNS 1.37.10/linux on :53
Mar 28 21:41:33 Andromeda nextdns[4453]: Listening on TCP/:53
Mar 28 21:41:33 Andromeda nextdns[4453]: Starting mDNS discovery
Mar 28 21:41:33 Andromeda nextdns[4453]: Listening on UDP/:53
Mar 28 21:41:38 Andromeda nextdns[4453]: Setting up router
Mar 28 21:41:38 Andromeda nextdns[4453]: Activating
Mar 28 21:46:00 Andromeda systemd[1]: Stopping NextDNS DNS53 to DoH proxy....
Mar 28 21:46:00 Andromeda nextdns[4453]: Received signal: terminated
Mar 28 21:46:00 Andromeda nextdns[4453]: Stopping NextDNS 1.37.10/linux
Mar 28 21:46:00 Andromeda nextdns[4453]: Restore router settings
Mar 28 21:46:00 Andromeda nextdns[4453]: Deactivating
Mar 28 21:46:00 Andromeda nextdns[4453]: NextDNS 1.37.10/linux stopped
Mar 28 21:46:01 Andromeda systemd[1]: Started NextDNS DNS53 to DoH proxy..
Mar 28 21:46:01 Andromeda systemd[1]: Starting NextDNS DNS53 to DoH proxy....
Mar 28 21:46:01 Andromeda nextdns[11713]: Starting NextDNS 1.37.10/linux on :53
Mar 28 21:46:01 Andromeda nextdns[11713]: Listening on TCP/:53
Mar 28 21:46:01 Andromeda nextdns[11713]: Starting mDNS discovery
Mar 28 21:46:01 Andromeda nextdns[11713]: Listening on UDP/:53
Mar 28 21:46:06 Andromeda nextdns[11713]: Setting up router
Mar 28 21:46:06 Andromeda nextdns[11713]: Activating
Mar 28 21:47:26 Andromeda nextdns[11713]: Received signal: terminated
Mar 28 21:47:26 Andromeda systemd[1]: Stopping NextDNS DNS53 to DoH proxy....
Mar 28 21:47:26 Andromeda nextdns[11713]: Stopping NextDNS 1.37.10/linux
Mar 28 21:47:26 Andromeda nextdns[11713]: Restore router settings
Mar 28 21:47:26 Andromeda nextdns[11713]: Deactivating
Mar 28 21:47:26 Andromeda nextdns[11713]: NextDNS 1.37.10/linux stopped
Mar 28 21:47:26 Andromeda systemd[1]: Started NextDNS DNS53 to DoH proxy..
Mar 28 21:47:26 Andromeda systemd[1]: Starting NextDNS DNS53 to DoH proxy....
Mar 28 21:47:26 Andromeda nextdns[12305]: Starting NextDNS 1.37.10/linux on :53
Mar 28 21:47:26 Andromeda nextdns[12305]: Listening on TCP/:53
Mar 28 21:47:26 Andromeda nextdns[12305]: Starting mDNS discovery
Mar 28 21:47:26 Andromeda nextdns[12305]: Listening on UDP/:53
Mar 28 21:47:31 Andromeda nextdns[12305]: Setting up router
Mar 28 21:47:31 Andromeda nextdns[12305]: Activating
sh-4.4# sh -c 'sh -c "$(curl -s https://nextdns.io/diag)"'
Welcome to NextDNS network diagnostic tool.
This tool will download a small binary to capture latency and routing informatio n
regarding the connectivity of your network with NextDNS. In order to perform a
traceroute, root permission is required. You may therefore be asked to provide
your password for sudo.
The source code of this tool is available at https://github.com/nextdns/diag
Do you want to continue? (press enter to accept)
Testing IPv6 connectivity
available: false
Fetching https://test.nextdns.io
status: ok
client: 87.64.172.119
protocol: UDP
dest IP: 45.90.28.106
server: anexia-dxb-1
Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
fusa-bru: 34.08ms
Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
zepto-bru: 72.977ms
Fetching PoP name for anycast primary IPv4 (45.90.28.0)
anexia-dxb: 149.155ms
Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
anexia-par: 28.077ms
Pinging PoPs
zepto-ams: 21.598ms
vultr-fra: 25ms
netbarista-par: 29ms
virtua-par: 33ms
anexia-par: 26.227ms
vultr-ams: 23.01ms
fusa-bru: 32.489ms
anexia-ams: 27.914ms
anexia-lux: 34.795ms
zepto-bru: 38.348ms
Traceroute for ultra low latency primary IPv4 (185.18.148.91)
1 10.0.0.1 5ms 3ms 3ms
2 192.168.1.1 4ms 4ms 4ms
3 10.24.97.72 11ms 10ms 12ms
4 * * *
5 91.183.242.96 20ms 18ms 18ms
6 195.219.227.22 18ms 19ms 18ms
7 195.219.194.153 23ms 21ms 20ms
8 130.117.15.101 21ms 22ms 22ms
9 130.117.50.5 22ms 21ms 20ms
10 154.54.58.198 28ms 29ms 29ms
11 130.117.2.190 28ms 31ms 28ms
12 154.25.2.98 30ms 29ms 29ms
13 * * *
14 * * *
15 185.18.148.91 33ms 33ms 34ms
Traceroute for ultra low latency secondary IPv4 (194.110.115.97)
1 10.0.0.1 3ms 4ms 4ms
2 192.168.1.1 5ms 4ms 4ms
3 10.24.97.72 11ms 13ms 14ms
4 * * *
5 91.183.242.96 16ms 16ms 18ms
6 * * *
7 * * *
8 80.81.192.165 23ms 23ms 24ms
9 * * *
10 82.102.29.43 35ms 34ms 32ms
11 212.103.51.61 41ms 39ms 38ms
12 * * *
13 45.11.107.155 52ms 53ms 49ms
14 194.110.115.97 48ms 52ms 61ms
Traceroute for anycast primary IPv4 (45.90.28.0)
1 10.0.0.1 4ms 3ms 5ms
2 192.168.1.1 4ms 3ms 4ms
3 10.24.97.72 11ms 11ms 11ms
4 * * *
5 91.183.242.96 16ms 21ms 17ms
6 * * *
7 * * *
8 10.246.114.23 32ms 31ms 32ms
9 10.246.114.65 * 45ms 44ms
10 10.246.113.206 159ms 158ms 159ms
11 * * *
12 45.90.28.0 148ms 147ms 149ms
Traceroute for anycast secondary IPv4 (45.90.30.0)
1 10.0.0.1 10ms 3ms 6ms
2 192.168.1.1 9ms 10ms 4ms
3 10.24.97.72 12ms 11ms 12ms
4 * * *
5 91.183.242.96 15ms 16ms 15ms
6 80.84.23.40 15ms 16ms 15ms
7 * * *
8 * * *
9 10.246.112.86 23ms 23ms 22ms
10 * * *
11 213.227.163.32 27ms 28ms 28ms
12 45.90.30.0 27ms 27ms 26ms
* Posted: https://nextdns.io/diag/4e17a6d0-aed6-11ec-a41a-c7e7f76a00de
Reply
Content aside
- 2 yrs agoLast active
- 139Views
-
1
Following