Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

55872 readers

631 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others

Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):

💰 Please help cover server costs.


Ko-fi	Liberapay

founded 2 years ago

MODERATORS

[email protected]

Two quick questions (lemmy.ml)

submitted 1 day ago by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

I use Surfshark, and the protocol options I have are: Open VPN TCP Open VPN UDP WireGuard

Which should I be using?

Also I have QbitTorrent (Win11), and was curious if the version mattered at all

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

[–] [email protected] 2 points 1 day ago (1 children)

If you do opt for OpenVPN, I believe UDP is generally better for performance. TCP support is mainly there for scenarios where UDP is blocked, or on dodgy connections where TCP's more proactive handling of dropped packets can reduce the time before a lost packet gets retransmitted.

It's great that you brought up TCP vs UDP. And you are totally right about TCP being a bit slower, higher overhead, but it's there for situations where UDP is blocked.

I've used my VPN at all sorts of hotels, coffeeshops, etc. I'd say 1 in 10 places block UDP (or more likely don't properly route UDP). If you're using a SIM card, you won't have any issues.

However, it's worth mentioning that WireGuard is UDP only. There are some hacks/workarounds to have it work over TCP, but then you're going to need to find WireGuard clients that also supports these hacks (which is possible on computers, but harder on cellphones/tablets).

If you want something that "just works" under all conditions, then you're looking at OpenVPN. Bonus, if you want to marginally improve the chance that everything just works, even in the most restrictive places (like hotel wifi), have your VPN used port 443 for TCP and 53 for UDP. These are the most heavily used ports for web and DNS. Meaning you VPN traffic will just "blend in" with normal internet noise (disclaimer: yes, deep packet inspection exists, but rustic hotel wifi's aren't going to be using it ;)

[–] CountVon 2 points 20 hours ago

However, it’s worth mentioning that WireGuard is UDP only.

That's a very good point, which I completely overlooked.

If you want something that “just works” under all conditions, then you’re looking at OpenVPN. Bonus, if you want to marginally improve the chance that everything just works, even in the most restrictive places (like hotel wifi), have your VPN used port 443 for TCP and 53 for UDP. These are the most heavily used ports for web and DNS. Meaning you VPN traffic will just “blend in” with normal internet noise (disclaimer: yes, deep packet inspection exists, but rustic hotel wifi’s aren’t going to be using it ;)

Also good advice. In my case the VPN runs on my home server, there are no UDP restrictions of any kind on my home network and WireGuard is great in that scenario. For a mobile VPN solution where the network is not under your control and could be locked down in any number of ways, you're definitely right that OpenVPN will be much more reliable when configured as you suggest.