Help Setting Up SOCKS5 Proxy on GL.iNet BE3600 (Slate7) Router – DNS and WebRTC Leak Issues

Routers VPN, DNS, Leaks
1

Hey everyone,

I’m trying to set up a SOCKS5 proxy on my GL.iNet BE3600 (Slate7) router to route traffic properly, but I’m running into some frustrating leaks that are undermining the whole point of using a proxy. I’ve been experimenting with Singbox and a couple of other proxy software options, but no matter what I do, it seems to tunnel my IP address successfully while still exposing my real DNS and causing WebRTC leaks. This basically defeats the purpose of anonymizing my connection.

Here’s a bit more detail on my setup:

  • Router: GL.iNet BE3600 (Slate7), running the latest firmware (version 4.8.1).

  • Proxy: SOCKS5 from a reliable provider (not a VPN, specifically SOCKS5 for selective routing).

  • Software tried: Singbox primarily, redsocks and like Shadowsocks or basic proxy configs via the router’s admin panel.

  • What happens: Traffic appears to go through the proxy IP when I check via sites like whatismyipaddress.com, but DNS queries leak my ISP’s DNS, and WebRTC tests (e.g., on browserleaks.com) show my real public IP.

I’ve double-checked the basic configs: proxy server IP/port, authentication, and enabling it for WAN or specific devices. But the DNS isn’t routing through the proxy, and WebRTC isn’t being blocked or masked.

My questions:

  • Is there a specific setting in the GL.iNet admin interface or Singbox config that I need to adjust to force DNS queries to route through the SOCKS5 proxy’s IP instead of leaking?

  • Could this be related to a firewall rule? Maybe I need to add or modify something in iptables, nftstable the router’s firewall to redirect DNS traffic (port 53) over the proxy?

  • Has anyone successfully set this up on the BE3600/Slate7? Any step-by-step tips, config snippets, or alternative software recommendations that handle DNS and WebRTC properly with SOCKS5?

I’d really appreciate any advice or troubleshooting steps – I’m not super advanced with networking, but I can follow detailed instructions. Thanks in advance for the help!

2

Hi, sorry to keep you waiting. Could I see your configuration, including the router and firewall settings? Additionally, I suggest you upgrade to the latest version and try again—we fixed some issues with TCP DNS not long ago. Besides, when it comes to preventing DNS leaks, choosing a VPN seems like a better option.

4

Well, I understand that VPN is the selling point of your router sometimes websites can detect you using a VPN, which literally defeats the purpose of me using the VPN. It's why sometimes it's best to opt for a Sock5. Services like Netflix, banking apps and even some social media can detect when you're using a VPN that alone in itself makes things frustrating and that is why i choose to use a proxy instead of a VPN. But Slate7 while a very solid router lacks proxy support by default and when you try to configure it and force DNS request to go through proxy the Internet stops working completely, and if you decide to use it without forcing the request to go through IP you get a massive WebRTC and DNS leak. It's like the DNS it's hard. I didn't wait that it can't be changed in the router, which is very frustrating because it's an OpenWRT router. I am using firmware version 4.8.3

Screenshot 2025-10-10 at 03.19.AM
Screenshot 2025-10-10 at 03.19.AM1410×1138 59.6 KB

5

Now our WireGuard VPN supports obfuscation, which can effectively prevent third-party software from analyzing your traffic. However, only the beta version has been released so far. Regarding the issue with the SOCKS proxy, we have made numerous modifications to dnsmasq to support the policy-based tunneling feature of the VPN, and I will follow up on this problem on my end.

1 Like
6

Thank you so much Zheng i really appreciate you. please let me know what you find so i can rerun my test again.

7

Please let me know your configuration so that I can reproduce your issue locally. Have you made any special configurations to the router or firewall?