You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The preferences section for Console Applications currently allows the use of variables:
%h (host) %p (port) %d (Console title) %i Project UUID) %n ( Node UUID) and %c (Server URL)
The preferences section for Packet Capture only shows support for %c (Capture File) in point help
but %d is used in the window title to describe the capture location.
-o "gui.window_title:%d"
I propose that another variable (%P or %T) should be available on both Console Applications and Packet Capture to contain the project name (as set in FILE->Edit Project).
This would be a useful addition to the wireshark command line
--capture-comment "%P %d"
The capture comment is saved in the pcapng capture file properties
This would be very useful for record keeping.
The text was updated successfully, but these errors were encountered:
Pcrossley69
changed the title
New variable in Packet Capture (and console) Preferences to hold the project name.
Feature Request - New variable in Packet Capture (and console) Preferences to hold the project name.
Oct 10, 2023
The preferences section for Console Applications currently allows the use of variables:
%h (host) %p (port) %d (Console title) %i Project UUID) %n ( Node UUID) and %c (Server URL)
The preferences section for Packet Capture only shows support for %c (Capture File) in point help
but %d is used in the window title to describe the capture location.
-o "gui.window_title:%d"
I propose that another variable (%P or %T) should be available on both Console Applications and Packet Capture to contain the project name (as set in FILE->Edit Project).
This would be a useful addition to the wireshark command line
--capture-comment "%P %d"
The capture comment is saved in the pcapng capture file properties
This would be very useful for record keeping.
The text was updated successfully, but these errors were encountered: