Verify that Xray started correctly and connected to the server. /container/logs/print Use code with caution.
{ "inbounds": [ "port": 10808, "protocol": "socks", "settings": "auth": "noauth", "udp": true , "tag": "socks-in" , { "port": 10809, "protocol": "http", "settings": {}, "tag": "http-in" } ], "outbounds": [ "protocol": "vmess", "settings": "vnext": [ "address": "YOUR_SERVER_IP_OR_DOMAIN", "port": YOUR_SERVER_PORT, "users": [ "id": "YOUR_V2RAY_UUID", "alterId": 0, "security": "auto" ] ] , "tag": "proxy-out" , { "protocol": "freedom", "settings": {}, "tag": "direct-out" } ] } Use code with caution.
Running V2Ray on MikroTik devices is achievable via RouterOS v7.4+ container support, enabling ARM/x86 routers to run Docker-based V2Ray or Xray images. The process involves enabling container mode, setting up virtual ethernet interfaces, and creating NAT rules to route traffic through the containerized service. For detailed setup instructions, visit MikroTik Documentation . Container as VPN - General - MikroTik community forum
Implementing V2Ray on MikroTik RouterOS: A Complete Guide Network censorship, strict firewalls, and deep packet inspection (DPI) present significant challenges for maintaining secure, open internet access. Traditional VPN protocols like OpenVPN or WireGuard are easily identified and blocked by advanced firewalls. v2ray mikrotik
Use /ip firewall mangle to "mark" connections originating from your LAN that match your destination address list.
Running V2Ray directly on a MikroTik router (via Container) offers several advantages over running it on computers or phones:
| Feature | Container Method (Recommended) | External PC Method | | :--- | :--- | :--- | | | High (requires CLI & networking knowledge) | Medium (simple routing rules) | | Performance | Best (low-latency, direct routing) | Good (adds network hop) | | Feature Support | Full (supports all V2Ray/Xray features) | Full (runs on a separate PC) | | Dependency | Router's container feature | A separate, always-on PC | | Hardware Requirement | ARM router with sufficient RAM | Minimal for router, any PC | Verify that Xray started correctly and connected to
You need the IP, Port, UUID, AlterId, and Transport settings (VMess/VLESS) from your V2Ray service provider.
Deploy V2Ray on your secondary Linux device inside your local network. 192.168.88.1 V2Ray Proxy Server IP: 192.168.88.10
This network ( 172.17.0.0/24 ) is now ready for your containers. Running V2Ray on MikroTik devices is achievable via
V2Ray can be resource-intensive. Monitor your CPU usage using /tool/profile .
: Give the VETH interface an IP address (e.g., 172.17.0.1/24 ) and assign the container a static IP (e.g., 172.17.0.2 ).
Enable the container mode on your MikroTik (this usually requires physical access or a "cold boot" for security). You will need to set up a veth interface and a bridge to allow the container to communicate with your local network. 2. Deploy Xray-Core and Tun2Socks