Skip to content
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

能支持 wsl 吗? #3

Open
hulucc opened this issue Feb 3, 2019 · 18 comments
Open

能支持 wsl 吗? #3

hulucc opened this issue Feb 3, 2019 · 18 comments

Comments

@hulucc
Copy link

hulucc commented Feb 3, 2019

No description provided.

@ji4ozhu
Copy link
Owner

ji4ozhu commented Feb 13, 2019

wsl???是什么,

@hulucc
Copy link
Author

hulucc commented Feb 13, 2019

https://docs.microsoft.com/en-us/windows/wsl/about
proxifier 工作在LSP层,支持不了

@ji4ozhu
Copy link
Owner

ji4ozhu commented Feb 14, 2019

https://docs.microsoft.com/en-us/windows/wsl/about
proxifier 工作在LSP层,支持不了
你试试进程那输入 wsl 启动的进程名。应该是可以的

@hulucc
Copy link
Author

hulucc commented Feb 15, 2019

启动进程运行完就结束了,网络不是通过那个进程走的

@ji4ozhu
Copy link
Owner

ji4ozhu commented Feb 15, 2019

启动进程运行完就结束了,网络不是通过那个进程走的

kkcap 的界面ui上有没有显示那个进程和流量。
比如你可以试试运行wsl里的wget 之类的做测试。

@xmdmk
Copy link

xmdmk commented Feb 17, 2019

启动进程运行完就结束了,网络不是通过那个进程走的

去任务管理器里看那个进程的详细信息,那里有运行时的名称,看下和你填的是不是一样的。

@hulucc
Copy link
Author

hulucc commented Feb 18, 2019

启动进程运行完就结束了,网络不是通过那个进程走的

去任务管理器里看那个进程的详细信息,那里有运行时的名称,看下和你填的是不是一样的。

pico process,和普通process不一样的

@ji4ozhu
Copy link
Owner

ji4ozhu commented Feb 18, 2019

你用其他方式找出来哪个进程联网,代理那个进程就可以了

@hulucc
Copy link
Author

hulucc commented Feb 18, 2019

你用其他方式找出来哪个进程联网,代理那个进程就可以了

https://slab.qq.com/news/tech/1460.html
pico 进程,代理不了

@ji4ozhu
Copy link
Owner

ji4ozhu commented Feb 18, 2019

你用其他方式找出来哪个进程联网,代理那个进程就可以了

https://slab.qq.com/news/tech/1460.html
pico 进程,代理不了
image

兄die.是可以代理 wsl 进程的哦。只要你的规则里输入的 联网进程名是正确的就可以了

@hulucc
Copy link
Author

hulucc commented Feb 19, 2019

666

@hulucc hulucc closed this as completed Feb 19, 2019
@hulucc
Copy link
Author

hulucc commented Feb 19, 2019

小弟试了下确实能捕捉到tcp的请求,但是dns似乎都没走,所以在wsl里curl www.google.com失败
image

@hulucc hulucc reopened this Feb 19, 2019
@ji4ozhu
Copy link
Owner

ji4ozhu commented Feb 19, 2019

小弟试了下确实能捕捉到tcp的请求,但是dns似乎都没走,所以在wsl里curl www.google.com失败

目前DNS是使用本地网卡的DNS进行解析的,过2天我更新一下。允许自定义dns解析。
建议使用直连ss不要用127.0.0.1 的本地转发。

@hulucc
Copy link
Author

hulucc commented Feb 19, 2019

辛苦啦~
用socks5是因为最后会用v2ray(WebSocket + TLS + CDN比较安全

@hulucc
Copy link
Author

hulucc commented Mar 25, 2019

试了下 20190227a,dns还是解析不上(看changelog里有dns forward
image

image

@florianmonfort
Copy link

@hulucc hi, I don't really understand how to use this with WSL? Is it possible?

@hulucc
Copy link
Author

hulucc commented Nov 21, 2019

@hulucc hi, I don't really understand how to use this with WSL? Is it possible?

Yes, it works with WSL, but not very well.
Just config the proxy like proxifier, and add rule like "curl"(without ".exe"). Then when you curl a url in the wsl bash, the connect should has gone through the proxy.
But you can't curl something like google because the kkcap is not "proxying" the dns resolving.

@a5066987
Copy link

a5066987 commented Feb 4, 2022

WSL直接用proxychains4。这是我折腾很久之后的最终解决方案

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

5 participants