Skip to content

[Bug Report] dae无法通过clash建立与github的ssh连接 #781

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
3 tasks done
f1sherb0y opened this issue Mar 12, 2025 · 4 comments
Open
3 tasks done

[Bug Report] dae无法通过clash建立与github的ssh连接 #781

f1sherb0y opened this issue Mar 12, 2025 · 4 comments

Comments

@f1sherb0y
Copy link

f1sherb0y commented Mar 12, 2025

Checks

  • I have searched the existing issues
  • I have read the documentation
  • Is it your first time sumbitting an issue

Current Behavior

已经确认:如果在~/.ssh/config里面配置如下就可以通过ssh 进行git clone,所以应该不是clash那边的问题

Host github.com
  Hostname ssh.github.com
  Port 443
  ProxyCommand socat - PROXY:127.0.0.1:%h:%p,proxyport=7897

dae配置如下:

global {
	log_level: debug
	wan_interface: auto
	dial_mode: domain
} 
node {
	clash: 'socks5://localhost:7897'
}
dns {
	upstream {
		alidns: 'udp://dns.alidns.com:53'
		googledns: 'tcp+udp://dns.google.com:53'
	}
	routing {
		request {
			fallback: alidns
		}
		response {
			upstream(googledns) -> accept
			!qname(geosite:cn) && ip(geoip:private) -> googledns
			fallback: accept
		}
	}
}
group {
	clash {
		policy: fixed(0)
	}
}
routing {
	pname(NetworkManager) -> direct
	pname(iwd) -> direct
	pname(iwctl) -> direct
	
	pname(clash) -> must_direct
	pname(clash-meta) -> must_direct
	pname(clash-verge-rev) -> must_direct
	pname(verge-mihomo) -> must_direct
	pname(clash-verge) -> must_direct
	pname(clash-verge-service) -> must_direct

	pname(qbittorrent) -> direct

	dip(geoip:private) -> direct
	dip(geoip:cn) -> direct
	domain(geosite:cn) -> direct
	fallback: clash
}

git clone 输出如下:

Cloning into 'LLM-SocialSimulation-DAI'...
Connection closed by 20.205.243.166 port 22
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

dae日志如下:

Mar 12 23:10:12 arch dae[6102]: level=info msg="192.168.31.152:53376 <-> 223.5.5.5:53" _qname=github.com. dialer=direct dscp=0 mac="a8:7e:ea:76:63:6c" network="udp4(DNS)" outbound=direct pid=8961 pname=ssh policy=fixed qtype=A
Mar 12 23:10:12 arch dae[6102]: level=debug msg="UDP(DNS) 192.168.31.152:53376 <-> Cache: github.com. AAAA"
Mar 12 23:10:12 arch dae[6102]: level=info msg="192.168.31.152:51618 <-> 20.205.243.166:22" dialer=clash dscp=18 ip="20.205.243.166:22" mac="a8:7e:ea:76:63:6c" network=tcp4 outbound=clash pid=0 pname=ssh policy=fixed sniffed=

Expected Behavior

No response

Steps to Reproduce

kernel version: 6.13.6-arch1-1

Environment

  • Dae version (use dae --version): git commit @ 2edc2d3
  • OS (e.g cat /etc/os-release): Arch linux
  • Kernel (e.g. uname -a): 6.13.6-arch1-1
  • Others:

Anything else?

No response

@dae-prow
Copy link
Contributor

dae-prow bot commented Mar 12, 2025

Thanks for opening this issue!

@f1sherb0y
Copy link
Author

f1sherb0y commented Mar 13, 2025

Here is a screenshot of wireshark captures.
On the left , i am using ( ssh -> clash -> github ), captured on wlan0 interface.
On the right, i am using ( ssh -> dae -> clash -> github ), captured on wlan0 and dae interfaces.

I can't figure out much here, but an obvious difference is that, when using dae, there are out-of-order packets from server.

Image

@szw0407
Copy link

szw0407 commented May 3, 2025

same issue.

@akiooo45
Copy link
Contributor

akiooo45 commented May 3, 2025

@szw0407 有机场会屏蔽22端口,所以应该使用443来git clone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants