Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chained proxy #95

Open
mahdi-ln opened this issue May 7, 2019 · 7 comments
Open

chained proxy #95

mahdi-ln opened this issue May 7, 2019 · 7 comments

Comments

@mahdi-ln
Copy link

mahdi-ln commented May 7, 2019

It consider / as a part of Provider id

$ python3 lthnvpnc.py connect 579234f94d61626b3af456bdad83ee17bfbd9e4d8ee433633d753a50df41e066/1A//localhost:6544
/home/m/.local/lib/python3.6/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.2) or chardet (3.0.4) doesn't match a supported version!
  RequestsDependencyWarning)
INFO:audit:action=START,type=SERVICE,obj=lthnvpnc,
ERROR:lthnvpnc:Provider id 579234F94D61626B3AF456BDAD83EE17BFBD9E4D8EE433633D753A50DF41E066/1A/ does not exists!
@pallas1
Copy link
Contributor

pallas1 commented May 7, 2019

Ok, but why are you using two slashes?

@mahdi-ln
Copy link
Author

mahdi-ln commented May 7, 2019

@mahdi-ln
Copy link
Author

mahdi-ln commented May 7, 2019

My problem solved using other method

@limosek
Copy link
Contributor

limosek commented May 7, 2019

Sorry, advanced chaining is not supported yet. We need to update documentation.
If you want to use chaining, please refer to https://github.com/LetheanMovement/lethean-vpn/blob/master/CLIENT.md#chaining

lthnvpnc --fork-on-connect connect provider1/serviceid1 --proxy-port 7777 &&
lthnvpnc connect provider2/serviceid2 --https-proxy-host 127.0.0.1 --https-proxy-port 7777

@ronnylov
Copy link

For chaining to work, the port used for the second proxy server must be open in squid.conf on the first proxy? I don't use port 8080 on most of my exit nodes but only have port 80, 443 and 8080 open in squid.conf (actually in tinyproxy which I use but anyway). I have not tested chaining yet.

@limosek
Copy link
Contributor

limosek commented May 12, 2019

This is client part. It has nothing to do with your squid.conf. First command will connect to remote node and force listenning port for incomming proxy requests to port 7777.
Second command will use local proxy port as outbound proxy, connect to second provider and force listening for proxy requests on port 7777.

Now, if you use 127.0.0.1:8186 (default proxy port of second dispatcher), you will be routed thru chained mode.

@ronnylov
Copy link

ronnylov commented May 15, 2019

Interesting. Then port 7777 must be open on exit node firewalls?
We need to document which ports must be opened.
Hmmm, ports are stored in sdp so 7777 is only internally tunneled port?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants