<?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: configuring ASA5505 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/configuring-asa5505/m-p/1178364#M861003</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normally Cisco recommends router at Publicly connected network for typically SMB-Large organization. But, connected public ip to ASA interface is not bad either.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can have DHCP done y Linksys wireless device. But, I strongly recommend doing NAT at ASA5505. Cisco ASA is good for NAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to have further strict policies for http, ftp, esmtp traffic, you can create application policy map and use them, use regex to block websites or web messengers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Apr 2009 00:15:09 GMT</pubDate>
    <dc:creator>roshan.maskey</dc:creator>
    <dc:date>2009-04-09T00:15:09Z</dc:date>
    <item>
      <title>configuring ASA5505</title>
      <link>https://community.cisco.com/t5/network-security/configuring-asa5505/m-p/1178363#M861000</link>
      <description>&lt;P&gt;How to best secure an inside network? ASA5505's outside interface has a static public IP. The following is the physical topology.&lt;/P&gt;&lt;P&gt;DSLmodem/router &amp;lt;&amp;gt; ASA5505 &amp;lt;&amp;gt; Linksys wireless router &amp;lt;&amp;gt; wireless users.&lt;/P&gt;&lt;P&gt;The DSL modem will be in bridge mode. The Linksys will provide DHCP to the internal users. &lt;/P&gt;&lt;P&gt;1. Is it best to assign a public IP to ASA's inside interface?&lt;/P&gt;&lt;P&gt;2. Linksys wireless would be connected to a switch port of the ASA and the remaining switch ports will be disabled. &lt;/P&gt;&lt;P&gt;3. PAT would be done on the Linksys.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 15:16:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/configuring-asa5505/m-p/1178363#M861000</guid>
      <dc:creator>saidfrh</dc:creator>
      <dc:date>2019-03-11T15:16:36Z</dc:date>
    </item>
    <item>
      <title>Re: configuring ASA5505</title>
      <link>https://community.cisco.com/t5/network-security/configuring-asa5505/m-p/1178364#M861003</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normally Cisco recommends router at Publicly connected network for typically SMB-Large organization. But, connected public ip to ASA interface is not bad either.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can have DHCP done y Linksys wireless device. But, I strongly recommend doing NAT at ASA5505. Cisco ASA is good for NAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to have further strict policies for http, ftp, esmtp traffic, you can create application policy map and use them, use regex to block websites or web messengers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Apr 2009 00:15:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/configuring-asa5505/m-p/1178364#M861003</guid>
      <dc:creator>roshan.maskey</dc:creator>
      <dc:date>2009-04-09T00:15:09Z</dc:date>
    </item>
  </channel>
</rss>

