![]() ![]() SFTP worked on one site through a tunnel (again, the sites are not consistent and IT doesn't always have the time to accomodate our needs). We had this problem when we tried using FTP, since it assigns random ports for data transfer. ![]() I see the option for adding known hosts in the folder settings, which lets me specify a host and port which would let me connect to port 80, and I'm going to test this out next time I get to the schools. I'm pretty certain that UPnP is not going to work given the strength of the IT in the schools. I've read a few posts in this forum about IT blocking "bittorrent-like" traffic, and requiring ports to be opened. One school district blocks everything but HTTP, and is even blocking SSH tunneling over HTTP (using Apache's mod_proxy / HTTP connect method). The networks at the schools are often extremely limited for obvious reasons. 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. This should work since git has an HTTP protocol for pulling. One of my alternative deployment solutions is using git to deploy the application (like Heroku uses). 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. One can do the external download and the peers can sync from that "master" and from each other. 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. In the best case the school is "wide open." 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?īasically in the worst case all data needs to be transferred over HTTP protocol, and *not* using HTTP connect (e.g., Apache's mod_proxy ). ![]() We need a synchronization solution that will work given these restrictions. 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.Īt some sites we do not have the ability to open firewall ports. Some locations allow FTP, SSH, SFTP, HTTP, and others are locked down to just HTTP. 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. The schools have varying and inconsistent firewall rules, so the sync isn't happening at some locations. 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). I work for a small research company that makes educational software/games, and we've got a deployment of 50 computers in 10+ schools. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |