<?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 Hi Carlos, in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/guest-public-wifi-interface-needs-access-to-internal-resource/m-p/2778344#M175345</link>
    <description>&lt;P&gt;Hi Carlos,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;You can create a static NAT between the guestwifi and web similar to your outside to web, this should work.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Shivapramod M&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 03 Nov 2015 01:12:14 GMT</pubDate>
    <dc:creator>Shivapramod M</dc:creator>
    <dc:date>2015-11-03T01:12:14Z</dc:date>
    <item>
      <title>Guest\Public_Wifi Interface needs access to internal resource via external IP</title>
      <link>https://community.cisco.com/t5/network-security/guest-public-wifi-interface-needs-access-to-internal-resource/m-p/2778343#M175344</link>
      <description>&lt;P&gt;I've got an ASA with two "outside" interfaces and twelve "inside" interfaces.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;One of those twelve inside interfaces is called "Guest_Wifi" and all it has access to is the internet. Some of the resources it needs access to are resources on another inside interface called "Web" that are also publicly accessible.&amp;nbsp; DNS for the "Guest_Wifi" network is being provided by a 3rd party (OpenDNS).&lt;/P&gt;
&lt;P&gt;How can I allow users on the "Guest_Wifi" network access to our resources in the "Web" interface via their external IP addresses?&lt;/P&gt;
&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 06:49:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/guest-public-wifi-interface-needs-access-to-internal-resource/m-p/2778343#M175344</guid>
      <dc:creator>carlos.garza</dc:creator>
      <dc:date>2019-03-12T06:49:28Z</dc:date>
    </item>
    <item>
      <title>Hi Carlos,</title>
      <link>https://community.cisco.com/t5/network-security/guest-public-wifi-interface-needs-access-to-internal-resource/m-p/2778344#M175345</link>
      <description>&lt;P&gt;Hi Carlos,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;You can create a static NAT between the guestwifi and web similar to your outside to web, this should work.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Shivapramod M&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Nov 2015 01:12:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/guest-public-wifi-interface-needs-access-to-internal-resource/m-p/2778344#M175345</guid>
      <dc:creator>Shivapramod M</dc:creator>
      <dc:date>2015-11-03T01:12:14Z</dc:date>
    </item>
    <item>
      <title>Hi Carlos,</title>
      <link>https://community.cisco.com/t5/network-security/guest-public-wifi-interface-needs-access-to-internal-resource/m-p/2778345#M175346</link>
      <description>&lt;P&gt;Hi Carlos,&lt;/P&gt;
&lt;P&gt;Adding to Shivpramod's suggestion, ensure you create appropriate ACLs to permit traffic between interfaces with different security levels.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;HTH,&lt;/P&gt;
&lt;P&gt;R.Seth&lt;/P&gt;</description>
      <pubDate>Tue, 03 Nov 2015 01:19:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/guest-public-wifi-interface-needs-access-to-internal-resource/m-p/2778345#M175346</guid>
      <dc:creator>Rishabh Seth</dc:creator>
      <dc:date>2015-11-03T01:19:03Z</dc:date>
    </item>
  </channel>
</rss>

