Repository navigation
|
use xray as the tunnel used by wireguard. everything is ok but the xray outbound freedom block the 127.0.0.1 traffic, the error log as below : how can i modify the config to allow the traffic ? |
Replies: 1 comment 1 reply
|
That's freedom's default safety policy. When traffic comes in through a VLESS, VMess, Trojan, Shadowsocks, Hysteria or WireGuard inbound and no finalRules entry matches, freedom blocks private/reserved IPs (including 127.0.0.1) and blackholes the connection. That's the blocked target ... blackholing connection line. Add an explicit allow rule on the remote server's freedom outbound. Rules are checked in order before the default: { "protocol": "freedom", "settings": { "finalRules": [ { "action": "allow", "network": "udp", "ip": ["127.0.0.1/32"] } ] } } You can also add "port": "" to keep the hole as small as possible. Docs: https://xtls.github.io/en/config/outbounds/freedom.html (see finalRules and the default safety policy warning). |
That's freedom's default safety policy. When traffic comes in through a VLESS, VMess, Trojan, Shadowsocks, Hysteria or WireGuard inbound and no finalRules entry matches, freedom blocks private/reserved IPs (including 127.0.0.1) and blackholes the connection. That's the blocked target ... blackholing connection line.
Add an explicit allow rule on the remote server's freedom outbound. Rules are checked in order before the default:
{ "protocol": "freedom", "settings": { "finalRules": [ { "action": "allow", "network": "udp", "ip": ["127.0.0.1/32"] } ] } }
You can also add "port": "" to keep the hole as small as possible.
Docs: https://xtls.github.io/en/config/outbounds/freedom.html (see final…