I have a bug where two BitTorrent Sync clients can't sync with each other in cloned VMs. Steps to reproduce: 1. Install Bittorrent Sync in a Windows 7 (probably any Windows version, have only tested in Win7) virtual machine. 2. Set BT sync to sync a folder with a new secret. (3. Make sure it can sync that folder with another machine on the network.) - Not needed other than to verify that the first two steps were correctly executed. 4. Make sure no other machines are using the same secret as the virtual machine. 5. Clone the VM and start both copies. - At this point the only two machines using the secret from step 2 should be these machines. Note 1: Setting a different device name in one of the VMs does NOT solve the problem. Note 2: Copying the folder "C:\Users\<USERNAME>\AppData\Roaming\BitTorrent Sync" from one Windows installation where BTSync is installed to another might also create the same issue, I can't verify this at the moment though. Result: The two VMs containing identical copies of "C:\Users\<USERNAME>\AppData\Roaming\BitTorrent Sync" won't be able to sync with each other. Temporary workarounds: Remove the folder "C:\Users\<USERNAME>\AppData\Roaming\BitTorrent Sync" in one of the VMs and set up BTSync manually with the secret from step 2. They now sync properly. -- OR -- Run a copy of BTSync (not a clone) on a third machine and let all syncing go through this machine, not efficient and might cause issues I have not yet seen since this third copy seems to think it is only talking to ONE client as is made obvious if changing the device name on one of the VMs. Under devices on this third machine the name will then keep changing between the two names. My thoughts: It seems to me there is some unique id which is generated when the configuration is first made and since that remains part of the VM clone the two instances can't communicate. Couldn't this be made to be recalculated on program start based on some unique identifier of the system? Eg. the MAC of the first NIC or possibly just use the change of the MAC as an indicator to recalculate the id in order to avoid this issue? If btsync could be configured by loading a config file in Windows the workaround could be automated, but as it is now this is not possible to automate. If you need more details please just ask.
