Transmission OpenVPN Guide

[jmaldonado91]

(Nov 09, 2015, 05:24 PM)Mike Wrote: OK so the top route which is the VPN gateway is taking precedence - this is generally what you want but there are some cases where it will be undesirable.

Here are two ways to fix this behavior:

Use another wireless router that support dynamic DNS services that is outside the VPN

Use firewall rules (ip tables) to route only torrent traffic through the VPN - there is a guide in progress for this but I have not tested it with this specific use case

I had hoped you could use curl to specify a gateway but it doesn't seem possible (makes sense since routing is a layer 3 thing).

The next thing I would try is something like this, I would help test but I'm having admin issues with the main site. Do let me know if you resolve this any time soon and I'll try and help when these admin issues are resolved.

I did some research on routing torrent traffic only and came across this http://www.ichimonji10.name/blog/1/
The author mentions opening ports for peers to send traffic and a port for DHT which needs to be done by VPN server, but I don't think this is necessary?

My plan is to follow the routing guide part for this. I would test something but I'm not home till the end of the week, and it just so happens that my Pi has either shutdown or public IP has changed

I've ordered an Odroid C+ for another project so if this doesn't work, I can just run the no-ip client there. It would be nice to get this working though.

[Mike]

Very curious if you get this working. It should definitely be possible to create another routing table (like this guy has) and then use iptables to create rules for routing traffic for specific destination ports through the new routing table. Maybe @tragidy has some ideas on how to do this.

[jmaldonado91]

(Nov 14, 2015, 05:50 PM)Mike Wrote: Very curious if you get this working. It should definitely be possible to create another routing table (like this guy has) and then use iptables to create rules for routing traffic for specific destination ports through the new routing table. Maybe @tragidy has some ideas on how to do this.

Sorry for not keeping you updated, I've been very busy with work the past two weeks.

I didn't give the IP routing tables a try because I managed to dig up another router which just so happened to be compatible with no-ip.com. So I've set that up to update no-ip and kept the VPN running on my pi.