sagar Guledagudda skrev 2011-08-03 06:59:
What are those local changes i suppose to do ???
Packages: zlib125ws.zip
Location: http://www.gzip.org/zlib/
Description: The zlib compression library (source and DLL versions)
License: zlib/libpng
Local changes:
From http://www.apachehaus.com/forum/ind
What are those local changes i suppose to do ???
On Mon, Aug 1, 2011 at 12:55 PM, Anders Broman
wrote:
> **
> Hi,
> Did you download the suport libraries? We have local changes to Zlib I
> think. If you did try forcing rebuild of zlib by deleteing the temp build
> dir for zlib.
> Regards
> Anders
Hi,
I have come across an issue whilst attempting to write a custom dissector
for the XCP protocol. The protocol sits on top of TCP and I am using the
tcp_dissect_pdus function to handle the reassembly of TCP packets to allow
successful dissecting of my PDUs.
The protocol includes a packet count
The Buildbot has detected a new failure of OSX-10.5-PowerPC on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/OSX-10.5-PowerPC/builds/3358
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-ppc
Build Reas
On Aug 2, 2011, at 2:25 PM, Stig Bjørlykke wrote:
> Are you sure? Isn't this for (some) regular wireless adapters on Windows?
> I'm not getting any information from my AirPcap...
WinPcap doesn't support NDIS 6.0, so it doesn't support the "native Wi-Fi" stuf
that was introduced in Vista, so it
On Aug 2, 2011, at 1:48 PM, Alex Lindberg wrote:
> Win32 in my case is XP + SP3.
>
> It stays in memory (GUI or tshark version) so that when I run another compile
> on windows, during the copy of the exe to wireshark-gtk, the build fails with
> "unable to copy" message. If I kill wireshark.ex
On Mon, Aug 1, 2011 at 11:41 PM, Guy Harris wrote:
>
> On Aug 1, 2011, at 1:51 PM, Anders Broman wrote:
>
>> so I assume these are shown for 802.11 interfaces.
>
> ...which, on Windows, means AirPcap interfaces.
Are you sure? Isn't this for (some) regular wireless adapters on Windows?
I'm not ge
Hi,
On Tue, Aug 02, 2011 at 01:48:59PM -0700, Alex Lindberg wrote:
> It stays in memory (GUI or tshark version) so that when I run another compile
> on windows, during the copy of the exe to wireshark-gtk, the build fails with
> "unable to copy" message. If I kill wireshark.exe from the task ma
Win32 in my case is XP + SP3.
It stays in memory (GUI or tshark version) so that when I run another compile
on windows, during the copy of the exe to wireshark-gtk, the build fails with
"unable to copy" message. If I kill wireshark.exe from the task manager, all
is good.
If I build the standa
On Aug 2, 2011, at 12:21 PM, Alex Lindberg wrote:
> When I quit a custom build of Wireshark (Win32), although the application
> disappears from the desktop, it remains in memory.
What do you mean "remains in memory"?
Perhaps Windows - which probably means Windows NT these days, with XP and lat
The Buildbot has detected a new failure of Ubuntu-10.04-x64 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Ubuntu-10.04-x64/builds/1949
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: ubuntu-10.04-x64
Build
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/3640
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.6-x64 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/OSX-10.6-x64/builds/3447
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.6-x64
Build Reason:
Bui
When I quit a custom build of Wireshark (Win32), although the application
disappears from the desktop, it remains in memory.
I use g_regex for a number of dissectors. In previous versions I was using the
PCRE library and did not have this issue.
When Wireshark quits, is there a "un-register" r
The Buildbot has detected a new failure of Clang-Code-Analysis on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Clang-Code-Analysis/builds/311
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: clang-code-analysis
Stephen Fisher wrote:
On Tue, Aug 02, 2011 at 11:22:03AM -0400, Jeff Morriss wrote:
If there was a way to tell if it was changed and only then generate it,
I would say yes. If it is re-generated without changes, I suspect the
compiler would recompile it every time.
'make' does that for you :-
Well, I guess your expectations are a bit off.
> 1. It would work on all protocols that had a FT_ABSOLUTE_TIME item
> (satisfying most of bug 1381)
It changed the date parser. It should work on any FT_ABSOLUTE_TIME item.
> 2. Missing date/time fields in the filter would be set to 0 and consider
On 8/2/2011 11:19 AM, Marc Petit-Huguenin wrote:
I had the same exact problem when my Debian sid distribution updated the gcc 4.6
compiler. I use 4.5 instead, and everything works.
Um... I suspect you had a slightly different problem when compiling
with GCC 4.6 which added a check for "un
Greetings,
I would like to know the steps to compute R-Factor or MOS using
Wireshark for VoIP/SIP traffic.
Thanks and Regards
R
___
Sent via:Wireshark-dev mailing list
Archives:http://www.wireshark.org/lists/wiresh
On Tue, Aug 02, 2011 at 11:22:03AM -0400, Jeff Morriss wrote:
> Do we already require Python to build Wireshark [even from a source
> distribution]?
I don't think so.
> > If there was a way to tell if it was changed and only then generate it,
> > I would say yes. If it is re-generated without
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/02/2011 03:47 AM, Kaul wrote:
> Fedora15/x64, r38309:
>
> packet-6lowpan.c: In function 'dissect_6lowpan_frag_first':
> packet-6lowpan.c:2125:25: error: 'save_fragmented' undeclared (first use in
> this
> function)
> packet-6lowpan.c:2125:25: n
Stephen Fisher wrote:
On Tue, Aug 02, 2011 at 08:42:53AM -0400, Maynard, Chris wrote:
Oops. Thanks. Would it make sense to have these types of dissectors
automatically generated at compile time?
Historically this wasn't done because it wasn't sure that asn2wrs was
"ready for prime time," i
Strange indeed. I don't recall ever touching that dissector.
Sorry for the noise.
Y.
On Tue, Aug 2, 2011 at 4:42 PM, Bill Meier wrote:
> On 8/2/2011 6:47 AM, Kaul wrote:
>
>> Fedora15/x64, r38309:
>>
>> packet-6lowpan.c: In function 'dissect_6lowpan_frag_first':
>> packet-6lowpan.c:2125:25: erro
On Tue, Aug 02, 2011 at 08:42:53AM -0400, Maynard, Chris wrote:
> Oops. Thanks. Would it make sense to have these types of dissectors
> automatically generated at compile time?
If there was a way to tell if it was changed and only then generate it,
I would say yes. If it is re-generated with
I was greatly intrigued by the patch from bug 6086 and my expectation was that
1. It would work on all protocols that had a FT_ABSOLUTE_TIME item (satisfying
most of bug 1381)
2. Missing date/time fields in the filter would be set to 0 and considered
"don't care" (ie "frame.time == 2011-08-02
On 8/2/2011 6:47 AM, Kaul wrote:
Fedora15/x64, r38309:
packet-6lowpan.c: In function 'dissect_6lowpan_frag_first':
packet-6lowpan.c:2125:25: error: 'save_fragmented' undeclared (first use in
this function)
packet-6lowpan.c:2125:25: note: each undeclared identifier is reported only
once for each
Oops. Thanks. Would it make sense to have these types of dissectors
automatically generated at compile time?
- Chris
> -Original Message-
> From: wireshark-commits-boun...@wireshark.org [mailto:wireshark-commits-
> boun...@wireshark.org] On Behalf Of etx...@wireshark.org
> Sent: Tuesda
Fedora15/x64, r38309:
packet-6lowpan.c: In function 'dissect_6lowpan_frag_first':
packet-6lowpan.c:2125:25: error: 'save_fragmented' undeclared (first use in
this function)
packet-6lowpan.c:2125:25: note: each undeclared identifier is reported only
once for each function it appears in
packet-6lowp
On Thu, Jul 14, 2011 at 09:31:27PM +0200, Jakub Zawadzki wrote:
> It's building graph (using Graphviz) based on the conversation list.
> Some screenshots:
> http://darkjames.pl/tmp/wireviz-1.png
> http://darkjames.pl/tmp/wireviz-2.png
> http://darkjames.pl/tmp/wireviz-3.png
Or screencast:
http
29 matches
Mail list logo
