There are situations where some application can interact or work only with http proxy but in corporate world you might need to use socks proxy to work with VPN set up.
To work around with, I found a good proxy client which will act as http proxy for socks dynamic port forwards.
To be simple
If you want to redirect all your http proxy traffic through your socks proxy, you can use privoxy (Can be installed with command like yum install privoxy)
privoxy looks into a file called config in the current directory to know where the socks proxy set it up.
General config will be something like this if you open dynamic port using command (ssh -D *:15998 corporateMachine@corporateNetwork.com)
forward-socks5 / localhost:15998 .
Now just issue command like below to run privoxy in background
Thats all, any http proxy call would redirect through the above socks proxy
For example, if you want your wget to go through socks proxy then just run below in your terminal and then issue wget
export http_proxy='http://localhost:8118'
Here you can not use any other port than 8118 :)
Ref: https://snaek.org/blog/2012/11/25/Making-git-svn-work-over-SSH-tunnel,-SOCKS-proxy-%26-HTTP-proxy/
To work around with, I found a good proxy client which will act as http proxy for socks dynamic port forwards.
To be simple
If you want to redirect all your http proxy traffic through your socks proxy, you can use privoxy (Can be installed with command like yum install privoxy)
privoxy looks into a file called config in the current directory to know where the socks proxy set it up.
General config will be something like this if you open dynamic port using command (ssh -D *:15998 corporateMachine@corporateNetwork.com)
forward-socks5 / localhost:15998 .
Now just issue command like below to run privoxy in background
Thats all, any http proxy call would redirect through the above socks proxy
For example, if you want your wget to go through socks proxy then just run below in your terminal and then issue wget
export http_proxy='http://localhost:8118'
Here you can not use any other port than 8118 :)
Ref: https://snaek.org/blog/2012/11/25/Making-git-svn-work-over-SSH-tunnel,-SOCKS-proxy-%26-HTTP-proxy/
