The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/4
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-xp-x86
Build Reason:
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/8
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-x86
Build Reason:
Build
Hi,
Could startup of Wireshark be speeded up by using treads for the init
routines in epan_init()?
Regards
Anders
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:
I'm running Wireshark 1.2.1 on Windows XP SP3.
When it starts, it gets to 51% while executing the Handing
off dissector logic, which happens to be 2dparityfec, and
then crashes.
The details are:
Unhandled exception at 0x007F3FC9: 0xC005: Access violation
reading location 0x02C8D000.
ecx ==
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/7
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-xp-x86
Build Reason:
jdhagen chorus.net wrote:
I'm running Wireshark 1.2.1 on Windows XP SP3.
When it starts, it gets to 51% while executing the Handing
off dissector logic, which happens to be 2dparityfec, and
then crashes.
The handing off dissector status window is not not updated for each
dissector so the
On Sep 1, 2009, at 2:11 AM, Anders Broman wrote:
Could startup of Wireshark be speeded up by using treads for the
init routines in epan_init()?
If you mean by running multiple init routines in parallel on a multi-
core machine, then it should be possible to run multiple protocol
init
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/17
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-x86
Build Reason:
The Buildbot has detected a new failure of OSX-10.5-ppc on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/OSX-10.5-ppc/builds/14
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-ppc
Build Reason:
I'm using Wireshark 1.0.4 with a WiFi device. When I select the device
in capture options panel, I cannot get the expected linktype
DLT_IEEE802_11_RADIO.
I know the device driver is in monitor mode and it works if I manually
add a DLT_IEEE802_11_RADIO type there and choose it.
But how does
It might be possible to create a ANS.1/BER description that is
compatible with both encodings.
FooBar ::= SEQUENCE OF
{
kludge KludgeFooBar
}
KludgeFooBar ::= CHOICE
{
item1 [0] IA5String
item2 [1] INTEGER
}
I think this might work and should be able to decode both types of encoding.
It
On Sep 1, 2009, at 4:41 PM, Joshua (Shiwei) Zhao wrote:
I'm using Wireshark 1.0.4 with a WiFi device. When I select the device
in capture options panel, I cannot get the expected linktype
DLT_IEEE802_11_RADIO.
I know the device driver is in monitor mode and it works if I manually
add a
On Sep 1, 2009, at 3:20 PM, Gerry Nadler wrote:
does anyone know if decoders for ISA100 and wireless HART are being
written, Both ISA100 and wireless HART use the IEEE 802.15.4 MAC
and PHY just like Zigbee
If ISA100 uses it the same way Wireless HART does, it'll require a new
DLT_
does anyone know if decoders for ISA100 and wireless HART are being
written, Both ISA100 and wireless HART use the IEEE 802.15.4 MAC and PHY
just like Zigbee
Thanks
Gerry
___
Sent via:Wireshark-dev mailing list
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 swz...@gmail.com
To:
1) In Wireshark, we can choose a default interface but cannot choose a
default linktype for that interface, right? Maybe we need to add that
option :)
2) Since I already set the driver to monitor mode, I thought winpcap
should return that as the default.
In fact, winpcap doesn't even return
I am working on an ASN1 based dissector where there where major changes between
V1 and V2 of the protocol. As such I must select in the proto.cnf file the
correct branch of the ASN1 tree to use. As an example:
Both v1 and v2:
FirstFoo ::= SEQUENCE
{
version [0] INTEGER
dataMessasge
No it's not airpcap. But they don't want us to disclose their name yet :)
I have the driver source code and it does return media type as
NdisMedium802_11_Radio if it receives an OID as I mentioned earlier.
But the driver never sees a request for those OIDs.
In Wireshark I also tried to add code
Hi,
Le mardi 01 septembre 2009 à 11:11 +0200, Anders Broman a écrit :
Hi,
Could startup of Wireshark be speeded up by using treads for the init
routines in epan_init()?
Is Wireshark startup really CPU bound?
Didier
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 swz...@gmail.com
To: winpcap-us...@winpcap.org;
No, it is NDIS 5.x on winxp.
On Tue, Sep 1, 2009 at 6:32 PM, Gianluca
Varennigianluca.vare...@cacetech.com wrote:
Is it an NDIS 6.x driver?
Have a nice day
GV
- Original Message -
From: Joshua (Shiwei) Zhao swz...@gmail.com
To: winpcap-us...@winpcap.org
Cc: Developer support
Is it an NDIS 6.x driver?
Have a nice day
GV
- Original Message -
From: Joshua (Shiwei) Zhao swz...@gmail.com
To: winpcap-us...@winpcap.org
Cc: Developer support list for Wireshark wireshark-dev@wireshark.org
Sent: Tuesday, September 01, 2009 5:48 PM
Subject: Re: [Winpcap-users] how
Is there a way to debug winpcap at runtime when Wireshark calls it?
Many thanks,
Joshua
On Tue, Sep 1, 2009 at 5:37 PM, Guy Harrisg...@alum.mit.edu wrote:
On Sep 1, 2009, at 5:31 PM, Joshua (Shiwei) Zhao wrote:
2) Since I already set the driver to monitor mode, I thought winpcap
should
23 matches
Mail list logo
