Wireshark-users: Re: [Wireshark-users] WireShark-1.2.X + WinPcap-4.0.2=APPCRASH@xxxxxxxxxxx
Date Index Thread Index Other Months All Mailing Lists
[Date Prev] [Date Next] [Thread Prev] [Thread Next]


From: "Gianluca Varenni" <gianluca.varenni@xxxxxxxxxxxx>
Date: Mon, 21 Sep 2009 20:35:50 -0700

Even on a 64bit version you can run the 32bit version of Wireshark.
 
If you want to use the 64bit version, I think you should use WinPcap 4.1beta5, as it's the only one shipping the 64bit version of the user level DLLs ("think" because I don't know if dumpcap is already a 64bit app, and I don't know if wireshark.exe depends on wpcap.dll).
 
GV
----- Original Message -----
From: Ionreflex
Sent: Monday, September 21, 2009 11:22 AM
Subject: Re: [Wireshark-users] WireShark-1.2.X + WinPcap-4.0.2=APPCRASH@xxxxxxxxxxx

Oups : 64bits, since Vista64...


2009/9/21 Gianluca Varenni <gianluca.varenni@xxxxxxxxxxxx>
Are you using the 32 or 64bit version of Wireshark?
 
Have a nice day
GV
----- Original Message -----
From: Ionreflex
Sent: Monday, September 21, 2009 10:20 AM
Subject: [Wireshark-users] WireShark-1.2.X + WinPcap-4.0.2 =APPCRASH@xxxxxxxxxxx

Hi all,

I was wondering if anybody has been able to run WireShark-1.2.X with latest WinPcap stable version, aka v4.0.2, on Vista64 Business Edition; the only way I've been able to make it work is if I installed WinPcap-4.1b5, but I'm kinda reluctant to do so, for 2 other programs : I also use Nmap, which is shipped with WinPcap-4.0.2, and Snort, which I know from past experiences that it just won't work with a beta version of WinPcap.

I've been searching through WireShark documentations, there's no indication that versions 1.2.0 and up require WinPcap-4.1bX, but apparently it is so unofficially... if I'm not doing something wrong, mind that!

Here's a snippet of the error, in french since my OS is in french...

[quote]

Signature du problème :
  Nom d’événement de problème: APPCRASH
  Nom de l’application: dumpcap.exe
  Version de l’application: 1.2.2.29910
  Horodatage de l'application: 4aaf2c84
  Nom du module par défaut: libglib-2.0-0.dll
  Version du module par défaut: 2.18.4.0
  Horodateur du module par défaut: 496876b2
  Code de l’exception: 40000015
  Décalage de l’exception: 000000000004bc5d
  Version du système: 6.0.6002.2.2.0.256.6
  Identificateur de paramètres régionaux: 3084
  Information supplémentaire n° 1: cfc2
  Information supplémentaire n° 2: 31790723910cd61fd5a8f1bcc4475ed8
  Information supplémentaire n° 3: 6066
  Information supplémentaire n° 4: a2218ed9eed514232c3aa91e74d44798

[/quote]

After that, WireShark loads, but it is impossible to capture since the WinPcap driver fails to initialize.

Thanks,



Ion

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe


___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
            mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe