<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Modify TTL value for security reasons.]]></title><description><![CDATA[<p dir="auto">Pfsense support Packet Mangle TTL ?</p>
]]></description><link>https://forum.netgate.com/topic/4435/modify-ttl-value-for-security-reasons</link><generator>RSS for Node</generator><lastBuildDate>Fri, 10 Apr 2026 20:25:05 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/4435.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 07 May 2007 00:47:28 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Modify TTL value for security reasons. on Mon, 07 May 2007 12:59:40 GMT]]></title><description><![CDATA[<p dir="auto">yeah, thanks ulrich, here …</p>
<p dir="auto">Bill Marquette<br />
Mon, 04 Sep 2006 10:09:44 -0700</p>
<p dir="auto">Or if you want fuck with the ISP and have a full blown network behind<br />
the pfSense box.</p>
<p dir="auto">Change the following line in /etc/inc/filter.inc<br />
      $rules .= "scrub all {$scrubnodf} {$mssclamp} fragment<br />
reassemble\n"; // reassemble all directions<br />
to:<br />
      $rules .= "scrub all min-ttl 255 {$scrubnodf} {$mssclamp}<br />
fragment reassemble\n"; // reassemble all directions</p>
<p dir="auto">That will reset the TTL to 255 (substitute whatever sufficiently high<br />
value appeals to you) as it passes through the pfSense box.  The above<br />
line lives on line 166 in filter.inc version 1.575.2.235.  BTW, this<br />
will have the other added advantage of being able to mask different<br />
OSs behind your pfSense box and the network layout as ALL packets will<br />
have a normalized TTL after traversing the firewall.</p>
<p dir="auto">I don't expect to ever put a gui wrapper around this, I feel it has<br />
rather limited use.</p>
<p dir="auto">--Bill</p>
]]></description><link>https://forum.netgate.com/post/154305</link><guid isPermaLink="true">https://forum.netgate.com/post/154305</guid><dc:creator><![CDATA[juanchoX]]></dc:creator><pubDate>Mon, 07 May 2007 12:59:40 GMT</pubDate></item><item><title><![CDATA[Reply to Modify TTL value for security reasons. on Mon, 07 May 2007 02:25:04 GMT]]></title><description><![CDATA[<p dir="auto">I don't know if pfsense supports it, but pf allows you to create rules based on the TTL value.  For instance, you should be suspicious of incoming packets with very low TTL (TTL = 1, 2, etc) because it's likely the result of firewalking.</p>
]]></description><link>https://forum.netgate.com/post/154262</link><guid isPermaLink="true">https://forum.netgate.com/post/154262</guid><dc:creator><![CDATA[rcarr]]></dc:creator><pubDate>Mon, 07 May 2007 02:25:04 GMT</pubDate></item><item><title><![CDATA[Reply to Modify TTL value for security reasons. on Mon, 07 May 2007 01:10:09 GMT]]></title><description><![CDATA[<p dir="auto">That may or may not be what you're after. If not, by "packet mangle TTL", what exactly do you mean?</p>
]]></description><link>https://forum.netgate.com/post/154255</link><guid isPermaLink="true">https://forum.netgate.com/post/154255</guid><dc:creator><![CDATA[cmb]]></dc:creator><pubDate>Mon, 07 May 2007 01:10:09 GMT</pubDate></item><item><title><![CDATA[Reply to Modify TTL value for security reasons. on Mon, 07 May 2007 01:06:20 GMT]]></title><description><![CDATA[<p dir="auto">See this URL for more information: http://www.mail-archive.com/discussion@pfsense.com/msg01782.html</p>
]]></description><link>https://forum.netgate.com/post/154254</link><guid isPermaLink="true">https://forum.netgate.com/post/154254</guid><dc:creator><![CDATA[sullrich]]></dc:creator><pubDate>Mon, 07 May 2007 01:06:20 GMT</pubDate></item></channel></rss>