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

Wireshark-dev: Re: [Wireshark-dev] services file and port ranges

From: "Maynard, Chris" <Christopher.Maynard@xxxxxxxxx>
Date: Mon, 7 Apr 2008 12:07:54 -0400
Another thing I just noticed:

discard           9/dccp   Discard SC:DISC
avt-profile-1   5004/dccp  RTP media data [RFC 3551,
RFC-ietf-dccp-rtp-07.txt]
avt-profile-2   5005/dccp  RTP control protocol [RFC 3551,
RFC-ietf-dccp-rtp-07.txt]

But parse_service_line() looks for "dcp", not "dccp".
- Chris

-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Maynard, Chris
Sent: Monday, April 07, 2008 11:57 AM
To: Developer support list for Wireshark
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.

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev