xjasonlyu / tun2socks

tun2socks - powered by gVisor TCP/IP stack
https://github.com/xjasonlyu/tun2socks/wiki
GNU General Public License v3.0
2.85k stars 405 forks source link

[Bug] symmetric NAT 192.168.1.100:58535->198.18.0.53:443: drop packet from 198.18.0.50:443 #144

Closed m2acgi closed 2 years ago

m2acgi commented 2 years ago

Verify steps

Version

v2.4.1

What OS are you seeing the problem on?

Linux

Description

大佬, tun2socks + clash fake-ip 模式,tun2socks 里面有很多这种 log, 请问是正常的还是存在什么问题?

WARN[0700] [UDP] symmetric NAT 192.168.1.100:58535->198.18.0.53:443: drop packet from 198.18.0.50:443
WARN[0700] [UDP] symmetric NAT 192.168.1.100:58535->198.18.0.53:443: drop packet from 198.18.0.50:443
WARN[0700] [UDP] symmetric NAT 192.168.1.100:58535->198.18.0.53:443: drop packet from 198.18.0.50:443
WARN[0700] [UDP] symmetric NAT 192.168.1.100:58535->198.18.0.53:443: drop packet from 198.18.0.50:443
WARN[0700] [UDP] symmetric NAT 192.168.1.100:58535->198.18.0.53:443: drop packet from 198.18.0.50:443
WARN[0700] [UDP] symmetric NAT 192.168.1.100:58535->198.18.0.53:443: drop packet from 198.18.0.50:443
WARN[0700] [UDP] symmetric NAT 192.168.1.100:58535->198.18.0.53:443: drop packet from 198.18.0.50:443
WARN[0700] [UDP] symmetric NAT 192.168.1.100:54917->198.18.0.48:443: drop packet from 198.18.0.50:443
WARN[0700] [UDP] symmetric NAT 192.168.1.100:54917->198.18.0.48:443: drop packet from 198.18.0.50:443
WARN[0700] [UDP] symmetric NAT 192.168.1.100:54917->198.18.0.48:443: drop packet from 198.18.0.50:443
WARN[0700] [UDP] symmetric NAT 192.168.1.100:58535->198.18.0.53:443: drop packet from 198.18.0.50:443
WARN[0700] [UDP] symmetric NAT 192.168.1.100:58535->198.18.0.53:443: drop packet from 198.18.0.50:443
WARN[0700] [UDP] symmetric NAT 192.168.1.100:58535->198.18.0.53:443: drop packet from 198.18.0.50:443
WARN[0701] [UDP] symmetric NAT 192.168.1.100:58535->198.18.0.53:443: drop packet from 198.18.0.50:443
WARN[0701] [UDP] symmetric NAT 192.168.1.100:58535->198.18.0.53:443: drop packet from 198.18.0.50:443

CLI or Config

上游为 socks5 的标准配置

Logs

No response

How to Reproduce

No response

xjasonlyu commented 2 years ago

因为使用symmetric NAT实现,这是正常的。

m2acgi commented 2 years ago

👍谢谢