<?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: Help with command line access list in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986376#M400828</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My apologies for the delay, I didn't get the auto email reply saying someone has replied.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;THis is really useful, the only issue I had was how amend a rule on a line, for example I have loads of rules like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside_access_in line 177 extended permit tcp 192.168.20.0 255.255.254.0 10.20.30.0 255.255.255.0 eq 80&lt;/P&gt;&lt;P&gt;access-list inside_access_in line 177 extended permit tcp 192.168.20.0 255.255.254.0 10.20.30.0 255.255.255.0 eq 443&lt;/P&gt;&lt;P&gt;access-list inside_access_in line 177 extended permit tcp 192.168.20.0 255.255.254.0 10.20.30.0 255.255.255.0 eq 139&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How would I add?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside_access_in line 177 extended permit tcp 192.168.20.0 255.255.254.0 10.20.30.0 255.255.255.0 eq 445&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;as it seemed to add it on a new line 178&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Packet tracer is great I use this alot and packet capture, but I didn't know you can bind it to your local Wireshark, I normally export and import in to Wireshark.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 16 Aug 2012 10:42:30 GMT</pubDate>
    <dc:creator>Andrew White</dc:creator>
    <dc:date>2012-08-16T10:42:30Z</dc:date>
    <item>
      <title>Help with command line access list</title>
      <link>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986371#M400823</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I use the ASDM for lots of work onour ASA, but I want to start using the CLI to add access lists.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just created a rul onthe ASDM and looked at the syslog server and the command it used was:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 321 extended permit tcp object-group DM_INLINE_NETWORK_333 host 172.22.1.4 object-group DM_INLINE_TCP_87&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the ASDM all I did was create one rule containing 2 source IP's (192.168.1.10 and 192.168.168.1.20)&amp;nbsp; to get to 172.22.1.4 on ports 80 and 443, how would write this in CLI for one rule, as the ASA seems to create these straneg DM_INLINE groups?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:42:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986371#M400823</guid>
      <dc:creator>Andrew White</dc:creator>
      <dc:date>2019-03-11T23:42:05Z</dc:date>
    </item>
    <item>
      <title>Re: Help with command line access list</title>
      <link>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986372#M400824</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;DM_INLINE are object-groups created by the ASDM when you insert more than one IP/network/port into a section in the ASDM configurations &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best way to check what the ASDM does is to do the following&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Open ASDM and open the "Tools" in the toolbar and click on "Preferences"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="http://supportforums.cisco.com/sites/default/files/legacy/5/4/0/97045-toolbar.jpg" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now check the appropriate box to make it so that ASDM will always preview the CLI format of the configurations to you before sending to the device&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="http://supportforums.cisco.com/sites/default/files/legacy/6/4/0/97046-menu.jpg" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since you checked the inserted command from log I think you probably missed the messages about the ASA creating the object-groups.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Personally I never use ASDM for access rules. I always make the object-groups and ACLs on the CLI side. Same for NAT configurations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this was helpfull &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Aug 2012 11:55:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986372#M400824</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2012-08-14T11:55:52Z</dc:date>
    </item>
    <item>
      <title>Re: Help with command line access list</title>
      <link>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986373#M400825</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;And to answer your actual question of how to write the rule on the CLI, you can do several ways&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Option 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333;"&gt;&lt;STRONG&gt;access-list outside_access_in permit tcp host 192.168.1.10 host 172.22.1.4 eq 80&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333;"&gt;&lt;STRONG&gt;access-list outside_access_in permit tcp host 192.168.1.10 host 172.22.1.4 eq 443&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333;"&gt;&lt;STRONG&gt;access-list outside_access_in permit tcp host 192.168.1.20 host 172.22.1.4 eq 80&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333;"&gt;&lt;STRONG&gt;access-list outside_access_in permit tcp host 192.168.1.20 host 172.22.1.4 eq 443&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Option 2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object-group network HTTP-HTTPS-SOURCE&lt;/STRONG&gt; (or any other descriptive name)&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object host 192.168.1.10&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object host 192.168.1.20&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list outside_access_in permit tcp object-group HTTP-HTTPS-SOURCE host 172.22.1.4 eq 80&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list outside_access_in permit tcp object-group HTTP-HTTPS-SOURCE host 172.22.1.4 eq 443&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Option 3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- This is basically what the ASDM did but with "ugly" object-group names&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object-group network HTTP-HTTPS-SOURCE (or any other descriptive name)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object host 192.168.1.10&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object host 192.168.1.20&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object-group service HTTP-HTTPS tcp&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; port-object eq www&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; port-object eq https&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list outside_access_in permit tcp object-group HTTP-HTTPS-SOURCE host 172.22.1.4 object-group HTTP-HTTPS&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Aug 2012 12:06:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986373#M400825</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2012-08-14T12:06:45Z</dc:date>
    </item>
    <item>
      <title>Help with command line access list</title>
      <link>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986374#M400826</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Probably the best reply I have ever had to a forum post, thanks very much!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm going to start using this.&amp;nbsp; The only issue I have sometimes is finding access rules in the command line to edit as we have so many, do you have any usefulcommands to use to locate an access list?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Aug 2012 13:17:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986374#M400826</guid>
      <dc:creator>Andrew White</dc:creator>
      <dc:date>2012-08-14T13:17:57Z</dc:date>
    </item>
    <item>
      <title>Re: Help with command line access list</title>
      <link>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986375#M400827</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;Can you give some example situation where you are facing problems usually?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are some command I use when checking access-lists&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;show run access-group&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;This command lists all the access-lists that are attached to an interface on the firewall&lt;/LI&gt;&lt;LI&gt;Example of output could be: &lt;STRONG&gt;access-group INSIDE-IN in interface inside&lt;/STRONG&gt;. Which would tell that an access-list with the name INSIDE-IN is attached on the interface named "inside" in the direction "in". In other words it would check traffic that is arriving towards the interface.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;show run access-list &lt;ACCESS-LIST name=""&gt;&lt;/ACCESS-LIST&gt;&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;Shows the access-list in short form. It doesnt show the IP addressses/networks configured under object-groups.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;show access-list &lt;ACCESS-LIST name=""&gt;&lt;/ACCESS-LIST&gt;&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;Shows the WHOLE access-list. It shows a ACL line (ACE) as several rows if there ACE contains object-groups&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;show run object-group&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;Shows all object-groups configured on the device&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;show run object-group id &lt;OBJECT-GROUP name=""&gt;&lt;/OBJECT-GROUP&gt;&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;Shows the configurations for only the object-group defined in the command&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;show access-list &lt;ACCESS-LIST name=""&gt; | include x.x.x.x&lt;/ACCESS-LIST&gt;&lt;/STRONG&gt;&amp;nbsp;&amp;nbsp; OR &lt;STRONG&gt;show access-list | include x.x.x.x&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;Shows all access-list lines in certain named access-lists or all access-lists that contain the IP address x.x.x.x&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also if you are familiar with the packet-tracer on the ASDM side, you can use it on the CLI side too. With the command "packet-tracer". The format is as follows&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;packet-tracer input &lt;INTERFACE&gt; &lt;PROTOCOL&gt; &lt;SOURCE ip="" address=""&gt; &lt;SOURCE port=""&gt; &lt;DESTINATION ip="" address=""&gt; &lt;DESTINATION port=""&gt;&lt;/DESTINATION&gt;&lt;/DESTINATION&gt;&lt;/SOURCE&gt;&lt;/SOURCE&gt;&lt;/PROTOCOL&gt;&lt;/INTERFACE&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you issue the command the output on the CLI will mention the access-list line that the traffic matches to and this way can help you locate some access-list statement, if you didnt already find it with the above commands.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Those are the things that I think of right now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Aug 2012 13:37:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986375#M400827</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2012-08-14T13:37:50Z</dc:date>
    </item>
    <item>
      <title>Re: Help with command line access list</title>
      <link>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986376#M400828</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My apologies for the delay, I didn't get the auto email reply saying someone has replied.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;THis is really useful, the only issue I had was how amend a rule on a line, for example I have loads of rules like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside_access_in line 177 extended permit tcp 192.168.20.0 255.255.254.0 10.20.30.0 255.255.255.0 eq 80&lt;/P&gt;&lt;P&gt;access-list inside_access_in line 177 extended permit tcp 192.168.20.0 255.255.254.0 10.20.30.0 255.255.255.0 eq 443&lt;/P&gt;&lt;P&gt;access-list inside_access_in line 177 extended permit tcp 192.168.20.0 255.255.254.0 10.20.30.0 255.255.255.0 eq 139&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How would I add?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside_access_in line 177 extended permit tcp 192.168.20.0 255.255.254.0 10.20.30.0 255.255.255.0 eq 445&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;as it seemed to add it on a new line 178&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Packet tracer is great I use this alot and packet capture, but I didn't know you can bind it to your local Wireshark, I normally export and import in to Wireshark.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Aug 2012 10:42:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986376#M400828</guid>
      <dc:creator>Andrew White</dc:creator>
      <dc:date>2012-08-16T10:42:30Z</dc:date>
    </item>
    <item>
      <title>Re: Help with command line access list</title>
      <link>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986377#M400829</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;It seems to me that the 3 lines of ACL that you have copy pasted are actually part of a single ACE which contains object-groups&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Notice the "&lt;STRONG&gt;line 177&lt;/STRONG&gt;" in each of the lines.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Though still if you use the line number 177 with new configuration it should bump the old line 177 configuration to line 178&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To start viewing the access-list in question from line 177 you can do this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;show access-list inside_access_in | begin line 177&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The first output line in the configuration should be the actual configuration that contains object-groups. If theres an object-group for the services/ports opened you might be able to add the line in question just by adding the port to the same group with the other. (80,139,443)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you need to add some network or remove some network from that line you need to modify the network-objects under the object-groups.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also heres a small example of the situation I'm talking about above&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;object-group used in ACL&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object-group network LAN&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object 10.10.10.0 255.255.255.0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object 10.10.20.0 255.255.255.0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object 10.10.30.0 255.255.255.0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The actual ACL configuration line&amp;nbsp;&amp;nbsp; &lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;show run access-list TEST&lt;/STRONG&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list TEST extended permit ip object-group LAN any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The same ACL in "opened" form&amp;nbsp;&amp;nbsp; &lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;show access-list TEST&lt;/STRONG&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list TEST; 3 elements; name hash: 0xd37fdb2b&lt;/P&gt;&lt;P&gt;access-list TEST line 1 extended permit ip object-group LAN any 0xeb9e6e99&lt;/P&gt;&lt;P&gt;&amp;nbsp; access-list TEST line 1 extended permit ip 10.10.10.0 255.255.255.0 any (hitcnt=0) 0x365de33c&lt;/P&gt;&lt;P&gt;&amp;nbsp; access-list TEST line 1 extended permit ip 10.10.20.0 255.255.255.0 any (hitcnt=0) 0xc98d1b29&lt;/P&gt;&lt;P&gt;&amp;nbsp; access-list TEST line 1 extended permit ip 10.10.30.0 255.255.255.0 any (hitcnt=0) 0x2a9982d3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Remove one network from the object-group and look at the ACL&amp;nbsp;&amp;nbsp; &lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;object-group network LAN&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;no network-object 10.10.10.0 255.255.255.0&lt;/STRONG&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;show access-list TEST&lt;/STRONG&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list TEST; 2 elements; name hash: 0xd37fdb2b&lt;/P&gt;&lt;P&gt;access-list TEST line 1 extended permit ip object-group LAN any 0xeb9e6e99&lt;/P&gt;&lt;P&gt;&amp;nbsp; access-list TEST line 1 extended permit ip 10.10.20.0 255.255.255.0 any (hitcnt=0) 0xc98d1b29&lt;/P&gt;&lt;P&gt;&amp;nbsp; access-list TEST line 1 extended permit ip 10.10.30.0 255.255.255.0 any (hitcnt=0) 0x2a9982d3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Aug 2012 10:53:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986377#M400829</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2012-08-16T10:53:35Z</dc:date>
    </item>
    <item>
      <title>Re: Help with command line access list</title>
      <link>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986378#M400830</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also I'm not sure how to search for this, but I used one of your search commands to find a rule that contained IP 192.168.20.90 and it didn't find it.&amp;nbsp; But on the ASDM I noticed it was in a group, so I guess it woudl be in one of those DM_INLINE groups.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How woudl I search for an IP in a rule if it is hidden in one of those DM_INLIE groups?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Aug 2012 10:55:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986378#M400830</guid>
      <dc:creator>Andrew White</dc:creator>
      <dc:date>2012-08-16T10:55:54Z</dc:date>
    </item>
    <item>
      <title>Re: Help with command line access list</title>
      <link>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986379#M400831</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;If you use the &lt;STRONG&gt;"show access-list"&lt;/STRONG&gt; format of the command it should open up all the object-groups in the ACL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you use &lt;STRONG&gt;"show run access-list"&lt;/STRONG&gt; format of the command it doesnt show the IP addresses under the object-groups.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using the access-list I created in the above message as an example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;show &lt;SPAN style="color: #ff0000;"&gt;run&lt;/SPAN&gt; access-list TEST&lt;/STRONG&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list TEST extended permit ip object-group LAN any&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;show access-list TEST&lt;/STRONG&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list TEST; 3 elements; name hash: 0xd37fdb2b&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list TEST line 1 extended permit ip object-group LAN any 0xeb9e6e99&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; access-list TEST line 1 extended permit ip 10.10.10.0 255.255.255.0 any (hitcnt=0) 0x365de33c&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; access-list TEST line 1 extended permit ip 10.10.20.0 255.255.255.0 any (hitcnt=0) 0xc98d1b29&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; access-list TEST line 1 extended permit ip 10.10.30.0 255.255.255.0 any (hitcnt=0) 0x2a9982d3&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Aug 2012 10:59:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/help-with-command-line-access-list/m-p/1986379#M400831</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2012-08-16T10:59:30Z</dc:date>
    </item>
  </channel>
</rss>

