Flatland_Spider wrote:The main problem is making a connection between your parent's network and your network. I'm assuming they are two physically separate areas.
Flatland_Spider wrote:This can be worked around by setting up some sort of VPN tunnel between the two routers. This is the simplest way, and it gives you the most options. With a VPN, it would be a route entry on the router.
You could go with SSH tunnels, but things get messy if the clients are Windows due to Windows not having most of the needed tools to really take advantage of it.
Flatland_Spider wrote:The next problem is throughput, as Flying Fox mentioned.
Upstream bandwidth is a problem. Cox may not throttle like some, but they aren't going to prioritize outbound traffic either. They've also started nagging people about reaching usage caps, so they may, or may not, start clamping down on "excessive usage" even though they don't mention usage caps in any of their advertising.
Flatland_Spider wrote:Finally, dynamic IPs and firewalls.
Unless you're paying for a business class line, you're going to have a dynamic IP, many ports will be filtered, and this would be in violation of the ToS. None of these are really problems, but they will make things harder.
bthylafh wrote:Guide to install Crashplan on FreeNAS:
bthylafh wrote:Maybe you could set up Owncloud on your server and install the client on your parents' computers.
njenabnit wrote:bthylafh wrote:Maybe you could set up Owncloud on your server and install the client on your parents' computers.
This is probably my leading option right now. It looks like a pretty neat tool! Do you have any experience with it that you could speak to? I would assume that once I get my port forwarding setup, it is open to WAN devices for connecting as well (such as my phone at work, my parent's desktop on their network, etc)?
Users browsing this forum: MSNbot Media and 4 guests