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
Is your feature request related to a problem? Please describe.
From time to time I have to deal with large pcaps (1M frames) and I'm given the frame numbers to check or a range of frames where to look. It is hard to navigate to specific frame number.
Describe the solution you'd like
It would help to have either a shortcut to Go to packet or some cmdline command or both. This would center the frames view pane to the desired packet number if possible. If not possible then move to end if the number is out of bounds or this also could throw error or something else to let the user know that there is no such frame.
Describe alternatives you've considered
I tried with applying filter like: frame.number eq num
But it only shows the specific frame number and when I then clear the filter the view moves back to frame # 1.
Additional context
No idea what to add here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
From time to time I have to deal with large pcaps (1M frames) and I'm given the frame numbers to check or a range of frames where to look. It is hard to navigate to specific frame number.
Describe the solution you'd like
It would help to have either a shortcut to
Go to packet
or some cmdline command or both. This would center the frames view pane to the desired packet number if possible. If not possible then move to end if the number is out of bounds or this also could throw error or something else to let the user know that there is no such frame.Describe alternatives you've considered
I tried with applying filter like:
frame.number eq num
But it only shows the specific frame number and when I then clear the filter the view moves back to frame # 1.
Additional context
No idea what to add here.
The text was updated successfully, but these errors were encountered: