<?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: able to ping from from inside interface but not outside in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/able-to-ping-from-from-inside-interface-but-not-outside/m-p/1132183#M892391</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does this device have two nics by any chance? Also, Check the routing table of the host "192.168.0.165" and make sure this host has a routing properly configured to route packets destined to the the VPN Pool of IP Addresses back to the client. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, what is this host? Is it a server or a VIP on a load balancer? Make sure that there are no filters that will block ICMP Traffic from the VPN Pool of IP Addresses. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Arul&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*Pls rate if it helps*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Dec 2008 22:16:03 GMT</pubDate>
    <dc:creator>ajagadee</dc:creator>
    <dc:date>2008-12-11T22:16:03Z</dc:date>
    <item>
      <title>able to ping from from inside interface but not outside</title>
      <link>https://community.cisco.com/t5/network-security/able-to-ping-from-from-inside-interface-but-not-outside/m-p/1132180#M892378</link>
      <description>&lt;P&gt;Users on vpn can not reach 1 particular host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ICMP is allowed since they are able to ping other devices on our network when vpn'd in.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using ASDM to rung the ping test..&lt;/P&gt;&lt;P&gt;the first result is with the outside interface as source..the second is inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Type escape sequence to abort.&lt;/P&gt;&lt;P&gt;Sending 5, 100-byte ICMP Echos to 192.168.0.165, timeout is 2 seconds:&lt;/P&gt;&lt;P&gt;?????&lt;/P&gt;&lt;P&gt;Success rate is 0 percent (0/5)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Type escape sequence to abort.&lt;/P&gt;&lt;P&gt;Sending 5, 100-byte ICMP Echos to 192.168.0.165, timeout is 2 seconds:&lt;/P&gt;&lt;P&gt;!!!!!&lt;/P&gt;&lt;P&gt;Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 m&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list a_splitTunnelAcl standard permit 172.20.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;access-list A_splitTunnelAcl standard permit 172.30.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;access-list A_splitTunnelAcl standard permit 192.168.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;access-list a_splitTunnelAcl standard permit 206.213.201.96 255.255.255.248&lt;/P&gt;&lt;P&gt;access-list A_splitTunnelAcl standard permit 206.213.207.96 255.255.255.248&lt;/P&gt;&lt;P&gt;access-list A_splitTunnelAcl standard permit host 64.14.47.15x&lt;/P&gt;&lt;P&gt;access-list A_splitTunnelAcl standard permit host 64.14.47.15x&lt;/P&gt;&lt;P&gt;access-list A_splitTunnelAcl standard permit host 64.14.47.16x&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;route outside 0.0.0.0 0.0.0.0 64.14.47.190 1&lt;/P&gt;&lt;P&gt;route inside 64.14.4 255.255.255.255 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 64.14.4255.255.255.255 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 64.14.47 255.255.255.255 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 64.14.47 255.255.255.255 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 64.14.4 255.255.255.255 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 64.14.47 255.255.255.255 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 64.14.47 255.255.255.255 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 64.14.4 255.255.255.255 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 64.14.4 255.255.255.255 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 64.14.47 255.255.255.255 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 64.14.4 255.255.255.255 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 64.14.4 255.255.255.255 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 64.14.4 255.255.255.255 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 64.14.4 255.255.255.255 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 172.20.0.0 255.255.0.0 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 192.168.0.0 255.255.0.0 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 206.213.20255.255.255.248 172.30.0.1 1&lt;/P&gt;&lt;P&gt;route inside 206.213.2 255.255.255.248 172.30.0.1 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;172.30.0.1 is the interface on our network&lt;/P&gt;&lt;P&gt;172.30.0.2 is the inside interface of the firewal&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 14:25:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/able-to-ping-from-from-inside-interface-but-not-outside/m-p/1132180#M892378</guid>
      <dc:creator>nygenxny123</dc:creator>
      <dc:date>2019-03-11T14:25:00Z</dc:date>
    </item>
    <item>
      <title>Re: able to ping from from inside interface but not outside</title>
      <link>https://community.cisco.com/t5/network-security/able-to-ping-from-from-inside-interface-but-not-outside/m-p/1132181#M892382</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can vpn users ping anything on 192.168.0.0? If not, 192.168.0.0 most likely needs a route to the vpn client subnet.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Dec 2008 20:27:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/able-to-ping-from-from-inside-interface-but-not-outside/m-p/1132181#M892382</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2008-12-11T20:27:18Z</dc:date>
    </item>
    <item>
      <title>Re: able to ping from from inside interface but not outside</title>
      <link>https://community.cisco.com/t5/network-security/able-to-ping-from-from-inside-interface-but-not-outside/m-p/1132182#M892387</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;yes they can hit 192.168.9.6 for example&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Dec 2008 21:18:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/able-to-ping-from-from-inside-interface-but-not-outside/m-p/1132182#M892387</guid>
      <dc:creator>nygenxny123</dc:creator>
      <dc:date>2008-12-11T21:18:35Z</dc:date>
    </item>
    <item>
      <title>Re: able to ping from from inside interface but not outside</title>
      <link>https://community.cisco.com/t5/network-security/able-to-ping-from-from-inside-interface-but-not-outside/m-p/1132183#M892391</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does this device have two nics by any chance? Also, Check the routing table of the host "192.168.0.165" and make sure this host has a routing properly configured to route packets destined to the the VPN Pool of IP Addresses back to the client. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, what is this host? Is it a server or a VIP on a load balancer? Make sure that there are no filters that will block ICMP Traffic from the VPN Pool of IP Addresses. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Arul&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*Pls rate if it helps*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Dec 2008 22:16:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/able-to-ping-from-from-inside-interface-but-not-outside/m-p/1132183#M892391</guid>
      <dc:creator>ajagadee</dc:creator>
      <dc:date>2008-12-11T22:16:03Z</dc:date>
    </item>
  </channel>
</rss>

