<?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 NATting problem in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/natting-problem/m-p/2084849#M394223</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Haha, 100% correct again, didn't realize that.&amp;nbsp; Thank you!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Dec 2012 15:18:53 GMT</pubDate>
    <dc:creator>WStoffel1</dc:creator>
    <dc:date>2012-12-12T15:18:53Z</dc:date>
    <item>
      <title>NATting problem</title>
      <link>https://community.cisco.com/t5/network-security/natting-problem/m-p/2084845#M394219</link>
      <description>&lt;P&gt;Hi all, got another natting problem (and ACL issue) I can't solve regarding an L2L tunnel.&amp;nbsp; Attached is the config, and nat control is enabled, which is actually a first for me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Issue:&amp;nbsp; Tunnel to 192.168.193.0/24 comes up, showing it up at the bottom of the attached config.&amp;nbsp; I need to be able to pass traffic from 3 local subnets defined as object-group network DM_INLINE_NETWORK_1 to the 192.168.193.0/24 and I'm unable to.&amp;nbsp; Any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:36:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/natting-problem/m-p/2084845#M394219</guid>
      <dc:creator>WStoffel1</dc:creator>
      <dc:date>2019-03-12T00:36:21Z</dc:date>
    </item>
    <item>
      <title>NATting problem</title>
      <link>https://community.cisco.com/t5/network-security/natting-problem/m-p/2084846#M394220</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You are missing the the ACL on the NAT 0 rule:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list 105&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please add the following ACL:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list 105 permit ip object-group DM_INLINE_NETWORK_1 192.168.193.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need to make sure the other site of the tunnel has already the same config otherwise will not work. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Juan Lombana&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate helpful posts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Dec 2012 14:24:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/natting-problem/m-p/2084846#M394220</guid>
      <dc:creator>julomban</dc:creator>
      <dc:date>2012-12-12T14:24:38Z</dc:date>
    </item>
    <item>
      <title>NATting problem</title>
      <link>https://community.cisco.com/t5/network-security/natting-problem/m-p/2084847#M394221</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Fast response and you nailed it.&amp;nbsp; Thank you!&amp;nbsp; Traffic was flowing immediately.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any particular reason it's permit IP and not Extended Permit like the rest of 105?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Dec 2012 15:01:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/natting-problem/m-p/2084847#M394221</guid>
      <dc:creator>WStoffel1</dc:creator>
      <dc:date>2012-12-12T15:01:22Z</dc:date>
    </item>
    <item>
      <title>NATting problem</title>
      <link>https://community.cisco.com/t5/network-security/natting-problem/m-p/2084848#M394222</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am glad to hear that. The "extended" line is implicit, if you look again at show access-list 105 you will see the last line with the extended as the rest. This is include it automatically into any ACL you created. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Juan Lombana&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Dec 2012 15:06:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/natting-problem/m-p/2084848#M394222</guid>
      <dc:creator>julomban</dc:creator>
      <dc:date>2012-12-12T15:06:56Z</dc:date>
    </item>
    <item>
      <title>NATting problem</title>
      <link>https://community.cisco.com/t5/network-security/natting-problem/m-p/2084849#M394223</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Haha, 100% correct again, didn't realize that.&amp;nbsp; Thank you!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Dec 2012 15:18:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/natting-problem/m-p/2084849#M394223</guid>
      <dc:creator>WStoffel1</dc:creator>
      <dc:date>2012-12-12T15:18:53Z</dc:date>
    </item>
    <item>
      <title>NATting problem</title>
      <link>https://community.cisco.com/t5/network-security/natting-problem/m-p/2084850#M394224</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Your welcome!! &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>Wed, 12 Dec 2012 15:37:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/natting-problem/m-p/2084850#M394224</guid>
      <dc:creator>julomban</dc:creator>
      <dc:date>2012-12-12T15:37:28Z</dc:date>
    </item>
  </channel>
</rss>

