tor2web is an HTTP proxy, it takes in requests for "foo.tld" and makes a corresponding request to "foo.onion" over Tor and provides back the response. It's important to note that it makes a corresponding request, it doesn't just take in an arbitrary TCP stream and forward it on for you, it's looking for a well formed HTTP request to make on your behalf.
The problem was the server was hosted on a non-standard ssh port (2022).
Use the LongLivedPorts to add your port in your torrc and make more stable connections for certain ports
If the ssh server is a hidden service, 22 127.0.0.1:2022 in your torrc will redirect this to a port in LongLivedPorts
You need a Stunnel with full verification enabled (verify=3 in config) and your local SSL microCA. For microCA I do recommend you to try either an OpenSSL perl scripts, or easyRSA as something more advanced.
See I2P's comparison page.
Packet switched instead of circuit switched
implicit transparent load balancing of messages across multiple peers, rather than a single path
resilience vs. failures by running multiple tunnels in parallel, plus rotating tunnels
scale each client's connections at O(1) instead of O(N) (Alice has e.g. 2 inbound tunnels that are used ...
The pro's of i2p is that in the tunnel-model it's possible to make a "garlic routing", but they're not implemented it yet in full scale. it will make possible to transmit multiple tunnel's packets in one "package". And I2P uses local site-naming directories rather one distributed one in Tor. Basically - except a tech deep-sea details - there's the main ...
In my opinion, the simplest way is to buy a safeplug box. https://pogoplug.com/safeplug
The box acts as a proxy for your computer to talk to Tor. What you need to do is to configure your computer to re-direct all connections to Safeplug.
P/s: Safeplug uses Privoxy as and proxy to talk to Tor. So if you are capable of configure Privoxy within your PC to talk ...