Open mahdi-ln opened 5 years ago
Ok, but why are you using two slashes?
My problem solved using other method
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
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.
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.
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?
It consider / as a part of Provider id