Help: I Want to Route All LAN Traffic Through a SOCKS5 Proxy on My GL.iNet Slate 7 Router (GL-BE3600)

Installing and Using OpenWrt Network and Wireless Configuration
1

Hi everyone,

I’m trying to route all internet traffic from all devices on my LAN through a SOCKS5 proxy using my router. I’m using a GL.iNet GL-BE3600 router running OpenWRT 23.05-SNAPSHOT. The router’s LAN IP is 192.168.8.1 and the LAN subnet is 192.168.8.0/24.

:wrench: What I Want to Achieve:

I want all LAN traffic (both TCP and UDP) to go through a remote SOCKS5 proxy (hosted externally), so every connected device uses that proxy without needing to install or configure anything on the devices themselves.

:brick: My SOCKS5 Proxy Details:

  • Type: SOCKS5
  • Host: [MY_PROXY_HOST]
  • Port: [MY_PROXY_PORT]
  • Username: [MY_USERNAME]
  • Password: [MY_PASSWORD]

(I can share actual credentials privately if needed for debugging.)

:test_tube: What I’ve Tried So Far:

  • I factory reset the router to clear all old configs.
  • I looked into sing-box, TPROXY, and nftables, but realized that SOCKS5 doesn’t support transparent proxying by default.
  • I read that tools like redsocks2 are needed to make this work, but I couldn’t find a working package for OpenWRT on my BE3600.
  • I want a clean setup from scratch, without any of my past Shadowsocks configs interfering.

:red_question_mark: What I Need Help With:

  • How can I transparently redirect all LAN traffic to my SOCKS5 proxy on this router?
  • What’s the recommended setup or package I should install for this on OpenWRT?
  • If I need redsocks2, can someone provide a working binary or help me compile it for the BE3600?
  • Is there a better method than redsocks2 for doing this in OpenWRT?

:light_bulb: Important Notes:

  • I want zero DNS leaks — DNS should also be routed through the SOCKS5 proxy.
  • I don’t want to configure each LAN device manually. The router should handle everything.
  • I’m okay with using iptables or nftables, as long as it works and is stable.

Thanks in advance to anyone who can help! I’ll follow your instructions step by step.

2

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

  1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
  2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
  3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

4

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.