-
Hi, I have the following working setup. Laptop with local xray with inbound wireguard and outgoings vless + freedom. Laptop has WG client that connects to this local xray and routes all traffic through it. Remote xray has vless inbound and freedom outbound. So far so good. The most common path is laptop -> WG -> xray local -> xray remote -> freedom. My goal and struggle is a new requirement to setup WG outbound on remove xray to connect to VPN network of a company. Here is what I did:
setup doesn't work and I'm not sure where the problem. I tried to change logging to debug/trace, but don't see anything in the logs to help me. My configuration, xray on laptop:
xray on remote server:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
In case somebody stumbles upon this thread. The problem was in |
Beta Was this translation helpful? Give feedback.
In case somebody stumbles upon this thread. The problem was in
"domainStrategy": "AsIs"
. My traffic that should go into xxx_vpn is HTTP, so sniffing added domain and routing is domain based by default. Changing toIPIfNoMatch
orIPOnDemand
solved the issue. I find it surprising. At the end, even if you sniffed domain from tls hello, xray still has tcp/ip connection and it has dst IP. Not sure why matching is not based on that IP and why documentation talks about resolving domain.