Opened 9 years ago

Closed 9 years ago

#899 closed defect (invalid)

SOCKS5 Ports

Reported by: DISABLED Owned by:
Priority: minor Milestone:
Component: apps/i2ptunnel Version: 0.9.4
Keywords: Cc:
Parent Tickets: Sensitive: no


Relevant log line:
ERROR i2ptunnel.socks.SOCKS5Server: No outproxy configured for port XXXX and no default configured either

My setup is a SOCKS 4/4a/5 proxy client I2PTunnel, I have no outproxies set, and I have the following custom option:

Upon my client trying to connect to clearnet.tld with the I2P SOCKS proxy I created ("SOCKS5"), the "connection not allowed by ruleset" is thrown (referring to SOCKS5). If I use Tor's MapAddress? functionality with the following line, I have no issues and connectivity is OK.

MapAddress? clearnet.tld xxx.onion


Change History (1)

comment:1 Changed 9 years ago by str4d

Component: unspecifiedapps/i2ptunnel
Milestone: 0.9.5
Resolution: invalid
Status: newclosed

This could be seen as a deficiency in the way I implemented IP mapping in the I2P SOCKS tunnel, but this usecase is not technically valid as it is not an IP mapping :P

I implemented IP mapping because I2P does not have a pseudo-DNS server like Tor does (this would be a very useful feature, incidentally). If a client is SOCKS-aware then it can use the standard SOCKS5 protocol (via the DOMAINNAME AddressType) to connect to .i2p addresses directly. For clients that are not SOCKS-aware, IP mapping enables them to be proxified with e.g. proxychains (without IP mapping, the client would attempt DNS resolution which would fail).

So if your client supports SOCKS5 then just use the .i2p address directly within it. If it doesn't, then use the IP mapping as implemented and use an IP address in your proxified client.

Note: See TracTickets for help on using tickets.