6 minute read
The Traffic Capture tool performs a traffic capture on the selected node, which can help troubleshoot connectivity issues.
The Sniff Interface Traffic tool allows you to monitor traffic in realtime but there are certain instances where you need to be able to capture traffic to a file for further analysis. For example, intermittent issues may require leaving a capture running for an unknown period of time. Or, perhaps you need to review the application data within the packet payload.
The Traffic Capture is started with a standard tcpdump filter, just like the sniff interface tool, and has a max capture file size. Once the capture is stopped the captured data is written to .pcap files which can then be transferred for review.
Because of the risk of data being visible, there are several restrictions and controls in place:
node-advanced::service:tg-capture
) must be granted on a per-user basis in a custom policy. Not even administrators have this feature by default.
Interfaces
under the Network
section.Field Name | Description |
---|---|
Status | Will display Stopped if the capture is idle or Running if there is an active capture. |
Interface | This dropdown field will list the available interfaces. Select the one with the traffic you wish to capture |
Filter | Input a valid tcpdump filter to limit the captured traffic to only what is desired. An overly broad filter can cause the capture file to fill quickly and overwrite older data. See useful filters below for additional information. |
Max Capture Size (MB) | Specify the maximum size in megabytes for the pcap capture files. If this number is greater than 10MB the capture will be divided into the appropriate number of 10MB files to make the captures more manageable. The maximum total size allowed is 1000MB (1G) which would be split into one hundred 10MB files. |
Delete Files On Start | If selected any existing pcap files in the captures directory will be deleted. This allows the user to be certain all capture files are related to the most recent run, and manages disk space consumption from multiple runs. |
Once it is believe the desired traffic has been captured you will need to stop the running capture to get access to the pcap files.
Interfaces
under the Network
section.Now that you have created the pcap files you will need to transfer them somewhere for analysis. The Trustgrid node has standard file transfer clients installed including scp, sftp, and ftp.
If the destination file server is on the local network of the node you will use the standard Terminal tool to run the file transfer commands.
You will need to ensure that:
Once you are in the terminal with the above configured an example scp command would look something like scp ~/captures/capture-2021-07-16_17-59-23.pcap0 username@172.16.100.10:/captures/capture-2021-07-16_17-59-23.pcap
.
If the destination file server is across a Trustgrid virtual network you will need to use the VPN Admin terminal to run the file transfer commands. This uses the nodes configured Virtual Management IP to communicate to remote resources.
Navigate to the node
Select the VPN panel. You may need to select the virtual network to use, if your device is connected to multiple.
Select the Admin Terminal
button from the tools dropdown.
You will need to ensure that:
Once you are in the admin terminal with the above configured, an example SCP command would look like scp ~/captures/capture-2021-07-16_17-59-23.pcap0 username@10.200.100.10:/captures/capture-2021-07-16_17-59-23.pcap
.
The below filters can be combined using “and” & “or” without quotes
not port 9000
not net 35.171.100.16/28 and not net X.X.X.X/X
or not net 35.171.100.16/28 and not host X.X.X.X
.Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.