headers
Stephen Fisher | 1 Nov 2007 01:36
Picon
Favicon

Re: dissecting data portion of IP

On Wed, Oct 31, 2007 at 03:03:12PM -0700, Guy Harris wrote:
> 
> On Oct 31, 2007, at 1:58 PM, Daniel Roman wrote:
> 
> > The IP Header of my packet contains 0xC8 for the Protocol Type. Can
> > I do dissector_add("ip.proto", 0xC8, myprotocol_handle); to instruct
> > wireshark to call my dissector if an IP protocol type of 0xC8 is >
> encountered?
> 
> ...that is what you should do.

Better yet, add your protocol's abbrevation and decimal number toward
the end of epan/ipproto.h and call dissector_add("ip.proto",
IP_PROTO_xxx, myprotocol_handle).

Steve

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev <at> wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Permalink | Reply | 2 comments |
headers
Guy Harris | 1 Nov 2007 01:42
Picon
Favicon

Re: dissecting data portion of IP


On Oct 31, 2007, at 5:36 PM, Stephen Fisher wrote:

> Better yet, add your protocol's abbrevation and decimal number toward
> the end of epan/ipproto.h and call dissector_add("ip.proto",
> IP_PROTO_xxx, myprotocol_handle).

...if he wants to contribute the dissector.

If not, it's probably more convenient to define IP_PROTO_xxx in his  
dissector, rather than modifying epan/ipproto.h.
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev <at> wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Permalink | Reply | 1 comment |
headers
zhou rui | 1 Nov 2007 06:46
Picon

any one has the wimax log file?

hi
any one has the wimax log file and kindly provide it?
want to try that with wireshark
 
thanks!
rui
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev <at> wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Permalink | Reply | 0 comments |
headers
daniel zhang | 1 Nov 2007 08:55
Picon

Voice (RTP stream) quality - mos, delay, bandwidth, ...

Is there anyone working on adding more statistics into the RTP stream analysis?

1. MOS
Voice quality was traditionally reported as a Mean Opinion Score (MOS) on a scale from 1-5 where 1 is the lowest and 5 the highest.
I am not an expert on this but I think probably we could add the MOS into Ethereal.

2. Delay
Don't know how to measure the delay of voice

3. Bandwidth usage
I think it will be more usage if we can have the statistics of Adverage bandwidth, Max bandwidth additional to the each package bandwidth.


Daniel

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev <at> wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Permalink | Reply | 4 comments |
headers
Guy Harris | 1 Nov 2007 18:45
Picon
Favicon

Re: Voice (RTP stream) quality - mos, delay, bandwidth, ...

daniel zhang wrote:

> 1. MOS
> Voice quality was traditionally reported as a Mean Opinion Score (MOS) 
> on a scale from 1-5 where 1 is the lowest and 5 the highest.
> I am not an expert on this but I think probably we could add the MOS 
> into Ethereal.

At least according to the Wikipedia article on the Mean Opinion Score:

	http://en.wikipedia.org/wiki/Mean_Opinion_Score

the score comes from people listening to particular phrases and giving 
their 1-to-5 rating of the quality of the sound, not from a calculation 
you could perform on a raw digital signal.  That means Wireshark (the 
new name for the program that used to be called "Ethereal") couldn't 
calculate the MOS for a given voice sample (at least not without a 
plugin that connects to a number of user's machines, plays the sample to 
the user, asks them for their rating, and then averages the results; I 
don't know whether that could be done in a way that conforms to ITU-T 
Recommendation P.800).
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev <at> wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Permalink | Reply | 3 comments |
headers
Sagun Shakya | 1 Nov 2007 20:23
Picon

Error compiling wireshark on Solaris

Hi,

I can the configure script with the following options:

./configure --disable-gtk2 LDFLAGS=-ldlpi  --without-zlib --enable-warnings-as-errors=no

The error complaing about LIBTOOL but I have libtool installed on my build system:
>which libtool
/opt/csw/bin/libtool

I've been trying to compile wireshark and I get this error:

> make
/opt/csw/bin/perl ./make-version.pl .
Version configuration file version.conf not found.  Using defaults.
This is not a SVN build.
svnversion.h is up-to-date.
make  all-recursive
Making all in tools
Making all in lemon
Making all in wiretap
make  all-am
Making all in doc
Making all in epan
Making all in crypt
if <at> LIBTOOL <at> --tag=CC --mode=compile gcc -DHAVE_CONFIG_H  -I. -I. -I../.. -I../..  -I/usr/local/include   -D_U_="__attribute__((unused))" -g -O2 -Wall -W -Wdeclaration-after-statement -Wendif-labels -Wpointer-arith -Wno-return-type -DFUNCPROTO=15 -I/usr/local/include -I/opt/csw/include/gtk- 1.2 -I/opt/csw/include/glib-1.2 -I/opt/csw/lib/glib/include -MT airpdcap.lo -MD -MP -MF ".deps/airpdcap.Tpo" -c -o airpdcap.lo airpdcap.c; \
then mv -f ".deps/airpdcap.Tpo" ".deps/airpdcap.Plo"; else rm -f ".deps/airpdcap.Tpo"; exit 1; fi
bash: <at> LIBTOOL <at> : command not found
*** Error code 1
make: Fatal error: Command failed for target `airpdcap.lo'
Current working directory /export/home/ss150715/wireshark/wireshark-0.99.6/epan/crypt
*** Error code 1
The following command caused the error:
failcom='exit 1'; \
for f in x $MAKEFLAGS; do \
  case $f in \
    *=* | --[!k]*);; \
    *k*) failcom='fail=yes';; \
  esac; \
done; \
dot_seen=no; \
target=`echo all-recursive | sed s/-recursive//`; \
list='crypt ftypes dfilter dissectors '; for subdir in $list; do \
  echo "Making $target in $subdir"; \
  if test "$subdir" = "."; then \
    dot_seen=yes; \
    local_target="$target-am"; \
  else \
    local_target="$target"; \
  fi; \
  (cd $subdir && make  $local_target) \
  || eval $failcom; \
done; \
if test "$dot_seen" = "no"; then \
  make  "$target-am" || exit 1; \
fi; test -z "$fail"
make: Fatal error: Command failed for target `all-recursive'
Current working directory /export/home/ss150715/wireshark/wireshark- 0.99.6/epan
*** Error code 1
The following command caused the error:
failcom='exit 1'; \
for f in x $MAKEFLAGS; do \
  case $f in \
    *=* | --[!k]*);; \
    *k*) failcom='fail=yes';; \
  esac; \
done; \
dot_seen=no; \
target=`echo all-recursive | sed s/-recursive//`; \
list='tools wiretap doc epan plugins packaging help codecs gtk'; for subdir in $list; do \
  echo "Making $target in $subdir"; \
  if test "$subdir" = "."; then \
    dot_seen=yes; \
    local_target="$target-am"; \
  else \
    local_target="$target"; \
  fi; \
  (cd $subdir && make  $local_target) \
  || eval $failcom; \
done; \
if test "$dot_seen" = "no"; then \
  make  "$target-am" || exit 1; \
fi; test -z "$fail"
make: Fatal error: Command failed for target `all-recursive'
Current working directory /export/home/ss150715/wireshark/wireshark-0.99.6
*** Error code 1
make: Fatal error: Command failed for target `all'

help would be appreciated,

Sagun

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev <at> wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Permalink | Reply | 501 comments |
headers
Sagun Shakya | 1 Nov 2007 20:36
Picon

Re: Error compiling wireshark on Solaris

Sorry about the garbled up message.

Let me try this again:

I ran the configure script with the following options:
./configure --disable-gtk2 LDFLAGS=-ldlpi  --without-zlib --enable-warnings-as-errors=no

The error is complaining about LIBTOOL but I have libtool installed on my build system:
>which libtool
/opt/csw/bin/libtool

The errors are as follows


> make
/opt/csw/bin/perl ./make-version.pl .
Version configuration file version.conf not found.  Using defaults.
This is not a SVN build.
svnversion.h is up-to-date.
make  all-recursive
Making all in tools
Making all in lemon
Making all in wiretap
make  all-am
Making all in doc
Making all in epan
Making all in crypt
if <at> LIBTOOL <at> --tag=CC --mode=compile gcc -DHAVE_CONFIG_H  -I. -I. -I../.. -I../..  -I/usr/local/include   -D_U_="__attribute__((unused))" -g -O2 -Wall -W -Wdeclaration-after-statement -Wendif-labels -Wpointer-arith -Wno-return-type -DFUNCPROTO=15 -I/usr/local/include -I/opt/csw/include/gtk- 1.2 -I/opt/csw/include/glib-1.2 -I/opt/csw/lib/glib/include -MT airpdcap.lo -MD -MP -MF ".deps/airpdcap.Tpo" -c -o airpdcap.lo airpdcap.c; \
then mv -f ".deps/airpdcap.Tpo" ".deps/airpdcap.Plo"; else rm -f ".deps/airpdcap.Tpo"; exit 1; fi
bash: <at> LIBTOOL <at> : command not found
*** Error code 1
make: Fatal error: Command failed for target `airpdcap.lo'
Current working directory /export/home/ss150715/wireshark/wireshark-0.99.6/epan/crypt
*** Error code 1
The following command caused the error:
failcom='exit 1'; \
for f in x $MAKEFLAGS; do \
  case $f in \
    *=* | --[!k]*);; \
    *k*) failcom='fail=yes';; \
  esac; \
done; \
dot_seen=no; \
target=`echo all-recursive | sed s/-recursive//`; \
list='crypt ftypes dfilter dissectors '; for subdir in $list; do \
  echo "Making $target in $subdir"; \
  if test "$subdir" = "."; then \
    dot_seen=yes; \
    local_target="$target-am"; \
  else \
    local_target="$target"; \
  fi; \
  (cd $subdir && make  $local_target) \
  || eval $failcom; \
done; \
if test "$dot_seen" = "no"; then \
  make  "$target-am" || exit 1; \
fi; test -z "$fail"
make: Fatal error: Command failed for target `all-recursive'
Current working directory /export/home/ss150715/wireshark/wireshark- 0.99.6/epan
*** Error code 1
The following command caused the error:
failcom='exit 1'; \
for f in x $MAKEFLAGS; do \
  case $f in \
    *=* | --[!k]*);; \
    *k*) failcom='fail=yes';; \
  esac; \
done; \
dot_seen=no; \
target=`echo all-recursive | sed s/-recursive//`; \
list='tools wiretap doc epan plugins packaging help codecs gtk'; for subdir in $list; do \
  echo "Making $target in $subdir"; \
  if test "$subdir" = "."; then \
    dot_seen=yes; \
    local_target="$target-am"; \
  else \
    local_target="$target"; \
  fi; \
  (cd $subdir && make  $local_target) \
  || eval $failcom; \
done; \
if test "$dot_seen" = "no"; then \
  make  "$target-am" || exit 1; \
fi; test -z "$fail"
make: Fatal error: Command failed for target `all-recursive'
Current working directory /export/home/ss150715/wireshark/wireshark-0.99.6
*** Error code 1
make: Fatal error: Command failed for target `all'

help would be appreciated,

Sagun 

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev <at> wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Permalink | Reply | 501 comments |
headers
Graeme Lunt | 2 Nov 2007 15:06

Wireshark Portable

Hi,

I have just checked in some initial Portable Apps (www.portableapps.com)
packaging for "Wireshark Portable". 

The Portable Apps environment will run on any USB flash drive, so you no
longer need a U3 device to have a portable Wireshark (see attached
screendump).

I am new to the Portable Apps environment, and NSIS on which the Portable
Apps rely, so I'd be grateful if anyone more familiar with Portable Apps
(ULFL?) could check it out (nmake -f makefile.nmake packaging_papps). Just
use "Options"/"Install New App" on the Portable Apps menu to install the
resulting WiresharkPortable-0.99.7.paf.exe.

Hopefully we can refine it (I'm talking to the Portable Apps guys) and then
get the buildbot building it.

Graeme


_______________________________________________
Wireshark-dev mailing list
Wireshark-dev <at> wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Permalink | Reply | 2 comments |
headers
Ulf Lamping | 2 Nov 2007 19:31
Picon

Re: Wireshark Portable

Graeme Lunt schrieb:
> Hi,
>
> I have just checked in some initial Portable Apps (www.portableapps.com)
> packaging for "Wireshark Portable". 
>   
Very nice!
> The Portable Apps environment will run on any USB flash drive, so you no
> longer need a U3 device to have a portable Wireshark (see attached
> screendump).
>
> I am new to the Portable Apps environment, and NSIS on which the Portable
> Apps rely, so I'd be grateful if anyone more familiar with Portable Apps
> (ULFL?) 
sorry, but now you know more about that topic than I do :-)
> could check it out (nmake -f makefile.nmake packaging_papps). Just
> use "Options"/"Install New App" on the Portable Apps menu to install the
> resulting WiresharkPortable-0.99.7.paf.exe.
>   
I get the following error, which looks like something is missing on my 
machine. Any ideas?

IfFileExists: "$PROGRAMDIRECTORY\$PROGRAMEXECUTABLE" ? FoundProgramEXE :
MessageBox: 48: "$PROGRAMEXECUTABLE was not found.  Please check your 
configuration"
Abort: ""
StrCmp "$SECONDARYLAUNCH" "true" equal=GetPassedParameters, nonequal=
Invalid command: FindProcDLL::FindProc
Error in script "WiresharkPortable.nsi" on line 160 -- aborting creation 
process
NMAKE : fatal error U1077: '"C:/Program Files\nsis\makensis.exe"' : 
return code '0x1'
Stop.
NMAKE : fatal error U1077: '"C:\Programme\Microsoft Visual Studio 
8\VC\BIN\nmake.exe"' : return code
 '0x2'
Stop.

Regards, ULFL
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev <at> wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Permalink | Reply | 1 comment |
headers
Graeme Lunt | 2 Nov 2007 21:49

Re: Wireshark Portable

Ulf,

> I get the following error, which looks like something is 
> missing on my machine. Any ideas?
> 
> 
> IfFileExists: "$PROGRAMDIRECTORY\$PROGRAMEXECUTABLE" ? 
> FoundProgramEXE :
> MessageBox: 48: "$PROGRAMEXECUTABLE was not found.  Please check your 
> configuration"
> Abort: ""
> StrCmp "$SECONDARYLAUNCH" "true" equal=GetPassedParameters, nonequal=
> Invalid command: FindProcDLL::FindProc
> Error in script "WiresharkPortable.nsi" on line 160 -- 
> aborting creation 
> process
> NMAKE : fatal error U1077: '"C:/Program Files\nsis\makensis.exe"' : 
> return code '0x1'
> Stop.
> NMAKE : fatal error U1077: '"C:\Programme\Microsoft Visual Studio 
> 8\VC\BIN\nmake.exe"' : return code
>  '0x2'
> Stop.

Ahh. Forgot about that step! Apologies.

I had to install the following NSIS plug-in : 
<http://nsis.sourceforge.net/Find_Process_By_Name>

We do care about multiple instances as an earlier instance may uninstall
WinPcap (when it exits) from under a running, second, instance.

Do you think it is acceptable to just add this step to section 4.17. of the
Wireshark Build Environment manual?
Or should we try and lose it?

Graeme

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev <at> wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Permalink | Reply | 0 comments |

Gmane