-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Comments
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. lthnvpnc --fork-on-connect connect provider1/serviceid1 --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. 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? |
It consider / as a part of Provider id
The text was updated successfully, but these errors were encountered: