mirror of
https://github.com/snail007/goproxy.git
synced 2026-04-27 16:35:49 +03:00
[GH-ISSUE #183] 协议转换后透明代理不支持telegram #113
Labels
No labels
TODO
bug
duplicate
enhancement
good first issue
help wanted
helpful
invalid
need-confirm
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/goproxy#113
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @yulinsoft on GitHub (Nov 25, 2018).
Original GitHub issue: https://github.com/snail007/goproxy/issues/183
启动命令如下
proxy sps -S ss -H chacha20-ietf -J ss密码 -T tcp -P SS服务器IP:10780 -t tcp -p 0.0.0.0:8080 --disable-ss --daemon --forever --log /var/log/proxy.log透明代理设置iptables命令如下
电脑和手机浏览google正常
手机打开telegram一直显示连接中
在telegram中设置socket5代理为路由器8080端口后正常。
日志如下
在手机wifi中设置http代理为路由器8080端口后,和透明代理时一样显示连接中。
透明代理时的日志如下:
同样的ip规则,在r2ray和ss-redir中,telegram都能正常工作,因此怀疑在此种条件下,proxy的透明代理只是处理了http代理,而没有处理socks代理。我感觉正常的处理流程应该是透明代理转发到更底层的socks代理上,不知道这样说对不对。
@yulinsoft commented on GitHub (Nov 25, 2018):
建议透明代理启用专门的端口,像v2ray一样,这样http和scoks还可以设置用户验证,不影响透明代理,现在的情况是设置用户验证后透明代理就不能用了。
@snail007 commented on GitHub (Feb 26, 2019):
手册已经说明,透明代理只支持http(s)协议,目标地址是从http(s)协议中获取,并不是同过iptabls转发的socket获取目标地址.