谢晓烜

Results 15 comments of 谢晓烜

> I didn't fully follow your description but it seems the real-ip plugin can fix your issue: https://docs.api7.ai/hub/real-ip Is the real-ip plug-in based on layer 7 proxy HTTP? But what...

> Envoy can both forward CONNECT request, encapsulate traffic in CONNECT and terminate CONNECT. Please check out https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/http/upgrades @alyssawilk I want to achieve is that all http/https in this pod...

> > Envoy can both forward CONNECT request, encapsulate traffic in CONNECT and terminate CONNECT. Please check out https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/http/upgrades > > @alyssawilk I want to achieve is that all http/https...

> apologies, but I think you're going to have to play around - I'm unfortunately too overloaded to dig in the way I'd need to to help out. OK, Thanks.

this is my setting: ``` - filters: - name: istio.stats typed_config: '@type': type.googleapis.com/stats.PluginConfig - name: envoy.filters.network.tcp_proxy typed_config: '@type': type.googleapis.com/envoy.extensions.filters.network.tcp_proxy.v3.TcpProxy access_log: - name: envoy.access_loggers.file typed_config: '@type': type.googleapis.com/envoy.extensions.access_loggers.file.v3.FileAccessLog log_format: text_format_source: inline_string: '[%START_TIME%]...

> 端口错了,要么修改 clash.yaml 把 tproxy-port 改为 60080 (同readme的配置),要么修改 ss-tproxy.conf,把 proxy_tcpport 和 proxy_udpport 改为 7893,总之必须保持一致。 好的,我修改了...但是.... ![image](https://github.com/zfl9/ss-tproxy/assets/65661595/a2f71249-b776-4f6b-b6e5-80c8d328f8a6) ![image](https://github.com/zfl9/ss-tproxy/assets/65661595/33525fc7-970b-49d7-b132-0ed1d865f50c) 这个情况你了解么?话说为什么百度也走了代理呀,不好意思,我是该领域的小白0.0

> 端口错了,要么修改 clash.yaml 把 tproxy-port 改为 60080 (同readme的配置),要么修改 ss-tproxy.conf,把 proxy_tcpport 和 proxy_udpport 改为 7893,总之必须保持一致。 这是我的clash配置 ![image](https://github.com/zfl9/ss-tproxy/assets/65661595/5ac3fd22-177b-4eb0-b5ad-aabe114ce70c) 这是我的ss-tproxy配置 ![image](https://github.com/zfl9/ss-tproxy/assets/65661595/c1ef3984-fc27-40b8-a93b-77586f580589) 端口已经改为和clash一致 其他选项均是默认配置

> clash配置问题?先自己检查下吧。readme的clash配置是测试过的,另外你说在docker部署?ss-tproxy在docker容器内?curl/wget 在宿主机? 搞了半个月没搞出来,我是在k8s集群部署的,clash是一个容器,wget是在另一个容器里面(这个容器里面用envoy把80流量拦截转发到clash容器的7893端口了,在这个容器里面通过环境变量http_proxy是能生效的),不知道您是否了解这方面...只要能提供帮助的话0.0

> 还有为什么你的 start_clash 会漏出 clash 日志?readme 里面已经把 stdout stderr 重定向到日志文件了呀。 我改了一下这个,输出到控制台了.