I2P support forum

Pluggable Transports (PTs) were developed by Tor as a way to add obfuscation transports to Tor bridges in a modular way.

I2P already has a modular transport system that decreases the barrier to adding alternative transports. Adding support for PTs would provide I2P with an easy way to experiment with alternative protocols, and get ready for blocking resistance.

Previous thread: http://zzz.i2p/topics/1551

I tried to use Tor's pluggable transports recently, I couldn't really get it to work. Documentation either isn't up-to-date and/or hard to find. Seemed to be dependent on me finding/installing/configuring and setting up configuration settings in Tor; which is not easy to do without proper documentation or guides.

Having pluggable transports in I2P would be good.
Would it be possible to use traffic obfuscation techniques with pluggable transports to have some "hidden" reseeds on networks where direct access to reseeds is blocked?

Hi!

Maybe it's possible to migrate meek PT to i2p.

This technique can help Chinese new users to reseed.

Another suggestion: when an old user has few peers known, there's no need to visit clearnet reseed servers through the outproxy. It would be better(maybe safer) to set up a few reseed servers inside i2p.

How do you like it?

PT in I2P would be for a TCP transport. It was never intended for reseed.
Our focus right now is NTCP2, which should be as good as PT.
We implemented reseed proxies a couple of releases ago to help users in China.
In-net reseed is hard. If you need to reseed, you probably can't connect in-network.

Yes, you are right about NTCP2.(I really look forward to it!)

But I think if a person needs to reseed, and he can't connect to most of the eepsites, it would be also hard to connect to false.i2p. So more choices means more chances(to reconnect to the network).

Hi

reseed proxy in kind of SOCKS or http proxy to be setup, like http proxy in browser are supported now for reseed.


echelon