Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Alternate server address when connected through home local network #5506

Closed
denniskhong opened this issue Jan 30, 2017 · 4 comments

Comments

@denniskhong
Copy link

denniskhong commented Jan 30, 2017

Most consumer grade routers do not allow NAT Loopback, unless the firmware has been changed to DD-WRT or Open-WRT. Accessing an ownCloud server connect to a home network is problematic when we want to access the same server both from outside the home network and from within the home network at other times, e.g. using a laptop. We can easily configure to have a dynamic domain name using services such as DyDNS and port-forwarding. But once we enter that dynamic domain name into our ownCloud client, we will not be able to access the same server from within the home network.

My request is to add a feature in the client software to allow a secondary server address (for home local network) which will be triggered when (1) the primary server address is not working or (2) when the system detects through its IP address that it has connected to a designated local network.

Thank you.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@phil-davis
Copy link
Contributor

Just a comment about what can work on some home routers. You can add a host override in the DNS forwarder that is built-in to the home router, thus for example pointing mycloud.example.com to 192.168.1.42 (the local private IP of your cloud server). Then when at home your client receives 192.168.1.42 as the IP of the cloud server and when on the public internet you get the public IP.

Of course that facility is not always available on every home router, just mentioning this here for the benefit of readers looking for ways to achieve this home-and-away functionality.

@SamuAlfageme
Copy link
Contributor

These are some more detailed implementation ideas for #203

@we-sell-bags
Copy link

we-sell-bags commented Feb 7, 2017

Personally.... I would enable the Router with a VPN.
then pop open a VPN connection via DDNS, Not a direct file syncing connnection.

when you are inside your WAN you get access, when you are outside and require access you fire up the VPN.

Simply opening up a consumer grade 'firewall' on multiple ports is asking for it, because you backend listeners have to be ROCK SOLID.

It also has the advantage of ONLY allowing a sync if the VPN is connected, so you are not pulling data over incredibly expensive roaming networks.(unless you specifically allow it)

@michaelstingl
Copy link
Contributor

Please run dnsmasq somewhere in your home network and point to this host in your routers DNS settings.

Here you can find more information:
https://wiki.debian.org/HowTo/dnsmasq

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants