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
Question: I2Pd and SOCKS #1986
Comments
Both SOCKS 4a and SOCKS 5 are fine for accessing internal addresses with |
Thanks. Do you know about outproxy traffic and v4 for internal? Also, where could I find this? |
I2P do not have IP addresses for internal resources.
I did not tested outproxies. |
SOCK4 for outproxy now, SOCK5 will be implemented later |
@orignal |
I don't know. Better to ask @majestrate |
probably. |
If this is the best we can get then this issue can be closed. |
if it can be of any use, in my privoxy configuration I use this: |
Yes, incoming socks4 works, the recent change is about upstream proxy only |
Original question
What versions of SOCKS does I2Pd support, both for staying within the anonymity network and outproxy?
The default config leads be to believe that for outproxy only 4 is supported (not even 4a).
The issues make me believe that for internal traffix 5 is okay.
I did not know where to look for documentation for this.
What does work (summary)
Footnotes
This is based on majestrate's statement ↩
The text was updated successfully, but these errors were encountered: