<?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: connecting two internal networks in un asa in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343737#M794859</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;generally what I do is:-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Create an inside to new interface ip access-list.&lt;/P&gt;&lt;P&gt;2) attache the acl to the nat (inside) 0 config&lt;/P&gt;&lt;P&gt;3) Create an new interface to inside ip access-list&lt;/P&gt;&lt;P&gt;4) attach the acl to the nat &amp;lt;&lt;NEW interface=""&gt;&amp;gt; 0&lt;/NEW&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then let the traffic flow - in both directions, when you have no hits on the acl from the new interface to the inside - you know your inside NAT exampt rule is bi-directional (sometimes it does not work straight away)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sometimes I leave them in there - especially, when I need to make the new interface part of a VPN - then the exmpt acl just gets expanded.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 21 Aug 2009 13:18:16 GMT</pubDate>
    <dc:creator>andrew.prince</dc:creator>
    <dc:date>2009-08-21T13:18:16Z</dc:date>
    <item>
      <title>connecting two internal networks in un asa</title>
      <link>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343731#M794853</link>
      <description>&lt;P&gt;HI&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a ASA5510, with a segment 192.168.1.0 in the interface inside but I need to configure other segment new and Both segments have to communicate, as I do ?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 16:08:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343731#M794853</guid>
      <dc:creator>ivanguzman</dc:creator>
      <dc:date>2019-03-11T16:08:14Z</dc:date>
    </item>
    <item>
      <title>Re: connecting two internal networks in un asa</title>
      <link>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343732#M794854</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Either:-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) User a router&lt;/P&gt;&lt;P&gt;2) Use another interface on the ASA, and configure the security policy accordingly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Aug 2009 08:37:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343732#M794854</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2009-08-21T08:37:43Z</dc:date>
    </item>
    <item>
      <title>Re: connecting two internal networks in un asa</title>
      <link>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343733#M794855</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andrew,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I configure another interface on the ASA, the new interface must have a security level lower than the inside.?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;how can I enable the new interface to communicate with the inside.?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks..!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Aug 2009 12:54:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343733#M794855</guid>
      <dc:creator>ivanguzman</dc:creator>
      <dc:date>2009-08-21T12:54:25Z</dc:date>
    </item>
    <item>
      <title>Re: connecting two internal networks in un asa</title>
      <link>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343734#M794856</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ivanquzman,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am in the same situation. I am in need of getting a security levl 100 to comunicate with a 75 on diff interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mine keeps erroring on the NAT rule stating that there isnt' any pool.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can some one shed some light on the suggested approach for configuration so I can verify that the I have the correct configuration?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.) I know the NAT rule needs to be on the higer seccurity.&lt;/P&gt;&lt;P&gt;2.) I know you need a Permit ACL on the lower interface to permit access inbound.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Aug 2009 13:00:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343734#M794856</guid>
      <dc:creator>hschaefers</dc:creator>
      <dc:date>2009-08-21T13:00:26Z</dc:date>
    </item>
    <item>
      <title>Re: connecting two internal networks in un asa</title>
      <link>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343735#M794857</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It can have the same security level if you want - depending on it's purpose, I generally give any other interfaces a lower security level, say 50.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I then do - is make a NAT exempt from the inside to the new interface (this is bi-directional)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once the NAT is working ok, I then write an ACL for any traffic that originates from the new interface to the inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Aug 2009 13:03:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343735#M794857</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2009-08-21T13:03:57Z</dc:date>
    </item>
    <item>
      <title>Re: connecting two internal networks in un asa</title>
      <link>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343736#M794858</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Andrew,&lt;/P&gt;&lt;P&gt;Do you put that exempt rule on the Higer security interface or make a seperate one for each lower interface?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Aug 2009 13:13:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343736#M794858</guid>
      <dc:creator>hschaefers</dc:creator>
      <dc:date>2009-08-21T13:13:06Z</dc:date>
    </item>
    <item>
      <title>Re: connecting two internal networks in un asa</title>
      <link>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343737#M794859</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;generally what I do is:-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Create an inside to new interface ip access-list.&lt;/P&gt;&lt;P&gt;2) attache the acl to the nat (inside) 0 config&lt;/P&gt;&lt;P&gt;3) Create an new interface to inside ip access-list&lt;/P&gt;&lt;P&gt;4) attach the acl to the nat &amp;lt;&lt;NEW interface=""&gt;&amp;gt; 0&lt;/NEW&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then let the traffic flow - in both directions, when you have no hits on the acl from the new interface to the inside - you know your inside NAT exampt rule is bi-directional (sometimes it does not work straight away)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sometimes I leave them in there - especially, when I need to make the new interface part of a VPN - then the exmpt acl just gets expanded.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Aug 2009 13:18:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343737#M794859</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2009-08-21T13:18:16Z</dc:date>
    </item>
    <item>
      <title>Re: connecting two internal networks in un asa</title>
      <link>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343738#M794860</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;the configuration would be as follows is correct or I'm missing some parameter?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface Ethernet0/1&lt;/P&gt;&lt;P&gt;nameif inside1&lt;/P&gt;&lt;P&gt;security-level 100&lt;/P&gt;&lt;P&gt;ip address 192.168.1.254 255.255.255.0 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface Ethernet0/2&lt;/P&gt;&lt;P&gt;nameif inside2&lt;/P&gt;&lt;P&gt;security-level 75&lt;/P&gt;&lt;P&gt;ip address 172.16.13.1 255.255.255.0 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list ACL_IN2 extended permit ip 172.16.13 255.255.255.0 192.168.1.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;static (inside,inside2) 172.16.13.0 172.16.13.0 netmask 255.255.0.0 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,inside2) 192.168.1.0 192.168.1.0 netmask 255.255.0.0 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group ACL_IN in interface inside&lt;/P&gt;&lt;P&gt;access-group ACL_IN2 in interface inside2&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Aug 2009 13:28:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343738#M794860</guid>
      <dc:creator>ivanguzman</dc:creator>
      <dc:date>2009-08-21T13:28:32Z</dc:date>
    </item>
    <item>
      <title>Re: connecting two internal networks in un asa</title>
      <link>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343739#M794861</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;that would be one way of doing it, I would&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list no-nat1 permit ip 172.16.13.0 255.255.255.0 192.168.1.0 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (inside1) 0 access-list no-nat1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list no-nat2 permit ip 192.168.1.0 255.255.255.0 172.16.13.0 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (inside2) 0 access-list no-nat2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above allows you to expand the nat-exemption the more interfaces you have.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;JMTPW&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Aug 2009 13:35:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343739#M794861</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2009-08-21T13:35:03Z</dc:date>
    </item>
    <item>
      <title>Re: connecting two internal networks in un asa</title>
      <link>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343740#M794862</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yup, got it working after your previous post Andrew and the ACL is still functional as I need it to be. Its looking like its a cross between what your both talking about.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Awesome, thanks gang.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Aug 2009 14:05:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343740#M794862</guid>
      <dc:creator>hschaefers</dc:creator>
      <dc:date>2009-08-21T14:05:09Z</dc:date>
    </item>
    <item>
      <title>Re: connecting two internal networks in un asa</title>
      <link>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343741#M794863</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;np - glad to help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Aug 2009 14:11:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/connecting-two-internal-networks-in-un-asa/m-p/1343741#M794863</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2009-08-21T14:11:01Z</dc:date>
    </item>
  </channel>
</rss>

