<?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: EIGRP routes in ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/eigrp-routes-in-asa/m-p/1681484#M561072</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Couple of things - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) i didn't notice yesterday but your acl is wrong, you need to be using a reverse mask so - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list intoout_route permit 192.168.0.0 255.255.0.0&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;should be &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list intoout_route permit 192.168.0.0 0.0.255.255 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) from memory the access-list is used to describe specific matches ie. you have specificed 192.168.0.0/16.&amp;nbsp; This does not mean anything that is covered by 192.168.0.0/16, such as 192.168.1.0/28 is also advertised because 192.168.1.0/28 is not an exact match. If you wanted to do that sort of thing you would need to use a prefix-list. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if you want to advertise 192.168.1.0/28 to the internet router - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list intoout_route permit 192.168.1.0 255.255.255.240 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) You may instead want to simply advertise a summary route such as 192.168.0.0/16 ie. only this route gets to the internet router but that is okay as it would also cover 192.168.1.0/28. If you do then the ASA would need to receive this route from an internal router. You can't simply add a route in the distribute-list and expect it to be advertised if the ASA is not receiving that route.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Jun 2011 11:25:37 GMT</pubDate>
    <dc:creator>Jon Marshall</dc:creator>
    <dc:date>2011-06-09T11:25:37Z</dc:date>
    <item>
      <title>EIGRP routes in ASA</title>
      <link>https://community.cisco.com/t5/network-security/eigrp-routes-in-asa/m-p/1681481#M561064</link>
      <description>&lt;P&gt;Hi Guys currently we have folwoing config in aur ASA&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;&lt;P&gt;router eigrp 90&lt;/P&gt;&lt;P&gt; no auto-summary&lt;/P&gt;&lt;P&gt; distribute-list intoout_route out interface outside&lt;/P&gt;&lt;P&gt; network 192.168.1.0 255.255.255.240&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list intoout_route permit 192.168.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now this ASA is connected to a switch and then there is an internet router............the ASA can see all the routes from (EIGRP) from internet router but the internet router nor the switch can see any eigrp routes from this ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The inside interface IP is 192.168.1.1 255.255.255.240&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;outside one is 192.168.1.10 255.255.255.240&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can someone plz tell me as i am going nuts&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:43:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/eigrp-routes-in-asa/m-p/1681481#M561064</guid>
      <dc:creator>The_guroo_2</dc:creator>
      <dc:date>2019-03-11T20:43:20Z</dc:date>
    </item>
    <item>
      <title>EIGRP routes in ASA</title>
      <link>https://community.cisco.com/t5/network-security/eigrp-routes-in-asa/m-p/1681482#M561065</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So the ASA is receiving a route from a L3 device on it's inside interface for 192.168.0.0/16 is it ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If it isn't then your config effectively would advertise nothing to the outside. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Jun 2011 11:56:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/eigrp-routes-in-asa/m-p/1681482#M561065</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2011-06-08T11:56:45Z</dc:date>
    </item>
    <item>
      <title>EIGRP routes in ASA</title>
      <link>https://community.cisco.com/t5/network-security/eigrp-routes-in-asa/m-p/1681483#M561069</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Jon for your reply......the conection is as under:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;firewall conected to core switch (inside IP is 192.168.1.1 and swicth ip (routed port) is 192.168.1.14/28&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ouside interface has ip of 192.168.1.17/28 (sorry for th elast post ip)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so eigrp is config &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;router eigrp 90&lt;/P&gt;&lt;P&gt; no auto-summary&lt;/P&gt;&lt;P&gt; distribute-list intoout_route out interface outside&lt;/P&gt;&lt;P&gt; network 192.168.1.0 255.255.255.240&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list intoout_route permit 192.168.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when i do sh eigrp nei&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the firewall does show th eneibour outsode interface (interneyt router) and the firewall is getting all routes from internet router via eigrp&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but when i check at internet router i am not getting a route of 192.168.1.0/28 why is that&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in access-list i have added 192.168.0.0/16 so technically 192.168.1.0/28 shd be allowed under this &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Jun 2011 23:31:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/eigrp-routes-in-asa/m-p/1681483#M561069</guid>
      <dc:creator>The_guroo_2</dc:creator>
      <dc:date>2011-06-08T23:31:26Z</dc:date>
    </item>
    <item>
      <title>Re: EIGRP routes in ASA</title>
      <link>https://community.cisco.com/t5/network-security/eigrp-routes-in-asa/m-p/1681484#M561072</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Couple of things - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) i didn't notice yesterday but your acl is wrong, you need to be using a reverse mask so - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list intoout_route permit 192.168.0.0 255.255.0.0&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;should be &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list intoout_route permit 192.168.0.0 0.0.255.255 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) from memory the access-list is used to describe specific matches ie. you have specificed 192.168.0.0/16.&amp;nbsp; This does not mean anything that is covered by 192.168.0.0/16, such as 192.168.1.0/28 is also advertised because 192.168.1.0/28 is not an exact match. If you wanted to do that sort of thing you would need to use a prefix-list. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if you want to advertise 192.168.1.0/28 to the internet router - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list intoout_route permit 192.168.1.0 255.255.255.240 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) You may instead want to simply advertise a summary route such as 192.168.0.0/16 ie. only this route gets to the internet router but that is okay as it would also cover 192.168.1.0/28. If you do then the ASA would need to receive this route from an internal router. You can't simply add a route in the distribute-list and expect it to be advertised if the ASA is not receiving that route.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Jun 2011 11:25:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/eigrp-routes-in-asa/m-p/1681484#M561072</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2011-06-09T11:25:37Z</dc:date>
    </item>
    <item>
      <title>EIGRP routes in ASA</title>
      <link>https://community.cisco.com/t5/network-security/eigrp-routes-in-asa/m-p/1681485#M561075</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jon&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your reply ....in ASA the access-list is oppsoite ...so subnet mask is used instaead of wild card mask&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;even in EIGRP that is the case.......its strange but thats how it works&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Jun 2011 14:45:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/eigrp-routes-in-asa/m-p/1681485#M561075</guid>
      <dc:creator>The_guroo_2</dc:creator>
      <dc:date>2011-06-09T14:45:52Z</dc:date>
    </item>
    <item>
      <title>EIGRP routes in ASA</title>
      <link>https://community.cisco.com/t5/network-security/eigrp-routes-in-asa/m-p/1681486#M561076</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Wow, i'm getting rusty. Yes of course, you are right, ASAs use standard subnet masks, my mistake.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But the rest is still relevant and why your internet router is not receiving any routes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Jun 2011 15:47:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/eigrp-routes-in-asa/m-p/1681486#M561076</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2011-06-09T15:47:32Z</dc:date>
    </item>
  </channel>
</rss>

