<?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 ASA loopback in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-loopback/m-p/2222606#M347973</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Only the product team could definitively answer "why" but the ASA doesn't suffer for lack of a loopback interface. If you want an "always on" management interface it has the dedicated interface(s) for that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 16 Jun 2013 13:56:45 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2013-06-16T13:56:45Z</dc:date>
    <item>
      <title>ASA loopback</title>
      <link>https://community.cisco.com/t5/network-security/asa-loopback/m-p/2222605#M347972</link>
      <description>&lt;P&gt;Hey all,&lt;/P&gt;&lt;P&gt;Can someone please explain me why does cisco firewall doesnt have a loopback interface while other vendors loke palo alto,F5 and juniper does have.&lt;/P&gt;&lt;P&gt;Thanks .&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:58:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-loopback/m-p/2222605#M347972</guid>
      <dc:creator>Csco12071985</dc:creator>
      <dc:date>2019-03-12T01:58:36Z</dc:date>
    </item>
    <item>
      <title>ASA loopback</title>
      <link>https://community.cisco.com/t5/network-security/asa-loopback/m-p/2222606#M347973</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Only the product team could definitively answer "why" but the ASA doesn't suffer for lack of a loopback interface. If you want an "always on" management interface it has the dedicated interface(s) for that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 16 Jun 2013 13:56:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-loopback/m-p/2222606#M347973</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2013-06-16T13:56:45Z</dc:date>
    </item>
    <item>
      <title>ASA loopback</title>
      <link>https://community.cisco.com/t5/network-security/asa-loopback/m-p/2222607#M347974</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So if i want to work with ospf, the router id will be determined by the manegment interface?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Jun 2013 06:36:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-loopback/m-p/2222607#M347974</guid>
      <dc:creator>Csco12071985</dc:creator>
      <dc:date>2013-06-17T06:36:08Z</dc:date>
    </item>
    <item>
      <title>Re: ASA loopback</title>
      <link>https://community.cisco.com/t5/network-security/asa-loopback/m-p/2222608#M347975</link>
      <description>&lt;P&gt;For OSPF on an ASA, it's much like an IOS router with respect to router-id. That is, the ASA will use either the highest numbered interface address by default or whatever router-id you specify (my preferred method) using the "router-id" command under the "router ospf" section. In the ASDM GUI it's set under "Configuration, Device Setup, Routing, OSPF, Setup, Advanced"&lt;/P&gt;</description>
      <pubDate>Mon, 09 Nov 2020 03:01:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-loopback/m-p/2222608#M347975</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2020-11-09T03:01:46Z</dc:date>
    </item>
  </channel>
</rss>

