[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-x86
The Buildbot has detected a new failure of OSX-10.5-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-x86/builds/344 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Build Source Stamp: HEAD Blamelist: jake BUILD FAILED: failed compile sincerely, -The Buildbot ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] [PATCH]: enhanced "what's past last mpls label?" heuristic
On Wed, Jul 9, 2008 at 12:22 AM, Jaap Keuter <[EMAIL PROTECTED]> wrote: > Hi, Hi, > If you submitted this in the bug database there is no need to post it here as > well. That's all. I see. I thought was still useful for someone to have a reference in wireshark-dev ml as well. Next time I'll use only the bugzilla system. > Thanx, > Jaap thanks Ciao FF ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
[Wireshark-dev] [Dev] parsing an excel file a nd adating the data to wireshark's functions
Hello everybody, I'm developping a plugin for a new protocol which have a main particularity : its frames are all different. Indeed, the data part of the frame is different for each frame and I have to pick up the traduction of these data parts in an excel file (I can use .csv, .xml or .xls). So I have to parse this file and to adapt it to the wireshark functions which still exist. My question is : Is there a person who still have done a thing like that? Thank you for your futures answers. Géraud Berthomier. ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
[Wireshark-dev] Wireshark version
Hello, Is there a reason the new version of the win32 Wireshark says 1.0.0 instead of 1.0.1? -martin ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] Wireshark version
Le Wed, 9 Jul 2008 14:36:22 +0200, "Martin Corraine (mcorrain)" <[EMAIL PROTECTED]> a écrit : > Hello, > > Is there a reason the new version of the win32 Wireshark says 1.0.0 > instead of 1.0.1? > > -martin > > In the release notes, we can see: New and Updated Features The following features are new (or have been significantly updated) since the last release: o The "About" box finally displays version 1.0. May be this is it? To confirm you're running the last version, I suggest you try to run Tshark -v in your command line, it should give you the right version number: $ tshark -v TShark 1.0.1 Copyright 1998-2008 Gerald Combs <[EMAIL PROTECTED]> and contributors. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- Guillaume BIENKOWSKI [EMAIL PROTECTED] ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] Wireshark version
Martin Corraine (mcorrain) wrote: > Hello, > > Is there a reason the new version of the win32 Wireshark says 1.0.0 > instead of 1.0.1? Where does it say that? In Help->About my Windows Wireshark says: Version 1.0.1 (SVN Rev 25639) ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] Wireshark version
I saw a report on this ML of someone downloading the 1.0.0 installer from the 1.0.1 link... is this another case? On Wed, Jul 9, 2008 at 2:59 PM, Jeff Morriss <[EMAIL PROTECTED]> wrote: > > > Martin Corraine (mcorrain) wrote: >> Hello, >> >> Is there a reason the new version of the win32 Wireshark says 1.0.0 >> instead of 1.0.1? > > Where does it say that? In Help->About my Windows Wireshark says: > > Version 1.0.1 (SVN Rev 25639) > ___ > Wireshark-dev mailing list > Wireshark-dev@wireshark.org > https://wireshark.org/mailman/listinfo/wireshark-dev > -- This information is top security. When you have read it, destroy yourself. -- Marshall McLuhan ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] Wireshark version
Yes. I go to the main wireshark.org home page and click on the download version 1.0.1. But the file says version 1.0.0. Then when I installed it I made sure it wasn't a typo. -martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Luis EG Ontanon Sent: Wednesday, July 09, 2008 9:03 AM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Wireshark version I saw a report on this ML of someone downloading the 1.0.0 installer from the 1.0.1 link... is this another case? On Wed, Jul 9, 2008 at 2:59 PM, Jeff Morriss <[EMAIL PROTECTED]> wrote: > > > Martin Corraine (mcorrain) wrote: >> Hello, >> >> Is there a reason the new version of the win32 Wireshark says 1.0.0 >> instead of 1.0.1? > > Where does it say that? In Help->About my Windows Wireshark says: > > Version 1.0.1 (SVN Rev 25639) > ___ > Wireshark-dev mailing list > Wireshark-dev@wireshark.org > https://wireshark.org/mailman/listinfo/wireshark-dev > -- This information is top security. When you have read it, destroy yourself. -- Marshall McLuhan ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] Wireshark version
Try cleaning the cache of your browser. On Wed, Jul 9, 2008 at 3:07 PM, Martin Corraine (mcorrain) <[EMAIL PROTECTED]> wrote: > Yes. I go to the main wireshark.org home page and click on the download > version 1.0.1. But the file says version 1.0.0. Then when I installed it > I made sure it wasn't a typo. > > -martin > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Luis EG > Ontanon > Sent: Wednesday, July 09, 2008 9:03 AM > To: Developer support list for Wireshark > Subject: Re: [Wireshark-dev] Wireshark version > > I saw a report on this ML of someone downloading the 1.0.0 installer > from the 1.0.1 link... > > is this another case? > > > On Wed, Jul 9, 2008 at 2:59 PM, Jeff Morriss <[EMAIL PROTECTED]> > wrote: >> >> >> Martin Corraine (mcorrain) wrote: >>> Hello, >>> >>> Is there a reason the new version of the win32 Wireshark says 1.0.0 >>> instead of 1.0.1? >> >> Where does it say that? In Help->About my Windows Wireshark says: >> >> Version 1.0.1 (SVN Rev 25639) >> ___ >> Wireshark-dev mailing list >> Wireshark-dev@wireshark.org >> https://wireshark.org/mailman/listinfo/wireshark-dev >> > > > > -- > This information is top security. When you have read it, destroy > yourself. > -- Marshall McLuhan > ___ > Wireshark-dev mailing list > Wireshark-dev@wireshark.org > https://wireshark.org/mailman/listinfo/wireshark-dev > ___ > Wireshark-dev mailing list > Wireshark-dev@wireshark.org > https://wireshark.org/mailman/listinfo/wireshark-dev > -- This information is top security. When you have read it, destroy yourself. -- Marshall McLuhan ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] Wireshark version
Thanks Luis. That probably shouldn't be like that. -martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Luis EG Ontanon Sent: Wednesday, July 09, 2008 9:10 AM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Wireshark version Try cleaning the cache of your browser. On Wed, Jul 9, 2008 at 3:07 PM, Martin Corraine (mcorrain) <[EMAIL PROTECTED]> wrote: > Yes. I go to the main wireshark.org home page and click on the > download version 1.0.1. But the file says version 1.0.0. Then when I > installed it I made sure it wasn't a typo. > > -martin > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Luis EG > Ontanon > Sent: Wednesday, July 09, 2008 9:03 AM > To: Developer support list for Wireshark > Subject: Re: [Wireshark-dev] Wireshark version > > I saw a report on this ML of someone downloading the 1.0.0 installer > from the 1.0.1 link... > > is this another case? > > > On Wed, Jul 9, 2008 at 2:59 PM, Jeff Morriss > <[EMAIL PROTECTED]> > wrote: >> >> >> Martin Corraine (mcorrain) wrote: >>> Hello, >>> >>> Is there a reason the new version of the win32 Wireshark says 1.0.0 >>> instead of 1.0.1? >> >> Where does it say that? In Help->About my Windows Wireshark says: >> >> Version 1.0.1 (SVN Rev 25639) >> ___ >> Wireshark-dev mailing list >> Wireshark-dev@wireshark.org >> https://wireshark.org/mailman/listinfo/wireshark-dev >> > > > > -- > This information is top security. When you have read it, destroy > yourself. > -- Marshall McLuhan > ___ > Wireshark-dev mailing list > Wireshark-dev@wireshark.org > https://wireshark.org/mailman/listinfo/wireshark-dev > ___ > Wireshark-dev mailing list > Wireshark-dev@wireshark.org > https://wireshark.org/mailman/listinfo/wireshark-dev > -- This information is top security. When you have read it, destroy yourself. -- Marshall McLuhan ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
[Wireshark-dev] how to caputer wimax R1 on windows platform
Hi, Now I am working to get the R1 message of wimax. I use wireshark that plus m2m and wimax module to capture and I plug-in a wimax usb dongle. How should I do to get the R1 message via wireshark. Thanks for your help.I am looking forward your reply. 鍾委導 DerickChung . 互聯電信股份有限公司 M-Skylink Telecom,lnc Tel :02-26588058 ext111 Fax :02-87518765 Msn:[EMAIL PROTECTED] e-mail :[EMAIL PROTECTED] ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] INET6_ADDRSTRLEN redefinition
ok, I got that error now. I wasn't using the 1.0.1 before. Did you find a work around? -martin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yunfan (Andy) Ying Sent: Tuesday, July 08, 2008 6:06 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] INET6_ADDRSTRLEN redefinition Nope, I'm running on a 32bit version of Windows XP. The svn sources can build without problems. It's only 1.0.1 that errors out with this INET6_ADDRSTRLEN macro redefinition error. --Andy On Tue, Jul 8, 2008 at 2:25 PM, Martin Corraine (mcorrain) <[EMAIL PROTECTED]> wrote: It complies fine on WinXP32 with VS2005EE. I've updated my sources this morning. Are you on Win64? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yunfan (Andy) Ying Sent: Tuesday, July 08, 2008 5:10 PM To: wireshark-dev@wireshark.org Subject: [Wireshark-dev] INET6_ADDRSTRLEN redefinition Anyone else run into this issue while compiling Wireshark 1.0.1 on Windows XP with VS2005? The INET6_ADDRSTRLEN defined in packet-ipv6.h seems to conflict with the INET6_ADDRSTRLEN of ws2tcpip.h in the Platform SDK. A simple #ifndef _WIN32 block around that definition seems to fix the issue. --Andy Error Dump: cl -DWIN32 -DNULL=0 -D_MT -D_DLL -WX -DHAVE_CONFIG_H /I.. /I../wiretap /IC:\wireshark-libs-1.0\glib\include\glib-2.0 /IC:\wireshark-libs-1.0\glib\lib\glib-2.0\include /IC:\wireshark-libs-1.0\gtk+\include /IC:\wireshark-libs-1.0\gtk+\include\gdk /IC:\wireshark-libs-1.0\gtk+\lib\gtk+\include /IC:\wireshark-libs-1.0\gnutls-2.3.8-1\include /DNOCRYPT /IC:\wireshark-libs-1.0\WPdpack\WPCAP\LIBPCAP /IC:\wireshark-libs-1.0\WPdpack\WPCAP\LIBPCAP\bpf /IC:\wireshark-libs-1.0\WPdpack\WPCAP\LIBPCAP\lbl /IC:\wireshark-libs-1.0\WPdpack\include /Zm800 -D_U_="" -D_NEED_VAR_IMPORT_ /Zi /W3 /MD /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DMSC_VER_REQUIRED=1400 /IC:\wireshark-libs-1.0\portaudio_v19\include /IC:\wireshark-libs-1.0\portaudio_v19\src\common -DHHC_DIR -Fd.\ -c follow_ssl.c follow_ssl.c C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\include\ws2tcpip.h(747) : error C2220: warning treated as error - no 'object' file generated C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\include\ws2tcpip.h(747) : warning C4005: 'INET6_ADDRSTRLEN' : macro redefinition C:\wireshark-1.0.1\epan/dissectors/packet-ipv6.h(37) : see previous definition of 'INET6_ADDRSTRLEN NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\cl.EXE"' : return code '0x2' Stop. NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\nmake.exe"' : return code '0x2' Stop ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] INET6_ADDRSTRLEN redefinition
Adding ifndef's seems to make it compile. In epan/dissectors/packet-ipv6.h: Change from: #define INET6_ADDRSTRLEN 46 To: #ifndef _WIN32 #define INET6_ADDRSTRLEN 46 #endif --Andy On Wed, Jul 9, 2008 at 9:24 AM, Martin Corraine (mcorrain) < [EMAIL PROTECTED]> wrote: > ok, I got that error now. I wasn't using the 1.0.1 before. Did you find a > work around? > > -martin > > -- > *From:* [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] *On Behalf Of *Yunfan (Andy) Ying > *Sent:* Tuesday, July 08, 2008 6:06 PM > *To:* Developer support list for Wireshark > *Subject:* Re: [Wireshark-dev] INET6_ADDRSTRLEN redefinition > > Nope, I'm running on a 32bit version of Windows XP. The svn sources can > build without problems. It's only 1.0.1 that errors out with this > INET6_ADDRSTRLEN macro redefinition error. > > --Andy > > On Tue, Jul 8, 2008 at 2:25 PM, Martin Corraine (mcorrain) < > [EMAIL PROTECTED]> wrote: > >> It complies fine on WinXP32 with VS2005EE. I've updated my sources this >> morning. Are you on Win64? >> >> -- >> *From:* [EMAIL PROTECTED] [mailto: >> [EMAIL PROTECTED] *On Behalf Of *Yunfan (Andy) Ying >> *Sent:* Tuesday, July 08, 2008 5:10 PM >> *To:* wireshark-dev@wireshark.org >> *Subject:* [Wireshark-dev] INET6_ADDRSTRLEN redefinition >> >> Anyone else run into this issue while compiling Wireshark 1.0.1 on >> Windows XP with VS2005? >> >> The INET6_ADDRSTRLEN defined in packet-ipv6.h seems to conflict with the >> INET6_ADDRSTRLEN of ws2tcpip.h in the Platform SDK. A simple #ifndef _WIN32 >> block around that definition seems to fix the issue. >> >> --Andy >> >> Error Dump: >> >> cl -DWIN32 -DNULL=0 -D_MT -D_DLL -WX -DHAVE_CONFIG_H /I.. /I../wiretap >> /IC:\wireshark-libs-1.0\glib\include\glib-2.0 >> /IC:\wireshark-libs-1.0\glib\lib\glib-2.0\include >> /IC:\wireshark-libs-1.0\gtk+\include >> /IC:\wireshark-libs-1.0\gtk+\include\gdk >> /IC:\wireshark-libs-1.0\gtk+\lib\gtk+\include >> /IC:\wireshark-libs-1.0\gnutls-2.3.8-1\include /DNOCRYPT >> /IC:\wireshark-libs-1.0\WPdpack\WPCAP\LIBPCAP >> /IC:\wireshark-libs-1.0\WPdpack\WPCAP\LIBPCAP\bpf >> /IC:\wireshark-libs-1.0\WPdpack\WPCAP\LIBPCAP\lbl >> /IC:\wireshark-libs-1.0\WPdpack\include /Zm800 -D_U_="" >> -D_NEED_VAR_IMPORT_ /Zi /W3 /MD /D_CRT_SECURE_NO_DEPRECATE >> /D_CRT_NONSTDC_NO_DEPRECATE /DMSC_VER_REQUIRED=1400 >> /IC:\wireshark-libs-1.0\portaudio_v19\include >> /IC:\wireshark-libs-1.0\portaudio_v19\src\common -DHHC_DIR -Fd.\ -c >> follow_ssl.c >> follow_ssl.c >> C:\Program Files\Microsoft Visual Studio >> 8\VC\PlatformSDK\include\ws2tcpip.h(747) : error C2220: warning treated as >> error - no 'object' file generated >> C:\Program Files\Microsoft Visual Studio >> 8\VC\PlatformSDK\include\ws2tcpip.h(747) : warning C4005: 'INET6_ADDRSTRLEN' >> : macro redefinition >> C:\wireshark-1.0.1\epan/dissectors/packet-ipv6.h(37) : see >> previous definition of 'INET6_ADDRSTRLEN >> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio >> 8\VC\BIN\cl.EXE"' : return code '0x2' >> Stop. >> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio >> 8\VC\BIN\nmake.exe"' : return code '0x2' >> Stop >> >> >> ___ >> Wireshark-dev mailing list >> Wireshark-dev@wireshark.org >> https://wireshark.org/mailman/listinfo/wireshark-dev >> >> > > ___ > Wireshark-dev mailing list > Wireshark-dev@wireshark.org > https://wireshark.org/mailman/listinfo/wireshark-dev > > ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] INET6_ADDRSTRLEN redefinition
I also found that if you comment out "#GNUTLS_DIR=$(WIRESHARK_LIBS)\gnutls-2.3.8-1" under ssl decryption in the Wireshark/config.nmake file it builds. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Corraine (mcorrain) Sent: Wednesday, July 09, 2008 12:25 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] INET6_ADDRSTRLEN redefinition ok, I got that error now. I wasn't using the 1.0.1 before. Did you find a work around? -martin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yunfan (Andy) Ying Sent: Tuesday, July 08, 2008 6:06 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] INET6_ADDRSTRLEN redefinition Nope, I'm running on a 32bit version of Windows XP. The svn sources can build without problems. It's only 1.0.1 that errors out with this INET6_ADDRSTRLEN macro redefinition error. --Andy On Tue, Jul 8, 2008 at 2:25 PM, Martin Corraine (mcorrain) <[EMAIL PROTECTED]> wrote: It complies fine on WinXP32 with VS2005EE. I've updated my sources this morning. Are you on Win64? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yunfan (Andy) Ying Sent: Tuesday, July 08, 2008 5:10 PM To: wireshark-dev@wireshark.org Subject: [Wireshark-dev] INET6_ADDRSTRLEN redefinition Anyone else run into this issue while compiling Wireshark 1.0.1 on Windows XP with VS2005? The INET6_ADDRSTRLEN defined in packet-ipv6.h seems to conflict with the INET6_ADDRSTRLEN of ws2tcpip.h in the Platform SDK. A simple #ifndef _WIN32 block around that definition seems to fix the issue. --Andy Error Dump: cl -DWIN32 -DNULL=0 -D_MT -D_DLL -WX -DHAVE_CONFIG_H /I.. /I../wiretap /IC:\wireshark-libs-1.0\glib\include\glib-2.0 /IC:\wireshark-libs-1.0\glib\lib\glib-2.0\include /IC:\wireshark-libs-1.0\gtk+\include /IC:\wireshark-libs-1.0\gtk+\include\gdk /IC:\wireshark-libs-1.0\gtk+\lib\gtk+\include /IC:\wireshark-libs-1.0\gnutls-2.3.8-1\include /DNOCRYPT /IC:\wireshark-libs-1.0\WPdpack\WPCAP\LIBPCAP /IC:\wireshark-libs-1.0\WPdpack\WPCAP\LIBPCAP\bpf /IC:\wireshark-libs-1.0\WPdpack\WPCAP\LIBPCAP\lbl /IC:\wireshark-libs-1.0\WPdpack\include /Zm800 -D_U_="" -D_NEED_VAR_IMPORT_ /Zi /W3 /MD /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DMSC_VER_REQUIRED=1400 /IC:\wireshark-libs-1.0\portaudio_v19\include /IC:\wireshark-libs-1.0\portaudio_v19\src\common -DHHC_DIR -Fd.\ -c follow_ssl.c follow_ssl.c C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\include\ws2tcpip.h(747) : error C2220: warning treated as error - no 'object' file generated C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\include\ws2tcpip.h(747) : warning C4005: 'INET6_ADDRSTRLEN' : macro redefinition C:\wireshark-1.0.1\epan/dissectors/packet-ipv6.h(37) : see previous definition of 'INET6_ADDRSTRLEN NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\cl.EXE"' : return code '0x2' Stop. NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\nmake.exe"' : return code '0x2' Stop ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] plugin
Hello Jaap, I built version 1.0.1 on win32 and have generated my plugin .dll. If I understand you correctly, I should be able to put this file in the "program files/wireshark/plugins/1.0.1" folder. This, however, doesn't work. What am I failing to do? Thanks, martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jaap Keuter Sent: Tuesday, July 08, 2008 6:26 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] plugin Hi, Yes you can, be be sure that: 1. be sure it's build for the intended release of Wireshark. The API/ABI isn't guaranteed stable between releases. 2. Be sure to drop it in the right release folder. Same reason as 1. Thanx, Jaap Martin Corraine (mcorrain) wrote: > Hello, > > Does anyone know if there is some way for you to drop a dissector > plugin into wireshark/plugins/1.0.X and have it work? I do have the > installer working but that's not what I would like to do if I don't have too. > > Thanks, > Martin > ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] plugin
Hi, Please specify "doesn't work". Does it get loaded (see about wireshark, plugin tabs), doesn't it get called for frames you expect, does it crash, or something else? Is there a platform difference between the WS version you have installed and the plugin build? Is the CRT compatible? Stuff like that makes M$-Win development so exiting, and that's why I stick to GNU/Linux, because it gives you just enough rope to hang yourself (M.S.) ;). Thanx, Jaap Martin Corraine (mcorrain) wrote: > Hello Jaap, > > I built version 1.0.1 on win32 and have generated my plugin .dll. If I > understand you correctly, I should be able to put this file in the > "program files/wireshark/plugins/1.0.1" folder. This, however, doesn't > work. What am I failing to do? > > Thanks, > martin > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jaap Keuter > Sent: Tuesday, July 08, 2008 6:26 PM > To: Developer support list for Wireshark > Subject: Re: [Wireshark-dev] plugin > > Hi, > > Yes you can, be be sure that: > 1. be sure it's build for the intended release of Wireshark. The API/ABI > isn't guaranteed stable between releases. > 2. Be sure to drop it in the right release folder. Same reason as 1. > > Thanx, > Jaap > > Martin Corraine (mcorrain) wrote: >> Hello, >> >> Does anyone know if there is some way for you to drop a dissector >> plugin into wireshark/plugins/1.0.X and have it work? I do have the >> installer working but that's not what I would like to do if I don't > have too. >> >> Thanks, >> Martin ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] plugin
Sorry Jaap, The Wireshark 1.0.1 installer that I downloaded for win32 is where I dropped the plugin. The Wireshark build that it was created from was from http://www.wireshark.org/download/src/. I used the wireshark-1.0.0.tar.gz. After building the code and getting the plugin, I drop it in. I then run Wireshark from program files/wireshark. I get the following error: see attachment. The dissector doesn't dissect any packets. The expressions box doesn't turn green either. Thanks, martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jaap Keuter Sent: Wednesday, July 09, 2008 1:19 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] plugin Hi, Please specify "doesn't work". Does it get loaded (see about wireshark, plugin tabs), doesn't it get called for frames you expect, does it crash, or something else? Is there a platform difference between the WS version you have installed and the plugin build? Is the CRT compatible? Stuff like that makes M$-Win development so exiting, and that's why I stick to GNU/Linux, because it gives you just enough rope to hang yourself (M.S.) ;). Thanx, Jaap Martin Corraine (mcorrain) wrote: > Hello Jaap, > > I built version 1.0.1 on win32 and have generated my plugin .dll. If I > understand you correctly, I should be able to put this file in the > "program files/wireshark/plugins/1.0.1" folder. This, however, doesn't > work. What am I failing to do? > > Thanks, > martin > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jaap Keuter > Sent: Tuesday, July 08, 2008 6:26 PM > To: Developer support list for Wireshark > Subject: Re: [Wireshark-dev] plugin > > Hi, > > Yes you can, be be sure that: > 1. be sure it's build for the intended release of Wireshark. The > API/ABI isn't guaranteed stable between releases. > 2. Be sure to drop it in the right release folder. Same reason as 1. > > Thanx, > Jaap > > Martin Corraine (mcorrain) wrote: >> Hello, >> >> Does anyone know if there is some way for you to drop a dissector >> plugin into wireshark/plugins/1.0.X and have it work? I do have the >> installer working but that's not what I would like to do if I don't > have too. >> >> Thanks, >> Martin ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev <>___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] INET6_ADDRSTRLEN redefinition
Yunfan (Andy) Ying wrote: > Anyone else run into this issue while compiling Wireshark 1.0.1 on > Windows XP with VS2005? > > The INET6_ADDRSTRLEN defined in packet-ipv6.h seems to conflict with the > INET6_ADDRSTRLEN of ws2tcpip.h in the Platform SDK. A simple #ifndef > _WIN32 block around that definition seems to fix the issue. This was fixed in the trunk with rev 25331: http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=25331 I added that revision to the "should-copy-to-the-1.0-trunk" list on the roadmap (so it should go into 1.0.2 or 1.0.3). ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] INET6_ADDRSTRLEN redefinition
On Wednesday, July 9, 2008, 5:47:45 PM, Yunfan (Andy) Ying wrote: > #ifndef _WIN32 > #define INET6_ADDRSTRLEN 46 > #endif It's probably better to directly #ifndef INET6_ADDRSTRLEN rather than assume that symbol will always be available alongside _WIN32. (The VS6 built-in headers have all the other IPv6 defs except this one.) Incidentally: http://www.wireshark.org/docs/wsug_html_chunked/ChBuildInstallWinBuild.html : 2.7. Building from source under Windows It is recommended to use the binary installer for Windows, until you want to start developing Wireshark on the Windows platform. For further information how to build Wireshark for Windows from the sources, have a look at the Development Wiki: http://wiki.wireshark.org/Development for the latest available development documentation. That's the entire text of that section. http://wiki.wireshark.org/Development : Win32: the Developer's Guide is currently invaluable for setting up a Win32 development environment John -- Dead stars still burn ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
[Wireshark-dev] defect 2656
What is the process for scheduling and assigning defects? ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
[Wireshark-dev] usb decoding
Hello all, I'm interested in translating USB capture files from Total Phase Beagle USB analyzers into something wireshark will display. The Beagle comes with a GUI for displaying traffic, but wireshark would be cool because it could dissect what's going on inside the usb traffic (eg, SCSI, PPP, etc). My initial plan is just to write a translater for .bgl to .pcap, but I need to figure out which dissector to target when I'm writing packet entries in .pcap. Maybe later I can write a capture plugin so Wireshark can drive the beagle directly. It looks like my current choice of dissectors are USB Raw (dlt 186) or USB with Linux encapsulation (dlt 189). The linux encapsulation appears to be the one with the best existing support, as the usb raw displays don't show a heck of a lot other than the data, and my poking around on the web suggests that dlt 189 was an early version. The linux encapsulation displays are better, but they are definitely oriented around displaying what is happening in the usb driver stack (what with the request/response stuff) as opposed to what a bus analyzer shows, which is more like the straightforward traffic that wireshark's ethernet displays show (timestamp:data). Ideally what I want is to show plain old usb traffic just like ethernet, either with literal packet display (eg, an IN packet on one line, then a DATA0 packet with a payload on the next, then an ACK or NAK packet on the next) or maybe with transaction display (With IN/DATA0/ACK all on the same line). So, I finally get around to my questions: 1. Is dlt 189 a development dead end? 2. Was dlt 189 also oriented around submit/response, or was it more suitable to what I'd like to do? 3. Should I just reserve a new dlt number and make a new dissector? Regards, --Gordon ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] serializing dissection tree to a file
On Jul 7, 2008, at 4:08 PM, MARK LANDRISCINA wrote: > I need the ability to serialize/deserialize the dissection tree > (epan_dissect_t) filled in by epan_dissect_run. > > Is this functionality already available, or is this something that I > will have to write myself? If by "serialize ... to a file" you mean "write out as PDML", that functionality exists in Wireshark and TShark. If you mean anything else, you will need to write it yourself - and if you need to be able to deserialize into a dissection tree, you will need to write that yourself. ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] defect 2656
On Jul 9, 2008, at 2:35 PM, Romel Khan wrote: > What is the process for scheduling and assigning defects? The process is that developers work on a bug if they have the time and interest. :-) (There is very little in the way of formal process for Wireshark development; it's a free software project and a lot of the developers work on it in their spare time, if they have any, and they often don't because they have other projects at work, or are on vacation, or have stuff to do at home, etc..) ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
[Wireshark-dev] Dissector - how to reject packets
The dissector I'm working on overrides the mbtcp dissector, to display a particular subset of the protocol in application-specific detail. My question is - what's the best way to reject those packets the dissector is not interested in? I thought that if the dissect_myprot function returned 0, the mbtcp dissector would then take over, but this doesn't seem to be the case. Should I use a heuristic dissector here, or is there another way to allow the packet to cascade back to the mbtcp dissector? -Patrick DISCLAIMER:--- This e-mail transmission and any documents, files and previous e-mail messages attached to it are private and confidential. They may contain proprietary or copyright material or information that is subject to legal professional privilege. They are for the use of the intended recipient only. Any unauthorised viewing, use, disclosure, copying, alteration, storage or distribution of, or reliance on, this message is strictly prohibited. No part may be reproduced, adapted or transmitted without the written permission of the owner. If you have received this transmission in error, or are not an authorised recipient, please immediately notify the sender by return email, delete this message and all copies from your e-mail system, and destroy any printed copies. Receipt by anyone other than the intended recipient should not be deemed a waiver of any privilege or protection. Thales Australia does not warrant or represent that this e-mail or any documents, files and previous e-mail messages attached are error or virus free. -- ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
[Wireshark-dev] buildbot failure in Wireshark (release) on Windows-XP-x86
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark (release). Full details are available at: http://buildbot.wireshark.org/release/builders/Windows-XP-x86/builds/18 Buildbot URL: http://buildbot.wireshark.org/release/ Buildslave for this Build: windows-xp-x86 Build Reason: Build Source Stamp: HEAD Blamelist: gerald BUILD FAILED: failed failed slave lost sincerely, -The Buildbot ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
