<?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: Problems accessing the internet in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/problems-accessing-the-internet/m-p/1382217#M694595</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For your router LAN to be able to route Internet traffic to the VPN tunnel towards the ASA, the crypto ACL needs to be:&lt;/P&gt;&lt;P&gt;On router: 10.14.0.0 0.0.255.255 any&lt;/P&gt;&lt;P&gt;On ASA: any 10.14.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On ASA, if you are routing the internet traffic out the outside interface of the ASA, you would need to configure the following:&lt;/P&gt;&lt;P&gt;same-security-traffic permit intra-interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And because the router LAN 10.14.0.0/16 is private ip address, before being routed towards the Internet on the ASA end, it needs to be PATed to public IP, hence you need to configure:&lt;/P&gt;&lt;P&gt;nat (outside) x 10.14.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;global (outside) x a.b.c.d&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OR/ you can use existing global sequence for example:&lt;/P&gt;&lt;P&gt;nat (outside) 10 10.14.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;which will use the corresponding global address of 12.69.103.129&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 24 Mar 2010 12:03:17 GMT</pubDate>
    <dc:creator>Jennifer Halim</dc:creator>
    <dc:date>2010-03-24T12:03:17Z</dc:date>
    <item>
      <title>Problems accessing the internet</title>
      <link>https://community.cisco.com/t5/network-security/problems-accessing-the-internet/m-p/1382216#M694574</link>
      <description>&lt;P&gt;Removed&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:25:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problems-accessing-the-internet/m-p/1382216#M694574</guid>
      <dc:creator>ronald.odom</dc:creator>
      <dc:date>2019-03-11T17:25:14Z</dc:date>
    </item>
    <item>
      <title>Re: Problems accessing the internet</title>
      <link>https://community.cisco.com/t5/network-security/problems-accessing-the-internet/m-p/1382217#M694595</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For your router LAN to be able to route Internet traffic to the VPN tunnel towards the ASA, the crypto ACL needs to be:&lt;/P&gt;&lt;P&gt;On router: 10.14.0.0 0.0.255.255 any&lt;/P&gt;&lt;P&gt;On ASA: any 10.14.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On ASA, if you are routing the internet traffic out the outside interface of the ASA, you would need to configure the following:&lt;/P&gt;&lt;P&gt;same-security-traffic permit intra-interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And because the router LAN 10.14.0.0/16 is private ip address, before being routed towards the Internet on the ASA end, it needs to be PATed to public IP, hence you need to configure:&lt;/P&gt;&lt;P&gt;nat (outside) x 10.14.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;global (outside) x a.b.c.d&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OR/ you can use existing global sequence for example:&lt;/P&gt;&lt;P&gt;nat (outside) 10 10.14.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;which will use the corresponding global address of 12.69.103.129&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Mar 2010 12:03:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problems-accessing-the-internet/m-p/1382217#M694595</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-03-24T12:03:17Z</dc:date>
    </item>
  </channel>
</rss>

