<?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: ISE TCP dump - limited filters in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/3587844#M510978</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It looks like this changed at some point (maybe with 2.3?) as I know I have used simple port filters in the past, but for some reason ISE won't take a port filter unless I also specify an 'ip host' filter. If you're trying to filter on a port, you might just include the ISE node IP address as a workaround.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Screen Shot 2018-04-10 at 10.46.20 am.png" class="image-1 jive-image" src="/legacyfs/online/fusion/116460_Screen Shot 2018-04-10 at 10.46.20 am.png" style="height: auto;" /&gt;&lt;/P&gt;&lt;P&gt;Maybe one of the TME's that monitor the community page can provide some clarification if this is expected behaviour or should be considered a bug.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Regards,&lt;/P&gt;&lt;P&gt;Greg&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 Apr 2018 00:53:24 GMT</pubDate>
    <dc:creator>Greg Gibbs</dc:creator>
    <dc:date>2018-04-10T00:53:24Z</dc:date>
    <item>
      <title>ISE TCP dump - limited filters</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/3587843#M510975</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I understand the ISE Admin Guide correctly, the ONLY expression that ISE supports is "ip host" ?&amp;nbsp; I have misunderstood 'standard' to mean that ISE supports the standard tcpdump expressions &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It would be nice to be able to apply the &lt;EM&gt;&lt;STRONG&gt;standard&lt;/STRONG&gt;&lt;/EM&gt; filters &lt;IMG src="https://community.cisco.com/legacyfs/online/emoticons/confused.png" /&gt; - would this be considered a feature request?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="jive-image image-2" src="https://community.cisco.com/legacyfs/online/fusion/116443_pastedImage_2.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="image-1 jive-image" src="https://community.cisco.com/legacyfs/online/fusion/116441_pastedImage_0.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Apr 2018 03:41:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/3587843#M510975</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2018-04-09T03:41:36Z</dc:date>
    </item>
    <item>
      <title>Re: ISE TCP dump - limited filters</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/3587844#M510978</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It looks like this changed at some point (maybe with 2.3?) as I know I have used simple port filters in the past, but for some reason ISE won't take a port filter unless I also specify an 'ip host' filter. If you're trying to filter on a port, you might just include the ISE node IP address as a workaround.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Screen Shot 2018-04-10 at 10.46.20 am.png" class="image-1 jive-image" src="/legacyfs/online/fusion/116460_Screen Shot 2018-04-10 at 10.46.20 am.png" style="height: auto;" /&gt;&lt;/P&gt;&lt;P&gt;Maybe one of the TME's that monitor the community page can provide some clarification if this is expected behaviour or should be considered a bug.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Regards,&lt;/P&gt;&lt;P&gt;Greg&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Apr 2018 00:53:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/3587844#M510978</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2018-04-10T00:53:24Z</dc:date>
    </item>
    <item>
      <title>Re: ISE TCP dump - limited filters</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/3587845#M510981</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;nice workaround &lt;IMG src="https://community.cisco.com/legacyfs/online/emoticons/cool.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Apr 2018 05:18:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/3587845#M510981</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2018-04-10T05:18:15Z</dc:date>
    </item>
    <item>
      <title>Re: ISE TCP dump - limited filters</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/3587846#M510985</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.cisco.com//u1/38995"&gt;hslai&lt;/A&gt;, do you have any knowledge about or comment on this change of behaviour for the tcpdump filter?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Apr 2018 21:28:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/3587846#M510985</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2018-04-10T21:28:23Z</dc:date>
    </item>
    <item>
      <title>Re: ISE TCP dump - limited filters</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/3587847#M510986</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;+1&lt;/P&gt;&lt;P&gt;I am guessing it might be due to moving this utility from flash to HTML5.&lt;/P&gt;&lt;P&gt;CSCvd36140 is an enhancement to allow other options and currently internal but I will add an RNE and make it external.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Apr 2018 21:48:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/3587847#M510986</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-04-10T21:48:33Z</dc:date>
    </item>
    <item>
      <title>Re: ISE TCP dump - limited filters</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/4095676#M560811</link>
      <description>This is unfortunately still a problem in 2.6 and 2.7. I wanted to capture all DHCP traffic via the TCPDump utility, sadly can't.</description>
      <pubDate>Mon, 01 Jun 2020 18:43:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/4095676#M560811</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2020-06-01T18:43:50Z</dc:date>
    </item>
    <item>
      <title>Re: ISE TCP dump - limited filters</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/4096127#M560833</link>
      <description>&lt;P&gt;funny you say that ... today I used the crude tcpdump on the CLI and captured all the output to a text file - I was testing the SMTP and I found what I was looking for. But it did feel a bit 1984'ish ... there's a perfectly good Linux tcpdump just sitting under the covers ... now if only I could get my grubby paws on it ... &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jun 2020 12:46:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/4096127#M560833</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2020-06-02T12:46:13Z</dc:date>
    </item>
    <item>
      <title>Re: ISE TCP dump - limited filters</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/4096146#M560834</link>
      <description>You will be pleasantly surprised in the next few months &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;</description>
      <pubDate>Tue, 02 Jun 2020 13:10:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/4096146#M560834</guid>
      <dc:creator>Anurag Sharma</dc:creator>
      <dc:date>2020-06-02T13:10:01Z</dc:date>
    </item>
    <item>
      <title>Re: ISE TCP dump - limited filters</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/4096208#M560837</link>
      <description>Hsing-Tsu made a great suggestion. Because I am pcaping a single node the following worked from the GUI, "ip hose &amp;lt;psn ip&amp;gt; and port 67".&lt;BR /&gt;&lt;BR /&gt;Eddie also suggested the CLI as an alternative, ex. "tech dumptcp 0 | inc "\.22 \&amp;gt;""&lt;BR /&gt;&lt;BR /&gt;The next GUI doesn't have this issue &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;</description>
      <pubDate>Tue, 02 Jun 2020 15:04:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/4096208#M560837</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2020-06-02T15:04:55Z</dc:date>
    </item>
    <item>
      <title>Re: ISE TCP dump - limited filters</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/4612933#M574878</link>
      <description>&lt;P&gt;Well ?&lt;/P&gt;
&lt;P&gt;In 2022, ISE 2.7 with patch 7 does not still have this repaired.&lt;/P&gt;
&lt;P&gt;So workaround with using ip host plus and port still works.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It seems it is BUG and that was not still fixed at all. What do you think now ?&lt;/P&gt;</description>
      <pubDate>Thu, 19 May 2022 10:06:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/4612933#M574878</guid>
      <dc:creator>stayd</dc:creator>
      <dc:date>2022-05-19T10:06:32Z</dc:date>
    </item>
    <item>
      <title>Re: ISE TCP dump - limited filters</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/4613496#M574891</link>
      <description>&lt;P&gt;Don't expect too much to get fixed in ISE 2.7. No matter what version of ISE you're on you're always at the mercy of Cisco making these tools available to you. All the while, the tools that can do the job are already there in Linux, but hidden from us (no access). Prime Infrastructure has root access, so does DNAC. Even a non-root shell would be nice.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 May 2022 20:23:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/4613496#M574891</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2022-05-19T20:23:31Z</dc:date>
    </item>
    <item>
      <title>Re: ISE TCP dump - limited filters</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/4632292#M575488</link>
      <description>&lt;P&gt;Can I expect it in version 3.1 ?&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jun 2022 10:27:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tcp-dump-limited-filters/m-p/4632292#M575488</guid>
      <dc:creator>stayd</dc:creator>
      <dc:date>2022-06-15T10:27:01Z</dc:date>
    </item>
  </channel>
</rss>

