zh-jq
commented
4 weeks ago This is my manifest (adopted from squid example):
--- runtime: thread_number: 2 controller: local: recv_timeout: 30 send_timeout: 1 server: - name: socks escaper: squid type: socks_proxy listen: address: "[::]:11080" - name: http escaper: squid type: http_proxy listen: address: "[::]:13128" resolver: - name: default type: c-ares server: 127.0.0.1 escaper: - name: squid type: proxy_http proxy_addr: host.docker.internal:10000 no_ipv6: true resolver: default resolve_strategy: IPv4OnlyI built a docker image and I run it like this (my cwd is the manifest file dir):
docker run -p 13128:13128 -v ./:/etc/g3proxy/config/ g3proxy -v -c /etc/g3proxy/config/g3proxy.yaml # Aug 18 01:17:41.565 INFO started SocksProxy SRT[socks_v1#0] <g3_daemon::listen::tcp(tcp.rs:71)> # Aug 18 01:17:41.565 INFO started HttpProxy SRT[http_v1#0] <g3_daemon::listen::tcp(tcp.rs:71)>
You can also set log: stdout in the main yaml config to see task logs, and you can add more -v to g3proxy command line to see more debug logs.
When i try to proxy (from the host, outside the container):
curl -v -x localhost:13128 ipinfo.ioI get
* Host localhost:13128 was resolved. * IPv6: ::1 * IPv4: 127.0.0.1 * Trying [::1]:13128... * Connected to localhost (::1) port 13128 > GET http://ipinfo.io/ HTTP/1.1 > Host: ipinfo.io > User-Agent: curl/8.7.1 > Accept: */* > Proxy-Connection: Keep-Alive > * Request completely sent off < HTTP/1.1 530 Origin DNS Error < Content-Type: text/html < Content-Length: 148 < Connection: Close < <html> <head><title>530 Origin DNS Error</title></head> <body> <div style="text-align: center;"><h1>530 Origin DNS Error</h1></div> </body> </html> * Closing connectionAs you can see, I'm trying to forward proxy from g3proxy (port 13128) to the backend http proxy (port 10000).
I can exec into the g3proxy container and
curl -x host.docker.internal:10000 ipinfo.iosuccessfully.
What's the resolved address for host.docker.internal? The 530 error response tells that this domain can't be resolved by 127.0.0.1:53.
I think the technical side of the docs are great but they do lack some prose. Squid's wikis are a great example.
Here's what I need for a production setup:
- Logging: assuming user:pass@host access, I must log
user, bytes sent, bytes received- Auth: I love squid's approach
You can find the logging/metrics format and the detailed configuration in dir g3proxy/doc, and you can use sphinx to generate html files, then it will be a bit easier to read.
Notes:
- no caching
Yes there is no caching. You can archive this by using a caching ICAP server.
- acl? do i need to worry about that? it's going to be hosted in k8s and exposed both externally as a NodePort service (to the internet) and internally as a ClusterIP.
Check the configuration doc and you will find options at server / user level.
Could you please help me out with a proper manifest file?
- Http proxy from 13128 to 10000 (this will eventually be in the same pod with the app container; right now testing on docker locally)
The one you pasted is OK as long as you set a correct resolver.
- Logging with the format described
- Sensible easy auth
Just add a user-group to the main yaml config file, you can found examples in https://github.com/bytedance/g3/tree/master/g3proxy/examples/hybrid_user_auth/user-group.d, which use a file as a dynamic source.
If you guys can get the docs in a human-readable state so people can get things done quickly this is gonna take over.
You can check the user guide first, and then use the sphinx generated html docs as a reference. It will be appreciated if you can help us to improve the docs.
NinoSkopac
zh-jq-b
I haven’t been able to get a forward proxy working yet. I’m trying to proxy to a http proxy (not squid, it’s a custom app coded in Go).
This is my manifest (adopted from squid example):
I built a docker image and I run it like this (my cwd is the manifest file dir):
When i try to proxy (from the host, outside the container):
I get
As you can see, I'm trying to forward proxy from g3proxy (port 13128) to the backend http proxy (port 10000).
I can exec into the g3proxy container and
curl -x host.docker.internal:10000 ipinfo.iosuccessfully.I think the technical side of the docs are great but they do lack some prose. Squid's wikis are a great example.
Here's what I need for a production setup:
user, bytes sent, bytes receivedNotes:
Could you please help me out with a proper manifest file?
This would greatly expedite my journey.
As always, Kind regards and have a great day, dear team behind this incredible piece of software.
Oh, and btw, memory consumption on this thing in Docker? Right now it's 9MB! That's more than 15x less than the good old Squid. If you guys can get the docs in a human-readable state so people can get things done quickly this is gonna take over.
Amazing work.
Nino