protocol used for
transferring the packets (I don’t know the details), and that might be one of
the reasons why it was never pushed back to upstream.
From: Yang Luo [mailto:hslu...@gmail.com]
Sent: Wednesday, April 13, 2016 5:14 PM
To: Developer support list for Wireshark; Gianluca Varenni
for 802.11 Beacon frames on
Windows
On Apr 13, 2016, at 9:23 AM, Gianluca Varenni
wrote:
>
> Please unicast me and I can give you some hints on how wpcap.dll is compiled
> on Windows. Shortly, we take the libpcap sources and apply a pretty
> substantial patch on it to compile on Wind
Subject: Re: [Wireshark-dev] Get "Malformed Packet" for 802.11 Beacon frames on
Windows
On 13 April 2016 at 17:23, Gianluca Varenni
mailto:gianluca.vare...@riverbed.com>> wrote:
Graham/Yang,
Please unicast me and I can give you some hints on how wpcap.dll is compiled on
Wind
Graham/Yang,
Please unicast me and I can give you some hints on how wpcap.dll is compiled on
Windows. Shortly, we take the libpcap sources and apply a pretty substantial
patch on it to compile on Windows.
Have a nice day
GV
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun.
Wireshark developers,
It looks like the number of emails strictly related to the pcap-ng file format
has increased recently, thanks to its adoption and improved support in
Wireshark.
Due to that, and to the fact that the spec is currently hosted on the
winpcap/NTAR website, we've created a new
I would be extremely careful with pcap_compile. Last time I checked the
sources. pcap_compile was not thread safe (because internally it uses global
variables), so you would need to use synchronization to protect concurrent
calls to that function.
Have a nice day
GV
-Original Message-
the changes can be found in the change log below.
Gianluca Varenni
WinPcap Team
Changelog from WinPcap 4.1.1
- Bug fixing:
+ Fixed a bug reported by Boaz Brickner (http://pcapdotnet.codeplex.com/):
the driver could cause an OS crash when an IRP_MJ_CLEANUP is
Quite interesting. Were you using a recent version of AVG?
If I remember well, AVG is free, so I can to reproduce it here
Have a nice day
GV
From: Ing. Rodrigo Castro
Sent: Wednesday, January 20, 2010 1:26 PM
To: Gianluca Varenni
Cc: wireshark-dev@wireshark.org
Subject: Re: [Wireshark-dev
That's a totally different story, then...
Can you take a screenshot of the performance tab in task manager and send it to
me privately?
Have a nice day
GV
From: Ing. Rodrigo Castro
Sent: Tuesday, January 19, 2010 4:12 AM
To: Gianluca Varenni
Cc: wireshark-dev@wireshark.org
Subjec
adcom 440 NIC Win XP controllers to the latest release,
and reproduced the same behavior booting with Dell WinXP Media Center, and also
with a WinXP UE.
Regards,
Rodrigo.
Message: 3
Date: Fri, 15 Jan 2010 15:00:38 -0800
From: "Gianluca Varenni"
Subject: Re: [Wireshark-dev] read error:
Well, it can mean everything...
- can you reproduce it consistently?
- did it happen after capturing hours and hours?
- if it's a USB network adapter, did you disconnect it?
- did it happen after getting your PC out of hibernation?
GV
--
From: "Gu
As far as I know NetMon uses an NDIS6 Native Wifi intermediate driver (I
don't remember the exact name of the technology, LWF?) to capture the
packets. WinPcap uses an NDIS5 protocol driver. I don't know if it's
possible to capture native 802.11 frames with an NDIS6 protocol driver, but
in any
/Win7/2008R2 x64.
Full details of the changes can be found in the change log below.
Gianluca Varenni
WinPcap Team
Changelog from WinPcap 4.1
==
- This release fixes a bug in the installer of WinPcap 4.1. The binaries
were not digitally signed, thus preventing the WinPcap
ndows configurations.
Finally, it included the latest version of libpcap (from
http://www.tcpdump.org/) in the 1.0 branch.
Full details of the changes can be found in the change log below.
As always, we profoundly thank all the users that tested the development
versions of WinPcap 4.1. Thanks!
Gianluca Va
cannot figure out....
>
>
> Thanks,
> Joshua
>
>
> On Tue, Sep 1, 2009 at 5:29 PM, Gianluca
> Varenni wrote:
>> On Windows/WinPcap the only devices that support any of the wireless DLTs
>> (DLT_IEEE802_11, DLT_IEEE802_11_RADIO or eventually DLT_PPI)
If you want to debug the winpcap driver (npf.sys) you will need two machines
(or eventually a virtual machine supporting your device) and WinDbg for
kernel debugging.
Have a nice day
GV
- Original Message -
From: "Joshua (Shiwei) Zhao"
To: ; "Developer support list for Wireshark"
Se
On Windows/WinPcap the only devices that support any of the wireless DLTs
(DLT_IEEE802_11, DLT_IEEE802_11_RADIO or eventually DLT_PPI) are the AirPcap
adapters.
Are you using an AirPcap adapter?
Have a nice day
GV
- Original Message -
From: "Joshua (Shiwei) Zhao"
To: "Developer suppo
twork monitor does display the device name/description
correctly. So maybe it could be a reference.
Regards,
Joshua
On Mon, Jul 27, 2009 at 9:12 AM, Gianluca Varenni
wrote:
It's one of those things I want to look at, but probably it won't happen
for the next release
es showing same
problem) on a same machine, currently it's hard to tell which one is which.
Thanks,
Joshua
On Fri, Jul 24, 2009 at 12:05 PM, Gianluca Varenni
wrote:
Microsoft is the wireless adapter.
Native wifi adapters on Vista/Win7 have an Intermediate driver (from MS)
Why are you using a checked version of the Windows Kernel?
Have a nice day
GV
- Original Message -
From: Gilmour, Scott
To: Gianluca Varenni ; Developer support listfor Wireshark
Cc: winpcap-bugs2
Sent: Friday, July 24, 2009 12:10 PM
Subject: Re: [Winpcap-bugs] [Wireshark
What does this tell? Is it the wifi card I have? Then why there is no
descriptive name like what we get on xp?
Thanks,
Joshua
On Fri, Jul 24, 2009 at 11:36 AM, Gianluca Varenni
wrote:
What is the list of adapters returned by Wireshark? Do you have an adapter
just called
What is the list of adapters returned by Wireshark? Do you have an adapter just
called "Microsoft"?
GV
- Original Message -
From: Joshua (Shiwei) Zhao
To: Developer support list for Wireshark
Sent: Friday, July 24, 2009 11:18 AM
Subject: [Wireshark-dev] Wireshark on vista
are you talking about Wireshark or Windows?
GV
- Original Message -
From: Gilmour, Scott
To: Gianluca Varenni ; Developer support list for Wireshark
Cc: winpcap-bugs2
Sent: Friday, July 24, 2009 11:18 AM
Subject: RE: [Winpcap-bugs] [Wireshark-dev] Windows 2008 Server
-boun...@wireshark.org] On Behalf Of Gianluca Varenni
Sent: Friday, July 24, 2009 12:46 PM
To: Developer support list for Wireshark
Cc: winpcap-bugs2
Subject: Re: [Wireshark-dev] Windows 2008 Server
Try to enable the generation of minidumps:
1. in the start menu, right click on Compute
support list for Wireshark
Sent: Friday, July 24, 2009 9:27 AM
Subject: Re: [Wireshark-dev] Windows 2008 Server
GV,
The folder c:\windows\minidump is empty.
What should I do next?
Thanks
Scott
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshar
shark
Sent: Friday, July 24, 2009 6:46 AM
Subject: Re: [Wireshark-dev] Windows 2008 Server
Gilmour, Scott wrote:
Graham,
Did you ever receive the memory.dmp file?
Thanks
Scott
It was Gianluca Varenni that was looking for the dump file.
--
Regards,
Graham B
v] Windows 2008 Server
I will reinstall Wireshark and send you the information.
Thanks
Scott
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Gianluca Varenni
Sent: Wednesday, July 22, 2009 11:27 AM
To: Developer suppor
Do you have a crash dump that you can send me?
Have a nice day
GV
- Original Message -
From: Graham Bloice
To: Developer support list for Wireshark
Sent: Wednesday, July 22, 2009 7:26 AM
Subject: Re: [Wireshark-dev] Windows 2008 Server
Gilmour, Scott wrote:
Graham,
Which kind of information do you need to write into the registry?
Can you show me some example?
Have a nice day
Gianluca Varenni
WinPcap Team
- Original Message -
From: "Guy Harris"
To: "Developer support list for Wireshark"
Sent: Tuesday, July 14, 2009 3:09 PM
Sub
Which specific file did you try to open?
Have a nice day
GV
- Original Message -
From: "SOLTANI FATEN"
To:
Sent: Friday, May 29, 2009 6:02 AM
Subject: [Wireshark-dev] wireshark cant read pcapNg file
> Hello,
> I tried to open PcapNG file from:
> http://wiki.wireshark.org/Development/
May 19, 2009 4:25 PM
Subject: Re: [Wireshark-dev] pcap-ng
> On Tue, May 19, 2009 at 2:59 PM, Gianluca Varenni
> wrote:
>> ntar reads and writes pcap-ng files (it was the first implementation of
>> the
>> pcap-ng format).
>>
>> You can find a version of it at
ntar reads and writes pcap-ng files (it was the first implementation of the
pcap-ng format).
You can find a version of it at
http://www.winpcap.org/ntar/
It compiles on Windows and Linux, and it should compile ok on other
platforms as well.
The ZIP/tarball snapshots are a bit dated, I admit th
I would be careful in replacing all the PULONG as "guint32 *" (and all the
other P... types).
PULONG is defined with a typedef as something like
typedef unsigned long *PULONG;
If you have line like this
PULONG a, b;
the sostitution would return
guint32 *a, b;
which is wrong.
Also, HANDLE a
- Original Message -
From: "Gerald Combs"
To: "Developer support list for Wireshark"
Sent: Friday, April 17, 2009 11:26 AM
Subject: Re: [Wireshark-dev] [Wireshark-commits] wireshark-win32-libs rev
233: /tags/2009-04-16/
> Bill Meier wrote:
>> ger...@wireshark.org wrote:
>>> http://an
- Original Message -
From: "Bill Meier"
To: "Developer support list for Wireshark"
Sent: Friday, April 17, 2009 10:52 AM
Subject: Re: [Wireshark-dev] [Wireshark-commits] wireshark-win32-libs
rev233: /tags/2009-04-16/
> ger...@wireshark.org wrote:
>> http://anonsvn.wireshark.org/viewv
uesday, April 07, 2009 10:39 AM
Subject: Re: [Wireshark-dev] Wrong FCS in 802.11 capture
> "Gianluca Varenni" wrote:
>
>> They definitely look like junk... did the capture contain *only* such
>> errored frames?
>> Which AirPcap adapter are you using (Classic, Tx,
- Original Message -
From: "Gisle Vanem"
To: "wireshark-dev"
Sent: Monday, April 06, 2009 10:40 PM
Subject: [Wireshark-dev] Wrong FCS in 802.11 capture
> Can anybody verify the attached live capure I did just now?
> All the frames in the capture seems to have wrong Frame Check Sequence
If the memory is allocated within the DLL, it should be freed from within
the DLL (i.e. you should provide a function exported by the DLL to free such
memory).
Allocating memory with malloc in a DLL and free'ing it from outside the DLL
is bad mojo.
http://msdn.microsoft.com/en-us/library/ms235
shark currently support the Controller Area Network (CAN)
> [1] ?
There is a pcap DLT_ value assigned to CAN 2.0:
/*
* Controller Area Network (CAN) v. 2.0B packets.
* DLT_ requested by Gianluca Varenni .
* Used to dump CAN packets coming from a CAN Vector board.
* More documentation on the CAN
ed at the end of this
message.
Being a beta release, as usual, we encourage people to test it and report
any anomaly or strange behavior to the WinPcap mailing lists.
Gianluca Varenni
WinPcap Team
Changelog from WinPcap 4.1 beta4
- Starting from this build, Wi
ed to share the idea as widely as possible so that when
someone else runs into the same problem, they can benefit from my experience.
The important thing is to resolve the issue one way or another.
Thanks,
Matt
On Wed, Nov 12, 2008 at 2:25 PM, Gianluca Varenni <[EMAIL PROTECTED]&g
We are aware of the problem with stripped down versions of Windows XP. Newer
versions of the WinPcap installer detect the problem, return the error and
install a slightly different version of the DLLs that do not require NetMon
(with the limitation of not being able to capture on dialup adapters
- Original Message -
From: "Guy Harris" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Tuesday, September 09, 2008 4:49 PM
Subject: Re: [Wireshark-dev] Problem with Intel® Wireless WiFi Link 4965AGN
card
>
> On Sep 9, 2008, at
Short story: the wireless adapter is probably one of the two "Microsoft"
ones.
Long story: starting from Vista, wireless drivers can be old style (NDIS
5.x) working exactly like in Windows 2000/XP, or native Wifi drivers
(NDIS6). In this case the driver is lightweight and delivers 802.11 frames
at the end of
this message.
Being a beta release, as usual, we encourage people to test it and
report any anomaly or strange behavior to the WinPcap mailing lists.
Gianluca Varenni
WinPcap Team
Changelog from WinPcap 4.1 beta2
- Added support for the CACE
Packets are not timestamped by Wireshark. They are timestamped by the WinPcap
driver. In case of the AirPcap adapters, each packets ships with two
timestamps, one generated by the driver (in the bpf/pcap header) and one
generated by the hardware within the PPI/radiotap header.
You cannot improv
out passing
> copied packets. Thus, is there any solution to my problem? Wireshark works
> fine, so there must be a way, isn't there?
>
>
> María de Fátima Requena Cabot (2488)
> +34 91 787 23 00 alhambra-eidos.es
>
>
> -Mensaje original-
> De: [EMAI
ms doesn't affect performance a lot
in case of high traffic.
Have a nice day
GV
>
> María de Fátima Requena Cabot (2488)
> +34 91 787 23 00 alhambra-eidos.es
>
>
>
> -Mensaje original-
> De: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] En nombre de Gianluc
that's because you are not calling the pcap_dumper function from within the
pcap_loop callback.
your "my_callback" function simply prints out "Welcome".
Even if you are running on *nix, I suggest you to have a look at the samples
included in the WinPcap developer's pack (examples-pcap folder).
a Cabot (2488)
+34 91 787 23 00 alhambra-eidos.es
-Mensaje original-
De: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] En nombre de Gianluca Varenni
Enviado el: lunes, 05 de mayo de 2008 18:17
Para: Developer support list for Wireshark
Asunto: Re: [Wireshark-dev] ring buffer
What do you mean b
Requena Cabot (2488)
+34 91 787 23 00 alhambra-eidos.es
-Mensaje original-
De: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] En nombre de Gianluca Varenni
Enviado el: viernes, 02 de mayo de 2008 22:33
Para: Developer support list for Wireshark
Asunto: Re: [Wireshark-dev] ring buffer
Out of curiosit
Out of curiosity, does the sample in the WinPcap developer's pack named
wpdpack\Examples-pcap\savedump lose packets as well?
Have a nice day
GV
- Original Message -
From: "Maria de Fatima Requena" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Friday, May 02, 200
- Original Message -
From: "Guy Harris" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Thursday, April 10, 2008 2:03 PM
Subject: Re: [Wireshark-dev] Triggers
> Luis EG Ontanon wrote:
>> I did not notice those replies to the bug.. Nice... I'll take a look...
>>
>>
A UAC problem?
If the WinPcap driver has not been started, Wireshark should run with
elevated privileges the first time. However, this problem should affect
Wireshark Portable as well as the installed Wireshark.
Have a nice day
GV
- Original Message -
From: "Graeme Lunt" <[EMAIL PROT
- Original Message -
From: "Stephen Fisher" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Tuesday, February 19, 2008 8:43 PM
Subject: Re: [Wireshark-dev] pcap-ng support
> On Mon, Feb 18, 2008 at 02:28:58PM -0800, Gianluca Varenni
D]>
To: "Developer support list for Wireshark"
Sent: Saturday, February 16, 2008 12:10 AM
Subject: Re: [Wireshark-dev] pcap-ng support
> On Thu, Jan 17, 2008 at 04:31:46PM -0800, Gianluca Varenni wrote:
>
>> FYI today I tried opening a pcap-ng file with wireshark rev 24118,
t;Ulf Lamping" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Tuesday, January 22, 2008 2:00 AM
Subject: Re: [Wireshark-dev] pcap-ng support
> Gianluca Varenni schrieb:
>> I just uploaded a new version of the spec here
>>
>> http://www.win
wireless traffic (802.11).
Full details can be found in the change log attached at the end of
this message.
Being a beta release, as usual, we encourage people to test it and
report any anomaly or strange behavior to the WinPcap mailing lists.
Gianluca Varenni
WinPcap Team
Changelog from
Tyson.
On Jan 18, 2008 7:01 AM, Ulf Lamping < [EMAIL PROTECTED]> wrote:
Gianluca Varenni schrieb:
> FYI today I tried opening a pcap-ng file with wireshark rev 24118, and
> it sort of worked.
>
> What works:
> - the first file I opened was a 50+M
: "Gianluca Varenni" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Monday, January 21, 2008 9:36 AM
Subject: Re: [Wireshark-dev] pcap-ng support
>
> - Original Message -
> From: "Ulf Lamping" <[EMAIL PROTECTED]>
&
; Stephen Donnelly schrieb:
>> > On Mon, 2008-01-21 at 22:00 +0100, Ulf Lamping wrote:
>> >> Gianluca Varenni schrieb:
>
>> >>> http://www.winpcap.org/pipermail/ntar-workers/2006-March/000122.html
>
>> > I believe part of the idea behind allowin
- Original Message -
From: "Ulf Lamping" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Friday, January 18, 2008 2:41 AM
Subject: Re: [Wireshark-dev] pcap-ng support
> Gianluca Varenni schrieb:
>> What doesn't work:
- Original Message -
From: "Stephen Fisher" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Thursday, January 17, 2008 6:19 PM
Subject: Re: [Wireshark-dev] pcap-ng support
> On Thu, Jan 17, 2008 at 05:45:04PM -0800, Gianluca Varenni wro
- Original Message -
From: "Stephen Fisher" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Thursday, January 17, 2008 4:52 PM
Subject: Re: [Wireshark-dev] pcap-ng support
> On Thu, Jan 17, 2008 at 04:31:46PM -0800, Gianluca Varenni
FYI today I tried opening a pcap-ng file with wireshark rev 24118, and it
sort of worked.
What works:
- the first file I opened was a 50+MB file generated with NTAR. Real
ethernet packets coming from a custom board. Wireshark opened the trace
without any problem, and the decoded packets made p
As a matter of fact, there's not much difference between the 3.1 devpack and
the 4.0.2 one (some typos here and there, fixes to the samples, but the
include and lib files have not been changed that much).
If you are planning to migrate to a new WinPcap devpack, I suggest you to
try the devpack
- Original Message -
From: "Will Barker" <[EMAIL PROTECTED]>
To: "'Developer support list for Wireshark'"
Sent: Monday, November 19, 2007 12:01 PM
Subject: Re: [Wireshark-dev] Extending wireshark's capture capabilities
>
> I now have my own device capturing frames and passing them up t
ly encourage all the developers to try
compiling all their WinPcap-based applications against the new WinPcap
developer's pack and report any compilation issue to the winpcap-bugs
mailing list (winpcap-bugswinpcap.org).
Gianluca Varenni
WinPcap Team
Cha
attached at the end of
this message.
Gianluca Varenni
WinPcap Team
Changelog from WinPcap 4.0.1
- Disabled support for monitor mode (also called TME, Table Management
Extensions) in the driver. This module suffers from several security
vulnerabilities that could
isk adresse . . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP aktivert . . . . . . . . . . : Nei
> Automatisk konfigurasjon aktivert : Ja
>
> Tunnelkort Lokal tilkobling* 10:
>
> Medietilstand . . . . . . . . . . : Medium frakoblet
> Tilkoblingsspesifikt DNS-suffiks
I think that those interfaces are exported as dialup connections. Under
Vista WinPcap does *not* support dialup-like interfaces.
Can you please post the output of ipconfig -a?
Thanks
GV
- Original Message -
From: <[EMAIL PROTECTED]>
To:
Sent: Wednesday, November 07, 2007 5:32 AM
Subj
What are the compilation errors you are encountering?
Please post the compilation output of Visual studio.
Have a nice day
GV
- Original Message -
From: Varuna De Silva
To: wireshark-dev@wireshark.org
Sent: Wednesday, October 17, 2007 11:47 PM
Subject: Re: [Wireshark-dev] [Wi
The function is implemented in Packet.dll, the sources are in
\winpcap\Packetntx\dll\packet32.cpp
It's my understanding that you implemented support for your card directly in
wpcap.dll. If so, the p->adapter field is a NULL/bogus pointer, so there Packet
API will receive a NULL/bogus pointer!
H
Paul,
did this error appear after a long time you were capturing? Which version of
WinPcap are you using? The error comes directly from WinPcap (and from its
kernel driver, most probably).
Have a nice day
GV
- Original Message -
From: Paul Ireland
To: wireshark-dev@wireshark.o
I didn't follow the thread too closely, so it's just "my two cents".
Be careful with the "temporary file model". Writing packets to disk can be
slw, so things can get even worse (you drop more packets because tshark
is slow *and* you are dumping to disk).
At least on windows it looks like i
You can still find the last Platform SDK that integrates with Visual Studio
6 here
http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm
Have a nice day
GV
- Original Message -
From: "Michael Lum" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent:
- Original Message -
From: "Ulf Lamping" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Thursday, September 27, 2007 5:22 PM
Subject: Re: [Wireshark-dev] [ntar-workers] Extending Wireshark libpcap
format support, or start using pcapng no
- Original Message -
From: "Ulf Lamping" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Thursday, September 27, 2007 2:01 PM
Subject: Re: [Wireshark-dev] [ntar-workers] Extending Wireshark libpcap
format support, or start using pcapng no
First of all, sorry for taking a bit of time to answer this thread, I was
working on libpcap/WinPcap. libpcap 1.0 is planned to come out soon...
Replies embedded below.
Have a nice
GV
- Original Message -
From: "Ulf Lamping" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark
- Original Message -
From: "Jeffrey Chen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc:
Sent: Sunday, September 16, 2007 3:07 AM
Subject: [Winpcap-team] Help! Error installing the MS Network Monitor Driver
> Hi all
>
> i'm using Wireshark for a class I'm taking and I keep getting thi
You need to install the VC runtime build 762 on the target machine. That is
the easiest way to have a version of Wireshark built with Visual Studio 2005
Express Edition SP1 running on a machine.
http://www.microsoft.com/downloads/details.aspx?FamilyID=200B2FD9-AE1A-4A14-984D-389C36F85647&display
- Original Message -
From: "Guy Harris" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Thursday, July 19, 2007 5:25 PM
Subject: Re: [Wireshark-dev] As requested
>
> On Jul 19, 2007, at 11:33 AM, Niklas Bergh wrote:
>
>> I was greeted with this message after resumi
- Original Message -
From: "Ulf Lamping" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Friday, July 13, 2007 6:05 PM
Subject: Re: [Wireshark-dev] Win32: remove binary zlib.dll completely and
compile it for all MSVC variants?
> Gerald Combs schrieb:
>> Ulf Lampin
- Original Message -
From: "Ulf Lamping" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Friday, July 13, 2007 4:15 AM
Subject: Re: [Wireshark-dev] [Wireshark-commits] rev 22259:
/trunk/packaging/nsis/ /trunk/packaging/nsis/: wireshark.nsi
> Jaap Keuter schrieb:
>>
- Original Message -
From: "Ulf Lamping" <[EMAIL PROTECTED]>
To:
Sent: Thursday, July 12, 2007 7:11 PM
Subject: Re: [Wireshark-dev] [Wireshark-commits] rev 22259:
/trunk/packaging/nsis/ /trunk/packaging/nsis/: wireshark.nsi
> [EMAIL PROTECTED] schrieb:
>> http://anonsvn.wireshark.org/
of
this message.
Being a beta release, as usual we encourage people to test it and
report any anomaly or strange behavior to the WinPcap mailing lists.
Gianluca Varenni
WinPcap Team
Changelog from WinPcap 4.0.1
- Added support for the Per Packet Info (PPI
.
Gianluca Varenni
WinPcap Team
Changelog from WinPcap 4.0
==
- Bug fixing:
* Fixed a bug in the dispatcher of the BIOCGSTATS IOCTL that caused
a BSOD if the parameters passed from user level were invalid. This
fix addresses a security vulnerability reported by
wireshark doesn't actually capture the packets on its own. It uses WinPcap to
capture the packets from the stack.
WinPcap is implemented as an NDIS protocol driver, so it works in parallel with
other protocols like TCP/IP. Things are a bit more complex when it comes to
VPNs and dialup adapters.
the time being
(especially considering that the final version is scheduled within some
days).
Just my two cents
Gianluca Varenni
WinPcap Team
>
>
> # The WinPcap developer's pack version Wireshark is build with.
> #
> # If you don't have the WPdpack, comment this line o
precious suggestions. Thanks!
Gianluca Varenni
WinPcap Team
Changelog from WinPcap 4.0 beta3
- Added support for Vista x64 by digitally signing all the binaries of
the WinPcap distribution.
- Better error handling in the installer - if the installation
- Original Message -
From: "Guy Harris" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Friday, January 12, 2007 11:59 AM
Subject: Re: [Wireshark-dev] Is pcap-ng/ntar still in roadmap?
> Gianluca Varenni wrote:
>
>> I would pr
- Original Message -
From: "Guy Harris" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Friday, January 12, 2007 10:21 AM
Subject: Re: [Wireshark-dev] Is pcap-ng/ntar still in roadmap?
> Benn Bollay wrote:
>
>> How difficult will the integration into the std tools
one section and packets from one
interface).
IMHO the best thing to do would be better decouple packet capture from
packet logging to file. libpcap is the capture library, NTAR (or any other
library) is the library used to read/write capture files.
Just my two cents.
GV
>
> Cheers!
&g
Benn,
regarding the NTAR project (i.e. the only implementation of the pcap-ng
"wannabe" spec so far) that I "maintain", I've been pretty busy in the last
year or so, thus not being able to work on it. The project is not dead at
all, I'm simply giving priority to other tasks...
As far as the in
- Original Message -
From: "Guy Harris" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Wednesday, December 20, 2006 2:36 AM
Subject: Re: [Wireshark-dev] Microsoft Visual C Version 6 support is a
bitoutdated ...
> However, I seem to remember the WinPcap developer
message.
Being a beta release, as usual we encourage people to test it and
report any anomaly or strange behavior to the WinPcap mailing lists.
The final release of WinPcap 4.0 is expected to be available by the
end of January 2007.
Gianluca Varenni
WinPcap Team
Changelog
official version of libpcap v0.9.5 available
on the tcpdump website.
Being a beta release, as usual we encourage people to test it and
report any anomaly or strange behavior to the WinPcap mailing lists.
The complete change log is attached at the end of this message.
Gianluca Varenni
WinPcap
- Original Message -
From: "abeni" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Wednesday, September 27, 2006 1:35 AM
Subject: Re: [Wireshark-dev] [PATCH] enable sniff on USB ports
> On Wed, 2006-09-27 at 08:14 +, ronnie sahlberg wrote:
>> On 9/20/06, abeni
.
Being a beta release, as usual we encourage people to test it and
report any anomaly or strange behavior to the WinPcap mailing lists.
The complete change log is attached at the end of this message.
Gianluca Varenni
WinPcap Team
Changelog
=
- Added support for AirPcap adapters
99 matches
Mail list logo
