Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 2433] New: add parsing of port ranges in ./wireshark/servi

Date: Wed, 9 Apr 2008 16:56:04 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2433

           Summary: add parsing of port ranges in ./wireshark/services
           Product: Wireshark
           Version: SVN
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: acferen@xxxxxxxxx


Created an attachment (id=1650)
 --> (http://bugs.wireshark.org/bugzilla/attachment.cgi?id=1650)
patch to parse port ranges in ./wireshark/services file

Build Information:
wireshark 1.0.99 (SVN Rev 24864)

Copyright 1998-2008 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GTK+ 2.12.0, with GLib 2.14.1, with libpcap 0.9.7, with libz
1.2.3.3, without POSIX capabilities, without libpcre, without SMI, without
ADNS,
without Lua, without GnuTLS, without Gcrypt, without Kerberos, without
PortAudio, without AirPcap.
NOTE: this build doesn't support the "matches" operator for Wireshark filter
syntax.

Running on Linux 2.6.22-14-generic, with libpcap version 0.9.7.

Built using gcc 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2).

--
Date:    Mon, 7 Apr 2008 11:57:03 -0400
From:   "Maynard, Chris" <Christopher.Maynard@xxxxxxxxx>  Add Mobile Alert
To:     "Developer support list for Wireshark" <wireshark-dev@xxxxxxxxxxxxx>
Subject:        [Wireshark-dev] services file and port ranges


I noticed that IANA lists a few ports in ranges.  For example, x11 is
listed as:
x11             6000-6063/tcp   X Window System
x11             6000-6063/udp   X Window System

But addr_resolv.c:parse_service_line() currently expects entries in
services(5) format, i.e., a single port only.  So, should IANA be
encouraged to change their format to avoid port ranges and comply with
the format specified in services(5)?  Or, more likely, should the
parsing of the services file be changed so that a range of ports is
allowed and any port within the range will be returned as the
corresponding service name?

- Chris
References: http://www.iana.org/assignments/port-numbers.


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.