<?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 FTD Inside interface not pingable from same subnet in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-inside-interface-not-pingable-from-same-subnet/m-p/4648953#M1091781</link>
    <description>&lt;P&gt;Guys I am having the strangest issue with all 3 FTD's where I assign 192.168.3.1 to port 1/1 within FMC. There is no subinterface etc it is a IP address assigned to the physical port. If i plug into an unmanaged switch I cannot ping 192.168.3.1 while connected with my laptop or other systems on 192.168.3. subnet. I can ping management at 192.168.3.11 from all systems. If i plug in laptop direct to port at this time I still cannot ping it. Now get this, if I restart the FTD and have my laptop plugged direct to 192.168.3.1 I can ping once it has restarted. The second i unplug and plug into unmanaged switch(Doesnt matter manufacturer i tried several) then it does not respond. WTH is up with this?m It seems that if I plug into a unifi switch I do not have this issue. What the heck is going on, the only thing different is unifi is trunk all by default but this FTD 192.168.3.1 is a physical port not VLAN assigned.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Jul 2022 18:17:09 GMT</pubDate>
    <dc:creator>keithcclark71</dc:creator>
    <dc:date>2022-07-12T18:17:09Z</dc:date>
    <item>
      <title>FTD Inside interface not pingable from same subnet</title>
      <link>https://community.cisco.com/t5/network-security/ftd-inside-interface-not-pingable-from-same-subnet/m-p/4648953#M1091781</link>
      <description>&lt;P&gt;Guys I am having the strangest issue with all 3 FTD's where I assign 192.168.3.1 to port 1/1 within FMC. There is no subinterface etc it is a IP address assigned to the physical port. If i plug into an unmanaged switch I cannot ping 192.168.3.1 while connected with my laptop or other systems on 192.168.3. subnet. I can ping management at 192.168.3.11 from all systems. If i plug in laptop direct to port at this time I still cannot ping it. Now get this, if I restart the FTD and have my laptop plugged direct to 192.168.3.1 I can ping once it has restarted. The second i unplug and plug into unmanaged switch(Doesnt matter manufacturer i tried several) then it does not respond. WTH is up with this?m It seems that if I plug into a unifi switch I do not have this issue. What the heck is going on, the only thing different is unifi is trunk all by default but this FTD 192.168.3.1 is a physical port not VLAN assigned.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jul 2022 18:17:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-inside-interface-not-pingable-from-same-subnet/m-p/4648953#M1091781</guid>
      <dc:creator>keithcclark71</dc:creator>
      <dc:date>2022-07-12T18:17:09Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Inside interface not pingable from same subnet</title>
      <link>https://community.cisco.com/t5/network-security/ftd-inside-interface-not-pingable-from-same-subnet/m-p/4648959#M1091782</link>
      <description>&lt;P&gt;is this virtual or Physical ? are you able to ping from FTD to other side ?&lt;/P&gt;
&lt;P&gt;Can you post the confg here. and route&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jul 2022 18:30:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-inside-interface-not-pingable-from-same-subnet/m-p/4648959#M1091782</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2022-07-12T18:30:51Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Inside interface not pingable from same subnet</title>
      <link>https://community.cisco.com/t5/network-security/ftd-inside-interface-not-pingable-from-same-subnet/m-p/4649087#M1091787</link>
      <description>&lt;P&gt;I could ping from the FTD to host but host not to it. Maybe bad interface?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Interface Ethernet1/1 "Inside", is up, line protocol is up&lt;BR /&gt;Hardware is EtherSVI, BW 1000 Mbps, DLY 10 usec&lt;BR /&gt;MAC address e069.ba7c.fe48, MTU 1500&lt;BR /&gt;IP address 192.168.3.1, subnet mask 255.255.255.0&lt;BR /&gt;Traffic Statistics for "Inside":&lt;BR /&gt;72 packets input, 4725 bytes&lt;BR /&gt;5 packets output, 140 bytes&lt;BR /&gt;65 packets dropped&lt;BR /&gt;1 minute input rate 0 pkts/sec, 54 bytes/sec&lt;BR /&gt;1 minute output rate 0 pkts/sec, 1 bytes/sec&lt;BR /&gt;1 minute drop rate, 0 pkts/sec&lt;BR /&gt;5 minute input rate 0 pkts/sec, 0 bytes/sec&lt;BR /&gt;5 minute output rate 0 pkts/sec, 0 bytes/sec&lt;BR /&gt;5 minute drop rate, 0 pkts/sec&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jul 2022 22:14:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-inside-interface-not-pingable-from-same-subnet/m-p/4649087#M1091787</guid>
      <dc:creator>keithcclark71</dc:creator>
      <dc:date>2022-07-12T22:14:01Z</dc:date>
    </item>
  </channel>
</rss>

