<?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: Firepower issues in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-issues/m-p/4559833#M1087696</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/133745"&gt;@cm&lt;/a&gt; that ping is from the FTD itself, so it doesn't need to nat. It will route the traffic from the outside interface.&lt;/P&gt;</description>
    <pubDate>Fri, 25 Feb 2022 17:58:17 GMT</pubDate>
    <dc:creator>Rob Ingram</dc:creator>
    <dc:date>2022-02-25T17:58:17Z</dc:date>
    <item>
      <title>Firepower issues</title>
      <link>https://community.cisco.com/t5/network-security/firepower-issues/m-p/4559783#M1087692</link>
      <description>&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I m having strange issues with my FTD. I am managing it from FDM as I don't have FMC. I am Seeing strange behavior. I have deleted all the rules NAT and ACP . But my Clients Still getting internet.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is what I get from the command line. There seem to be some in Built statements in the system seen from show nat...Auto NAT... Further do i need to upgrade hardware from the current version below&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;gt;&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt; show nat&lt;/P&gt;&lt;P&gt;Auto NAT Policies (Section 2)&lt;BR /&gt;1 (nlp_int_tap) to (inside) source static nlp_server_0_http_intf3 interface service tcp https https&lt;BR /&gt;translate_hits = 0, untranslate_hits = 0&lt;BR /&gt;2 (nlp_int_tap) to (outside) source dynamic nlp_client_0_intf2 interface&lt;BR /&gt;translate_hits = 0, untranslate_hits = 0&lt;BR /&gt;3 (nlp_int_tap) to (inside) source dynamic nlp_client_0_intf3 interface&lt;BR /&gt;translate_hits = 0, untranslate_hits = 0&lt;BR /&gt;4 (nlp_int_tap) to (diagnostic) source dynamic nlp_client_0_intf4 interface&lt;BR /&gt;translate_hits = 0, untranslate_hits = 0&lt;BR /&gt;5 (nlp_int_tap) to (outside) source dynamic nlp_client_0_ipv6_intf2 interface ipv6&lt;BR /&gt;translate_hits = 0, untranslate_hits = 0&lt;BR /&gt;6 (nlp_int_tap) to (inside) source dynamic nlp_client_0_ipv6_intf3 interface ipv6&lt;BR /&gt;translate_hits = 0, untranslate_hits = 0&lt;BR /&gt;7 (nlp_int_tap) to (diagnostic) source dynamic nlp_client_0_ipv6_intf4 interface ipv6&lt;BR /&gt;translate_hits = 0, untranslate_hits = 0&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt; show xlate&lt;BR /&gt;2 in use, 3 most used&lt;BR /&gt;Flags: D - DNS, e - extended, I - identity, i - dynamic, r - portmap,&lt;BR /&gt;s - static, T - twice, N - net-to-net&lt;BR /&gt;TCP PAT from nlp_int_tap:169.254.1.3 443-443 to inside:192.168.1.1 443-443&lt;BR /&gt;flags sr idle 1:55:58 timeout 0:00:00&lt;/P&gt;&lt;P&gt;&amp;gt;&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt; show version&lt;BR /&gt;-------------------[ firepower ]--------------------&lt;BR /&gt;Model : Cisco Firepower 2130 Threat Defense (77) Version 6.2.3 (Build 83)&lt;BR /&gt;UUID : 9cf20e9c-37d7-11ec-8011-db2581d87e9c&lt;BR /&gt;Rules update version : 2017-09-13-001-vrt&lt;BR /&gt;VDB version : 290&lt;BR /&gt;----------------------------------------------------&lt;/P&gt;&lt;P&gt;&amp;gt;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Feb 2022 16:49:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-issues/m-p/4559783#M1087692</guid>
      <dc:creator>cm</dc:creator>
      <dc:date>2022-02-25T16:49:51Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower issues</title>
      <link>https://community.cisco.com/t5/network-security/firepower-issues/m-p/4559785#M1087693</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/133745"&gt;@cm&lt;/a&gt; clear the current connections, see if the clients can access then.&lt;/P&gt;
&lt;P&gt;You are running FTD version 6.2.3, you should definately upgrade to 7.0.1 which is the latest recommended version.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://software.cisco.com/download/home/286312107/type/286306337/release/7.0.1" target="_blank"&gt;https://software.cisco.com/download/home/286312107/type/286306337/release/7.0.1&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Feb 2022 16:54:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-issues/m-p/4559785#M1087693</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2022-02-25T16:54:37Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower issues</title>
      <link>https://community.cisco.com/t5/network-security/firepower-issues/m-p/4559829#M1087695</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97036"&gt;@Rob Ingram&lt;/a&gt;&amp;nbsp; thanks Rob.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have cleared ...&amp;nbsp;But the session is up&amp;nbsp; it seem to have worked But How do clear&amp;nbsp; inbuilt Auto rules is it in material.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;gt;&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt; clear conn&lt;BR /&gt;8 connection(s) deleted.&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt; show nat&lt;/P&gt;&lt;P&gt;Auto NAT Policies (Section 2)&lt;BR /&gt;1 (nlp_int_tap) to (inside) source static nlp_server_0_http_intf3 interface service tcp https https&lt;BR /&gt;translate_hits = 0, untranslate_hits = 0&lt;BR /&gt;2 (nlp_int_tap) to (outside) source dynamic nlp_client_0_intf2 interface&lt;BR /&gt;translate_hits = 0, untranslate_hits = 0&lt;BR /&gt;3 (nlp_int_tap) to (inside) source dynamic nlp_client_0_intf3 interface&lt;BR /&gt;translate_hits = 0, untranslate_hits = 0&lt;BR /&gt;4 (nlp_int_tap) to (diagnostic) source dynamic nlp_client_0_intf4 interface&lt;BR /&gt;translate_hits = 0, untranslate_hits = 0&lt;BR /&gt;5 (nlp_int_tap) to (outside) source dynamic nlp_client_0_ipv6_intf2 interface ipv6&lt;BR /&gt;translate_hits = 0, untranslate_hits = 0&lt;BR /&gt;6 (nlp_int_tap) to (inside) source dynamic nlp_client_0_ipv6_intf3 interface ipv6&lt;BR /&gt;translate_hits = 0, untranslate_hits = 0&lt;BR /&gt;7 (nlp_int_tap) to (diagnostic) source dynamic nlp_client_0_ipv6_intf4 interface ipv6&lt;BR /&gt;translate_hits = 0, untranslate_hits = 0&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt; show xlate&lt;BR /&gt;1 in use, 3 most used&lt;BR /&gt;Flags: D - DNS, e - extended, I - identity, i - dynamic, r - portmap,&lt;BR /&gt;s - static, T - twice, N - net-to-net&lt;BR /&gt;TCP PAT from nlp_int_tap:169.254.1.3 443-443 to inside:192.168.1.1 443-443&lt;BR /&gt;flags sr idle 3:19:05 timeout 0:00:00&lt;/P&gt;&lt;P&gt;&amp;gt;&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt; ping 8.8.8.8&lt;BR /&gt;Type escape sequence to abort.&lt;BR /&gt;Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:&lt;BR /&gt;!!!!!&lt;BR /&gt;Success rate is 100 percent (5/5), round-trip min/avg/max = 1/8/10 ms&lt;BR /&gt;&amp;gt; show&lt;BR /&gt;Syntax error: The command is not completed&lt;BR /&gt;&amp;gt; show&lt;BR /&gt;Syntax error: The command is not completed&lt;BR /&gt;&amp;gt; show&lt;/P&gt;</description>
      <pubDate>Fri, 25 Feb 2022 17:53:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-issues/m-p/4559829#M1087695</guid>
      <dc:creator>cm</dc:creator>
      <dc:date>2022-02-25T17:53:14Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower issues</title>
      <link>https://community.cisco.com/t5/network-security/firepower-issues/m-p/4559833#M1087696</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/133745"&gt;@cm&lt;/a&gt; that ping is from the FTD itself, so it doesn't need to nat. It will route the traffic from the outside interface.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Feb 2022 17:58:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-issues/m-p/4559833#M1087696</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2022-02-25T17:58:17Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower issues</title>
      <link>https://community.cisco.com/t5/network-security/firepower-issues/m-p/4559842#M1087697</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97036"&gt;@Rob Ingram&lt;/a&gt;&amp;nbsp;Yes the Ping from Devices But the Client (Ghost ) session dropped...After clearing connection... Thanks Boss. but my question still remains.&amp;nbsp; How do I get rid of the Auto Nat rule.... It seems inbuilt. While I have to Upgrade my software together with other smart licensing ... Is it safe to deploy the ftd in the mean time until resources permit to upgrade ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Feb 2022 18:15:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-issues/m-p/4559842#M1087697</guid>
      <dc:creator>cm</dc:creator>
      <dc:date>2022-02-25T18:15:03Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower issues</title>
      <link>https://community.cisco.com/t5/network-security/firepower-issues/m-p/4559850#M1087698</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/133745"&gt;@cm&lt;/a&gt; you don't get rid of them, they are built in nat rules that help the system needs to operate.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Feb 2022 18:21:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-issues/m-p/4559850#M1087698</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2022-02-25T18:21:49Z</dc:date>
    </item>
  </channel>
</rss>

