Damus
GHOST profile picture
GHOST
@GHOST

Freedom Maxi | Privacy Advocate

Author of @npub15qan37zr8fzk8qwdtq54ltpn46kfwyq7aesyl0pp6zzqwtruu8cqcap0lv

7816fb7da6d86e625e6ac613af53fbea3e8fcfc2

Relays (4)
  • wss://hist.nostr.land – read & write
  • wss://nostrcheck.me/relay – read & write
  • wss://relay.damus.io – read & write
  • wss://relay.primal.net – read & write

Recent Notes

GHOST profile picture
The Chicago Bears and the Miami Hurricanes are doing well in football? What decade are we in?
GHOST profile picture
- Enable VPN kill switch so it blocks all traffic when the tunnel is down
- Set the VPN as default route before network comes up (always on VPN)
- Disable OS fallback DNS and captive portal probes if possible
- Push DNS through the tunnel explicitly (VPN provided DNS or your own over the tunnel)
- Possibly overkill but useful for peace of mind. Block port 53 outside the tunnel with firewall rules

If DNS can’t reach anything unless the VPN interface is up, then it’s working.

I’ve covered this a couple of times but the confusion is making me think this is one of those times when I think I’m being clear but I’m actually not. I might have to write a guide just for this question.
GHOST profile picture
I don’t think you are hearing me. That test is telling you the status NOW. Not at connection. Leaks happen:

- During network join
- During captive portal checks
- During OS service startup
- Before the VPN hooks routing and DNS

By the time you’re connected and run this test, the damage may already be done.