this post was submitted on 10 Aug 2023
1073 points (98.2% liked)

Technology

59414 readers
3769 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] masterairmagic@sh.itjust.works 5 points 1 year ago (3 children)

Can this actually work? If you run Wireguard on a non-default port, is it possible to tell that it's wireguard?

[–] dr_robot@kbin.social 21 points 1 year ago

Most open source vpn protocols, afaik, do not obfuscate what they are, because they're not designed to work in the presence of a hostile operator. They only encrypt the user data. That is, they will carry information in their header that they are such and such vpn protocol, but the data payload will be encrypted.

You can open up wireshark and see for yourself. Wireshark can very easily recognize and even filter wireguard packets regardless of port number. I've used it to debug my firewall setups.

In the past when I needed a VPN in such a situation, I had to resort to a paid option where the VPN provider had their own protocol which did try to obfuscate the nature of the protocol.

[–] AES@lemmy.ronsmans.eu 13 points 1 year ago* (last edited 1 year ago)

Yes ofc they can. The Wireguard protocol is not designed to be hidden.

Interesting read: https://www.ntkernel.com/how-to-bypass-egypts-wireguard-ban/

[–] mruczek@lemm.ee 12 points 1 year ago (2 children)

Chinese firewall can detect it, AFAIK

[–] InverseParallax@lemmy.world 3 points 1 year ago

Gfw is mostly picky about anything udp or where both ports are unknown. Also if the known port (server) isn't from a licensed block.

Basically there are heuristics that lead to either a reset, a temp block, or a perm block, but it seems to vary from time to time a lot.

[–] Spiritreader@lemmy.world 2 points 1 year ago

Wireguard through gfw worked fine when I tried it. The other client did have a static IP and static Port tho, that probably helped