[Wireshark-bugs] [Bug 14180] Add range capability to "in" display filters

2018-04-18 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14180 --- Comment #11 from Peter Wu --- This feature was discussed at https://www.wireshark.org/lists/wireshark-dev/201804/msg00058.html which also resulted in the change from the proposed "1662-1664" syntax to

[Wireshark-bugs] [Bug 14180] Add range capability to "in" display filters

2018-04-18 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14180 Peter Wu changed: What|Removed |Added Status|IN_PROGRESS |RESOLVED

[Wireshark-bugs] [Bug 14180] Add range capability to "in" display filters

2018-04-18 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14180 --- Comment #9 from Gerrit Code Review --- Change 26998 merged by Stig Bjørlykke: dfilter: add range support to set membership operator ("f in {x .. y}") https://code.wireshark.org/review/26998 -- You

[Wireshark-bugs] [Bug 14180] Add range capability to "in" display filters

2018-04-18 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14180 --- Comment #8 from Gerrit Code Review --- Change 26999 had a related patch set uploaded by Peter Wu: dfilter: make spaces around ".." optional in display filter https://code.wireshark.org/review/26999

[Wireshark-bugs] [Bug 14180] Add range capability to "in" display filters

2018-04-18 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14180 --- Comment #7 from Gerrit Code Review --- Change 26998 had a related patch set uploaded by Peter Wu: dfilter: add range support to set membership operator ("f in {x .. y}")

[Wireshark-bugs] [Bug 14180] Add range capability to "in" display filters

2018-04-17 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14180 --- Comment #6 from Gerrit Code Review --- Change 26945 merged by Anders Broman: dfilter: add range support to set membership operator ("f in {x .. y}") https://code.wireshark.org/review/26945 -- You

[Wireshark-bugs] [Bug 14180] Add range capability to "in" display filters

2018-04-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14180 --- Comment #5 from Gerrit Code Review --- Change 26960 had a related patch set uploaded by Peter Wu: dfilter: make spaces around ".." optional in display filter https://code.wireshark.org/review/26960

[Wireshark-bugs] [Bug 14180] Add range capability to "in" display filters

2018-04-14 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14180 --- Comment #4 from Gerrit Code Review --- Change 26945 had a related patch set uploaded by Peter Wu: [RFC] dfilter: add range support to set membership operator https://code.wireshark.org/review/26945

[Wireshark-bugs] [Bug 14180] Add range capability to "in" display filters

2018-04-09 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14180 --- Comment #3 from Peter Wu --- To illustrate the compiled logic, this is what is currently being created for a hypothethical "tcp.port in {1-4 6 8-9}" filter: (tcp.port >= 1 and tcp.port <= 4) or tcp.port == 6 or

[Wireshark-bugs] [Bug 14180] Add range capability to "in" display filters

2018-04-09 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14180 Peter Wu changed: What|Removed |Added CC|

[Wireshark-bugs] [Bug 14180] Add range capability to "in" display filters

2017-11-08 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14180 --- Comment #1 from Christopher Maynard --- This doesn't directly address the bug, but at least for now you can make use of a Display Filter Macro[1] in this case. For example: Analyze -> Display Filter