Skip to content
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

Open
o0nd7ots opened this issue Dec 1, 2023 · 10 comments
Open

Question: I2Pd and SOCKS #1986

o0nd7ots opened this issue Dec 1, 2023 · 10 comments

Comments

@o0nd7ots
Copy link

o0nd7ots commented Dec 1, 2023

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)

Destination v4 v4a v5
I2P useless works works
clearnet works probably1 to be implemented

Footnotes

  1. This is based on majestrate's statement

@Vort
Copy link
Contributor

Vort commented Dec 1, 2023

Both SOCKS 4a and SOCKS 5 are fine for accessing internal addresses with 127.0.0.1:4447.

@o0nd7ots
Copy link
Author

o0nd7ots commented Dec 1, 2023

Thanks. Do you know about outproxy traffic and v4 for internal?

Also, where could I find this?

@Vort
Copy link
Contributor

Vort commented Dec 1, 2023

I2P do not have IP addresses for internal resources.
That's why SOCKS 4 (without a) makes no sense.

Do you know about outproxy traffic

I did not tested outproxies.
But I heard that developers want to fix SOCKS support for them.
It's like plans for indefinite future.

@orignal
Copy link
Contributor

orignal commented Dec 5, 2023

SOCK4 for outproxy now, SOCK5 will be implemented later

@o0nd7ots
Copy link
Author

o0nd7ots commented Dec 5, 2023

@orignal
Thanks. Does 4a work?

@orignal
Copy link
Contributor

orignal commented Dec 5, 2023

I don't know. Better to ask @majestrate

@majestrate
Copy link
Contributor

@orignal Thanks. Does 4a work?

probably.

@o0nd7ots
Copy link
Author

o0nd7ots commented Dec 6, 2023

If this is the best we can get then this issue can be closed.
I will try to work that info in to the documentation/readme.

@Alfa21tpp
Copy link

if it can be of any use, in my privoxy configuration I use this:
forward-socks4a .i2p 127.0.0.1:4447 .
so v4a is verified, imo

@orignal
Copy link
Contributor

orignal commented Feb 21, 2024

Yes, incoming socks4 works, the recent change is about upstream proxy only

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants