<?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: ASA Thinks Route Is Directly Connected When Its Not in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3192162#M1065878</link>
    <description>&lt;P&gt;Any one&amp;nbsp;have any ideas?&lt;/P&gt;</description>
    <pubDate>Sun, 01 Oct 2017 18:17:39 GMT</pubDate>
    <dc:creator>pugs17211721</dc:creator>
    <dc:date>2017-10-01T18:17:39Z</dc:date>
    <item>
      <title>ASA Thinks Route Is Directly Connected When Its Not</title>
      <link>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3188274#M1065873</link>
      <description>&lt;P&gt;I have an ASA that is behaving quite peculiar.&amp;nbsp;I am trying to get to (IP's&amp;nbsp;changed for security purposes) 10.16.37.98. This site is a bank that we need to send information to, it just so happens to be the next block of IP's from our same ISP as our secondary (failover link) is. Here is my interface connectivity for the related interface:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;interface Ethernet0/0&lt;BR /&gt;description Internet Connection&lt;BR /&gt;speed 100&lt;BR /&gt;duplex full&lt;BR /&gt;nameif outside&lt;BR /&gt;security-level 0&lt;BR /&gt;ip address 10.16.37.74 255.255.255.248&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;By subnetting rules, only 10.16.37.73 - 79, should be directly connected, so I am a bit confused as to why the following is happening:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;show route outside 199.16.37.98&lt;/P&gt;&lt;P&gt;&amp;lt;route codes removed&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;C 10.16.37.72 255.255.255.248 is directly connected, outside&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone have any ideas? Here is the pertinent show version from the ASA:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cisco Adaptive Security Appliance Software Version 9.1(6)&lt;/P&gt;&lt;P&gt;Compiled on Fri 27-Feb-15 13:50 by builders&lt;BR /&gt;System image file is "disk0:/asa916-k8.bin"&lt;BR /&gt;Config file at boot was "startup-config"&lt;/P&gt;&lt;P&gt;&amp;lt;hostname&amp;gt; up 2 days 2 hours&lt;BR /&gt;failover cluster up 2 days 2 hours&lt;/P&gt;&lt;P&gt;Hardware: ASA5510, 1024 MB RAM, CPU Pentium 4 Celeron 1599 MHz,&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 14:21:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3188274#M1065873</guid>
      <dc:creator>pugs17211721</dc:creator>
      <dc:date>2020-02-21T14:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Thinks Route Is Directly Connected When Its Not</title>
      <link>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3188290#M1065874</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Do you "ip classless" on your running-config?&lt;/P&gt;</description>
      <pubDate>Fri, 22 Sep 2017 20:51:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3188290#M1065874</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2017-09-22T20:51:51Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Thinks Route Is Directly Connected When Its Not</title>
      <link>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3188303#M1065875</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope you are fine, I understand that you are changing you ip adresses for security purposes, based on the following statement:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ip address 10.16.37.74 255.255.255.248&amp;nbsp;&lt;/P&gt;&lt;P&gt;10.16.37.74 is an available ip address within the 10.16.37.72/29 subnet that can be assigned to a host or device.&lt;/P&gt;&lt;P&gt;The network id is&amp;nbsp;&lt;SPAN&gt;10.16.37.72/29&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;the broadcast address is 10.16.37.79.&lt;/P&gt;&lt;P&gt;the available ip address are from 10.16.37.78 to 10.16.37.78 (those can be assigned to hosts or devices)&lt;/P&gt;&lt;P&gt;The reason why the ASA is showing you in the routing table the 10.16.37.72 network as directly connected is because 10.16.37.74 ip address resides within&amp;nbsp;that subnet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Sep 2017 22:49:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3188303#M1065875</guid>
      <dc:creator>Kornelia Gutierrez</dc:creator>
      <dc:date>2017-09-22T22:49:39Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Thinks Route Is Directly Connected When Its Not</title>
      <link>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3189009#M1065876</link>
      <description>&lt;P&gt;It does not take this command&lt;/P&gt;</description>
      <pubDate>Mon, 25 Sep 2017 12:58:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3189009#M1065876</guid>
      <dc:creator>pugs17211721</dc:creator>
      <dc:date>2017-09-25T12:58:03Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Thinks Route Is Directly Connected When Its Not</title>
      <link>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3189010#M1065877</link>
      <description>&lt;P&gt;I am looking at routing for the .98 address, this is not in the same subnet.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Sep 2017 12:58:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3189010#M1065877</guid>
      <dc:creator>pugs17211721</dc:creator>
      <dc:date>2017-09-25T12:58:44Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Thinks Route Is Directly Connected When Its Not</title>
      <link>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3192162#M1065878</link>
      <description>&lt;P&gt;Any one&amp;nbsp;have any ideas?&lt;/P&gt;</description>
      <pubDate>Sun, 01 Oct 2017 18:17:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3192162#M1065878</guid>
      <dc:creator>pugs17211721</dc:creator>
      <dc:date>2017-10-01T18:17:39Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Thinks Route Is Directly Connected When Its Not</title>
      <link>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3192173#M1065879</link>
      <description>&lt;P&gt;Did you try to use IP classless as I said?&lt;/P&gt;</description>
      <pubDate>Sun, 01 Oct 2017 19:16:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3192173#M1065879</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2017-10-01T19:16:53Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Thinks Route Is Directly Connected When Its Not</title>
      <link>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3192500#M1065880</link>
      <description>&lt;P&gt;it does not take that command, like i mentioned above:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(config)# ip classless&lt;BR /&gt;^&lt;BR /&gt;ERROR: % Invalid input detected at '^' marker.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Oct 2017 15:56:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3192500#M1065880</guid>
      <dc:creator>pugs17211721</dc:creator>
      <dc:date>2017-10-02T15:56:55Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Thinks Route Is Directly Connected When Its Not</title>
      <link>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3192510#M1065881</link>
      <description>&lt;P&gt;In doing some more digging, this is actually an EIGRP problem&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ASA# show route | inc &amp;lt;removed for security&amp;gt;&amp;nbsp;&lt;BR /&gt;D 10.16.37.80 255.255.255.240 [90/3584] via 192.168.20.10, 0:08:30, inside&lt;BR /&gt;C 10.16.37.72 255.255.255.248 is directly connected, outside&lt;BR /&gt;D 10.16.37.0 255.255.255.0 is a summary, 0:12:42, Null0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the /28 is not correct, but it is learning it via itself (192.168.20.10 is its inside interface)&lt;/P&gt;</description>
      <pubDate>Mon, 02 Oct 2017 16:14:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3192510#M1065881</guid>
      <dc:creator>pugs17211721</dc:creator>
      <dc:date>2017-10-02T16:14:25Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Thinks Route Is Directly Connected When Its Not</title>
      <link>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3192513#M1065882</link>
      <description>&lt;P&gt;turns out it was EIGRP. It was configured to summarize the routes, once I did no auto-summary on the eigrp&amp;nbsp;configuration, all works as intended.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;router eigrp 100&lt;BR /&gt;&lt;STRONG&gt;no auto-summary&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;lt;line 1 is actually our ISP as well, just in the other datacenter&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;D 10.16.37.80 255.255.255.240 [90/3584] via 192.168.20.10, 0:03:51, inside&lt;BR /&gt;C 10.16.37.72 255.255.255.248 is directly connected, outside&lt;/P&gt;</description>
      <pubDate>Mon, 02 Oct 2017 16:22:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3192513#M1065882</guid>
      <dc:creator>pugs17211721</dc:creator>
      <dc:date>2017-10-02T16:22:21Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Thinks Route Is Directly Connected When Its Not</title>
      <link>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3192526#M1065883</link>
      <description>&lt;P&gt;Good!&lt;/P&gt;&lt;P&gt;&amp;nbsp;Thanks for let us know.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Oct 2017 16:42:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-thinks-route-is-directly-connected-when-its-not/m-p/3192526#M1065883</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2017-10-02T16:42:07Z</dc:date>
    </item>
  </channel>
</rss>

