<?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: Fowarding Inside Traffic in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fowarding-inside-traffic/m-p/949932#M918445</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The solution I proposed to you seems more simpler, but this is just my opinion.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also use the port-redirection method. However you would need a redirection for each service you want LAN users to access, like FTP, HTTPS etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 14 Jun 2008 08:50:43 GMT</pubDate>
    <dc:creator>Farrukh Haroon</dc:creator>
    <dc:date>2008-06-14T08:50:43Z</dc:date>
    <item>
      <title>Fowarding Inside Traffic</title>
      <link>https://community.cisco.com/t5/network-security/fowarding-inside-traffic/m-p/949929#M918435</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I have an ASA 5540 and I would like to forward all HTTP traffic comming from LAN to my Proxy server on DMZ. This Proxy will filter the content and send the traffic back to ASA and ASA must forward to INTERNET (please check the attachment). &lt;/P&gt;&lt;P&gt;What should be the configuration on ASA to do this?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tauer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 12:58:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fowarding-inside-traffic/m-p/949929#M918435</guid>
      <dc:creator>Tauer Drumond</dc:creator>
      <dc:date>2019-03-11T12:58:41Z</dc:date>
    </item>
    <item>
      <title>Re: Fowarding Inside Traffic</title>
      <link>https://community.cisco.com/t5/network-security/fowarding-inside-traffic/m-p/949930#M918439</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Assuming LAN = 192.168.1.0 /24&lt;/P&gt;&lt;P&gt;DMZ = 172.16.16.0/24 &lt;/P&gt;&lt;P&gt;Outside = 172.17.17.0/24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PROXY SERVER = 172.16.16.16&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside-in permit icmp 192.168.1.0 255.255.255.255 any &lt;/P&gt;&lt;P&gt;! you can be more specific with ICMP types&lt;/P&gt;&lt;P&gt;access-list inside-in permit tcp 192.168.1.0 255.255.255.255 host 172.16.16.16 eq 8080&lt;/P&gt;&lt;P&gt;access-list inside-in deny ip 192.168.1.0 255.255.255.255 any log&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please note if your PROXY is MS ISA, then you cannot run Secure NAT mode with one interface, you can only run Cache or Web Proxy mode I think.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list dmz-in permit ip host 172.16.16.16  any&lt;/P&gt;&lt;P&gt;! This can be made more secure by permitting &lt;/P&gt;&lt;P&gt;! only wanted protocols like http,https,ftp etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (dmz) 1 172.16.16.16 255.255.255.255&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;! Static One to One NAT might be a better   &lt;/P&gt;&lt;P&gt;! option, to keep 'no nat-control' active&lt;/P&gt;&lt;P&gt;I'm sure this has a lot of mistakes, its just a template.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Jun 2008 19:56:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fowarding-inside-traffic/m-p/949930#M918439</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-06-12T19:56:13Z</dc:date>
    </item>
    <item>
      <title>Re: Fowarding Inside Traffic</title>
      <link>https://community.cisco.com/t5/network-security/fowarding-inside-traffic/m-p/949931#M918442</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Farrukh,&lt;/P&gt;&lt;P&gt;Should I apply some port redirection?&lt;/P&gt;&lt;P&gt;All traffic on interface LAN to INTERNET on port 80 (HTTP) I do a port forward to PROXY on port 8080... &lt;/P&gt;&lt;P&gt;And all traffic on port 80 came from PROXY, I nat to outside interface.&lt;/P&gt;&lt;P&gt;Is that allright?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Jun 2008 01:33:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fowarding-inside-traffic/m-p/949931#M918442</guid>
      <dc:creator>Tauer Drumond</dc:creator>
      <dc:date>2008-06-13T01:33:44Z</dc:date>
    </item>
    <item>
      <title>Re: Fowarding Inside Traffic</title>
      <link>https://community.cisco.com/t5/network-security/fowarding-inside-traffic/m-p/949932#M918445</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The solution I proposed to you seems more simpler, but this is just my opinion.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also use the port-redirection method. However you would need a redirection for each service you want LAN users to access, like FTP, HTTPS etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 14 Jun 2008 08:50:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fowarding-inside-traffic/m-p/949932#M918445</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-06-14T08:50:43Z</dc:date>
    </item>
    <item>
      <title>Re: Fowarding Inside Traffic</title>
      <link>https://community.cisco.com/t5/network-security/fowarding-inside-traffic/m-p/949933#M918447</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, Set the client machines gateway IP  of Proxy Server and the gateway of proxy server must be used ASA FW IP. As per my opinion, this is one of the simple and very good way. All please give your feedback in this regard.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 14 Jun 2008 17:53:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fowarding-inside-traffic/m-p/949933#M918447</guid>
      <dc:creator>ray_stone</dc:creator>
      <dc:date>2008-06-14T17:53:26Z</dc:date>
    </item>
    <item>
      <title>Re: Fowarding Inside Traffic</title>
      <link>https://community.cisco.com/t5/network-security/fowarding-inside-traffic/m-p/949934#M918450</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;RAY,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yup I'll go with ray.&lt;/P&gt;&lt;P&gt;but I'll try all three methods.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 15 Jun 2008 11:36:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fowarding-inside-traffic/m-p/949934#M918450</guid>
      <dc:creator>nomair_83</dc:creator>
      <dc:date>2008-06-15T11:36:06Z</dc:date>
    </item>
    <item>
      <title>Re: Fowarding Inside Traffic</title>
      <link>https://community.cisco.com/t5/network-security/fowarding-inside-traffic/m-p/949935#M918452</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI, &lt;/P&gt;&lt;P&gt;what should be the line configuration to all HTTP traffic coming from LAN and redirect to the PROXY on DMZ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jun 2008 12:20:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fowarding-inside-traffic/m-p/949935#M918452</guid>
      <dc:creator>Tauer Drumond</dc:creator>
      <dc:date>2008-06-17T12:20:15Z</dc:date>
    </item>
  </channel>
</rss>

