sebknzl Posted December 18, 2013 Report Share Posted December 18, 2013 (edited) Hello! Currently we can't "bind" the IP btsync listens to or rather advertises. In my experience, if a btsync-instance advertises a wrong IP, the instance may not be found quickly by other peers. This is especially annoying if it is supposed to be a "server"-instance. In my case, I have a vserver-instance and btsync thinks its IP is "127.0.0.2". DHT helps, but it's turned off by default. Please Devs, fix that! (Haven't looked, but I'm sure it's already on the Wishlist) I've hacked a workaround for Linux for now, see https://gist.github.com/sebknzl/8027609 -Seb Edited December 18, 2013 by sebknzl Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.