Opened 8 years ago

Closed 7 years ago

#1066 closed enhancement (fixed)

Add port demultiplexing support to standard server tunnel

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



Copy demux code from HTTP server tunnel.

UI instead of advanced options would be a bonus.

Combining standard and HTTP or IRC would be a lot harder.


Change History (7)

comment:1 Changed 8 years ago by zzz

To be useful, this also requires a dest port backend config and UI in Standard Client Tunnel.

comment:2 Changed 8 years ago by zzz

Owner: set to zzz
Status: newaccepted

Support added to standard and IRC client tunnels in 3ddedb08de8709fb784e8557b80feefe0d1ddf8a

Server side still to-do.

comment:3 Changed 8 years ago by zzz


Here's the way it's going to work on the server side (on standard, IRC, and HTTP server tunnels)

To forward traffic for incoming I2P port 9999 to server port 1234, set custom option (bottom of i2ptunnel edit page) . You may use localhost or an IP instead of For HTTP servers you will probably also want to set spoofedHost.9999=example.i2p to get the hostname right to keep the webserver happy (this is an existing feature).

Traffic for any incoming port of 0 or a port not configured in custom options will go to the default target host and port set at the top of the i2ptunnel edit page, as it does now.

To be checked in as soon.

I have no plans to add a GUI for this.

comment:5 Changed 8 years ago by killyourtv

This looks very nice. I'll test it $SOON.

comment:6 Changed 8 years ago by killyourtv

Status: acceptedtesting

comment:7 Changed 7 years ago by zzz

Resolution: fixed
Status: testingclosed
Note: See TracTickets for help on using tickets.