Ethereal-dev: Re: [ethereal-dev] Picking up info along the way and making it available

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 Jr." <gram@xxxxxxxxxxxxxxxxxxx>
Date: Sun, 28 Mar 1999 06:41:44 -0600 (CST)
As Lars Gaarden said:
> 
> It seems to me that many protocol analyzers have to implement some kind
> of state machine to properly decode sessions. Instead of implementing all
> this separately for each single protocol, wouldn't it be better to make a
> generic facility to keep state? That is - make it possible for the dissect-*
> routines to save state to a structure, and later retrieve it.

Absolutely. That's why I mentioned that IPX/NCP could take advantage of the
routines. I don't want people to forget that the non-IP protocols!

Are you talking about the information that IPX passes to NCP during
dissection (the NetWare server's internal IPX network number), or are you
talking about the hash table that NCP keeps in order to coordinate NCP
replies with their NCP requests?

--gilbert
-- 
Gilbert Ramirez                Voice:  +1 210 358 4032
Technical Services             Fax:    +1 210 358 1122
University Health System       San Antonio, Texas, USA