Opened 9 years ago
Last modified 20 months ago
#648 assigned enhancement
outbound (proxy) node support
| Reported by: | l4t3r | Owned by: | sadie |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | router/transport | Version: | 0.9 |
| Keywords: | peer-selection anti-censorship | Cc: | |
| Parent Tickets: | #1097, #2472 | Sensitive: | no |
Description
Allow client to configure outbound (proxy) node. The similar
functionality is already implemented by Tor and it gives possibility
to select several low-latency peers to improve performance.
This might be handy for nodes in corporate networks with restricted or no internet access.
Subtickets
Change History (7)
comment:1 Changed 9 years ago by
| Component: | unspecified → router/transport |
|---|---|
| Owner: | set to zzz |
comment:2 Changed 9 years ago by
Primary request is to relay all the traffic through several, manually selected (trusted) peers. Let's say, we have one edge I2P node, with both WAN and LAN links, and large LAN network with nodes, connecting to the rest of I2P network via this node, though all interconnection happens within LAN segment without relay.
HTTP Proxy / Socks proxy would be good addition, but this is rather bonus.
comment:3 Changed 9 years ago by
This is one use case for a feature we call "restricted routes", which has been on the far, far, far distant roadmap since the beginning of I2P 9 years ago. It's no closer now.
See http://www.i2p2.i2p/todo and http://zzz.i2p/topics/114
It's quite complex, as there are a lot of possible use cases, and a lot of options on how to do it.
comment:4 Changed 8 years ago by
| Parent Tickets: | → 1097 |
|---|
comment:5 Changed 7 years ago by
| Keywords: | peer-selection anti-censorship added |
|---|
comment:6 Changed 3 years ago by
| Parent Tickets: | 1097 → 1097, 2472 |
|---|
comment:7 Changed 20 months ago by
| Owner: | changed from zzz to sadie |
|---|---|
| Sensitive: | unset |
| Status: | new → assigned |
overall outproxy ticket is #2472
Are you asking for ability to use an HTTP proxy to transport all I2P traffic through a corporate firewall? Or some other type of proxy?
Or do you want to connect using the standard I2P transport protocols, but only to one (or a few) peers who will relay all the traffic? This is what we call "restricted routes".