<?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 5520 ACCESS -OUTSIDE TO INSIDE in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5520-access-outside-to-inside/m-p/1887866#M458212</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are you configuring in CLI or ASDM?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPad App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 Mar 2012 22:30:45 GMT</pubDate>
    <dc:creator>CESAR GONZALEZ</dc:creator>
    <dc:date>2012-03-13T22:30:45Z</dc:date>
    <item>
      <title>ASA 5520 ACCESS -OUTSIDE TO INSIDE</title>
      <link>https://community.cisco.com/t5/network-security/asa-5520-access-outside-to-inside/m-p/1887863#M458209</link>
      <description>&lt;P&gt;We have a 5520 ASA which allows external users access to resources on our internal LAN network.  The resources that access is needed to are on a 192.168.x.x subnets.  These subnets cannot be routed across our WAN links.  All of our external sites are on a 10.x.x.x subnets and are routable across all our WAN links.  We are in the process of migrating the servers from 192.168.x.x to a 10.x.x.x address so we can take the ASA out in the near future.  The problem I am having is we want to give access to servers on a 10.115.50.0/24 subnet but not NAT the traffic.  What would be the rule that would allow access to 10.115.50.0/24 from 10.94.198.0/25 without any NATting but still keep my rules that NAT traffic to the 192.168.x.x&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Apologies if this is easy to do but I am not a firewall expert and thanks for looking and responding&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPad App&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:41:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5520-access-outside-to-inside/m-p/1887863#M458209</guid>
      <dc:creator>actkillerby</dc:creator>
      <dc:date>2019-03-11T22:41:37Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5520 ACCESS -OUTSIDE TO INSIDE</title>
      <link>https://community.cisco.com/t5/network-security/asa-5520-access-outside-to-inside/m-p/1887864#M458210</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you try adding a NAT Exempt Rule, with this option you can specify the source and destination network that will be exempted of the NAT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPad App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Mar 2012 22:24:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5520-access-outside-to-inside/m-p/1887864#M458210</guid>
      <dc:creator>CESAR GONZALEZ</dc:creator>
      <dc:date>2012-03-13T22:24:28Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5520 ACCESS -OUTSIDE TO INSIDE</title>
      <link>https://community.cisco.com/t5/network-security/asa-5520-access-outside-to-inside/m-p/1887865#M458211</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you have an example I can use please. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Mar 2012 22:29:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5520-access-outside-to-inside/m-p/1887865#M458211</guid>
      <dc:creator>actkillerby</dc:creator>
      <dc:date>2012-03-13T22:29:19Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5520 ACCESS -OUTSIDE TO INSIDE</title>
      <link>https://community.cisco.com/t5/network-security/asa-5520-access-outside-to-inside/m-p/1887866#M458212</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are you configuring in CLI or ASDM?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPad App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Mar 2012 22:30:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5520-access-outside-to-inside/m-p/1887866#M458212</guid>
      <dc:creator>CESAR GONZALEZ</dc:creator>
      <dc:date>2012-03-13T22:30:45Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5520 ACCESS -OUTSIDE TO INSIDE</title>
      <link>https://community.cisco.com/t5/network-security/asa-5520-access-outside-to-inside/m-p/1887867#M458213</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside_nat0_outbound line 12 extended permit ip 10.10.10.0 255.255.255.0 10.20.20.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPad App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Mar 2012 22:34:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5520-access-outside-to-inside/m-p/1887867#M458213</guid>
      <dc:creator>CESAR GONZALEZ</dc:creator>
      <dc:date>2012-03-13T22:34:21Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5520 ACCESS -OUTSIDE TO INSIDE</title>
      <link>https://community.cisco.com/t5/network-security/asa-5520-access-outside-to-inside/m-p/1887868#M458214</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From CLI &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Mar 2012 22:38:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5520-access-outside-to-inside/m-p/1887868#M458214</guid>
      <dc:creator>actkillerby</dc:creator>
      <dc:date>2012-03-13T22:38:26Z</dc:date>
    </item>
  </channel>
</rss>

