Add port demultiplexing support to standard server tunnel

[zzz]

​http://forum.i2p/viewtopic.php?t=10767

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.

[zzz]

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

[zzz]

Support added to standard and IRC client tunnels in 0.9.8.1-8 3ddedb08de8709fb784e8557b80feefe0d1ddf8a

Server side still to-do.

[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 example.com port 1234, set custom option (bottom of i2ptunnel edit page) targetForPort.9999=example.com:1234 . You may use localhost or an IP instead of example.com. 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 0.9.8.1-9 soon.

I have no plans to add a GUI for this.

[zzz]

As above. 0.9.8.1-9 e78a493fc5a7bd52556193f0393e0d92bc97f981

[killyourtv]

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