Sign in to follow this  
jemxpat

Forcing Btsync To Use One (Non Default) Network Interface

Recommended Posts

I am using 1.3.109 on linux with config file, no GUI. The linux machine has two external networks, one a public IP and the other a VPN without a default route, so that traffic on the VPN network is exchanged only with other hosts on the VPN.

 

When btsync starts, it logs a message of the form:

 

Using IP address 123.45.67.89

 

String firewals on the public address kill most btsync traffic on that interface. I would like btsync to consider the private, VPN interface as its primary address, and set up all listeners there. Especially, LAN discovery of peers (enabled via "search_lan" : true ) should happen on the VPN interface.

 

Is there any way to either force or trick btsync into binding to the interface of my chosing? Can this be done with version 1.4, an upgrade I have declined so far.

 

-jem

Share this post


Link to post
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this