apt install redsocks /etc/redsocks.conf :
/tool sniffer quick ip-protocol=tcp port=1080 Check that packets reach the V2Ray proxy. v2ray mikrotik
On a LAN client, check public IP:
/ip firewall nat add chain=srcnat src-address=192.168.88.0/24 dst-address=192.168.88.2 action=accept Some RouterOS versions (7.x) support containers. You can run a lightweight Linux with V2Ray. Step 1 – Enable containers /container config set registry-url=https://registry-1.docker.io tmpdir=containers Step 2 – Pull and run a V2Ray container /container add remote-image=v2ray/official:latest interface=veth1 root-dir=containers/v2ray /container start 0 Step 3 – Expose SOCKS5 port Bind container port 1080 to router’s IP. Step 4 – Transparent proxy inside container? This is complex because the container lacks full network control. Easier: Use SOCKS5 proxy on client devices manually, or run redsocks inside the container with TPROXY (requires advanced network namespaces – often unstable on RouterOS). apt install redsocks /etc/redsocks
Avoid containers for transparent proxying. Use an external Linux box. Testing & Verification On MikroTik: Step 1 – Enable containers /container config set
Example with redsocks (simpler):
{ "inbounds": [ { "port": 1080, "protocol": "socks", "settings": { "auth": "no", "udp": true } } ], "outbounds": [ { "protocol": "vmess", "settings": { "vnext": [ { "address": "your-v2ray-server.com", "port": 443, "users": [{ "id": "uuid", "alterId": 0, "security": "auto" }] } ] } } ] } Run V2Ray: v2ray run -c config.json Install redsocks or iptables TPROXY to redirect traffic to V2Ray’s SOCKS5.