loveisgrief/i2p-docker-proxy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
54 Commits 2 Branches 0 Tags
177a4ad5f7d3ef5ce71a0e09cee832f08ae73725
Commit Graph

5 Commits

Author SHA1 Message Date
LoveIsGrief
177a4ad5f7 cli: Rename the env vars for the params 
It also shortens the command-line argument in exec.sh

#4 - Investigate extending pr0xy to use SAM
 2020-12-13 20:19:58 +01:00
LoveIsGrief
8026c04a7b Actually pass ip_dict to FakeResolver 
It wasn't being passed so the client tunnel would just fail

#4 - Investigate extending pr0xy to use SAM
 2020-12-13 20:18:29 +01:00
LoveIsGrief
77c2a69267 cli: Convert port params to int 
Otherwise strings are passed and it can't start up.
Sockets can't be created when a string is passed as the port param

#4 - Investigate extending pr0xy to use SAM
 2020-12-13 17:29:57 +01:00
LoveIsGrief
0c4a9a81e3 Actually pass port param to transparent proxy 
It was always starting on port 1234 when in fact, it had to start on 10080 (set in Dockerfile)

#4 - Investigate extending pr0xy to use SAM
 2020-12-13 17:28:49 +01:00
LoveIsGrief
3ea2f2a453 First implementation of transparent client tunnel using SAM 
The transparent proxy creates a client tunnel to the requested destination for each client connection.
This is untested for now, but a server tunnel is also incoming if this works well.

#4 - Investigate extending pr0xy to use SAM
 2020-12-13 00:09:17 +01:00