Privacy

32506 readers

1014 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
Don't promote proprietary software
Try to keep things on topic
If you have a question, please try searching for previous discussions, maybe it has already been answered
Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
Be nice :)

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago

MODERATORS

VPN connections keep getting blocked (lemmy.ca)

submitted 1 day ago by hellfire103@lemmy.ca to c/privacy@lemmy.ml

17 comments fedilink hide all child comments

So, for privacy and security reasons, I use a VPN. This is normally Mullvad (with DAITA and quantum resistance enabled), but I have ProtonVPN, Windscribe, and Orbot handy in case something doesn't work.

However, lately I've noticed my connections being blocked. This is across three different ISPs: Sky, Virgin, and Wifinity. I have tried all three VPNs and Orbot, and I have tried several protocols (WireGuard, OpenVPN, IKEv2, Stealth, and of course SOCKS5) to no avail.

The logical solution would be to use a bridge in Orbot, but the button seems to have been removed. Also, by using Orbot, I will not be protected by my DNS.

I am currently using iOS, but my other machines run Linux and I will be getting a GrapheneOS phone in the near future.

Can anyone help?

you are viewing a single comment's thread
view the rest of the comments

[–] user224@lemmy.sdf.org 8 points 1 day ago

Other than DAITA, Quantum resistance may also be a problem. From experience, the key exchange needs near-perfect connection, otherwise it keeps failing.
This is further made into a problem by Android's private DNS handling. If it times out for long enough (seems like 10 seconds), then even after Mullvad finally connects, the DNS won't work.