{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigv4ke4cyb2ly4knzc7exgsozg47xaszi3ht7q3t3dd6vzqy6gdfu",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mlcpxmpbdvl2"
  },
  "path": "/t/glinet-services-leak-ip/37721#post_1",
  "publishedAt": "2026-05-08T01:17:25.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "GLiNet’s Firmware 4.9 is in beta, but this occurs on 4.8 as well.\n\nWhen you create a VPN tunnel through Wireguard, even with Enhanced Kill Switch and the option to specifically “Force GLiNet Services to use the VPN”, this doesn’t appear to be the case for at least the following services:\n\ncloudflare\n\ntime.cloudflare\n\ngl-inet\n\nfw.gl-inet\n\nfirmware-api.gl-inet\n\nany domain you use nslookup to test\n\nThese are registered as being accessed by your true IP, despite the Wireguard connection. Any on-device Wireguard configuration successfully cloaks the IP. The router-based configuration as deployed by Gl-inet seemingly does not.\n\nPreviously I monitored outgoing connections or DNS lookups through anonymized logs. Now switching that off, I see it’s detecting my true IP, which I always want to hide.\n\nCould anyone verify the same? Or is this a non-issue?\n\nMy DNS requests are being done over QUIC to nextdns, it was their logs that provided the IP leak.",
  "title": "GLiNet Services Leak IP?"
}