aboutsummaryrefslogtreecommitdiffstats
path: root/doc/README.tapping
diff options
context:
space:
mode:
authorGuy Harris <guy@alum.mit.edu>2002-10-25 01:11:03 +0000
committerGuy Harris <guy@alum.mit.edu>2002-10-25 01:11:03 +0000
commit1e7af41606b75e02d6d08d9a3cd87dd8a31c7147 (patch)
tree2c9e229137a883fd54ba422391cda19ae3c0e776 /doc/README.tapping
parentf94df3780a505eeb2bf6e1f7599a5b3ff1d18834 (diff)
From Ronnie Sahlberg: update the tap documentation to reflect recent
changes. svn path=/trunk/; revision=6501
Diffstat (limited to 'doc/README.tapping')
-rw-r--r--doc/README.tapping8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/README.tapping b/doc/README.tapping
index d9be923..025502a 100644
--- a/doc/README.tapping
+++ b/doc/README.tapping
@@ -59,7 +59,7 @@ The two functions to start or stop tapping are
register_tap_listener(char *tapname, void *tapdata, char *fstring,
void (*reset)(void *tapdata),
- int (*packet)(void *tapdata, packet_info *pinfo, void *<pointer>),
+ int (*packet)(void *tapdata, packet_info *pinfo, epan_dissect_t *edt, void *<pointer>),
void (*draw)(void *tapdata),
remove_tap_listener(void *tapdata);
@@ -105,7 +105,7 @@ listener that it is about to start [re]reading a capture file or a new capture
from an interface and that your application should reset any state it has
in the *tapdata instance.
-int (*packet)(void *tapdata, packet_info *pinfo, void *data)
+int (*packet)(void *tapdata, packet_info *pinfo, epan_dissect_t *edt, void *data)
This callback is used whenever a new packet has arrived at the tap and that
it has passed the filter (if there were a filter).
The *data structure type is specific to each tap.
@@ -160,8 +160,8 @@ Well, try this :
Let struct contain an email address?
Then you have something simple that will make ethereal send an email
- out automagically for each and every time it dissects (or the user
- clicks on) a packet containing TCP traffic to port 57.
+ out automagically for each and every time it dissects
+ a packet containing TCP traffic to port 57.
Please put in some rate limitation if you do this.
Let struct contain a command line and make (*packet) execute it?