Ethereal-users: Re: [Ethereal-users] Mis-interpreted field in RSVP

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Gilbert Ramirez <gilramir@xxxxxxxxx>
Date: Wed, 11 Apr 2001 15:30:35 -0500
Steve Yao wrote:
> 
> >
> >
> > > I used Ethereal 0.8.10 to decode some RSVP messages.
> > > I found that Ethereal mis-interpreted the message type field
> > > in the RSVP header when the value is 20. It is supposed to
> > be the Hello
> > > message type defined in RSVP-TE. But Ethereal displayed
> > "Explicit Route
> > > Object" as the message type. Interestingly, the Class Num
> > field for Explicit
> > > Route Object is defined to be 20.
> >

The comments in packet-rsvp.c say this:

/*
 * NOTES
 *
 * This module defines routines to disassemble RSVP packets, as defined
in
 * RFC 2205. All objects from RC2205 are supported, in IPv4 and IPv6
mode.
 * In addition, the Integrated Services traffic specification objects
 * defined in RFC2210 are also supported. 
 *
 * IPv6 support is not completely tested
 *
 * Mar 3, 2000: Added support for MPLS/TE objects, as defined in 
 * <draft-ietf-mpls-rsvp-lsp-tunnel-04.txt>
 */


Was Hello added in a draft after version 4?

BTW, this URL,  

http://www.isi.edu/in-notes/iana/assignments/rsvp-parameters

shows many more RSVP message types that the current
dissector does not handle.

--gilbert