https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14319
Michael Mann <mman...@netscape.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |CONFIRMED
CC| |mman...@netscape.net
Ever confirmed|0 |1
Hardware|x86 |All
OS|Windows 10 |All
Summary|Unable to add custom port |Not all protocol port
|to protocol |preferences support ranges
Severity|Major |Enhancement
--- Comment #2 from Michael Mann <mman...@netscape.net> ---
For all protocols that have port preferences, it's not obvious to the user
which can support ranges and which support single values, because its all just
an text box.
When I refactored the code to have Decode As and port preferences be more
closely related, I wanted to add support so that all port preferences could be
ranges (since those are a superset of single values), but never got around to
it. Patches welcome ;)
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
