<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Traceroute, tracert, mtr and the Firepower. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/traceroute-tracert-mtr-and-the-firepower/m-p/3348971#M1031832</link>
    <description>This is not good news (about FTD I mean).&lt;BR /&gt;As for my trace issue, I cannot trace from ASA itself specifying the source interface.</description>
    <pubDate>Thu, 15 Mar 2018 07:18:18 GMT</pubDate>
    <dc:creator>Florin Barhala</dc:creator>
    <dc:date>2018-03-15T07:18:18Z</dc:date>
    <item>
      <title>Traceroute, tracert, mtr and the Firepower.</title>
      <link>https://community.cisco.com/t5/network-security/traceroute-tracert-mtr-and-the-firepower/m-p/3347804#M1031829</link>
      <description>&lt;P&gt;I have a new set of Firepower 2130 appliances and a Management Center 1000. One of the differences between the 5525x and the Firepower is that some users can run traceroute, tracert or mtr and get useful information. Other users cannot get past their gateway. This worked correctly on the ASA 5525x but when the consultant did the conversion to the Firepower rules some weird stuff happened.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Where is traceroute, etal set up? I know the process uses ICMP and/or UDP but just allowing those outbound has not cured the problem. Is there some inspection rule I need to create?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 15:30:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traceroute-tracert-mtr-and-the-firepower/m-p/3347804#M1031829</guid>
      <dc:creator>Stephen Carville</dc:creator>
      <dc:date>2020-02-21T15:30:39Z</dc:date>
    </item>
    <item>
      <title>Re: Traceroute, tracert, mtr and the Firepower.</title>
      <link>https://community.cisco.com/t5/network-security/traceroute-tracert-mtr-and-the-firepower/m-p/3348325#M1031830</link>
      <description>&lt;P&gt;I am also interested in this as we might migrate this year.&lt;/P&gt;
&lt;P&gt;Meantime can you share your current traceroute "config ". I am having some issues to make it work on my current ASAs.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Mar 2018 12:00:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traceroute-tracert-mtr-and-the-firepower/m-p/3348325#M1031830</guid>
      <dc:creator>Florin Barhala</dc:creator>
      <dc:date>2018-03-14T12:00:46Z</dc:date>
    </item>
    <item>
      <title>Re: Traceroute, tracert, mtr and the Firepower.</title>
      <link>https://community.cisco.com/t5/network-security/traceroute-tracert-mtr-and-the-firepower/m-p/3348576#M1031831</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/315231"&gt;@Florin Barhala&lt;/a&gt; wrote:&lt;BR /&gt;
&lt;P&gt;I am also interested in this as we might migrate this year.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;I've only had it a few days but, so far, I am unimpressed.&amp;nbsp; Even a simple change like blacklisting the IP of a CNC server requires redeploying the entire policy.&amp;nbsp; That takes five to ten minutes.&amp;nbsp; Don't get me started on the HTML 5 interface.&lt;BR /&gt;&lt;BR /&gt;What was Cisco thinking?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;Meantime can you share your current traceroute "config ". I am having some issues to make it work on my current ASAs.&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;As I recall, on the ASA&amp;nbsp; I first had to create an object list for the icmp types I wanted to accept from outside:&lt;BR /&gt;&lt;BR /&gt;object-group icmp-type icmp_permit&lt;BR /&gt;&amp;nbsp;description icmp types allowed&lt;BR /&gt;&amp;nbsp;icmp-object echo-reply&lt;BR /&gt;&amp;nbsp;icmp-object source-quench&lt;BR /&gt;&amp;nbsp;icmp-object time-exceeded&lt;BR /&gt;&amp;nbsp;icmp-object traceroute&lt;BR /&gt;&amp;nbsp;icmp-object unreachable&lt;BR /&gt;&lt;BR /&gt;Then on the outside interface acl I added:&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; permit icmp any any object-group icmp_permit&lt;BR /&gt;&lt;BR /&gt;Finally, the global policy map had to be made aware of icmp&lt;BR /&gt;&lt;BR /&gt;policy-map global_policy&lt;BR /&gt;&amp;nbsp;class inspection_default&lt;BR /&gt;&amp;nbsp; &amp;lt;buncha stuff&amp;gt;&lt;BR /&gt;&amp;nbsp; inspect icmp &lt;BR /&gt;&amp;nbsp; inspect icmp error&lt;/P&gt;</description>
      <pubDate>Wed, 14 Mar 2018 16:02:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traceroute-tracert-mtr-and-the-firepower/m-p/3348576#M1031831</guid>
      <dc:creator>Stephen Carville</dc:creator>
      <dc:date>2018-03-14T16:02:04Z</dc:date>
    </item>
    <item>
      <title>Re: Traceroute, tracert, mtr and the Firepower.</title>
      <link>https://community.cisco.com/t5/network-security/traceroute-tracert-mtr-and-the-firepower/m-p/3348971#M1031832</link>
      <description>This is not good news (about FTD I mean).&lt;BR /&gt;As for my trace issue, I cannot trace from ASA itself specifying the source interface.</description>
      <pubDate>Thu, 15 Mar 2018 07:18:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traceroute-tracert-mtr-and-the-firepower/m-p/3348971#M1031832</guid>
      <dc:creator>Florin Barhala</dc:creator>
      <dc:date>2018-03-15T07:18:18Z</dc:date>
    </item>
  </channel>
</rss>

