Opened 9 years ago

Closed 9 years ago

Last modified 8 years ago

#5593 closed Enhancement (duplicate)

Binding to IP

Reported by: mathewparet Owned by:
Priority: High Milestone: None Set
Component: Transmission Version: 2.82
Severity: Normal Keywords:


This is rather a feature request than a bug.

I just saw Vaze and it has an awsome feature that enables it to be bound to a network interface / IP that can be configured to the VPN interface. This way when my VPN connection fails, Vaze automatically blocks itself. Making torrenting more secure.

It would be nice to have the same feature in Transmission. Except for this binding to network feature, I don't like Vaze.

Change History (3)

comment:1 Changed 9 years ago by livings124

  • Resolution set to duplicate
  • Status changed from new to closed

I believe this is a duplicate/related to #776.

comment:2 follow-up: Changed 9 years ago by x190

Related to #2313.

@mathewparet: You already have the ability to bind to a specific address.

comment:3 in reply to: ↑ 2 Changed 9 years ago by mathewparet

Replying to x190:

Related to #2313.

@mathewparet: You already have the ability to bind to a specific address.

Actually I need to bind to an interface rather than an IP. I am using a VPN and the IP keeps changing each time I connect to the VPN. Transmission provides an option to bind to IP but since the VPN IP keeps changing, it isn't useful for my need (to download only via VPN). So I am looking for an option to bind to an interface.

EG. If my VPN is on eth1, then, transmission should be able to bind to eth1 so that whatever IP eth1 has will be used for binding.

Advantages would be:

  1. Since it would bind to the interface and not ip, it doesn't matter if VPN IP changes
  2. If the VPN goes down, transmission would go offline along with it so it wont download using my actual ip, so my actual IP stays hidden.
Note: See TracTickets for help on using tickets.