<?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 Port Forwarding Help in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/port-forwarding-help/m-p/1703829#M556465</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have a couple of ASA 5505's which work fine for what they are doing VPN and all that - we have 1 DLINK DFR-700 Firewall left and I need to get a new ASA to replace this since it is old.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All this box really does is port forward external clients to 1 address on the internal lan for client software updates.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So my question is since I have never really done this is does anybody have any example configs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So lets say we have client a with IP 1.1.1.1 and client b has 2.2.2.2 - at the moment this is what happens client a and b come in through http and get mapped to the internal http server 10.10.1.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I need to setup about 100 clients which can come in through http only - get mapped to the internal IP and also keeping the internal server to be able to access anything outside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Make sense?&lt;/P&gt;&lt;P&gt;Any help would be great - thanks&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 20:29:48 GMT</pubDate>
    <dc:creator>andrewgarlick</dc:creator>
    <dc:date>2019-03-11T20:29:48Z</dc:date>
    <item>
      <title>Port Forwarding Help</title>
      <link>https://community.cisco.com/t5/network-security/port-forwarding-help/m-p/1703829#M556465</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have a couple of ASA 5505's which work fine for what they are doing VPN and all that - we have 1 DLINK DFR-700 Firewall left and I need to get a new ASA to replace this since it is old.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All this box really does is port forward external clients to 1 address on the internal lan for client software updates.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So my question is since I have never really done this is does anybody have any example configs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So lets say we have client a with IP 1.1.1.1 and client b has 2.2.2.2 - at the moment this is what happens client a and b come in through http and get mapped to the internal http server 10.10.1.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I need to setup about 100 clients which can come in through http only - get mapped to the internal IP and also keeping the internal server to be able to access anything outside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Make sense?&lt;/P&gt;&lt;P&gt;Any help would be great - thanks&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:29:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/port-forwarding-help/m-p/1703829#M556465</guid>
      <dc:creator>andrewgarlick</dc:creator>
      <dc:date>2019-03-11T20:29:48Z</dc:date>
    </item>
    <item>
      <title>Re: Port Forwarding Help</title>
      <link>https://community.cisco.com/t5/network-security/port-forwarding-help/m-p/1703830#M556467</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andrew,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I understand you configuration correctly, you've got close to about 100 clients on the outside, which needs to be connected to your internal http server, so I assume your network topology is something like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;outside----------ASA-------------inside&lt;/P&gt;&lt;P&gt;(clients)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (server)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now to publish this particulatr server to the outside world , you would need to map it to a public ip address, lets say 100.100.100.100&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;and if you do not have a free IP address, you can use static port forwarding (which would only use a single potrt, instead of the whole IP address).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) tcp 100.100.100.100 443 10..10.10.10.10 443&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Along with that you would need to allow access to clients by applying an access-list on the outside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list outside_access extended permit tcp ho 1.1.1.1 ho 100.100.100.100&lt;/P&gt;&lt;P&gt;access-group outsidfe_access in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To give access to the internal users for the internet, you need the following rules:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 1 0 0&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The complete internal users would be patted to your outside interafce of the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is a document for ASA NAT/PAT:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a008046f31a.shtml"&gt;http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a008046f31a.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if this was wat you were looking out for.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Varun Rao&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 May 2011 18:28:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/port-forwarding-help/m-p/1703830#M556467</guid>
      <dc:creator>varrao</dc:creator>
      <dc:date>2011-05-05T18:28:38Z</dc:date>
    </item>
  </channel>
</rss>

