<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Andryan's Random Notes &#187; FTP</title>
	<atom:link href="http://blog.nirkabel.org/category/ftp/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nirkabel.org</link>
	<description>This blog is here to stay</description>
	<lastBuildDate>Fri, 20 Jan 2012 03:17:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>iptables port forwarding rules for BattleNET games</title>
		<link>http://blog.nirkabel.org/2007/05/22/iptables-port-forwarding-rules-for-battlenet-games/</link>
		<comments>http://blog.nirkabel.org/2007/05/22/iptables-port-forwarding-rules-for-battlenet-games/#comments</comments>
		<pubDate>Tue, 22 May 2007 04:14:50 +0000</pubDate>
		<dc:creator>Andryan</dc:creator>
				<category><![CDATA[FTP]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Netfilter]]></category>
		<category><![CDATA[Plesk]]></category>
		<category><![CDATA[Technical]]></category>

		<guid isPermaLink="false">http://andryan.wordpress.com/2007/05/22/battlenet-games-iptables-rules/</guid>
		<description><![CDATA[This script will create port forwarding rules on port 36xxx to 192.168.1.xxx:36xxx.]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.nirkabel.org/wp-content/uploads/2007/05/script.txt" target="_blank">This script</a> will create port forwarding rules on port 36xxx to 192.168.1.xxx:36xxx.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nirkabel.org/2007/05/22/iptables-port-forwarding-rules-for-battlenet-games/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Active/Passive FTP Explanation</title>
		<link>http://blog.nirkabel.org/2006/01/23/activepassive-ftp-explanation/</link>
		<comments>http://blog.nirkabel.org/2006/01/23/activepassive-ftp-explanation/#comments</comments>
		<pubDate>Mon, 23 Jan 2006 18:05:50 +0000</pubDate>
		<dc:creator>Andryan</dc:creator>
				<category><![CDATA[FTP]]></category>
		<category><![CDATA[References]]></category>
		<category><![CDATA[Technical]]></category>

		<guid isPermaLink="false">http://andryan.wordpress.com/2006/01/23/activepassive-ftp-explanation/</guid>
		<description><![CDATA[I keep forgetting the key differences between passive and active FTP. Here&#8217;s a good link.. http://slacksite.com/other/ftp.html]]></description>
			<content:encoded><![CDATA[<p align="left">I keep forgetting the key differences between passive and active FTP.<br />
Here&#8217;s a good link.. <a href="http://slacksite.com/other/ftp.html" target="_blank">http://slacksite.com/other/ftp.html</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nirkabel.org/2006/01/23/activepassive-ftp-explanation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Passive FTP workaround for Plesk&#8217;s proftpd</title>
		<link>http://blog.nirkabel.org/2006/01/23/passive-ftp-workaround-for-plesks-proftpd/</link>
		<comments>http://blog.nirkabel.org/2006/01/23/passive-ftp-workaround-for-plesks-proftpd/#comments</comments>
		<pubDate>Mon, 23 Jan 2006 17:35:26 +0000</pubDate>
		<dc:creator>Andryan</dc:creator>
				<category><![CDATA[FTP]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Plesk]]></category>
		<category><![CDATA[Technical]]></category>

		<guid isPermaLink="false">http://andryan.wordpress.com/2006/01/23/passive-ftp-workaround-for-plesks-proftpd/</guid>
		<description><![CDATA[Add the following line: PassivePorts 49152 65534 to /etc/proftpd.conf NOT /etc/proftpd.include as that file will be overwritten by Plesk regularly. No need to restart xinetd (/etc/init.d/xinetd restart) as proftpd is executed only when a connection has been attempted on the port. Add the following line: /sbin/iptables -A INPUT -p tcp &#8211;dport 49152:65534 -j ACCEPT to [...]]]></description>
			<content:encoded><![CDATA[<p align="left">Add the following line:<br />
PassivePorts 49152 65534<br />
to /etc/proftpd.conf<br />
NOT /etc/proftpd.include as that file will be overwritten by Plesk regularly.</p>
<p align="left">No need to restart xinetd (/etc/init.d/xinetd restart) as proftpd is executed only when a connection has been attempted on the port.</p>
<p align="left">Add the following line:<br />
/sbin/iptables -A INPUT -p tcp &#8211;dport 49152:65534 -j ACCEPT<br />
to /usr/local/psa/var/modules/firewall/firewall-active.sh</p>
<p align="left">That&#8217;s all!<br />
Just need to make sure that the last incoming traffic rule is set to deny all.</p>
<p align="left">Valid for Plesk 7.5.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nirkabel.org/2006/01/23/passive-ftp-workaround-for-plesks-proftpd/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

