<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Use your Linux server as a proxy (SSH Tunnel + SOCKS Proxy Forwarding)	</title>
	<atom:link href="https://www.binarytides.com/linux-ssh-socks-proxy/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.binarytides.com/linux-ssh-socks-proxy/</link>
	<description>News, Technology, Entertainment and more</description>
	<lastBuildDate>Thu, 29 Dec 2016 09:39:09 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.2</generator>
	<item>
		<title>
		By: proxy list txt 2016		</title>
		<link>https://www.binarytides.com/linux-ssh-socks-proxy/comment-page-1/#comment-101381</link>

		<dc:creator><![CDATA[proxy list txt 2016]]></dc:creator>
		<pubDate>Thu, 29 Dec 2016 09:39:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/?p=7732#comment-101381</guid>

					<description><![CDATA[An anonymous proxy also does not show a true IP address, but does modify 
the request fields, creating it straightforward to detect via log 
evaluation that the user is making use of a proxy.]]></description>
			<content:encoded><![CDATA[<p>An anonymous proxy also does not show a true IP address, but does modify<br />
the request fields, creating it straightforward to detect via log<br />
evaluation that the user is making use of a proxy.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: GNU-FTW		</title>
		<link>https://www.binarytides.com/linux-ssh-socks-proxy/comment-page-1/#comment-76855</link>

		<dc:creator><![CDATA[GNU-FTW]]></dc:creator>
		<pubDate>Tue, 10 May 2016 13:49:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/?p=7732#comment-76855</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.binarytides.com/linux-ssh-socks-proxy/comment-page-1/#comment-76853&quot;&gt;GNU-FTW&lt;/a&gt;.

What I forgot to add is, if the server is only listening on the loopback address you wont be able to connect to it from another computer.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.binarytides.com/linux-ssh-socks-proxy/comment-page-1/#comment-76853">GNU-FTW</a>.</p>
<p>What I forgot to add is, if the server is only listening on the loopback address you wont be able to connect to it from another computer.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: GNU-FTW		</title>
		<link>https://www.binarytides.com/linux-ssh-socks-proxy/comment-page-1/#comment-76853</link>

		<dc:creator><![CDATA[GNU-FTW]]></dc:creator>
		<pubDate>Tue, 10 May 2016 13:45:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/?p=7732#comment-76853</guid>

					<description><![CDATA[Great article, thanks for sharing. 
But to the command you should add the listening address, because by default is going to listen only at the loopback address (127.0.0.1).

In this example, I use the port 50000

With the OP way: 
Command: ssh -D 50000 user@localhost

Actual listening port and address

netstat -ntpl &#124; grep 50000
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 127.0.0.1:50000         0.0.0.0:*               LISTEN      9838/ssh
tcp6       0      0 ::1:50000               :::*                    LISTEN      9838/ssh

With the other way
Command: ssh -D 0.0.0.0:50000 user@localhost

Actual listening port and address

netstat -ntpl &#124; grep 50000
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 0.0.0.0:50000           0.0.0.0:*               LISTEN      9878/ssh]]></description>
			<content:encoded><![CDATA[<p>Great article, thanks for sharing.<br />
But to the command you should add the listening address, because by default is going to listen only at the loopback address (127.0.0.1).</p>
<p>In this example, I use the port 50000</p>
<p>With the OP way:<br />
Command: ssh -D 50000 user@localhost</p>
<p>Actual listening port and address</p>
<p>netstat -ntpl | grep 50000<br />
(Not all processes could be identified, non-owned process info<br />
 will not be shown, you would have to be root to see it all.)<br />
tcp        0      0 127.0.0.1:50000         0.0.0.0:*               LISTEN      9838/ssh<br />
tcp6       0      0 ::1:50000               :::*                    LISTEN      9838/ssh</p>
<p>With the other way<br />
Command: ssh -D 0.0.0.0:50000 user@localhost</p>
<p>Actual listening port and address</p>
<p>netstat -ntpl | grep 50000<br />
(Not all processes could be identified, non-owned process info<br />
 will not be shown, you would have to be root to see it all.)<br />
tcp        0      0 0.0.0.0:50000           0.0.0.0:*               LISTEN      9878/ssh</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
