search

v2ray / v2ray-core

A platform for building proxies to bypass network restrictions.
https://www.v2ray.com/
MIT License
45.32k stars 8.94k forks source link

配置了Tproxy透明代理，国内网站访问正常，外国网站无响应，日志输出v2ray.com/core/proxy/dokodemo: unable to get destination #2225

Closed ifaws closed 4 years ago

ifaws commented 4 years ago

1) V2Ray版本 客户端与VPS端版本相同 V2Ray 4.22.1 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.13 linux/arm)

2) 使用场景 作为局域网透明代理，为局域网设备及本机提供智能代理服务 Raspberrypi 4 - Raspbian buster lite - V2ray - ss-tproxy 'ip:192.168.1.8 - gateway:192.168.1.1 - mask:255.255.255.0'

3) 不正常的现象 V2Ray配置了Tproxy，搭配ss-tproxy使用，配置完成后，局域网设备可以通过代理访问国内网站，外国网站无响应，检查V2Ray及ss-tproxy配置文件，未发现填错的地方。 dig @127.0.0.1 -p65353 www.baidu.com 输出正常 dig @127.0.0.1 -p65353 www.google.com 响应超时

; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> @127.0.0.1 -p65353 www.google.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

4) 你期待看到的正确表现是怎样的？ 局域网设备的网关及DNS指向透明代理设备，局域网设备可以按照配置访问国内网站，以及通过代理访问外国网站。

5) 配置文件 服务器端配置:

  1 { 
  2     "log":{ 
  3             "acess":"/var/log/v2ray/acess.log", 
  4             "error":"/var/log/v2ray/error.log", 
  5             "loglevel":"warning" 
  6     }, 
  7     "inbounds": [{ 
  8     "port": 20124, 
  9     "protocol": "vmess", 
 10     "settings": { 
 11       "clients": [ 
 12         { 
 13           "id": "UUID", 
 14           "level": 1, 
 15           "alterId": 64 
 16         } 
 17       ] 
 18     } 
 19   }], 
 20   "outbounds": [{ 
 21     "protocol": "freedom", 
 22     "settings": {} 
 23   },{ 
 24     "protocol": "blackhole", 
 25     "settings": {}, 
 26     "tag": "blocked" 
 27   }], 
 28   "routing": { 
 29     "rules": [ 
 30       { 
 31         "type": "field", 
 32         "ip": ["geoip:private"], 
 33         "outboundTag": "blocked" 
 34       } 
 35     ] 
 36   } 
 37 }

客户端配置:

    {
  "inbounds": [
    {
     "tag":"transparent",
     "port": 12345,
     "listen":"0.0.0.0",
     "protocol": "dokodemo-door",
     "settings": {
       "network":"tcp,udp",
       "followRediect":true
     },
     "sniffing":{
       "enabled":true,
        "destOverride":["http","tls"]
     },
   "streamSettings":{
     "sockopt":{
       "tproxy":"tproxy"
     }
   }
    },
 {
    "port":1080,
    "protocol":"socks",
    "sniffing":{
        "enabled":true,
        "destOverride":["http","tls"]
    },
    "settings":{
        "auth":"noauth"
    }
 }
  ],

    "outbounds": [
    {
        "tag":"proxy",
     "protocol":"vmess",
         "settings":{
                 "vnext":[
                      {
            "address":"1.2.3.4",
            "port":20124,
            "users":[
                {
                 "id":"UUID",
                 "alterId":64
                     }
             ]
              }
              ]
              },
        "mux":{
            "enabled":true
        }
    }
    ]
  }

6) 错误日志

服务器端错误日志:

    root@localhost:~# cat /var/log/v2ray/error.log
    2020/02/03 03:29:33 [Warning] v2ray.com/core: V2Ray 4.22.1 started
    2020/02/03 03:31:19 [Warning] v2ray.com/core: V2Ray 4.22.1 started

客户端错误日志:

root@raspberrypi:/home/pi# cat /var/log/v2ray/error.log
2020/02/07 12:50:38 [Debug] v2ray.com/core/app/proxyman/inbound: creating stream worker on 0.0.0.0:12345
2020/02/07 12:50:38 [Debug] v2ray.com/core/app/proxyman/inbound: creating stream worker on 0.0.0.0:1080
2020/02/07 12:50:38 [Info] v2ray.com/core/transport/internet/tcp: listening TCP on 0.0.0.0:12345
2020/02/07 12:50:38 [Info] v2ray.com/core/transport/internet/udp: listening UDP on 0.0.0.0:12345
2020/02/07 12:50:38 [Info] v2ray.com/core/transport/internet/tcp: listening TCP on 0.0.0.0:1080
2020/02/07 12:50:38 [Warning] v2ray.com/core: V2Ray 4.22.1 started
2020/02/07 12:50:50 [Debug] [351108695] v2ray.com/core/proxy/dokodemo: processing connection from: 192.168.1.8:35033
2020/02/07 12:50:50 [Info] [351108695] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/dokodemo: unable to get destination
2020/02/07 12:50:56 [Debug] [1188929081] v2ray.com/core/proxy/dokodemo: processing connection from: 192.168.1.8:35033
2020/02/07 12:50:56 [Info] [1188929081] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/dokodemo: unable to get destination
2020/02/07 12:50:56 [Debug] [2727490863] v2ray.com/core/proxy/dokodemo: processing connection from: 192.168.1.8:35033
2020/02/07 12:50:56 [Info] [2727490863] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/dokodemo: unable to get destination
2020/02/07 12:50:56 [Debug] [2637517469] v2ray.com/core/proxy/dokodemo: processing connection from: 192.168.1.8:35033

7) 访问日志 /var/log/v2ray/access.log

   cat /var/log/v2ray/access.log
   //无输出

8) 其它相关的配置文件（如 Nginx）和相关日志。

9) --test配置文件测试

root@raspberrypi:/home/pi# /usr/bin/v2ray/v2ray --test --config /etc/v2ray/config.json
V2Ray 4.22.1 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.13 linux/arm)
A unified platform for anti-censorship.
Configuration OK.

10) V2Ray运行状态

root@raspberrypi:/home/pi# ps -ef | grep v2ray
root       564     1    0  12:50    ?     00:00:00 /usr/bin/v2ray/v2ray -config /etc/v2ray/config.json
root       914   888  0  13:14   pts/0    00:00:00 grep v2ray
root@raspberrypi:/home/pi# systemctl status v2ray
● v2ray.service - V2Ray Service
   Loaded: loaded (/etc/systemd/system/v2ray.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2020-02-07 12:50:37 CST; 1h 26min ago
 Main PID: 564 (v2ray)
    Tasks: 11 (limit: 4915)
   Memory: 19.2M
   CGroup: /system.slice/v2ray.service
           └─564 /usr/bin/v2ray/v2ray -config /etc/v2ray/config.json

Feb 07 12:50:37 raspberrypi systemd[1]: Started V2Ray Service.
Feb 07 12:50:38 raspberrypi v2ray[564]: V2Ray 4.22.1 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.13 linux/arm)
Feb 07 12:50:38 raspberrypi v2ray[564]: A unified platform for anti-censorship.
root@raspberrypi:/home/pi# netstat -an|grep LISTEN
tcp        0      0 0.0.0.0:60053           0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:53              0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     
tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN     
tcp6       0      0 :::60053                :::*                    LISTEN     
tcp6       0      0 :::53                   :::*                    LISTEN     
tcp6       0      0 :::22                   :::*                    LISTEN     
tcp6       0      0 :::1080                 :::*                    LISTEN     
tcp6       0      0 :::12345                :::*                    LISTEN     
tcp6       0      0 ::1:6010                :::*                    LISTEN     
unix  2      [ ACC ]     STREAM     LISTENING     17466    /run/user/1000/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     17472    /run/user/1000/gnupg/S.gpg-agent.browser
unix  2      [ ACC ]     STREAM     LISTENING     17475    /run/user/1000/gnupg/S.dirmngr
unix  2      [ ACC ]     STREAM     LISTENING     17477    /run/user/1000/gnupg/S.gpg-agent.extra
unix  2      [ ACC ]     STREAM     LISTENING     17479    /run/user/1000/gnupg/S.gpg-agent.ssh
unix  2      [ ACC ]     STREAM     LISTENING     17481    /run/user/1000/gnupg/S.gpg-agent
unix  2      [ ACC ]     STREAM     LISTENING     10877    /var/run/dhcpcd.sock
unix  2      [ ACC ]     STREAM     LISTENING     10879    /var/run/dhcpcd.unpriv.sock
unix  2      [ ACC ]     STREAM     LISTENING     1407     /run/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     1413     /run/systemd/fsck.progress
unix  2      [ ACC ]     STREAM     LISTENING     1417     /run/systemd/journal/stdout
unix  2      [ ACC ]     SEQPACKET  LISTENING     1444     /run/udev/control
unix  2      [ ACC ]     STREAM     LISTENING     10691    /run/avahi-daemon/socket
unix  2      [ ACC ]     STREAM     LISTENING     10696    /var/run/dbus/system_bus_socket
unix  2      [ ACC ]     STREAM     LISTENING     10700    /run/thd.socket
mzz2017 commented 4 years ago

94856228-0C39-4F91-834F-8A87D8A59F26

followRedirect

上述拼写错误。

我不确定修正拼写后是否会正常，但在相关的issues中出现了同样的提示 #2214 #2209

ifaws commented 4 years ago

问题已解决，确实followRedirect拼写错误…羞涩了，感谢提醒