From ec8b62e099ea427f5bfb87f1cb6b76ec6df11329 Mon Sep 17 00:00:00 2001 From: Jack Ivanov Date: Mon, 24 Oct 2016 19:16:34 +0400 Subject: [PATCH] Update README.md #105 --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 4cc8473..d3372f7 100644 --- a/README.md +++ b/README.md @@ -67,7 +67,10 @@ Depending on the platform, you may need one or multiple of the following files. If you turned on the optional SSH tunneling role, then local user accounts will be created for each user in `config.cfg` and an SSH authorized_key file will be in the `config` directory (user.ssh.pem). SSH user accounts do not have shell access and their tunneling options are limited. This is done to ensure that users have the least access required to tunnel through the server. -Make sure to access the server using 'ssh -N' with these limited accounts. +Make sure to access the server using 'ssh -N' with these limited accounts. +In order to make a tunnel you have to run this command: +`ssh -D 127.0.0.1:1080 -f -q -C -N user@ip -i configs/ip_user.ssh.pem` +Don't forget to change `ip` and `user`. And then you can configure your browsers to use 127.0.0.1:1080 as sock4/5 ## Adding or Removing Users