<?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 TCPdump with NAC in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/tcpdump-with-nac/m-p/1145098#M774183</link>
    <description>&lt;P&gt;How can I use TCPdump with the CAS?  When specifying a physical interface while using TCPdump, it only picks up broadcast traffic.  For example tcpdump -vv -nn -i eth1.  Is there special options to look at all traffic through the CAS in my L3 deployment.  Do I need to use the fake interfaces?&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 11:21:54 GMT</pubDate>
    <dc:creator>hillegas</dc:creator>
    <dc:date>2020-02-21T11:21:54Z</dc:date>
    <item>
      <title>TCPdump with NAC</title>
      <link>https://community.cisco.com/t5/network-security/tcpdump-with-nac/m-p/1145098#M774183</link>
      <description>&lt;P&gt;How can I use TCPdump with the CAS?  When specifying a physical interface while using TCPdump, it only picks up broadcast traffic.  For example tcpdump -vv -nn -i eth1.  Is there special options to look at all traffic through the CAS in my L3 deployment.  Do I need to use the fake interfaces?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 11:21:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcpdump-with-nac/m-p/1145098#M774183</guid>
      <dc:creator>hillegas</dc:creator>
      <dc:date>2020-02-21T11:21:54Z</dc:date>
    </item>
    <item>
      <title>Re: TCPdump with NAC</title>
      <link>https://community.cisco.com/t5/network-security/tcpdump-with-nac/m-p/1145099#M774188</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I use eth0 and fake0 dumps together.  1 is the inbound and one seems to represent an outbound.  It may also be that it represents the internal routing within the cas.&lt;/P&gt;&lt;P&gt;However, to me it was easier to get a real picture by spanning the switch ports connected to the cas off to a wireshark device.  Then perform the capture on the wireshark device.&lt;/P&gt;&lt;P&gt;Keep in mind if you are spanning from a remote switch your capture will not include vlan tags so if possible consider spanning to a port on the same switch connected to the CAS.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Mar 2009 13:38:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcpdump-with-nac/m-p/1145099#M774188</guid>
      <dc:creator>greg.washburn</dc:creator>
      <dc:date>2009-03-19T13:38:48Z</dc:date>
    </item>
  </channel>
</rss>

