Ethereal-dev: Re: [Ethereal-dev] more leap stuff

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: Guy Harris <gharris@xxxxxxxxx>
Date: Fri, 22 Mar 2002 03:45:06 -0800
On Tue, Mar 19, 2002 at 03:58:09AM -0800, Guy Harris wrote:
> Instead, you'd need to associate the LEAP state with the packet using
> the "p_add_proto_data()" routine, and get it with "p_get_proto_data()".

I've just checked in a change to do that.

It means that you can now start up Ethereal on the "leap.dump-double"
capture, click on frame 6, and see it dissected as an AP Response.

> You should probably create conversations for LEAP messages - do it the
> same way the SMB dissector does, as SMB can also run atop TCP/IP or atop
> a raw link layer.  Attach a LEAP state to the conversation when you
> create it, and, on the first pass through the capture (when
> "pinfo->fd->flags.visited" is false), update that state, and use it to
> figure out what various fields mean.

I haven't done that yet.  (The first pass would be checked for by the
code that already exists to check whether the frame has any data
attached to it or not.)