Search the Community
Showing results for tags 'tunnel'.
Currently, when sync runs between two hosts at different locations on our WAN, the traffic is pushed through our IPSEC tunnels saturating the connection and the transfer speed is significantly slowed. Is there a firewall rule I can put in place that will make this traffic traverse the internet instead of going over these links?
I work for a small research company that makes educational software/games, and we've got a deployment of 50 computers in 10+ schools. We're currently synchronizing our application and media content from our server to the schools, and our log files from the schools to our server using SyncBack (FTP, yes I know -- without the S, no need to lecture). The schools have varying and inconsistent firewall rules, so the sync isn't happening at some locations. I know the limitations of the networks and why the transfers aren't working, so I'm not asking how to get through the firewall limitations This question is more to determine if btsync can get through strict firewall rules. Some locations allow FTP, SSH, SFTP, HTTP, and others are locked down to just HTTP. I've tried using WinSCP instead of SyncBack and tunneling SSH over HTTP using Aache mod_proxy, but even this is detected at some sites as a malicious proxy attack. At some sites we do not have the ability to open firewall ports. We need a synchronization solution that will work given these restrictions. Is btsync capable of handling this scenario? What ports does btsync use, what protocols for establishing the network (peer detection) and what protocol and ports for data transfer? Basically in the worst case all data needs to be transferred over HTTP protocol, and *not* using HTTP connect (e.g., Apache's mod_proxy ). In the best case the school is "wide open." I think btsync will work great for us, as it will limit the external bandwidth since not all 10 computers at each site will need to download the application updates. One can do the external download and the peers can sync from that "master" and from each other. In the worst case scenario that the school is completely shut off from the world, we could upgrade just by stopping by with an updated laptop and btsync would propagate all the changes to the peers on the LAN. I'd like to avoid that if possible. Thanks in advance! cm p.s. One of my alternative deployment solutions is using git to deploy the application (like Heroku uses). This should work since git has an HTTP protocol for pulling. The downsides are that we have a *lot* of data in our application/media and don't need/want to store the version history/deltas (in my tests the initial repo was about 1.8x as large as the folder hierarchy); and all the clients would have to pull all the changes, hogging network bandwidth.