Russia starts blocking VPN at the protocol (WireGuard, OpenVPN) levelsimple@lemm.ee to Technology@lemmy.world – 1068 points – 11 months agovpncentral.com175Post a CommentPreviewYou are viewing a single commentView all commentsShow the parent commentChinese firewall can detect it, AFAIKGfw 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.Wireguard through gfw worked fine when I tried it. The other client did have a static IP and static Port tho, that probably helped
Chinese firewall can detect it, AFAIKGfw 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.Wireguard through gfw worked fine when I tried it. The other client did have a static IP and static Port tho, that probably helped
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.
Wireguard through gfw worked fine when I tried it. The other client did have a static IP and static Port tho, that probably helped
Chinese firewall can detect it, AFAIK
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.
Wireguard through gfw worked fine when I tried it. The other client did have a static IP and static Port tho, that probably helped