{"id":2034,"date":"2016-01-13T00:13:33","date_gmt":"2016-01-13T00:13:33","guid":{"rendered":"http:\/\/emtunc.org\/blog\/?p=2034"},"modified":"2017-02-24T15:10:40","modified_gmt":"2017-02-24T15:10:40","slug":"packet-capture-palo-alto-management-interface","status":"publish","type":"post","link":"https:\/\/emtunc.org\/blog\/01\/2016\/packet-capture-palo-alto-management-interface\/","title":{"rendered":"Packet Capture on a Palo Alto Management Interface"},"content":{"rendered":"

In this quick how-to I will show you how you can very easily and quickly\u00a0run a packet capture on a Palo Alto management interface.
\nSome reasons why you may want to capture packets on the management interface is to capture traffic such as RADIUS and Syslog which is processed via the management plane. Management traffic cannot be captured using the ‘packet capture’ feature on the GUI so we need to do it using the CLI.
\n<\/p>\n

    \n
  1. First SSH to the Palo<\/li>\n
  2. Now we use the tcpdump command to start capturing. It is optional to create filters but I would recommend doing so if you are looking for specific trafficIf you want to capture packets\u00a0from<\/strong> a specific IP address then you would use something like this:\n
    tcpdump filter \"src 10.70.0.1\"<\/pre>\n
    to<\/strong> a specific address:<\/p>\n
    tcpdump filter \"src 10.70.0.1\"<\/pre>\n
    to or from a specific address (both sides of the conversation)<\/p>\n
    tcpdump filter \"host 10.70.0.1\"<\/pre>\n
    specific port<\/p>\n
    tcpdump filter \"port 514\"<\/pre>\n
    Note that by default only 68 or 96 bytes of data will be captured per packet depending on which hardware model you have. You can use the option snaplen<\/strong> to determine how many bytes you want to capture. Enter snaplen 0<\/strong> to capture the entire packet. For example:<\/p>\n
    tcpdump filter \"host 10.70.0.1\" snaplen 0<\/pre>\n
    You’ll see something like this:<\/p>\n
    \"packet<\/a><\/li>\n
  3. When you are happy that you have captured enough traffic, simply press CTRL+C to stop.
    \nNow it’s time to export the capture so we can view it in Wireshark. The Palo supports exporting via SCP or TFTP. I chose to use the latter as it literally takes less than a minute to set up a TFTP server\u00a0on a Windows machine.
    \nDownload the mini-portable     TFTP server here<\/a>. Make sure you select the ‘zip’ version if you want the portable version\u00a0(i.e., no installation).
    \nWhen you run the tool, it requires no configuration although you may need to allow port 69 on your local machine’s firewall (I did).<\/li>\n
  4. Now run the tftp export command on the Palo. It should only take a few seconds to get the capture off the Palo and on to your machine. Replace 10.10.10.10 with your machine’s IP.\n
    tftp export mgmt-pcap from mgmt.pcap to 10.10.10.10<\/pre>\n
    All done! That’s how you run a packet capture on a Palo Alto management interface using TCPDump.<\/li>\n<\/ol>\n
    If you by chance already have a SCP server set up then the command will start with scp and follow a similar format.<\/p>\n","protected":false},"excerpt":{"rendered":"
    In this quick how-to I will show you how you can very easily and quickly\u00a0run a packet capture on a Palo Alto management interface. Some reasons why you may want to capture packets on the management interface is to capture traffic such as RADIUS and Syslog which is processed via the management plane. Management traffic […]<\/p>\n","protected":false},"author":32,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"footnotes":""},"categories":[1],"tags":[221,220,18,12],"class_list":["post-2034","post","type-post","status-publish","format-standard","hentry","category-tech","tag-packet-capture","tag-palo-alto","tag-tcpdump","tag-wireshark"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p1trTO-wO","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts\/2034","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/users\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/comments?post=2034"}],"version-history":[{"count":11,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts\/2034\/revisions"}],"predecessor-version":[{"id":2476,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts\/2034\/revisions\/2476"}],"wp:attachment":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/media?parent=2034"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/categories?post=2034"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/tags?post=2034"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}