search

vernesong / OpenClash

A Clash Client For OpenWrt
MIT License
17.52k stars 3.18k forks source link

[Bug] wifi-calling TCP连接完成后有时无UDP连接 #2933

Closed rbbt065 closed 1 year ago

rbbt065 commented 1 year ago

Verify Steps

OpenClash Version

v0.45.78-beta

Bug on Environment

Official OpenWrt

Bug on Platform

Linux-amd64(x86-64)

To Reproduce

iPhone手机连接旁路由上的openclash时在与服务器发生tcp连接后不会进一步产生udp连接

Describe the Bug

在clash for windows通过移动热点让手机开通wifi calling时，通过日志文件可以看到在与T-mobile服务器建立tcp连接后很快就产生了对应的udp连接，可以成功开启wifi-calling功能，日志如下所示： clash for windows

而在openclash中使用同一套配置文件，内核日志却只显示建立tcp连接，而无法建立udp连接，如下： openclash 但偶尔也能成功进行udp连接

OpenClash Log

OpenClash Log: 2023-01-10 15:31:02 OpenClash Start Successful! 2023-01-10 15:31:02 Step 9: Add Cron Rules, Start Daemons... 2023-01-10 15:31:02 Step 8: Restart Dnsmasq... 2023-01-10 15:31:02 Tip: Waiting for TUN Interface Start... 2023-01-10 15:31:02 Tip: Firewall4 was Detected, Use NFTABLE Rules... 2023-01-10 15:31:02 Step 7: Set Firewall Rules... 2023-01-10 15:31:01 Step 6: Wait For The File Downloading... 2023-01-10 15:30:58 Step 5: Check The Core Status... 2023-01-10 15:30:57 Tip: Detected The Exclusive Function of The TUN Core, Use TUN Core to Start... 2023-01-10 15:30:57 Step 4: Start Running The Clash Core... 2023-01-10 15:30:56 Tip: You have seted the authentication of SOCKS5/HTTP(S) proxy with【Clash:YXqEDWzl】 2023-01-10 15:30:56 Step 3: Modify The Config File... 2023-01-10 15:30:56 Tip: Because of the file【 /etc/openclash/config/Clash_Config.yaml 】modificated, Pause quick start... 2023-01-10 15:30:56 Step 2: Check The Components... 2023-01-10 15:30:56 Step 1: Get The Configuration... 2023-01-10 15:30:56 OpenClash Start Running... 2023-01-10 15:30:56 Step 6: Delete OpenClash Residue File... 2023-01-10 15:30:56 Step 5: Restart Dnsmasq... 2023-01-10 15:30:56 Step 4: Close The Clash Core Process... 2023-01-10 15:30:56 Step 3: Close The OpenClash Daemons... 2023-01-10 15:30:55 Step 2: Delete OpenClash Firewall Rules... 2023-01-10 15:30:55 Step 1: Backup The Current Groups State... 2023-01-10 15:30:55 OpenClash Stoping... 2023-01-10 15:30:55 Config File【Clash_Config】Update Successful! 2023-01-10 15:30:55 Config File【Clash_Config】Are Updates, Start Replacing... 2023-01-10 15:30:55 Config File Download Successful, Check If There is Any Update... 2023-01-10 15:30:53 Start Updating Config File【Clash_Config】... Core Log: 2023-01-10 15:24:45 INF [TCP] connected lAddr=192.168.3.21:62253 rAddr=dispatcher.is.autonavi.com:443 mode=rule rule=RuleSet(AppleRules) proxy=DIRECT 2023-01-10 15:24:45 DBG [TCP] accept connection lAddr=192.168.3.21:62253 rAddr=dispatcher.is.autonavi.com:443 inbound=TUN 2023-01-10 15:24:45 INF [TCP] connected lAddr=192.168.3.21:54837 rAddr=graph.instagram.com:443 mode=rule rule=Match() proxy=USA_zj[🇺🇸 USA CN2 GIA] 2023-01-10 15:24:45 INF [TCP] connected lAddr=192.168.3.21:54835 rAddr=gateway.facebook.com:443 mode=rule rule=Match() proxy=USA_zj[🇺🇸 USA CN2 GIA] 2023-01-10 15:24:45 INF [TCP] connected lAddr=192.168.3.21:54836 rAddr=edge-mqtt.facebook.com:443 mode=rule rule=Match() proxy=USA_zj[🇺🇸 USA CN2 GIA] 2023-01-10 15:24:43 DBG [Matcher] find process failed error=process not found addr=graph.instagram.com 2023-01-10 15:24:43 DBG [TCP] accept connection lAddr=192.168.3.21:54837 rAddr=graph.instagram.com:443 inbound=TUN 2023-01-10 15:24:43 INF [UDP] connected, doesn't match any rule lAddr=192.168.3.21:53135 rAddr=108.160.163.106:443 proxy=DIRECT 2023-01-10 15:24:43 DBG [Matcher] UDP not supported, skip proxy=USA_zj 2023-01-10 15:24:43 DBG [Matcher] find process failed error=process not found addr=108.160.163.106 2023-01-10 15:24:43 DBG [UDP] accept session lAddr=192.168.3.21:53135 rAddr=108.160.163.106:443 inbound=TUN 2023-01-10 15:24:43 DBG [Matcher] find process failed error=process not found addr=edge-mqtt.facebook.com 2023-01-10 15:24:43 DBG [TCP] accept connection lAddr=192.168.3.21:54836 rAddr=edge-mqtt.facebook.com:443 inbound=TUN 2023-01-10 15:24:43 DBG [Matcher] find process failed error=process not found addr=gateway.facebook.com 2023-01-10 15:24:43 DBG [TCP] accept connection lAddr=192.168.3.21:54835 rAddr=gateway.facebook.com:443 inbound=TUN 2023-01-10 15:24:39 INF [UDP] connected lAddr=192.168.3.9:53142 rAddr=time.apple.com:123 mode=rule rule=RuleSet(AppleRules) proxy=DIRECT 2023-01-10 15:24:39 DBG [Matcher] UDP not supported, skip proxy=USA_zj 2023-01-10 15:24:39 DBG [UDP] accept session lAddr=192.168.3.9:53142 rAddr=time.apple.com:123 inbound=TUN 2023-01-10 15:24:37 INF [UDP] connected lAddr=192.168.3.9:57795 rAddr=time.apple.com:123 mode=rule rule=RuleSet(AppleRules) proxy=DIRECT 2023-01-10 15:24:37 DBG [Matcher] UDP not supported, skip proxy=USA_zj 2023-01-10 15:24:37 DBG [UDP] accept session lAddr=192.168.3.9:57795 rAddr=time.apple.com:123 inbound=TUN 2023-01-10 15:24:37 INF [UDP] connected lAddr=192.168.3.9:53241 rAddr=time.apple.com:123 mode=rule rule=RuleSet(AppleRules) proxy=DIRECT 2023-01-10 15:24:37 DBG [Matcher] UDP not supported, skip proxy=USA_zj 2023-01-10 15:24:37 DBG [UDP] accept session lAddr=192.168.3.9:53241 rAddr=time.apple.com:123 inbound=TUN 2023-01-10 15:24:37 DBG [DNS] dns response source=https://1.1.1.1/dns-query qType=A name=time.apple.com. answer=["17.253.16.125","17.253.16.253","17.253.4.125"] 2023-01-10 15:24:37 DBG [DNS] dns response source=223.5.5.5:53 qType=A name=dns.google. answer=["8.8.8.8","8.8.4.4"] 2023-01-10 15:24:14 INF [UDP] connected lAddr=192.168.3.19:40805 rAddr=112.124.32.90:3000 mode=rule rule=RuleSet(cncidr) proxy=DIRECT 2023-01-10 15:24:14 DBG [Matcher] find process failed error=process not found addr=112.124.32.90 2023-01-10 15:24:14 DBG [UDP] accept session lAddr=192.168.3.19:40805 rAddr=112.124.32.90:3000 inbound=TUN 2023-01-10 15:24:12 INF [TCP] connected lAddr=192.168.3.21:62252 rAddr=101.226.94.124:80 mode=rule rule=RuleSet(cncidr) proxy=DIRECT 2023-01-10 15:24:12 DBG [Matcher] find process failed error=process not found addr=101.226.94.124 2023-01-10 15:24:12 DBG [TCP] accept connection lAddr=192.168.3.21:62252 rAddr=101.226.94.124:80 inbound=TUN 2023-01-10 15:24:12 INF [TCP] connected lAddr=192.168.3.21:62250 rAddr=albert.apple.com:443 mode=rule rule=RuleSet(AppleAPIRules) proxy=USA_zj[🇺🇸 USA CN2 GIA] 2023-01-10 15:24:12 INF [TCP] connected lAddr=192.168.3.21:62251 rAddr=eas3.msg.t-mobile.com:443 mode=rule rule=IPCIDR(208.54.0.0/16) proxy=USA_jc[🇺🇸 USA San Jose 03 [Premium]] 2023-01-10 15:24:12 DBG [Matcher] find process failed error=process not found addr=eas3.msg.t-mobile.com 2023-01-10 15:24:12 DBG [TCP] accept connection lAddr=192.168.3.21:62251 rAddr=eas3.msg.t-mobile.com:443 inbound=TUN 2023-01-10 15:24:12 DBG [TCP] accept connection lAddr=192.168.3.21:62250 rAddr=albert.apple.com:443 inbound=TUN

OpenClash Config

No response

Expected Behavior

每次手机与openclash连接后均能在tcp连接后成功进行udp连接

Screenshots

No response

rbbt065 commented 1 year ago

补充：日志为openclash工作在redir-host TUN模式下的内核日志，尝试过切换为redir-host（兼容）、redir-host（混合）、fake-ip（兼容）、fake-ip（TUN）、fake-ip（混合）模式，均存在此该问题。而使用clash for windows无论是redir-host TUN亦或是fake-ip TUN 都可以成功完成udp连接

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days

xuezihe commented 12 months ago

upup,遇到相同的问题

jjaychen1e commented 9 months ago

Same issue here. Any update? @xuezihe @rbbt065