sabreW4K3@lazysoci.al to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.comEnglish · 2 days agoGoogle Receives Piracy Shield Orders to Block Pirate Sites in Public DNS * TorrentFreaktorrentfreak.comexternal-linkmessage-square23linkfedilinkarrow-up190arrow-down10
arrow-up190arrow-down1external-linkGoogle Receives Piracy Shield Orders to Block Pirate Sites in Public DNS * TorrentFreaktorrentfreak.comsabreW4K3@lazysoci.al to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.comEnglish · 2 days agomessage-square23linkfedilink
minus-squarereluctant_squidd@lemmy.calinkfedilinkEnglisharrow-up4·1 day agoWhat I suggest/have done: Rent a cheap VPS in a non-five eyes country that comes with a static ipv4. SSH on random port with certificate auth only. No root, no password auth. setup WireGuard server with random port. firewall block all incoming except ssh and WireGuard port at first. set home server to connect via wireguard as sole client to VPS. individually add any ports you want to go to the home server from the internet as NAT forwarded ports. Basically WWW -> VPS -> Home. have a separate WireGuard VPN for outgoing from the home server. profit? But it’s crazy complicated. At least it was for me. Not for the faint hearted imo.
What I suggest/have done:
Rent a cheap VPS in a non-five eyes country that comes with a static ipv4.
SSH on random port with certificate auth only. No root, no password auth.
setup WireGuard server with random port.
firewall block all incoming except ssh and WireGuard port at first.
set home server to connect via wireguard as sole client to VPS.
individually add any ports you want to go to the home server from the internet as NAT forwarded ports. Basically WWW -> VPS -> Home.
have a separate WireGuard VPN for outgoing from the home server.
profit?
But it’s crazy complicated. At least it was for me. Not for the faint hearted imo.