-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[Bug] IN-PORT规则在http代理协议下没有生效 #1162
Labels
bug
Something isn't working
Comments
wwqgtxx
added a commit
that referenced
this issue
Apr 4, 2024
试过 c893e3c 了么 |
试了一下,http的问题解决了。但我发现tproxy也有同样的问题... |
你说的是tcp还是udp还是两者都有 |
tcp有问题,udp看log有在被分流没有问题 |
wwqgtxx
added a commit
that referenced
this issue
Apr 4, 2024
试试 #1162 |
最新的build修好tproxy了,谢谢 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Verify steps
Mihomo version
Mihomo Meta alpha-b56e73a linux amd64 with go1.22.1 Wed Apr 3 15:41:59 UTC 2024 Use tags: with_gvisor
What OS are you seeing the problem on?
Linux
Mihomo config
Mihomo log
Description
根据文档描述,IN-PORT匹配入站(listener)端口来分流 https://wiki.metacubex.one/config/rules/
预期效果: 8001(mixed), 8002(http), 8003(socks5), 三个代理按入站端口分流
实际效果:
使用http代理没有被IN-PORT规则进行分流,socks5是可以的
log里面从上到下4个请求分别是:
curl checkip.amazonaws.com -x http://127.0.0.1:8001
curl checkip.amazonaws.com -x socks5://127.0.0.1:8001
curl checkip.amazonaws.com -x http://127.0.0.1:8002
curl checkip.amazonaws.com -x socks5://127.0.0.1:8003
其中只有socks5的两个请求成功分流(proxy1),http的都匹配到最终规则(proxy2)
The text was updated successfully, but these errors were encountered: