<?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: Make Linux ignore a ping</title>
	<atom:link href="http://www.tech-recipes.com/rx/202/make-linux-ignore-a-ping/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tech-recipes.com/rx/202/make-linux-ignore-a-ping/</link>
	<description>Computer and technology tutorials and guides</description>
	<lastBuildDate>Sat, 21 Nov 2009 18:18:34 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: MacBaine</title>
		<link>http://www.tech-recipes.com/rx/202/make-linux-ignore-a-ping/comment-page-1/#comment-1618</link>
		<dc:creator>MacBaine</dc:creator>
		<pubDate>Thu, 14 Apr 2005 10:53:41 +0000</pubDate>
		<guid isPermaLink="false">guid-fix-me!#comment-1618</guid>
		<description>No answer to an ICMP ping does not automatically mean, that your machine does not exist.  

If your machine would not exist, the last router _before_ your machine would send an ICMP not reachable message.

Doing strange things with your ICMP config buys you absolutely nothing in respect to an attacker, but may easily make legitimate network use more difficult.  E.g. look how MTU discovery works and how it does not because &quot;wise&quot; admins disallow their machines to send ICMP replys.

Regards,
Jim</description>
		<content:encoded><![CDATA[<p>No answer to an ICMP ping does not automatically mean, that your machine does not exist.  </p>
<p>If your machine would not exist, the last router _before_ your machine would send an ICMP not reachable message.</p>
<p>Doing strange things with your ICMP config buys you absolutely nothing in respect to an attacker, but may easily make legitimate network use more difficult.  E.g. look how MTU discovery works and how it does not because &#8220;wise&#8221; admins disallow their machines to send ICMP replys.</p>
<p>Regards,<br />
Jim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bofh468</title>
		<link>http://www.tech-recipes.com/rx/202/make-linux-ignore-a-ping/comment-page-1/#comment-24</link>
		<dc:creator>bofh468</dc:creator>
		<pubDate>Mon, 10 Nov 2003 21:48:25 +0000</pubDate>
		<guid isPermaLink="false">guid-fix-me!#comment-24</guid>
		<description>Even better:

don&#039;t ignore ICMP echos:
&lt;code&gt;sysctl -w net.ipv4.icmp_echo_ignore_all=0&lt;/code&gt;


do ignore ICMP echos:
&lt;code&gt;sysctl -w net.ipv4.icmp_echo_ignore_all=1&lt;/code&gt;


sysctl -a will give you a nice list of values that you can tweak.

If you&#039;re running a Redhat-based system, you can plop the desired values in /etc/sysctl.conf.</description>
		<content:encoded><![CDATA[<p>Even better:</p>
<p>don&#8217;t ignore ICMP echos:<br />
<code>sysctl -w net.ipv4.icmp_echo_ignore_all=0</code></p>
<p>do ignore ICMP echos:<br />
<code>sysctl -w net.ipv4.icmp_echo_ignore_all=1</code></p>
<p>sysctl -a will give you a nice list of values that you can tweak.</p>
<p>If you&#8217;re running a Redhat-based system, you can plop the desired values in /etc/sysctl.conf.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
