<?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: Inside interface outbound ACL applied but not blocking traff in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/inside-interface-outbound-acl-applied-but-not-blocking-traffic/m-p/1571739#M607029</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It appears that you need to change the source and destination on this ACL&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside_access_out extended deny object-group sslvpn-denied-protocols&amp;nbsp; 192.168.61.0 255.255.255.0 object obj_any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;as this line below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside,any) source static obj-192.168.61.0 obj-192.168.61.0 destination static obj-192.168.60.0 obj-192.168.60.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;indicates that the n/w 192.168.61.0 lives on the inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Nov 2010 18:53:33 GMT</pubDate>
    <dc:creator>Kureli Sankar</dc:creator>
    <dc:date>2010-11-11T18:53:33Z</dc:date>
    <item>
      <title>Inside interface outbound ACL applied but not blocking traffic</title>
      <link>https://community.cisco.com/t5/network-security/inside-interface-outbound-acl-applied-but-not-blocking-traffic/m-p/1571737#M607027</link>
      <description>&lt;P&gt;I have the following ACL below applied to inside interface in the outbound direction but it is not blocking ports I want it to currently.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not sure what I'm fundamentally missing in order to make this work.&amp;nbsp; Can someone provide suggestions?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA5505 Ver 8.3(2)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;object network obj_any &lt;BR /&gt; subnet 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;object network obj-192.168.60.0 &lt;BR /&gt; subnet 192.168.60.0 255.255.255.0&lt;/P&gt;&lt;P&gt;object network obj-192.168.61.0 &lt;BR /&gt; subnet 192.168.61.0 255.255.255.0&lt;/P&gt;&lt;P&gt;object service Microsoft-DS &lt;BR /&gt; service tcp destination eq 445 &lt;BR /&gt; description Microsoft-DS&lt;/P&gt;&lt;P&gt;object network obj_192.168.61.4 &lt;BR /&gt; host 192.168.61.4&lt;BR /&gt; description Inside_Interface_IP&lt;/P&gt;&lt;P&gt;object-group service sslvpn-denied-protocols&lt;BR /&gt; description Deny SSLVPN user access to these services&lt;BR /&gt; service-object object Microsoft-DS &lt;BR /&gt; service-object tcp-udp destination eq cifs &lt;BR /&gt; service-object tcp destination eq ftp &lt;BR /&gt; service-object tcp destination eq ftp-data &lt;BR /&gt; service-object tcp destination eq imap4 &lt;BR /&gt; service-object tcp destination eq netbios-ssn &lt;BR /&gt; service-object tcp destination eq pop2 &lt;BR /&gt; service-object tcp destination eq pop3 &lt;BR /&gt; service-object tcp destination eq smtp &lt;BR /&gt; service-object udp destination eq nameserver &lt;BR /&gt; service-object udp destination eq netbios-dgm &lt;BR /&gt; service-object udp destination eq netbios-ns&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;nat (inside,any) source static obj-192.168.61.0 obj-192.168.61.0 destination static obj-192.168.60.0 obj-192.168.60.0&lt;BR /&gt;!&lt;BR /&gt;object network obj_any&lt;BR /&gt; nat (inside,outside) dynamic interface&lt;BR /&gt;access-group inside_access_out out interface inside&lt;/P&gt;&lt;P&gt;access-list inside_access_out extended deny object-group sslvpn-denied-protocols object obj_any 192.168.61.0 255.255.255.0 &lt;BR /&gt;access-list inside_access_out extended permit ip any 192.168.61.0 255.255.255.0&lt;/P&gt;&lt;P&gt;!&lt;BR /&gt;interface Vlan1&lt;BR /&gt; description Internal UD LAN&lt;BR /&gt; nameif inside&lt;BR /&gt; security-level 100&lt;BR /&gt; ip address 192.168.61.4 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 19:08:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-interface-outbound-acl-applied-but-not-blocking-traffic/m-p/1571737#M607027</guid>
      <dc:creator>pattyj</dc:creator>
      <dc:date>2019-03-11T19:08:06Z</dc:date>
    </item>
    <item>
      <title>Re: Inside interface outbound ACL applied but not blocking traff</title>
      <link>https://community.cisco.com/t5/network-security/inside-interface-outbound-acl-applied-but-not-blocking-traffic/m-p/1571738#M607028</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not very familiar with the ACL syntax in 8.3 yet but just a note:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside_access_out extended deny object-group sslvpn-denied-protocols object obj_any 192.168.61.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Isn't the object-group that you want to deny for services specified as the source here?&lt;/P&gt;&lt;P&gt;I mean... normally it would be like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside_access_out extended deny&amp;nbsp; object obj_any 192.168.61.0 255.255.255.0 object-group sslvpn-denied-protocols&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So that the denied server are the destination ports (not the source ports).&lt;/P&gt;&lt;P&gt;I'm not sure on this one, but you can give it a try..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Federico.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Nov 2010 18:39:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-interface-outbound-acl-applied-but-not-blocking-traffic/m-p/1571738#M607028</guid>
      <dc:creator>Federico Coto Fajardo</dc:creator>
      <dc:date>2010-11-11T18:39:28Z</dc:date>
    </item>
    <item>
      <title>Re: Inside interface outbound ACL applied but not blocking traff</title>
      <link>https://community.cisco.com/t5/network-security/inside-interface-outbound-acl-applied-but-not-blocking-traffic/m-p/1571739#M607029</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It appears that you need to change the source and destination on this ACL&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside_access_out extended deny object-group sslvpn-denied-protocols&amp;nbsp; 192.168.61.0 255.255.255.0 object obj_any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;as this line below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside,any) source static obj-192.168.61.0 obj-192.168.61.0 destination static obj-192.168.60.0 obj-192.168.60.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;indicates that the n/w 192.168.61.0 lives on the inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Nov 2010 18:53:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-interface-outbound-acl-applied-but-not-blocking-traffic/m-p/1571739#M607029</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-11-11T18:53:33Z</dc:date>
    </item>
    <item>
      <title>Re: Inside interface outbound ACL applied but not blocking traff</title>
      <link>https://community.cisco.com/t5/network-security/inside-interface-outbound-acl-applied-but-not-blocking-traffic/m-p/1571740#M607030</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;I'm sorry I didn't specify context.&amp;nbsp; The ASA is setup as an SSLVPN.&amp;nbsp; I want to block traffic to certain ports like FTP, NetBIOS, SMTP on the 192.168.61.0/24 inside network for the SSL VPN clients.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SSL VPN User ---------Internet------ASA5505---Internal LAN--192.168.61.0/24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to block SSL VPN users from getting certain services on the LAN behind the ASA5505 so I thought I would deny these services as outbound on the Inside ASA interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does that make more sense?&amp;nbsp; Thanks for the replies.&amp;nbsp; Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Nov 2010 19:27:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-interface-outbound-acl-applied-but-not-blocking-traffic/m-p/1571740#M607030</guid>
      <dc:creator>pattyj</dc:creator>
      <dc:date>2010-11-11T19:27:05Z</dc:date>
    </item>
    <item>
      <title>Re: Inside interface outbound ACL applied but not blocking traff</title>
      <link>https://community.cisco.com/t5/network-security/inside-interface-outbound-acl-applied-but-not-blocking-traffic/m-p/1571741#M607031</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess that makes sense yes, but the recommended way to block traffic inside a tunnel is by creating ACLs and applying them to the group-policy used by the clients.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can configure them via ASDM or CLI under the group-policy with the command ''vpn-filter'' and associate the ACL. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Federico.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Nov 2010 20:22:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-interface-outbound-acl-applied-but-not-blocking-traffic/m-p/1571741#M607031</guid>
      <dc:creator>Federico Coto Fajardo</dc:creator>
      <dc:date>2010-11-11T20:22:33Z</dc:date>
    </item>
  </channel>
</rss>

