<?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 Which Debug in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/which-debug/m-p/2276535#M348117</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;The easiest way to test this is when you know the source and destination IP address and ports used by the connection&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then you can use the &lt;STRONG&gt;"packet-tracer"&lt;/STRONG&gt; command on the ASA&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;packet-tracer input &lt;INTERFACE nameif=""&gt; &lt;TCP or="" udp=""&gt; &lt;SOURCE ip=""&gt; &lt;SOURCE port=""&gt; &lt;DESTINATION ip=""&gt; &lt;DESTINATION port=""&gt;&lt;/DESTINATION&gt;&lt;/DESTINATION&gt;&lt;/SOURCE&gt;&lt;/SOURCE&gt;&lt;/TCP&gt;&lt;/INTERFACE&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The &lt;STRONG&gt;&lt;INTERFACE nameif=""&gt;&lt;/INTERFACE&gt;&lt;/STRONG&gt; is the &lt;STRONG&gt;"nameif" &lt;/STRONG&gt;of the interface behind which the connecting host is located at&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, 13 Jun 2013 10:16:41 GMT</pubDate>
    <dc:creator>Jouni Forss</dc:creator>
    <dc:date>2013-06-13T10:16:41Z</dc:date>
    <item>
      <title>Which Debug</title>
      <link>https://community.cisco.com/t5/network-security/which-debug/m-p/2276534#M348116</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'd like to see if an ASA is blocking / dropping traffic whenI try to connect to a server. I'm basically getting timeout errors every so often, and want to see if it's the ASA which is in the path of the traffic.&lt;/P&gt;&lt;P&gt;What's the best Debug command to run to see IP traffic in general and check if the ASA is causing issues? Can I filter the debug via IP so I can narrow it down to whatever my source IP is? New to the ASA and want to narrow my debug down as much as I can.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:57:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/which-debug/m-p/2276534#M348116</guid>
      <dc:creator>GRANT3779</dc:creator>
      <dc:date>2019-03-12T01:57:21Z</dc:date>
    </item>
    <item>
      <title>Which Debug</title>
      <link>https://community.cisco.com/t5/network-security/which-debug/m-p/2276535#M348117</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;The easiest way to test this is when you know the source and destination IP address and ports used by the connection&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then you can use the &lt;STRONG&gt;"packet-tracer"&lt;/STRONG&gt; command on the ASA&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;packet-tracer input &lt;INTERFACE nameif=""&gt; &lt;TCP or="" udp=""&gt; &lt;SOURCE ip=""&gt; &lt;SOURCE port=""&gt; &lt;DESTINATION ip=""&gt; &lt;DESTINATION port=""&gt;&lt;/DESTINATION&gt;&lt;/DESTINATION&gt;&lt;/SOURCE&gt;&lt;/SOURCE&gt;&lt;/TCP&gt;&lt;/INTERFACE&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The &lt;STRONG&gt;&lt;INTERFACE nameif=""&gt;&lt;/INTERFACE&gt;&lt;/STRONG&gt; is the &lt;STRONG&gt;"nameif" &lt;/STRONG&gt;of the interface behind which the connecting host is located at&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, 13 Jun 2013 10:16:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/which-debug/m-p/2276535#M348117</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-06-13T10:16:41Z</dc:date>
    </item>
    <item>
      <title>Which Debug</title>
      <link>https://community.cisco.com/t5/network-security/which-debug/m-p/2276536#M348118</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;Thanks for that. WHen using this command, can I leave out certain parts, e.g Source port? As this would be randomly generate I'd imagine. Can I just use Source IP with the packet tracer command?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jun 2013 11:10:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/which-debug/m-p/2276536#M348118</guid>
      <dc:creator>GRANT3779</dc:creator>
      <dc:date>2013-06-13T11:10:26Z</dc:date>
    </item>
    <item>
      <title>Which Debug</title>
      <link>https://community.cisco.com/t5/network-security/which-debug/m-p/2276537#M348119</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;You need to enter the information mentioned above.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can insert any random source port you want so its not really an issue with using this command.&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, 13 Jun 2013 11:45:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/which-debug/m-p/2276537#M348119</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-06-13T11:45:52Z</dc:date>
    </item>
    <item>
      <title>Which Debug</title>
      <link>https://community.cisco.com/t5/network-security/which-debug/m-p/2276538#M348120</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The command isn't available from CLI or ASDM.. It's running in transparent mode but i'm sure there are default settings causing an issue somewhere.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's a 551X.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jun 2013 11:51:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/which-debug/m-p/2276538#M348120</guid>
      <dc:creator>GRANT3779</dc:creator>
      <dc:date>2013-06-13T11:51:52Z</dc:date>
    </item>
    <item>
      <title>Which Debug</title>
      <link>https://community.cisco.com/t5/network-security/which-debug/m-p/2276539#M348121</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;Yes, the command is not available when the ASA is in Transparent mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I am not mistaken (dont use Transparent firewalls really) you still should be able to do a packet capture on the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you monitored the ASA logs while connecting to the remote site?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you facing problems connecting to some local server behind the ASA or is the server on the Internet?&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, 13 Jun 2013 11:56:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/which-debug/m-p/2276539#M348121</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-06-13T11:56:34Z</dc:date>
    </item>
  </channel>
</rss>

