Traffic splitting: How can I route ONLY torrenting traffic through Eddie on Mac OSX?

[craftadvisory 0]

Traffic splitting: How can I route ONLY torrenting traffic through Eddie on Mac OSX? Is this even a smart thing to do? I want to protect myself from potential repercussions of using private trackers but I always don't want to call un necessary scrutiny to myself by hiding my browser activity. Am i misguided in my thinking? Should I just run all my traffic through airvpn tunnel?

[NaDre 157]

Traffic splitting: How can I route ONLY torrenting traffic through Eddie on Mac OSX? Is this even a smart thing to do? I want to protect myself from potential repercussions of using private trackers but I always don't want to call un necessary scrutiny to myself by hiding my browser activity. Am i misguided in my thinking? Should I just run all my traffic through airvpn tunnel?

 

I think the only reason for not using the VPN for everything is if you find it inconvenient. For example sites blocked to you that would not be on your normal IP (or just harassing you every time they see your IP change), or if you perceive delays due to latency, or issues that your ISP has with peering to the AirVPN server you choose.

 

If you decide you want to split traffic, I have written fairly detailed explanations in this forum on how to do it for Windows and Linux. But I do not have a  Mac, and so don't want to give anyone the expectation that I can help someone trouble-shoot this.

 

But having made that proviso that I cannot provide detailed assistance, the usual thing is:

 

1) to set up your routing so that the VPN is not used by default, but does allow "source address routing"

 

2 ) bind your torrent client to the VPN interface

 

For 1), I mentioned a way to do source address routing for BSD (and Mac is a version of BSD) here:

 

https://airvpn.org/topic/21340-airvpn-tor-obfs4-bridges/?do=findComment&comment=58426

 

I think the the third option may work for Mac:

...

3) Using the "pf" firewall:

 

https://www.freebsd.org/cgi/man.cgi?query=pfctl

 

It seems that MacOS does have this. See:

 

https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man5/pf.conf.5.html

https://en.wikipedia.org/wiki/PF_(firewall)

https://discussions.apple.com/thread/6720409

 

It is more effort with "pfctl". There is a single set of input statements that get reloaded using pfctl. I included a statement like this:

pass out route-to (em0 192.168.88.1) from 192.168.88.124

It seems that the syntax of rules for pf has changed a lot in recent releases. So the syntax above may not be what is needed for MacOS.

...

 

 

If you are using uTorrent, I suspect that telling it to bind to the VPN interface is done exactly as for uTorrent in Windows. For an example of that have a look at this Windows guide:

 

https://airvpn.org/topic/9491-guide-to-setting-up-vpn-just-for-torrenting-on-windows/?p=10317

 

If you are using some other client, you will have to find out where (if anywhere) in its set up GUI you can specify the IP interface to bind to.

 

I am afraid that is about all I have to offer.

[Grape Jewce 4]

If you have the resources (from your PC), the easiest and convenient way would be setting up a VM (Virtual Machine). You can also use the network lock feature in it and basically use that VM just for whatever you want to go through the VPN.