#Wireshark packet capture icmp full#
#Wireshark packet capture icmp download#

This is where a tool like Wireshark comes in handy. You can change and tweak the capture filters to suite your needs.Most of the times, when your network crashes or you come across an issue, you have to search through your captured packets to find the problem. You can use both receive and transmit stage capture files for troubleshooting or NAT verification. Let's configure the firewall for packet capture. The transmit stage have the firewall external IP (source NAT) to the server public IP #2, and the return packet from the server public IP to the client private IP #4.The receive stage have the client private IP to the server public IP #1, and the return packet from the server public IP to the firewall external IP #3 (receive stage is pre-NAT).When the traffic leaves the Firewall (post-NAT), the source IP of the SSH traffic will be 200.1.1.1 TRAFFIC FLOW Let's initiate SSH connection from the CLIENT to the SERVER. I configured a SOURCE NAT policy which translates the source IP of the client to the Palo Alto interface public routable IP of 200.1.1.1 when going out to the Internet.

#Wireshark packet capture icmp download#

Step 2 - Configure receive stage RECEIVE STAGE Step 3 - Initiate some traffic and download the capture file CLIENT> ping 172.16.1.10Ĩ4 bytes from 172.16.1.10 icmp_seq=2 ttl=63 time=4.393 msĨ4 bytes from 172.16.1.10 icmp_seq=3 ttl=63 time=1.809 msĨ4 bytes from 172.16.1.10 icmp_seq=4 ttl=63 time=1.618 msĨ4 bytes from 172.16.1.10 icmp_seq=5 ttl=63 time=1.184 ms DOWNLOAD CAPTURE FILE WIRESHARKĪs you can see above, both echo request and echo reply are captured on the receive stage.Įxample 2 - Packet Capture with NAT Diagram NAT DIAGRAM

#Wireshark packet capture icmp full#

You will then need to merge both capture files to have the full picture. If you only configure filter Id-1 then the receive stage will capture packet #1 and the transmit stage will capture packet#4. receive stage - packets 1 & 2 (shown on the example below).For this example, one stage (receive) is more than enough. The filter shown below captures both echo request and echo reply on both receive and transmit stage. Packets 3 & 4 are egressing the firewall.Packets 1 & 2 are ingressing the firewall.

You can configure packet capture by going to Monitor > Packet Capture RECEIVE AND TRANSMIT STAGES Initiate a ping from CLIENT to the SERVER and capture both ICMP echo request and ICMP echo reply.

transmit - captures packets as they egress out of the firewall engine (post-NAT).

receive - captures the packets as they ingress the firewall interface before they go into the firewall engine (pre-NAT).

firewall - captures packets in the firewall stage.

Example, security polciy denying the traffic

Packet captures are session/flow based, so having a single filter is enough for capturing both inbound and outbound traffic.

Four packet capture filters can be added with a variety of attributes.

Packet capture is very useful when you troubleshoot network connectivity issues or monitor suspicious activity.