I am very confused and this is the 2nd notice I have received. I am using a VPN (TrustZone) with uTorrent.
I’ve been reading articles but in all honesty I don’t understand how the copyright holder was able to identify my IP and what I should do to protect myself in the future. This is the context, “The copyright owner has identified the Internet Protocol (‘IP’) address associated with your Service account at the time as the source of the infringing works.”
Does the TrustZone VPN client have Leak Protection / Kill Switch settings in it? That’s what you want, so in case the VPN connection drops you won’t accidentally expose your normal non-VPN IP address.
If you’re receiving notices it sounds like maybe those aren’t enabled so you’re leaking whenever the VPN connection goes down.
Request IP: 65.49.8.116, Hurricane Electric (6939), United States (NA)
If you are using a proxy it seems to be an anonymous HTTP or a socks proxy.
Operating System: Windows
Same results for all tests.
Browser: Firefox
Same results for all tests.
Connection type: You are connected via Ethernet or modem and have made 10 hops.
Timezone Difference: The time zone of your browser settings and the time zone of your request IP location match.
DNS Request Source: We did get DNS requests from the following IPs:
69.252.228.135: Comcast Cable (7922), United States (NA) (Leak?)
74.125.80.77: Google (15169), United States (NA) (Leak?)
We received DNS requests from you via a DNS server from another AS (routable network) than your HTTP request. This could mean that your DNS requests are leaking
IPv6 Request Source: We were not able to detect an IPv6 request.
SSL traffic: 65.49.8.116
WebRTC IP Leak: We could not detect an IP via WebRTC.
Flash support: Your browser has Flash disabled.
WebGL support: WebGL is enabled.
SSL Setup Security: Probably Ok
Third party cookies: Supported
HTTP Request Leaks: We could not find any HTTP request type leaks.
Yes it does and yes it was enabled. I had already checked that. Near as I can tell, it’s not exactly a TrustZone problem but a torrent process problem where in my IP is exposed by the torrent software to something called the swarm. I think that means all people currently connected at a given time, place. I switched to ipVanish which provides a Socks5 proxy for torrenting. What I need to figure out now is whether that really does hide my actual IP. Do you happen to know how I can test for that?
Update: I signed up for ipVanish because it had specific information and directions for people like me (don’t know how, need simple straight forward instructions). Configured the torrent according to their directions and reran the tests above including the UDP/HTTP torrent additional tests.
Results the same except that now I can see in uTorrent that I’m using a proxy. What I’m concerned about are the apparent DNS leaks. Should I be worried and if so, what should I do to fix?
Near as I can tell, it’s not exactly a TrustZone problem but a torrent process problem where in my IP is exposed by the torrent software to something called the swarm.
A VPN connection is an entire encrypted connection, everything including torrents is tunneled through it. The torrent swarm(s) can only see your VPN provider’s IP address normally unless something else is going on.
I don’t know too much about the Trust.Zone configuration so can’t offer anything specific about them, though the VPN provider does seem reliable so it makes me think there’s something off in your specific configuration. Have you already tried reaching out to their support?
I switched to ipVanish which provides a Socks5 proxy
Proxy is less secure than VPN, I wouldn’t trust it personally since you’re now relying on the torrent client not to leak. There’s no such thing as a kill switch with a proxy. But some people just use the proxy so that’s your call.
What I need to figure out now is whether that really does hide my actual IP.
Looking into this some more, it does look like Trust.Zone does not privide their own DNS for the VPN connection.
I don’t follow how they offer DNS Leak protection if they don’t have their own DNS. Without offering DNS their entire VPN service leaks DNS to whichever DNS your main internet connection is using.
So in this instance you may as well use Google’s DNS to get around the issue (or some other DNS). The rest of Trust.Zone’s VPN services seem OK (far as I can tell).
Clearly I’m even more confused.
I’ve repeatedly run the suggested tests (https://ipleak.net/, https://www.doileak.com) and no leaks are showing using ipVanish. Yet, I had the same results when I was using TrustZone.
As far as the proxy, I start the VPN and have the proxy inside the torrent program at the same time. Is that a mistake? I thought maybe I was getting double protection. ipVanish does have a kill switch as well – though it’s not in the configuration/preferences. When my network experienced a problem, the kill switch kicked in, so it must be built in and not an option. Or so it seems.
OK. That would explain why I was detected when using TrustZone. Thank you. I told them I want to cancel and they are giving me grief insisting that if I followed their directions (which I did repeatedly, including their tests), there wouldn’t be any problems. Well, the only thing they had in their instructions was to use the Google DNS servers but another article I read talked about transparent DNS proxies (DNS leak test) and near as I can tell, my iSP uses this technology and can trap Google DNS queries. At least I think so.