21
edits
REST API description: Difference between revisions
Jump to navigation
Jump to search
→Pcap extraction
No edit summary |
|||
| Line 273: | Line 273: | ||
* '''captureToMedia''': Whether to store a pcap on an external storage device (= true) or download to your computer (= false). Requires the use of the '''storageUuid''' parameter. | * '''captureToMedia''': Whether to store a pcap on an external storage device (= true) or download to your computer (= false). Requires the use of the '''storageUuid''' parameter. | ||
* '''storageUuid:''' Specifies the storage device to store the capture file on when '''captureToMedia''' is true. | * '''storageUuid:''' Specifies the storage device to store the capture file on when '''captureToMedia''' is true. | ||
* '''datalinkType:''' Specifies the datalink type to be used in the PCAP. The default value is ''ethernet'' but if raw 802.11 WiFi packets are to be captured the datalink type must be ''radiotap'' to create a PCAP file with Radiotap headers and 802.11 WiFi packets. | |||
* '''mm-id''': If you are extracting a Pcap from a parallel Pcap analysis job or a multi device connected Allegro Network Multimeter, you have to specify the device and the slot where to get the data from. The syntax is: <code>mm-id=<device name>:<slot id></code>. If the capture shall be performed on the local device, the device name can be omited (e.g. mm-id=:1 for the first replay slot on the local device). | * '''mm-id''': If you are extracting a Pcap from a parallel Pcap analysis job or a multi device connected Allegro Network Multimeter, you have to specify the device and the slot where to get the data from. The syntax is: <code>mm-id=<device name>:<slot id></code>. If the capture shall be performed on the local device, the device name can be omited (e.g. mm-id=:1 for the first replay slot on the local device). | ||