From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
/* camel_counter.c
|
|
|
|
* camel message counter for Wireshark
|
|
|
|
* Copyright 2006 Florent Drouin (based on h225_counter.c from Lars Roland)
|
|
|
|
*
|
2008-02-18 22:39:03 +00:00
|
|
|
* $Id$
|
|
|
|
*
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
* Wireshark - Network traffic analyzer
|
|
|
|
* By Gerald Combs <gerald@wireshark.org>
|
|
|
|
* Copyright 1998 Gerald Combs
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or
|
|
|
|
* modify it under the terms of the GNU General Public License
|
|
|
|
* as published by the Free Software Foundation; either version 2
|
|
|
|
* of the License, or (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License
|
|
|
|
* along with this program; if not, write to the Free Software
|
|
|
|
* Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifdef HAVE_CONFIG_H
|
|
|
|
#include "config.h"
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#ifdef HAVE_SYS_TYPES_H
|
|
|
|
# include <sys/types.h>
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#include <string.h>
|
|
|
|
#include <gtk/gtk.h>
|
|
|
|
|
2008-04-13 00:55:59 +00:00
|
|
|
#include <epan/epan.h>
|
|
|
|
#include <epan/packet_info.h>
|
|
|
|
#include <epan/value_string.h>
|
|
|
|
#include <epan/tap.h>
|
|
|
|
#include <epan/packet.h>
|
|
|
|
#include <epan/asn1.h>
|
|
|
|
#include <epan/camel-persistentdata.h>
|
|
|
|
|
|
|
|
#include "../globals.h"
|
|
|
|
#include "../stat_menu.h"
|
|
|
|
#include "../register.h"
|
|
|
|
#include "../timestats.h"
|
|
|
|
#include "../simple_dialog.h"
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
|
|
|
#include "gtk/main.h"
|
|
|
|
#include "gtk/dlg_utils.h"
|
|
|
|
#include "gtk/gui_utils.h"
|
|
|
|
#include "gtk/gui_stat_util.h"
|
2008-04-13 00:55:59 +00:00
|
|
|
#include "gtk/tap_dfilter_dlg.h"
|
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
|
|
|
static void gtk_camelcounter_reset(void *phs);
|
|
|
|
static int gtk_camelcounter_packet(void *phs,
|
|
|
|
packet_info *pinfo _U_,
|
2008-08-05 17:33:14 +00:00
|
|
|
epan_dissect_t *edt _U_,
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
const void *phi);
|
|
|
|
static void gtk_camelcounter_draw(void *phs);
|
|
|
|
static void win_destroy_cb(GtkWindow *win _U_, gpointer data);
|
|
|
|
static void gtk_camelcounter_init(const char *optarg, void *userdata _U_);
|
|
|
|
void register_tap_listener_gtk_camelcounter(void);
|
|
|
|
|
|
|
|
/* following values represent the size of their valuestring arrays */
|
|
|
|
|
|
|
|
struct camelcounter_t {
|
|
|
|
GtkWidget *win;
|
|
|
|
GtkWidget *vbox;
|
|
|
|
char *filter;
|
|
|
|
GtkWidget *scrolled_window;
|
|
|
|
GtkCList *table;
|
|
|
|
guint32 camel_msg[camel_MAX_NUM_OPR_CODES];
|
|
|
|
};
|
|
|
|
|
|
|
|
static void gtk_camelcounter_reset(void *phs)
|
|
|
|
{
|
|
|
|
struct camelcounter_t * p_counter= ( struct camelcounter_t *) phs;
|
|
|
|
int i;
|
2008-08-05 17:33:14 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
/* Erase Message Type count */
|
|
|
|
for(i=0;i<camel_MAX_NUM_OPR_CODES;i++) {
|
2008-08-05 17:33:14 +00:00
|
|
|
p_counter->camel_msg[i]=0;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If there is a valid camel operation, increase the value in the array of counter
|
|
|
|
*/
|
|
|
|
static int gtk_camelcounter_packet(void *phs,
|
|
|
|
packet_info *pinfo _U_,
|
2008-08-05 17:33:14 +00:00
|
|
|
epan_dissect_t *edt _U_,
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
const void *phi)
|
|
|
|
{
|
|
|
|
struct camelcounter_t * p_counter =(struct camelcounter_t *)phs;
|
|
|
|
const struct camelsrt_info_t * pi=phi;
|
|
|
|
if (pi->opcode != 255)
|
|
|
|
p_counter->camel_msg[pi->opcode]++;
|
2008-08-05 17:33:14 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void gtk_camelcounter_draw(void *phs)
|
|
|
|
{
|
|
|
|
struct camelcounter_t *p_counter=(struct camelcounter_t *)phs;
|
|
|
|
int i;
|
|
|
|
char *str[2];
|
2008-08-05 17:33:14 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
for(i=0;i<2;i++) {
|
|
|
|
str[i]=g_malloc(sizeof(char[256]));
|
|
|
|
}
|
|
|
|
/* Now print Message and Reason Counter Table */
|
|
|
|
/* clear list before printing */
|
|
|
|
gtk_clist_clear(p_counter->table);
|
2008-08-05 17:33:14 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
for(i=0;i<camel_MAX_NUM_OPR_CODES;i++) {
|
|
|
|
/* Message counter */
|
|
|
|
if(p_counter->camel_msg[i]!=0) {
|
2008-08-05 17:33:14 +00:00
|
|
|
g_snprintf(str[0], sizeof(char[256]),
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
"Request %s", val_to_str(i,camel_opr_code_strings,"Unknown message "));
|
|
|
|
g_snprintf(str[1], sizeof(char[256]),
|
|
|
|
"%d", p_counter->camel_msg[i]);
|
|
|
|
gtk_clist_append(p_counter->table, str);
|
2008-08-05 17:33:14 +00:00
|
|
|
}
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
} /* Message Type */
|
|
|
|
gtk_widget_show(GTK_WIDGET(p_counter->table));
|
|
|
|
}
|
|
|
|
|
|
|
|
static void win_destroy_cb(GtkWindow *win _U_, gpointer data)
|
|
|
|
{
|
|
|
|
struct camelcounter_t *hs=(struct camelcounter_t *)data;
|
2008-08-05 17:33:14 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
protect_thread_critical_region();
|
|
|
|
remove_tap_listener(hs);
|
|
|
|
unprotect_thread_critical_region();
|
2008-08-05 17:33:14 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
if(hs->filter){
|
|
|
|
g_free(hs->filter);
|
|
|
|
hs->filter=NULL;
|
|
|
|
}
|
|
|
|
g_free(hs);
|
|
|
|
}
|
|
|
|
|
|
|
|
static const gchar *titles[]={
|
|
|
|
"Message Type or Reason",
|
|
|
|
"Count" };
|
|
|
|
|
|
|
|
static void gtk_camelcounter_init(const char *optarg, void *userdata _U_)
|
|
|
|
{
|
|
|
|
struct camelcounter_t *p_camelcounter;
|
2008-08-05 17:33:14 +00:00
|
|
|
const char *filter=NULL;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
GString *error_string;
|
|
|
|
GtkWidget *bbox;
|
|
|
|
GtkWidget *close_bt;
|
2008-08-05 17:33:14 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
if(strncmp(optarg,"camel,counter,",14) == 0){
|
|
|
|
filter=optarg+14;
|
|
|
|
} else {
|
|
|
|
filter=NULL;
|
|
|
|
}
|
2008-08-05 17:33:14 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
p_camelcounter=g_malloc(sizeof(struct camelcounter_t));
|
|
|
|
p_camelcounter->filter=g_strdup(filter);
|
2008-08-05 17:33:14 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
gtk_camelcounter_reset(p_camelcounter);
|
2008-08-05 17:33:14 +00:00
|
|
|
|
2009-06-21 20:42:07 +00:00
|
|
|
/* transient_for top_level */
|
|
|
|
p_camelcounter->win=dlg_window_new("Wireshark: CAMEL counters");
|
|
|
|
gtk_window_set_destroy_with_parent (GTK_WINDOW(p_camelcounter->win), TRUE);
|
|
|
|
|
|
|
|
gtk_window_set_default_size(GTK_WINDOW(p_camelcounter->win), 500, 300);
|
2008-08-05 17:33:14 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
p_camelcounter->vbox=gtk_vbox_new(FALSE, 3);
|
|
|
|
gtk_container_set_border_width(GTK_CONTAINER(p_camelcounter->vbox), 12);
|
2008-08-05 17:33:14 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
init_main_stat_window(p_camelcounter->win, p_camelcounter->vbox, "CAMEL Messages Counters", filter);
|
2008-08-05 17:33:14 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
/* init a scrolled window*/
|
|
|
|
p_camelcounter->scrolled_window = scrolled_window_new(NULL, NULL);
|
|
|
|
|
|
|
|
p_camelcounter->table = create_stat_table(p_camelcounter->scrolled_window, p_camelcounter->vbox, 2, titles);
|
2008-08-05 17:33:14 +00:00
|
|
|
|
2009-06-05 22:42:47 +00:00
|
|
|
error_string=register_tap_listener("CAMEL", p_camelcounter, filter, 0,
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
gtk_camelcounter_reset,
|
|
|
|
gtk_camelcounter_packet,
|
|
|
|
gtk_camelcounter_draw);
|
|
|
|
|
|
|
|
if(error_string){
|
2008-10-31 09:53:56 +00:00
|
|
|
simple_dialog(ESD_TYPE_ERROR, ESD_BTN_OK, "%s", error_string->str);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
g_string_free(error_string, TRUE);
|
|
|
|
g_free(p_camelcounter);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Button row. */
|
|
|
|
bbox = dlg_button_row_new(GTK_STOCK_CLOSE, NULL);
|
|
|
|
gtk_box_pack_end(GTK_BOX(p_camelcounter->vbox), bbox, FALSE, FALSE, 0);
|
|
|
|
|
2008-04-09 05:37:53 +00:00
|
|
|
close_bt = g_object_get_data(G_OBJECT(bbox), GTK_STOCK_CLOSE);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
window_set_cancel_button(p_camelcounter->win, close_bt, window_cancel_button_cb);
|
|
|
|
|
2008-04-09 05:37:53 +00:00
|
|
|
g_signal_connect(p_camelcounter->win, "delete_event", G_CALLBACK(window_delete_event_cb), NULL);
|
|
|
|
g_signal_connect(p_camelcounter->win, "destroy", G_CALLBACK(win_destroy_cb), p_camelcounter);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
|
|
|
gtk_widget_show_all(p_camelcounter->win);
|
|
|
|
window_present(p_camelcounter->win);
|
|
|
|
|
2009-06-05 22:42:47 +00:00
|
|
|
cf_retap_packets(&cfile);
|
2008-10-13 18:37:00 +00:00
|
|
|
gdk_window_raise(p_camelcounter->win->window);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static tap_dfilter_dlg camel_counter_dlg = {
|
|
|
|
"CAMEL Messages and Response Status",
|
|
|
|
"camel,counter",
|
|
|
|
gtk_camelcounter_init,
|
|
|
|
-1
|
|
|
|
};
|
|
|
|
|
|
|
|
void /* Next line mandatory */
|
|
|
|
register_tap_listener_gtk_camelcounter(void)
|
|
|
|
{
|
2009-07-08 18:36:31 +00:00
|
|
|
register_dfilter_stat(&camel_counter_dlg, "_GSM/CAMEL",
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
REGISTER_STAT_GROUP_TELEPHONY);
|
|
|
|
|
|
|
|
}
|