On Aug 5, 2011, at 12:10 AM, tue...@wireshark.org wrote:
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=38349
User: tuexen
Date: 2011/08/05 12:10 AM
Log:
Generate the capure sync pipe correctly.
Fix obtained from Irene Ruengeler.
Directory: /trunk/
ChangesPath
Hi,
in Wireshark 1.6.1, i'm unable to Decode As ... ASN.1
It works in Ethereal 0.10.5 (yes, i know, that's old) for the same trace file.
Anybody knows why and when the ASN1 dissector got dysfunctional?
Am i missing some preference settings?
Does anybody have an example of a functional ASN1
The Buildbot has detected a new failure of Visual-Studio-Code-Analysis on
Wireshark (development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Visual-Studio-Code-Analysis/builds/1519
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build:
On Aug 5, 2011, at 9:28 AM, Guy Harris wrote:
On Aug 5, 2011, at 12:10 AM, tue...@wireshark.org wrote:
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=38349
User: tuexen
Date: 2011/08/05 12:10 AM
Log:
Generate the capure sync pipe correctly.
Fix obtained from Irene
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/3947
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 Windows-7-x64 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/2619
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-7-x64
Build Reason:
On Fri, Aug 5, 2011 at 9:19 AM, tue...@wireshark.org wrote:
Log:
Add support for multiple interfaces to the capture options dialog.
Really nice!
Some initial comments after short time testing:
* The Edit Interfaces Settings should default to the OK button when
pressing enter in Capture
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/3376
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-ppc
Build
And some more comments:
* Capture packets in monitor mode is enabled for devices not supporting this.
* When manually selecting all interfaces in the list, should the
checkbox Capture on all interfaces be automatically checked?
* I get wrong link-layer for some of my remote (rpcap) devices. This
On 04/08/2011 20:23, Guy Harris wrote:
On Aug 4, 2011, at 10:47 AM, Roland Knall wrote:
There should be a file called core in the directory you called Wireshark
from. Please send this file.
More precisely, please send this file, and the entire build directory for
Wireshark, to somebody
/home/jmayer/work/wireshark/svn/trunk/gtk/main_welcome.c: In function
âadd_interface_to_listâ:
/home/jmayer/work/wireshark/svn/trunk/gtk/main_welcome.c:904:26: error:
âcapture_airpcap_16_xpmâ undeclared (first use in this function)
On Fri, Aug 05, 2011 at 12:00:52PM +0200, Joerg Mayer wrote:
/home/jmayer/work/wireshark/svn/trunk/gtk/main_welcome.c: In function
âadd_interface_to_listâ:
/home/jmayer/work/wireshark/svn/trunk/gtk/main_welcome.c:904:26: error:
âcapture_airpcap_16_xpmâ undeclared (first use in this
On Fri, Aug 05, 2011 at 02:45:09AM +0200, Joerg Mayer wrote:
Directory: /trunk/wsutil/
ChangesPath Action
+1 -1 CMakeLists.txtModified
GLIB2_LIBRARIES - GLIB2_LDFLAGS
Is this really the correct place or should this be fixed in FindGLIB2 instead?
From
On Aug 5, 2011, at 12:19 PM, Joerg Mayer wrote:
On Fri, Aug 05, 2011 at 12:00:52PM +0200, Joerg Mayer wrote:
/home/jmayer/work/wireshark/svn/trunk/gtk/main_welcome.c: In function
âadd_interface_to_listâ:
/home/jmayer/work/wireshark/svn/trunk/gtk/main_welcome.c:904:26: error:
Joerg Mayer wrote:
On Thu, Aug 04, 2011 at 06:33:34PM -0400, Jeff Morriss wrote:
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=38340
User: cmaynard
Don't report svn version if not building from svn. Change prompted by
Hello,
I try to implement a UDP checksum routine. Unfortunately it calculates a
completely different value than Wireshark does. I don't known what I am
doing wrong. Can you help me?
The calculation is done using a UDP pseudo header with the structure
struct pseudo
{
uint32 source;
You've forgotten to include the UDP payload in your calculation. For the
calculation the pseudo header must be in front of UDP header and UDP payload.
Helge
Original-Nachricht
Datum: Fri, 5 Aug 2011 15:45:38 +0200
Von: news.gmane.com andreassand...@gmx.net
An:
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/3956
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: osx-10.5-x86
Build Reason:
thanks for fixing it!
Not completely - I only fixed the trivial stuff :-) The following is still open:
jmayer@egg:~/work/wireshark/svn/build/gtk make -k main_welcome.o capture_dlg.o
[ 5%] Building C object gtk/CMakeFiles/ui.dir/main_welcome.c.o
Hi,
On 08/05/2011 04:01 AM, Jeff Morriss wrote:
On 08/04/2011 07:35 PM, Tony Trinh wrote:
Isn't Python also necessary for the Wireshark Python API? (It's disabled
by default, unlike the Lua API.)
Yes, but here we're talking about whether we have/should have a (hard)
requirement to have
Hi,
Backtrace file is attached.
Thanks,
On 8/5/2011 2:32 AM, Guy Harris wrote:
On Aug 4, 2011, at 12:25 PM, Roland Knall wrote:
An exception in packet.c can be nearly anything. The backtrace is what
I am looking for,
Yes, as I said. My point is that sending us the core dump won't
I just tried to fix the stuff in main_welcome.c:
Index: main_welcome.c
===
--- main_welcome.c (revision 38365)
+++ main_welcome.c (working copy)
@@ -72,6 +72,9 @@
#include airpcap.h
#include airpcap_loader.h
#include
On Aug 5, 2011, at 5:59 PM, Joerg Mayer wrote:
I just tried to fix the stuff in main_welcome.c:
Index: main_welcome.c
===
--- main_welcome.c (revision 38365)
+++ main_welcome.c (working copy)
@@ -72,6 +72,9 @@
On Aug 5, 2011, at 8:21 AM, Ngo Hoang Thang wrote:
Backtrace file is attached.
Unfortunately, there don't seem to be any symbols in the binary, so there
aren't any symbols in the backtrace, so there's not much we can do about it.
On 8/5/11 5:01 AM, Joerg Mayer wrote:
On Fri, Aug 05, 2011 at 02:45:09AM +0200, Joerg Mayer wrote:
Directory: /trunk/wsutil/
ChangesPath Action
+1 -1 CMakeLists.txtModified
GLIB2_LIBRARIES - GLIB2_LDFLAGS
Is this really the correct place or should this be
On Fri, Aug 05, 2011 at 10:07:10AM -0700, Gerald Combs wrote:
I'm trying to use CMake with MacPorts, with GLib, GTK+, et al residing
in /opt/local. After running cmake . I end up with the following in
CMakeCache.txt:
GLIB2_LDFLAGS:INTERNAL=-L/opt/local/lib;-lglib-2.0;-lintl;-liconv
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/320
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build:
On 8/5/11 10:15 AM, Joerg Mayer wrote:
Yes, I have undone your change and checked in something that I hope is
the right fix to FindGLIB2 earlier today.
Using r38367:
$ make wsutil
Linking C shared library ../lib/libwsutil.dylib
ld: library not found for -lglib-2.0
collect2: ld returned 1 exit
On Aug 5, 2011, at 5:59 PM, Joerg Mayer wrote:
I just tried to fix the stuff in main_welcome.c:
Index: main_welcome.c
===
--- main_welcome.c (revision 38365)
+++ main_welcome.c (working copy)
@@ -72,6 +72,9 @@
On Fri, Aug 5, 2011 at 7:23 PM, Gerald Combs ger...@wireshark.org wrote:
$ make wsutil
Linking C shared library ../lib/libwsutil.dylib
ld: library not found for -lglib-2.0
collect2: ld returned 1 exit status
I still have to do this to make it build with cmake and xcode:
On Aug 5, 2011, at 11:20 AM, Stig Bjørlykke wrote:
On Fri, Aug 5, 2011 at 9:19 AM, tue...@wireshark.org wrote:
Log:
Add support for multiple interfaces to the capture options dialog.
Really nice!
Hi Stig,
thank you... Comments are really welcome.
See my comments in-line.
Best regards
On Aug 5, 2011, at 11:36 AM, Stig Bjørlykke wrote:
And some more comments:
* Capture packets in monitor mode is enabled for devices not supporting
this.
If there is a way to figure out if it is supported, we should handle that
correctly,
I agree.
* When manually selecting all interfaces
On Aug 5, 2011, at 2:09 PM, Michael Tuexen wrote:
On Aug 5, 2011, at 11:36 AM, Stig Bjørlykke wrote:
And some more comments:
* Capture packets in monitor mode is enabled for devices not supporting
this.
If there is a way to figure out if it is supported,
There is, and the code used to
The tools/make-manuf script attempts to gather Ethernet codes from IEEE, but
also from CaveBear at http://www.cavebear.com/CaveBear/Ethernet/Ethernet.txt,
but unfortunately this link is dead.
I could not find any meaningful contact information to Karl Auerbach on the site
other than Santa Cruz,
34 matches
Mail list logo
