<?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 2 Asa Firewall Internal Network in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/2-asa-firewall-internal-network/m-p/2505940#M234719</link>
    <description>&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/media/capture2_2.png" class="migrated-markup-image" /&gt;&lt;/P&gt;&lt;P&gt;Just wondering if you guys/ladies can push me in the right direction.&lt;/P&gt;&lt;P&gt;I am planning on having 2 ASA Firewall on my internal networks connected to 2 different ISPs. See diagram above.&lt;/P&gt;&lt;P&gt;Is this the way to go? What i want to accomplish is:&lt;/P&gt;&lt;P&gt;People connecting with VPN should go trough the 5512 firewall. But the problem is reaching the 172.26.x.x network from the anyconnect vpn users.&lt;/P&gt;&lt;P&gt;Any ideas?&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know that i can use the 5505 for the vpn users etc. but i rather use the 5512.&lt;/P&gt;&lt;P&gt;Is this a total NO NO???&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 04:46:47 GMT</pubDate>
    <dc:creator>Shane Riley</dc:creator>
    <dc:date>2019-03-12T04:46:47Z</dc:date>
    <item>
      <title>2 Asa Firewall Internal Network</title>
      <link>https://community.cisco.com/t5/network-security/2-asa-firewall-internal-network/m-p/2505940#M234719</link>
      <description>&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/media/capture2_2.png" class="migrated-markup-image" /&gt;&lt;/P&gt;&lt;P&gt;Just wondering if you guys/ladies can push me in the right direction.&lt;/P&gt;&lt;P&gt;I am planning on having 2 ASA Firewall on my internal networks connected to 2 different ISPs. See diagram above.&lt;/P&gt;&lt;P&gt;Is this the way to go? What i want to accomplish is:&lt;/P&gt;&lt;P&gt;People connecting with VPN should go trough the 5512 firewall. But the problem is reaching the 172.26.x.x network from the anyconnect vpn users.&lt;/P&gt;&lt;P&gt;Any ideas?&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know that i can use the 5505 for the vpn users etc. but i rather use the 5512.&lt;/P&gt;&lt;P&gt;Is this a total NO NO???&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 04:46:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/2-asa-firewall-internal-network/m-p/2505940#M234719</guid>
      <dc:creator>Shane Riley</dc:creator>
      <dc:date>2019-03-12T04:46:47Z</dc:date>
    </item>
    <item>
      <title>Hello; If the switch does</title>
      <link>https://community.cisco.com/t5/network-security/2-asa-firewall-internal-network/m-p/2505941#M234722</link>
      <description>&lt;P&gt;Hello;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the switch does support routing, you can do a bunch of stuff. Of course, you may need to have routes on both ASAs, and the switch would do the rest of the routing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I dont see the problem. On the ASA 5512 put a route to the 172 network pointing to the switch. The switch has to have the same route but pointing to the 5505.&lt;/P&gt;&lt;P&gt;Then you do the same for the return part.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let me know.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mike.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Sep 2014 20:40:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/2-asa-firewall-internal-network/m-p/2505941#M234722</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2014-09-18T20:40:11Z</dc:date>
    </item>
  </channel>
</rss>

