<?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: Cisco ASA pinging tools.cisco.com using IPv4 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-asa-pinging-tools-cisco-com-using-ipv4/m-p/4496251#M1084771</link>
    <description>&lt;P&gt;Looks like the call-home section doesn't have a http option to force it to use IPv4 or there is a way to configure a destination address with a fqdn using an IP address.&lt;/P&gt;</description>
    <pubDate>Tue, 02 Nov 2021 00:55:04 GMT</pubDate>
    <dc:creator>latenaite2011</dc:creator>
    <dc:date>2021-11-02T00:55:04Z</dc:date>
    <item>
      <title>Cisco ASA pinging tools.cisco.com using IPv4</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-pinging-tools-cisco-com-using-ipv4/m-p/4496248#M1084770</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone know how to force the Cisco ASA to ping tools.cisco.com using IPv4?&amp;nbsp; The WAN/External interface has both IPv4 and IPv6 configured and when pinging tools.cisco.com from the ASA directly, it defaults to IPv6, see below for output (actual address masked):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;firewall# ping tools.cisco.com&lt;BR /&gt;Type escape sequence to abort.&lt;BR /&gt;Sending 5, 100-byte ICMP Echos to 20XX:XXX:XXXX:X::Xa, timeout is 2 seconds:&lt;BR /&gt;?????&lt;BR /&gt;Success rate is 0 percent (0/5)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not sure how to make it use IPv4 and I think this is causing the Call-home feature to fail.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 02 Nov 2021 00:28:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-pinging-tools-cisco-com-using-ipv4/m-p/4496248#M1084770</guid>
      <dc:creator>latenaite2011</dc:creator>
      <dc:date>2021-11-02T00:28:00Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA pinging tools.cisco.com using IPv4</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-pinging-tools-cisco-com-using-ipv4/m-p/4496251#M1084771</link>
      <description>&lt;P&gt;Looks like the call-home section doesn't have a http option to force it to use IPv4 or there is a way to configure a destination address with a fqdn using an IP address.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Nov 2021 00:55:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-pinging-tools-cisco-com-using-ipv4/m-p/4496251#M1084771</guid>
      <dc:creator>latenaite2011</dc:creator>
      <dc:date>2021-11-02T00:55:04Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA pinging tools.cisco.com using IPv4</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-pinging-tools-cisco-com-using-ipv4/m-p/4496253#M1084772</link>
      <description>&lt;P&gt;This has been fixed by configuring a public DNS server.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Nov 2021 01:20:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-pinging-tools-cisco-com-using-ipv4/m-p/4496253#M1084772</guid>
      <dc:creator>latenaite2011</dc:creator>
      <dc:date>2021-11-02T01:20:18Z</dc:date>
    </item>
  </channel>
</rss>

