Tag Info

Hot answers tagged

9

It sounds to me like you need a socks client, or a ssh client that understand socks. -D is for ssh to be a socks server/proxy. You could use ssh under tsocks, or another SOCKS wrapper. Or use ssh's ProxyCommand in conjunction with socat or nc -X: ssh -o ProxyCommand='socat - socks:B:%h:21,socksport=1080' C To have a HTTP proxy that uses the SOCKS server ...


8

Just found a new solution for this recently that is REALLY neat. Take a look at sshuttle. https://github.com/apenwarr/sshuttle/


6

As pointed out by enzitib,tsocks can be used to use a SOCKS proxy with yum. To be more detailed, one can use it like this: $ export TSOCKS_CONF_FILE=$HOME/.tsocks.conf $ cat .tsocks.conf server = 127.0.0.1 server_port = 1080 $ tsocks yum ... By default tsocks uses SOCKS version 4 - but you can configure 5 via the 'server_type' directive. For ...


5

First, you need tun2socks (often a part of the 'badvpn' package). tun2socks sets up a virtual interface which you can route traffic through, and that traffic will get sent through the target socks proxy. Setting it up gets a little tricky as you only want to route certain traffic through the tunnel. This script should do what you want: #!/bin/bash ...


5

Do you know flossmanuals.net? They've got a great manual on How to Bypass Internet Censorship (also as epub and pdf for offline use -- and note the translations, among others in Farsi). Among many tools and methods, they cover SOCKS proxies. But given a VPS somewhere, the other ways they mention should be considered, too. (For example how to use ssh to ...


5

I am showing you a very basic way to do it. Here I am assuming that B is directly accessible from A. There may be variations according to various situations. On A: ssh -D socks_port B This will open up the port socks_port on A as a SOCKS proxy. On your system: ssh -L local_port:localhost:socks_port A This will forward local_port on your system to ...


4

You'll need to install and configure an actual SOCKS server on the server, such as Dante, SS5, Delegate or Srelay.


4

So, if I understand correctly, you can ssh from machine 1 to machine 2 but not from your laptop (from which you can ssh to machine 1). So you'd like to have a socks server on machine 1 and use it from your laptop? So looks like all you need is port forward that 8080: run on your laptop: ssh -nL 8080:localhost:8080 machine1 ssh -C2qnN -D 8080 ...


4

How about using two different configuration files for tsocks? According to this manpage, tsocks will read its configuration from the file specified in the TSOCKS_CONF_FILE environment variable. So you could split your tsocks.conf to tsocks.1081.conf and tsocks.1082.conf and then do something like this (bash syntax): $ ...


4

SOCKS5 is a protocol (i.e. in the application layer of OSI), so plain network-routing (e.g. via iptables) alone won't do. (It's probably necessary, but not sufficient.) What you need is a proxifier. Without having tried it, tun2socks, allowing you to "socksify TCP at the network layer", looks promising (as does proxychains, without iptables but prefixing ...


4

With: socat tcp-listen:12345,reuseaddr,fork,bind=127.1 socks:218.62.97.105:11.11.11.11:3128,socksport=1080 you will have a socat waiting for TCP connections on port 12345 on the loopback interface, and forward them to 11.11.11.11:3128 by way of the socks server on 218.62.97.105:1080 You can then use that to connect to D: ssh -o ProxyCommand='socat - ...


3

Here is how it does it: static int getdestaddr_iptables(int fd, const struct sockaddr_in *client, const struct sockaddr_in *bindaddr, struct sockaddr_in *destaddr) { socklen_t socklen = sizeof(*destaddr); int error; error = getsockopt(fd, SOL_IP, SO_ORIGINAL_DST, destaddr, &socklen); if (error) { ...


3

The -D option enables a SOCKS4/5 server. It is not identical to an normal HTTP/FTP-proxy and need therefore to be interfaced differently. A lot of browser support SOCKS proxies, but usually not via a http_proxy/ftp_proxy environment variable. You can wrap programs, which do not support SOCKS directly, with tsocks. See also ...


3

The tsocks application can socksify every other applications tsocks app args


2

I get the same result, and looking at the strace output, it tries to connect to URL_HOST directly. However if I use curl -x socks5://SOCKS_SERVER:1080 "THE_URL_FROM_BROWSER" It does work as expected (use socks4a or socks5h to have hostnames resolved by the proxy, if supported)


2

Youtube-dl doesn't support a SOCKS proxy. There's a feature request for it, with links to a couple of working proposals. Youtube-dl supports HTTP proxies out of the box. To benefit from this support, you'll need to run a proxy on myserver.com. Pretty much any lightweight proxy will do, for example tinyproxy. The proxy only needs to listen to local ...


2

According to this ticket (and that one),you need to decide what to proxy: connections to the tracker or all connections (including the ones to peers): Proxying tracker connections can be done using the patch mentioned here or using something like Polipo, mentioned here Proxying everything can be done, as you already tried, using socksifiers like tsocks, ...


2

I use tsocks for this purpose. It's a wrapper that catches all connects and forwards them according to your tsocks.conf file. For instance: server = 127.0.0.1 server_type = 5 server_port = 1338 Where as you already have a ssh-proxy set on localhost port 1338. Using this method, you can nest connections since the next ssh session running in the tsocks ...


2

A possibility could be to download whatever you need from your client and then send those files by scp to your server if it accept scp. scp file_to_send user@server_ip:/location_of_the_file I don't know if what your asking is possible as your server has no acces to the client.


2

That's about it, but you've inverted home and office. The point is that the office firewall rejects outgoing connections other than web traffic. But since HTTPS traffic and SSH traffic are both encrypted, it can't easily distinguish between them, so the firewall just blocks outgoing connections to ports other than 443 (the standard HTTPS port) and probably ...


1

I am not entirely clear on what the post talks about but I have been using something similar to redirect the http traffic over ssh from a remote server which does not support X forwarding. I do it as follows: ssh -L23000:localhost:23000 user@remotehost [remotehost] $ python -m SimpleHTTPServer 23000 Open browser on localhost and point it to ...


1

You should use telnet in order to check if the port forwarding works: telnet localhost 1234 It's probably not working as you use the wrong SSH options (twice): ssh -L localhost:1234:remoteip:5634 user@remoteip or (depending on it on which interface(s) the server is listening: ssh -L localhost:1234:localhost:5634 user@remoteip


1

Go to 'Applications' tab at the right select 'System Tools' click on 'YaST' enter the root password and then you will find an icon 'proxy' click on it and complete the form. Hope this help you. greetz, Tony


1

I suspect mailx is configured to use sendmail so tsocks is redundant here. What happens if you omit it? tsocks may actually be in the way - if you don't have a rule in /etc/tsocks.conf to bypass the proxy for the loopback interface it could send the message to the proxy when it shouldn't.


1

You could install something like Srelay, a free Socks proxy server software for Linux: http://socks-relay.sourceforge.net/


1

You can create a long-running SSH connection on the server to itself using ssh user@localhost -D 0.0.0.0:1234. You can create a script that verify if this command is running and put it on crontab to ensure if the connection fails for some reason it'll restart the job.


1

Below configuration will enforce authentication: internal: eth0 port = 53200 internal: 127.0.0.1 port = 53200 external: eth0 method: username user.privileged: root client pass { from: 0.0.0.0/0 to: 0.0.0.0/0 log: error # connect disconnect } pass { from: 0.0.0.0/0 to: 0.0.0.0/0 protocol: tcp udp log: error # connect disconnect }


1

something like following path { reaches = 10.132.165.95/255.255.0.0 server = 127.0.0.1 server_type = 5 server_port = 1084 }


1

You can build VPN-like tunnels with SSH. The concept is essentially, connect your external network interface via ssh to some target machine. Create an internal only network interface. Change routing so that all traffic goes over the internal interface and hence out via the external tunnel. Here's one tutorial, ...


1

I think Fedora packages tsocks, which works similarly.



Only top voted, non community-wiki answers of a minimum length are eligible