I have a Synology NAS at home (let's call it ananas), it is attached to my router via ethernet.
I also have a desktop (let's call it Aero), it is connected to the same router via wifi.
I configured in another country, a laptop (xps13), I could access the NAS without any problem (the ports were open and I used NAT) using https rsync over ssh and ssh.

Here is a map of the local network: network map

However now that I am back home, I just can't find the NAS by using nmap (without -Pn, it is just not listed while everything else is), can't ping it, and can't ssh into it. The twist is that this only happens on the laptop.

Running route -n on the xps 13 yields:

[soulthym@xps13 ~]$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface         UG    600    0        0 wlp2s0   U     600    0        0 wlp2s0

And on the Aero:

[soulthym@Aero ~]$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface         UG    303    0        0 wlp3s0   U     303    0        0 wlp3s0   U     600    0        0 wlp3s0

For debugging purposes I disabled the firewall on the NAS, disabled IP auto-blocking on the NAS, and set the exact same firewall on both the Desktop and the Laptop (using /etc/iptables/iptables.rules).

From the xps13 I get:

[soulthym@xps13 ~]$ nmap -Pn
Starting Nmap 7.70 ( https://nmap.org ) at 2019-08-19 18:22 CEST
Nmap scan report for ananas-1.home (
Host is up (0.16s latency).
All 1000 scanned ports on ananas-1.home ( are filtered

Nmap done: 1 IP address (1 host up) scanned in 8.88 seconds

Whereas I get all the ports from the Aero.

Same story goes for pinging, works beautifully from the Aero, but the xps13 yields:

[soulthym@xps13 ~]$ ping
PING ( 56(84) bytes of data.
From icmp_seq=1 Destination Host Unreachable
From icmp_seq=2 Destination Host Unreachable
From icmp_seq=3 Destination Host Unreachable

And while ssh-ing:

ssh: connect to host port $PORT: No route to host
[soulthym@xps13 ~]$ ip neigh dev wlp2s0 lladdr xx:xx:xx:xx:xx:xx REACHABLE dev wlp2s0 lladdr xx:xx:xx:xx:xx:xx STALE dev wlp2s0 FAILED xxxx::xxxx:xxxx:xxxx:xxxx 
             dev wlp2s0 lladdr xx:xx:xx:xx:xx:xx router REACHABLE 

(the above fragment was moved from a comment, and was broken there)

This only happens when using the local network. I can use a VPN and connect to the public IP but that is just a temporary fix that doesn't fit the use for backups...

Any idea of what I could have done wrong here?

  • Your nmap output for xps13 indicates that it knows the host is up, but ports are filtered by a firewall. Is it possible that there is a filter on your NAT that's blocking xps13?
    – Peschke
    Commented Aug 19, 2019 at 17:02
  • @Peschke not that I know of, and it would mean it only blocks this specific ip? Because it works when using a VPN or ssh-ing from the public IP
    – Soulthym
    Commented Aug 19, 2019 at 17:06
  • I'm not sure. I reread the nmap man page for -Pn, which says it treats all hosts as online. Therefore, I think my observation about xps13 seeing your NAT as up is incorrect. Can xps13 access or ping Aero while connected to your local network?
    – Peschke
    Commented Aug 19, 2019 at 17:11
  • No in fact it can not, and while scanning without -Pn it did not find the NAS. I'll edit and add this information to the post
    – Soulthym
    Commented Aug 19, 2019 at 17:14
  • If Aero's iptables allows pings, is your router not allowing xps13 to communicate on the internal network? Maybe check the router settings. I'm out of other ideas at the moment.
    – Peschke
    Commented Aug 19, 2019 at 17:23

1 Answer 1


Adding a DNS entry in the router's DNS itself allows to bypass the issue. As of now, I can not access the NAS by IP but at least I can by "nickname".

  • What is in the DNS record? Commented Jul 2, 2020 at 17:06

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .