Synology NAS behind router

RouterOS General
1

Hello

I bought a Synology NAS. I’d like to setup DS File tool, from and outside my LAN, without QuickConnect functionality (easy but not performant).
Therefore,

  • I subscribe to Synology DNS as I don’t have a fix IP → x.myds.me
  • I forwarded required port (5000) to my NAS

Working perfeclty.. from outside the LAN. :smiley:
From inside the LAN, I’m struggeling to connect via x.myds.me.

I read Mikrotik tutorial about Hairpin NAT, and tried to configure my router accordingly but without success.. :frowning:

Could someone give me a hand ?

Please find below my configuration.

Thanks a lot in advance !

Architecture :

  • router : 192.168.88.1
  • NAS (server) : 192.168.88.237 (IP fixed)
  • phone (client) - on WiFi : 192.168.88.238 (IP fixed)

Current configuration (ok from outside LAN) :

  • Defautl Mikrotik NAT rule:
chain = srcnat
out-interface = ether1-gateway
action = masquerade
  • Port forwarding :
chain = dstnat
protocol = 6
dst-port = 5000
in-interface = ether1-gateway
action = dst-nat
to-address = 192.168.88.237
to-ports = 5000

I tried following srcnat rule but with no success :

chain = srcnat
src-address = 192.168.88.0/24
dst-address = 192.168.88.237
protocol = 6
dst-port = 5000
out-interface = bridge-local
action = masquerade
2

Can’t assign IP address greater than X.X.X.254.

3

Thx for your answer.
Indeed, I tried to change a little bit my config in the post in order to avoid spreading info on the net (paranoia ?) but you discovered the trick :wink:
Same question, with information updated in the description of the post.

Thx beforehand

4

Assuming you are using your MTK as the DNS server for the LAN, you could just add x.myds.me into the DNS server as a static entry, and point it at the internal IP of the Synology. Then you don’t need to mess with NAT hairpin at all.

The only “problem” with this is from your own LAN, you won’t be able to determine if x.myds.me is pointing to your WAN IP, but the Synology itself can tell you if it does or not (it complains if it can’t update the DDNS name).

5

Thx for your reply
DNS is a service from Synology itself, I have no fix IP..
Isn’t hairpin NAT the solution here ?
Any idea if the problem is coming from the setup I made ?

6

I have a synology NAS and you can try and make hairpin or loopback work but just create a static DNS entry for the inside LAN that points the FQDN to the local IP then you should be all set.
are you using a dynamic DNS service like DYNDNS for outside?

THanks leon

7

hum.. this is Chinese for me :open_mouth:
Yes, I’m using a dynamic DNS service (xxx.myds.me)
Could you give me some more details on how to do this ?