Why are ranges not possible in display filter frame.number?

asked 2018-05-03 09:02:48 +0000

LeSpocky
18 ●1 ●1 ●4 http://blog.antiblau.de/

updated 2018-05-03 11:50:45 +0000

I want to use a display filter to only show a certain range of frames. What works:

frame.number >= 20 && frame.number <= 30

I tried the more user friendly way with ranges, which does not work:

frame.number in { 20..30 }

Why is that? According to the user guide I would have expected the range notation to work with simple numbers like that.

(I tried with Version 2.2.6 on Debian 9 GNU/Linux and MS Windows 7 and with v2.4.5 also on Windows 7.)

edit retag flag offensive close merge delete

add a comment

2 Answers

Sort by » oldest newest most voted

answered 2018-05-03 11:27:26 +0000

Jaap

13742 ●711 ●115

It works with Wireshark 2.6.0 and later.

edit flag offensive delete link

Comments

You're right. I just saw it in the documentation and that seems to be bleeding edge (which is good). The 2.6.0 announcement notes this as a new feature: https://www.wireshark.org/news/201804... :-)

LeSpocky ( 2018-05-03 11:54:12 +0000 )edit

add a comment

answered 2023-01-05 10:31:04 +0000

ubuzabdi
1

another way, I'm using =Version 4.0.1

(frame.number == 480) || (frame.number == 482)

edit flag offensive delete link

add a comment

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Why are ranges not possible in display filter frame.number?

2 Answers

Comments

Your Answer

Question Tools

Stats

Related questions

Why are ranges not possible in display filter frame.number? edit

2 Answers

Comments

Your Answer

Question Tools

Stats

Related questions

Why are ranges not possible in display filter frame.number?