coewar

Members
  • Posts

    57
  • Joined

  • Last visited

Everything posted by coewar

  1. Opened new post to be more specific on this topic. I have servers that are already interconnected via SSH tunnels and I can tunnel anything TCP without a problem and it works great. Since BTSync uses UDP, not TCP, I had to figure out how to tunnel UDP. Well, I got the UDP tunneling working by using Zebedee which is wrapping the UDP inside TCP. I made some tests and verified the communication. I also am dumping the data and can see some BTSync data arriving. However, somehow BTSync just doesn't care. I configure to a specific port for BTSync to use, but wonder if it needs something besides that custom port. I probably won't bother continuing this as it seems to be more complicated than it's worth. I'm forced to open FW UDP ports. I know that's better performance, but I was less concerned about that. This was for experimentation but needed to tunnel UDP for different purpose anyway so thought to include BTSync in that test. Agonizing details: To outline, here's what I have, making up port numbers: ServerA and ClientA are the same box just either acting as a server or as a Client. ServerB and ClientB are another box, same story. ClientA BTSync -> 127.0.0.2 : 2001 ClientA Zebedee -> 127.0.0.1 2002 ClientA SSH tunnel -> ServerB : 22 -> 127.0.0.1 : 2000 ServerB Zebedee -> 127.0.0.2 : 3000 ServerB BTSync ClientB BTSync -> 127.0.0.2 : 2001 ClientB Zebedee -> 127.0.0.1 2002 ClientB SSH tunnel -> ServerA : 22 -> 127.0.0.1 : 2000 ServerA Zebedee -> 127.0.0.2 : 3000 ServerA BTSync ServerA has SSH service on port 22 ServerA has Zebedee service listening in TCP/UDP mode on port 2000. ServerA has BTSync listening on UDP 3000. ServerB has SSH service on port 22 ServerB has Zebedee service listening in TCP/UDP mode on port 2000. ServerB has BTSync listening on UDP 3000. Starting at the basics, both servers have SSH connections to each other. Both SSH connections have client to server TCP tunnel where locally 127.0.0.1 : 2002 tunnels to the other server's 127.0.0.1 : 2000 which is the Zebedee service. Then, each server's Zebedee service is configured to accept connections on port 2000, and allows TCP and UDP redirection to 127.0.0.2 : 3000 which is the BTSync service. It seemed that if I used just 127.0.0.1 in BTSync, it almost fooled itself in thinking it's syncing with itself. But by using something like 127.0.0.2, or .3, etc it seemed to at least try to make the connections and data went.. but again somehow it did not care or maybe somehow it did not reach the other side all the way to BTSync.
  2. ahh.. there it is. Thanks. It was actually under Roaming in my setup. Not that it does much good with this binary data file right now. Why AppData? Hoping for the day it's just simply stored in a text file with the folder. No reason to buy into the Microsoft Windows complex way to store settings when the simple Linux way of "it's just right there in a text file" would work perfectly fine in Windows also.
  3. Looking at that actually. Thanks. But back to the main part of my question... locating platform independent config files in the folders being synchronized to contain 100% of the configuration. ??
  4. Actually, I happen to be researching right now how to tunnel UDP as we have another need for this. Just found this loaded article on that; http://wiki.networksecuritytoolkit.org/nstwiki/index.php/Tunnelling_UDP_Traffic_Through_An_SSH_Connection However... BitTorrent sync has this option "lan_use_tcp" which you can set to True.. so .. that really should do the trick, if it did what it says it's doing. Because by adding the host of "127.0.0.1:xxx" it really should be trying to use LAN I guess.. and hence use TCP.
  5. I plan to use BitTorrent Sync for these purposes: - Backups of family's documents on multiple computers in the home. All sync with a folder on a main server that then utilizes a different backup solution. And using Dropbox was not so hot as it kind of has folder restrictions that did not work for me. - Keeping an active backup of some servers in one data center to another and another. Server is holding some bunch of files we use plus also Git repositories. - Staring changes of software to production servers. We can centralize each server if we wanted to in a "pushing server" which would be the same server that is being backed up in the previous point. - Keeping active DR backup of another server when there is no current and well defined process yet.
  6. I know the Windows version is lagging.. but where are any of the settings stored now? There is nothing in the Program Files folder other than BTSync.exe. There is nothing useful in the folders' themselves. .SyncID has some binary crap (is that the config?) and then there is just .SyncIgnore and .SyncTrash folder. I can not find any of the settings in the Registry.
  7. Using Git as an example, on Linux or Windows, in the .git folder there is bunch of cool stuff and all the configuration and everything is there. Since BTsync has this .SyncTrash folder and also a couple of other files in the folder's root (on Windows anyway), it would make sense to put 100% of the configuration of a folder in some .BitSync folder or something like that. The configuration to include in there would be the Remotes. What I would like, is to override the hosts to use like 127.0.0.1 and port xxxx as I want to channel it through an SSH tunnel in certain situations where the FW rules are already in place and we have our own security credentials, etc. Using the Windows GUI "Use predefined hosts" is not working at all.. it is not attempting to make a connection to the local IP/port I specify that I've created a tunnel for. But anyway, great product idea.. I've actually been working on my own version just a few weeks ago.. using a combination of Git and WinSCP. Your solution has a much nicer "package" and handles the large files better of course.