VPN location claims don't match real traffic exits
1–10 of 333 posts
Re: VPN location claims don't match real traffic exits
#2While exits matter to avoid countries with a nation-wide firewall, the geoip industry is a scourge.
If an ISP wants to help their users avoid geoblocking via https://www.rfc-editor.org/rfc/rfc8805.html more power to them.
Re: VPN location claims don't match real traffic exits
#3While exits matter to avoid countries with a nation-wide firewall, the geoip industry is a scourge. If an ISP wants to help their users avoid geoblocking via https://www.rfc-editor.org/rfc/rfc8805.html more power to them.
With CGNAT becoming more widespread, formats like this might need expansion to include location data for ports. Ie. Port 10,000-20,000 are consumers in New york, port numbers 20000-30000 are in Boston, etc.
Re: VPN location claims don't match real traffic exits
#4Cool, even our privacy protection is fraught with scammers and liars.
Re: VPN location claims don't match real traffic exits
#5Cool, even our privacy protection is fraught with scammers and liars.
well to be fair it's not always important to have the server at the geoip since a lot of the time you can measure the real latency of a user behind an ip address anyway.
the only important bit is that it is made clear whenever a given country falls under some category that allows things such as traffic analysis and cataloging.
it's actually often times preferrable to lie about the server location for lower latency access geo-blocked content, particulary when accessing US geo-restricted content in europe.
if you want true privacy you have to use special tools that not only obfuscate the true origin, but also bounce your traffic around (which most of these vpns provide as an option)
Re: VPN location claims don't match real traffic exits
#6I am not sure that I really understand what they did. I am also missing some major VPNs in the list.
I currently use AirVPN but this has something to do with my use case and pricing.
Why do you want to use a VPN?
- Privacy
- Anonymity (hint: don't!)
- unblock geolocation
- torrents
- GFC
The last point is the hardest.
Re: VPN location claims don't match real traffic exits
#7While exits matter to avoid countries with a nation-wide firewall, the geoip industry is a scourge. If an ISP wants to help their users avoid geoblocking via https://www.rfc-editor.org/rfc/rfc8805.html more power to them.
Can really spot someone who has never had to deal with OFAC with a comment like this. Even if I don't necessarily agree with the concept, or who is actually being blocked, my business is dead in the water if I'm a) sent to prison or b) fined out of existence.
Geographic IP information is one of our best tools to defend against those outcomes, and if anything it should be better.
Re: VPN location claims don't match real traffic exits
#8Mullvad is the only VPN I will ever trust. Yet again they ace the test.
Re: VPN location claims don't match real traffic exits
#9While exits matter to avoid countries with a nation-wide firewall, the geoip industry is a scourge. If an ISP wants to help their users avoid geoblocking via https://www.rfc-editor.org/rfc/rfc8805.html more power to them.
With CGNAT becoming more widespread, formats like this might need expansion to include location data for ports. Ie. Port 10,000-20,000 are consumers in New york, port numbers 20000-30000 are in Boston, etc.
Do you have actual evidence of this? What ASN operates this way?
Re: VPN location claims don't match real traffic exits
#10Mullvad is the only VPN I will ever trust. Yet again they ace the test.
Not sure why you've been downvoted. Somebody protecting their business?