Ethereal-dev: RE: [ethereal-dev] conversation wildcard entry

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

From: Jeff Foster <jfoste@xxxxxxxxxxxx>
Date: Tue, 17 Oct 2000 14:17:06 -0500
> 
> 
> I have coded the conversation code to allow wildcards on the destination
> port and/or address. Now the conversation_new call will include another
> value (options) that can be used to create a conversation with the 
> destination port and/or address as a wildcard.  A conversation wildcard
> value will match any port and/or address.
> 
> I planned to use these functions to change a wildcard -
> 
> void conversation_set_dst_addr( conversation_t *conv, address *dst);
> void conversation_set_dst_port( conversation_t *conv, guint32 port);

Attached are the new files for conversation.c and conversation.h

These files will have to updated to change these calls

	conversation_new ---> old_conversation_new
	find_conversation ---> old_find_conversation

packet-quake.c
packet-ncp2222.inc
packet-socks.c
packet-rlogin.c
packet-msproxy.c
packet-smtp.c
packet-smb.c
packet-rpc.c
packet-afs.c
packet-bxxp.c
packet-rtsp.c

I have also attached a bash script to do the conversion.


Jeff Foster
jfoste@xxxxxxxxxxxx



Attachment: clean_conv.sh
Description: Binary data

Attachment: conversation.c
Description: Binary data

Attachment: conversation.h
Description: Binary data