# Synology target both from LAN & externally?

**URL:** https://forum.duplicati.com/t/synology-target-both-from-lan-externally/2724
**Category:** Uncategorized
**Created:** [March 3, 2018, 2:33pm UTC](https://forum.duplicati.com/t/synology-target-both-from-lan-externally/2724 "2018-03-03T14:33:20Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![JonMikelV](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/j/439d5e/32.png) [@JonMikelV](https://forum.duplicati.com/u/JonMikelV)
#### Post date: [March 3, 2018, 7:09pm UTC](https://forum.duplicati.com/t/synology-target-both-from-lan-externally/2724/5 "2018-03-03T19:09:43Z")

</div>

This sounds like a similar issue that prompted me to post this topic:

> [@Fallback destination connection option?](https://forum.duplicati.com/t/fallback-destination-connection-option/2429):
>
> I have a backup set up to my unRAID box over my LAN (high speed) but it can also be accessed over the internet (slower speed). I think it might be nice to allow for “failover” destination connection options. I picture it working like this - there’s still only the one destination, but different ways to connect to it: if can connect via LAN (onsite) use that else if can connect via SFTP (offsite) use that fail “destination not available”

For me, while I could always use the external reference that basically meant that I was backing up at my broadband speeds rather than my LAN speeds.

I haven’t tested this theory yet but one potential workaround might be a `--run-script-before` script that figures out if the destination is available on the local LAN then adjusts the server and port values as necessary.

Theoretically the destination can be adjusted by setting the `DUPLICATI__REMOTEURL` in the script, though I’m not sure about setting the port. And, again, I haven’t actually tested this yet. 😉

---

_[View the full topic](https://forum.duplicati.com/t/synology-target-both-from-lan-externally/2724)._