Ethereal-dev: Re: [ethereal-dev] RPC dissector

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 <guy@xxxxxxxxxx>
Date: Thu, 28 Oct 1999 18:05:58 -0700 (PDT)
> Perhaps what's needed here is to
> 
> 	1) have the conversation routines take as arguments separate
> 	   port number types for the source and destination port;
> 
> 	2) have the client port number be of type PT_NONE, with a value
> 	   of 0, so that, in effect, all requests from a given machine to a
> 	   given server port on a given machine are treated as part of
> 	   the same conversation, regardless of the port whence they
> 	   came (and all replies from a given machine and a given server
> 	   port to a given machine are treated as part of that
> 	   conversation, regardless of the port to which they're
> 	   directed).

...or perhaps both port numbers should be PT_NONE, so that the
conversation keeps track solely of the client and server IP addresses,
to handle protocols other than portmapper/rpcbind and NFS where the port
number might change across a reboot.