Opened 4 years ago

Last modified 4 years ago

#2086 open defect

Allow manual configuration of outproxy host/port/proxy type for HTTP(S) client tunnel

Reported by: Reportage Owned by:
Priority: minor Milestone: undecided
Component: apps/i2ptunnel Version: 0.9.32
Keywords: i2p http tunnel, web browsing, proxy Cc:
Parent Tickets: Sensitive: no


I2P detects Orchid and uses it to relay http traffic outside the network.
It would be useful to expose more options in the http client proxy tunnel,
in similar vein to the recent improvements in the console reseeding
configuration. This would allow the use of a custom proxy service, for example
Tor, rather than limiting the user to the orchid java plugin.

  • proxy host
  • proxy port
  • proxy type
  • user/pass authorization


Change History (2)

comment:1 Changed 4 years ago by zzz

Status: newopen

This could be a very simple plugin. That might be a good way to start to see if there's any demand.

comment:2 Changed 4 years ago by Reportage

As a related proposal, with support for nominating a custom proxy service, specifically Tor, baked into the console, adding .onion address support to SusiDNS in a separate addressbook would be an interesting idea and could potentially attract more Tor users to I2P by providing a viable, locally controlled dns type service currently absent in the Tor sphere.

Last edited 4 years ago by Reportage (previous) (diff)
Note: See TracTickets for help on using tickets.