Skip to content
selective vpn bittorrent peer listening port closed
Got a problem with Viscosity or need help? Ask here!
hi,
i have been all over the web and have not found solution to my quandary. so i'm posting ...
i am using viscosity to connect to ipredator ipn service and running the transmission bittorrent client.
in the standard set up ipredator forces all traffic over vpn, even if you un-tick option in viscosity client. they seem to do this with routes. here is what my routing tables looks like after connecting to vpn :
... almost. the peer listening port, which was open with 0/1 route in place, is now closed. and this ends up excluding peers and all the rest.
i have no idea why it has stopped working, and this is the final blocking point for my 'selective' vpn situation. any help or advice would be greatly appreciated.
- scott
i have been all over the web and have not found solution to my quandary. so i'm posting ...
i am using viscosity to connect to ipredator ipn service and running the transmission bittorrent client.
in the standard set up ipredator forces all traffic over vpn, even if you un-tick option in viscosity client. they seem to do this with routes. here is what my routing tables looks like after connecting to vpn :
Code: Select all
i suspect that the route 0/1 is forcing all traffic over ipredator. so i deleted the 0/1 route and left the others as-is. i then bound transmission to the ip address provided by ipredator. after declaring the torrent sites and their trackers in viscosity network pane as using the vpn gateway. all is good ...Internet:
Destination Gateway Flags Refs Use Netif Expire
0/1 anon-49-1.vpn.ipre UGSc 5 0 tun0
default 192.168.0.1 UGSc 6 390 en0
46.246.49/24 anon-49-31.vpn.ipr UGSc 8 0 tun0
46.246.49.2/32 192.168.0.1 UGSc 1 0 en0
anon-49-31.vpn.ipr anon-49-31.vpn.ipr UH 1 0 tun0
127 localhost UCS 2 22710 lo0
localhost localhost UH 6 7554000 lo0
128.0/1 anon-49-1.vpn.ipre UGSc 1 0 tun0
169.254 link#4 UCS 1 0 en0
valinor.local 0:1a:62:3:b7:fd UHLSWi 0 57 en0
192.168.0 link#4 UCS 8 0 en0
192.168.0.1 0:24:d4:ac:e2:44 UHLWIir 6 45652 en0 1195
192.168.0.10 0:23:df:a7:66:b4 UHLWIi 2 3772537 en0 855
192.168.0.14 0:1a:62:3:b7:fd UHLWIi 1 221905110 en0 1097
192.168.0.15 localhost UHS 0 132134 lo0
... almost. the peer listening port, which was open with 0/1 route in place, is now closed. and this ends up excluding peers and all the rest.
i have no idea why it has stopped working, and this is the final blocking point for my 'selective' vpn situation. any help or advice would be greatly appreciated.
- scott
Hi Scott,
Your VPN Provider would be pushing out the "redirect-gateway" command, which overrides Viscosity's local "Send all traffic over VPN connection" option. You're right in that it's adding the 0/1 route, however the 128.0/1 route is also part of the routing used to redirect all traffic over the VPN connection. For more information see the "def1" option of the "--redirect-gateway" command in the OpenVPN Man Page.
Only deleting the 0/1 route means you're going to see some IPs still going through the VPN. You'll need to remove both to override it. You can also find some other techniques in this forum post: http://www.sparklabs.com/forum/viewtopi ... 1049#p1049
However that said, I don't believe Transmission is capable of doing what you want here. I could be wrong, however I believe it's IP binding option under Mac OS X will just bind the socket to relevant IP address: actual network traffic will still flow following your system routing table. So binding to your VPN IP address may still result in traffic flowing over your normal network connection, or not at all.
Cheers,
James
Your VPN Provider would be pushing out the "redirect-gateway" command, which overrides Viscosity's local "Send all traffic over VPN connection" option. You're right in that it's adding the 0/1 route, however the 128.0/1 route is also part of the routing used to redirect all traffic over the VPN connection. For more information see the "def1" option of the "--redirect-gateway" command in the OpenVPN Man Page.
Only deleting the 0/1 route means you're going to see some IPs still going through the VPN. You'll need to remove both to override it. You can also find some other techniques in this forum post: http://www.sparklabs.com/forum/viewtopi ... 1049#p1049
However that said, I don't believe Transmission is capable of doing what you want here. I could be wrong, however I believe it's IP binding option under Mac OS X will just bind the socket to relevant IP address: actual network traffic will still flow following your system routing table. So binding to your VPN IP address may still result in traffic flowing over your normal network connection, or not at all.
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
2 posts
Page 1 of 1