i2pd go through proxy

[bingmatv]

How to let i2pd go through a proxy, maybe socks5 proxy? The question is not to set my web browser to go through i2pd, but to let i2pd go through proxy.

[Vort]

With ntcp2.proxy probably.
https://i2pd.readthedocs.io/en/latest/user-guide/configuration/#ntcp2

[orignal]

maybe socks5 proxy

Maybe Tor specifically?

[bingmatv]

Maybe Tor specifically?

Some other programs also use socks5, e.g, shadowsocks, oilelpqt, V2Ray.

[bingmatv]

With ntcp2.proxy probably. https://i2pd.readthedocs.io/en/latest/user-guide/configuration/#ntcp2

Does it require the socks5 proxy support UDP fragments? I'm unsure how socks5 forwards UDP. I tried my self-made proxy to understand socks5 protocol, since I'm unsure how to correctly forward UDP so my self-made proxy failed to forward I2P traffic. But it seems that TCP streams are correctly forwarded, only UDP doesn't work.

[Vort]

NTCP2 uses TCP, while SSU2 uses UDP.
For UDP support you may try ssu2.proxy option instead.
However, I do not see why it may be needed.
If NTCP2 works fine, it is totally enough for proper functioning of i2pd.

[orignal]

Some other programs also use socks5, e.g, shadowsocks, oilelpqt, V2Ray.

For shadowsocks you can also configure SSU2 through a proxy. Tell me what you need and I will provide a config example.

[bingmatv]

I'm curious about Page 8 of socks5 RFC, it has FRAG (fragment) field, DST.ADDR and DST.PORT for address and port. If the socks5 server accepted a UDP ASSOCIATE command with fragments, the FRAG counts from 1 and ends at 127. When FRAG is still between 1 and 127, either DST.ADDR or DST.PORT has been changed, should the client reset FRAG to 1? Or just accumulate FRAG again for any different DST.ADDR and DST.PORT?

[orignal]

i2pd always sets zero to this field