<?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>Ephemeral &#8211; VeriTeknik</title>
	<atom:link href="https://www.veriteknik.net.tr/en/tag/ephemeral/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.veriteknik.net.tr/en/</link>
	<description>VeriTeknik Bilişim &#124; VeriTeknik Bilişim</description>
	<lastBuildDate>Fri, 22 Apr 2011 09:05:05 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>Ephemeral port range for FTP</title>
		<link>https://www.veriteknik.net.tr/en/ephemeral-port-range-for-ftp/</link>
					<comments>https://www.veriteknik.net.tr/en/ephemeral-port-range-for-ftp/#respond</comments>
		
		<dc:creator><![CDATA[ckaraca]]></dc:creator>
		<pubDate>Fri, 22 Apr 2011 09:05:05 +0000</pubDate>
				<category><![CDATA[LINUX Help]]></category>
		<category><![CDATA[Ephemeral]]></category>
		<category><![CDATA[FTP]]></category>
		<category><![CDATA[port]]></category>
		<guid isPermaLink="false">http://plugged.in/?p=6</guid>

					<description><![CDATA[<p>The standart linux distrubition calls that the ephemeral port range be between 1024 and 4999. We we all know that some of these ports are used for other more importand applications than FTP. So security is an issue because leaving those original ports open leads to major security holes. Rather than openning ports that need [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.veriteknik.net.tr/en/ephemeral-port-range-for-ftp/">Ephemeral port range for FTP</a> appeared first on <a rel="nofollow" href="https://www.veriteknik.net.tr/en/">VeriTeknik</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>The standart linux distrubition calls that the ephemeral port range be between 1024 and 4999. We we all know that some of these ports are used for other more importand applications than FTP. So security is an issue because leaving those original ports open leads to major security holes. Rather than openning ports that need higher security for FTP we will change the port range. With this modified port range you can open your firewall to ports that do not have any use but PASV FTP.</p>
<p>First find out what the defined port range is</p>
<blockquote><p># cat /proc/sys/net/ipv4/ip_local_port_range<br />
1024 4999</p></blockquote>
<p>Know select the port range that you wan, I will define a port range of my desire but this is up to the network admin.<br />
To change the port range you have two option</p>
<p>Edit with nano or vi /proc/sys/net/ipv4/ip_local_port_range<br />
Or</p>
<blockquote><p>echo &#8220;55001 65535&#8221; &gt; /proc/sys/net/ipv4/ip_local_port_range</p></blockquote>
<p>These will both change the port, chech this with # cat /proc/sys/net/ipv4/ip_local_port_range</p>
<p>To make these changes permanent as these definitions will vanish on every reboot you need to put a script in /etc/sysctl.conf</p>
<p>Nano or vi /etc/sysctl.conf<br />
Add</p>
<blockquote><p># Controls Ephemeral Port Range (this is for the admin to remember what it is)<br />
net.ipv4.ip_local_port_range = 55001 65535</p></blockquote>
<p>Save<br />
Exit<br />
Reboot (if you like)<br />
And you are done!</p>
<p>The post <a rel="nofollow" href="https://www.veriteknik.net.tr/en/ephemeral-port-range-for-ftp/">Ephemeral port range for FTP</a> appeared first on <a rel="nofollow" href="https://www.veriteknik.net.tr/en/">VeriTeknik</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.veriteknik.net.tr/en/ephemeral-port-range-for-ftp/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">6</post-id>	</item>
	</channel>
</rss>
