<?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 Allow traffic inside to outside in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/allow-traffic-inside-to-outside/m-p/1856842#M492806</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The host should be able to acess the public website just fine, unless there are entries in your ACLs that are&lt;/P&gt;&lt;P&gt;preventing it from doing so. As far as restricting based on traffic, I'm sure you could do some sort of traffic polcing&lt;/P&gt;&lt;P&gt;or QoS for that specific host, but I have no idea how. I've never done that on an ASA before, so I don't want to tell&lt;/P&gt;&lt;P&gt;you wrong.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 19 Nov 2011 13:12:52 GMT</pubDate>
    <dc:creator>JohnTylerPearce</dc:creator>
    <dc:date>2011-11-19T13:12:52Z</dc:date>
    <item>
      <title>Allow traffic inside to outside</title>
      <link>https://community.cisco.com/t5/network-security/allow-traffic-inside-to-outside/m-p/1856839#M492800</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One Host on inside network needs to access customized application hosted on Internet. Its a customized application run on port 80, 443, 5000-to-50020 &lt;/P&gt;&lt;P&gt;How do I allow this host access for this specific application. I got ASA 5510 and host is in the inside network, we also got an ACL on inside interface to have control. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Host IP on inside network&amp;nbsp; - 172.16.30.15&lt;/P&gt;&lt;P&gt;Application to access - 74.219.x.x&lt;/P&gt;&lt;P&gt;Inside ACL name - inside-acl&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:53:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/allow-traffic-inside-to-outside/m-p/1856839#M492800</guid>
      <dc:creator>paultim68</dc:creator>
      <dc:date>2019-03-11T21:53:00Z</dc:date>
    </item>
    <item>
      <title>Allow traffic inside to outside</title>
      <link>https://community.cisco.com/t5/network-security/allow-traffic-inside-to-outside/m-p/1856840#M492803</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Well, by default, all traffic from a higher security-level interface is allowed access to a lower-security level interface, unless there is a specific entry in an ACL that is blocking it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have to include an entry in the "inside-acl" to get it out, I would do the following&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object-group service CustApp tcp&lt;/P&gt;&lt;P&gt; port-object 80&lt;/P&gt;&lt;P&gt; port-object 443&lt;/P&gt;&lt;P&gt; port-object range 5000 50020&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside-acl permit tcp host 172.16.30.15 74.219.0.0 255.255.0.0 object-group service CustApp&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think that's right. I sometimes have to use the ? mark to help me out, I'm winging this without an ASA handy.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Nov 2011 11:26:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/allow-traffic-inside-to-outside/m-p/1856840#M492803</guid>
      <dc:creator>JohnTylerPearce</dc:creator>
      <dc:date>2011-11-19T11:26:11Z</dc:date>
    </item>
    <item>
      <title>Allow traffic inside to outside</title>
      <link>https://community.cisco.com/t5/network-security/allow-traffic-inside-to-outside/m-p/1856841#M492805</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks John&lt;/P&gt;&lt;P&gt;what happens if the host access access public website &lt;A href="https://community.cisco.com/www.yahoo.com" target="_blank"&gt;www.yahoo.com&lt;/A&gt; ( port 80 ) ; will it be blocked&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can i restrict bandwidth for this host to use 256kbps max for this connection (in/out)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Nov 2011 11:37:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/allow-traffic-inside-to-outside/m-p/1856841#M492805</guid>
      <dc:creator>paultim68</dc:creator>
      <dc:date>2011-11-19T11:37:06Z</dc:date>
    </item>
    <item>
      <title>Allow traffic inside to outside</title>
      <link>https://community.cisco.com/t5/network-security/allow-traffic-inside-to-outside/m-p/1856842#M492806</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The host should be able to acess the public website just fine, unless there are entries in your ACLs that are&lt;/P&gt;&lt;P&gt;preventing it from doing so. As far as restricting based on traffic, I'm sure you could do some sort of traffic polcing&lt;/P&gt;&lt;P&gt;or QoS for that specific host, but I have no idea how. I've never done that on an ASA before, so I don't want to tell&lt;/P&gt;&lt;P&gt;you wrong.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Nov 2011 13:12:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/allow-traffic-inside-to-outside/m-p/1856842#M492806</guid>
      <dc:creator>JohnTylerPearce</dc:creator>
      <dc:date>2011-11-19T13:12:52Z</dc:date>
    </item>
    <item>
      <title>Allow traffic inside to outside</title>
      <link>https://community.cisco.com/t5/network-security/allow-traffic-inside-to-outside/m-p/1856843#M492808</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi John&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want internal host &lt;STRONG&gt;172.16.30.15&lt;/STRONG&gt; to talk to external host &lt;STRONG&gt;74.219.x.x&lt;/STRONG&gt; on port 80, 443,5000 50020 only.&amp;nbsp; Traffic initiated from host 172.16.30.15 to any other host on internet should be blocked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Nov 2011 05:09:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/allow-traffic-inside-to-outside/m-p/1856843#M492808</guid>
      <dc:creator>paultim68</dc:creator>
      <dc:date>2011-11-20T05:09:08Z</dc:date>
    </item>
    <item>
      <title>Allow traffic inside to outside</title>
      <link>https://community.cisco.com/t5/network-security/allow-traffic-inside-to-outside/m-p/1856844#M492810</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; I would apply this to the inside interface. Now, I have no idea what specific entries you have on&lt;/P&gt;&lt;P&gt;your inside access list, so I'll write it, as if it's a brand new configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside_access_in permit tcp host 172.16.30.15 74.219.0.0 255.255.0.0 obect-group service Ports&lt;/P&gt;&lt;P&gt;access-list inside_access_in deny ip host 172.16.30.15 any&lt;/P&gt;&lt;P&gt;access-list inside_access_in permit ip any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group inside_access_in in interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will allow host 172.16.30.15 tcp access to 74.219.x.x on the specific ports, then all other IP traffic&lt;/P&gt;&lt;P&gt;will be denied via the next line. Then you will have a permit ip any any at the end. That way everything else&lt;/P&gt;&lt;P&gt;is wide open outbound.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Nov 2011 18:32:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/allow-traffic-inside-to-outside/m-p/1856844#M492810</guid>
      <dc:creator>JohnTylerPearce</dc:creator>
      <dc:date>2011-11-20T18:32:00Z</dc:date>
    </item>
  </channel>
</rss>

