[Wireshark-dev] buildbot failure in Wireshark (development) on Ubuntu-10.04-x64
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/18 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-10.04-x64 Build Reason: Build Source Stamp: 32683 Blamelist: stig BUILD FAILED: failed test.sh sincerely, -The Buildbot ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] buildbot failure in Wireshark (development) on Solaris-10-SPARC
The Buildbot has detected a new failure of Solaris-10-SPARC on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Solaris-10-SPARC/builds/137 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: solaris-10-sparc Build Reason: Build Source Stamp: 32683 Blamelist: stig BUILD FAILED: failed test.sh sincerely, -The Buildbot ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] tshark (Windows) not working
Hi All, I can't get tshark to work anymore. I get this error: E:\wireshark-src\wireshark-gtk2tshark -i 2 Capturing on Intel(R) 82567LM Gigabit Network Connection ** ERROR:column-utils.c:879:???: code should not be reached E:\wireshark-src\wireshark-gtk2 It seems to be related to the changes related to the timestamps which Stig has been working on. Is anyone else facing issues? I am on revision 32686. Thanks, Abhik. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Incorrect check for MIT Kerberos in configure
Not signing up for bugzilla to report a bug. Sorry. ... checking whether to use kerberos... yes checking krb5.h usability... yes checking krb5.h presence... yes checking for krb5.h... yes checking whether the Kerberos library is Heimdal or MIT... no configure: error: Kerberos not found MIT Kerberos is installed and found right where I told configure. The problem is that you are checking for MIT vs. Heimdal by the existence of the string Massachusetts Institute of Technology in $krb5_dir/include/krb5.h and it should be checked in $krb5_dir/include/krb5/krb5.h I confirmed this with the MIT Kerberos developers in their IRC server just now. # grep Mass /usr/mitkrb18/include/krb5.h # grep Mass /usr/mitkrb18/include/krb5/krb5.h * Copyright 1989,1990,1995,2001, 2003, 2007 by the Massachusetts Institute of Technology. # ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Wireshark Capture Program Shut Down Problem = Please Assist
Hello, I am working with a customer who is capturing Ethernet data off of their Managed Switch using Wireshark and their program is shutting down unexpectedly and stopping the capture of data. They are capturing data every (3) minutes using multiple files for a total of 480 files. The goal is to have 480 (3) minute increments of data over the course of 24 hours. The system shuts down around the 48th file and stops capturing data. The Data files are ~20 MB of data so the Network is very very busy. It is being used for Process Controls and Messaging, etc. Can you assist on common culprits which cause these unecessary shutdowns of Wireshark? Please call (402.321.5057) or email me (jemi...@ra.rockwell.com). Thanks! John E. Miles Field Service Engineer (FSE) Customer Support Maintenance (CSM) Rockwell Automation 5103 S. 111th St. Omaha, NE Office: 402.593.4185 Mobile: 402.321.5057 Email: jemi...@ra.rockwell.com ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Wireshark Capture Program Shut Down Problem = Please Assist
Memory usage might be one culprit. Have you tried using dumpcap instead of Wireshark? Dumpcap works very well for long term capturing. - Chris From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of John E Miles Sent: Wednesday, May 05, 2010 1:47 PM To: wireshark-dev@wireshark.org Cc: kris.chanc...@intervet.com Subject: [Wireshark-dev] Wireshark Capture Program Shut Down Problem = Please Assist Importance: High Hello, I am working with a customer who is capturing Ethernet data off of their Managed Switch using Wireshark and their program is shutting down unexpectedly and stopping the capture of data. They are capturing data every (3) minutes using multiple files for a total of 480 files. The goal is to have 480 (3) minute increments of data over the course of 24 hours. The system shuts down around the 48th file and stops capturing data. The Data files are ~20 MB of data so the Network is very very busy. It is being used for Process Controls and Messaging, etc. Can you assist on common culprits which cause these unecessary shutdowns of Wireshark? Please call (402.321.5057) or email me (jemi...@ra.rockwell.com). Thanks! John E. Miles Field Service Engineer (FSE) Customer Support Maintenance (CSM) Rockwell Automation 5103 S. 111th St. Omaha, NE Office: 402.593.4185 Mobile: 402.321.5057 Email: jemi...@ra.rockwell.com CONFIDENTIALITY NOTICE: The contents of this email are confidential and for the exclusive use of the intended recipient. If you receive this email in error, please delete it from your system immediately and notify us either by email, telephone or fax. You should not copy, forward, or otherwise disclose the content of the email. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] [Wireshark-commits] rev 32687: /trunk/ /trunk/: acinclude.m4
etx...@wireshark.org wrote: http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=32687 User: etxrab Date: 2010/05/06 08:39 AM Log: Check for pcap_create Using pcap create and pcap_activate should make it possible to set the capture buffer size on Linux systems as well as Windows. Help to implement it would be apreciated :-) Ref: http://seclists.org/tcpdump/2009/q3/151 Some work has already been done, see: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=475 ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-7-x64
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/182 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-7-x64 Build Reason: Build Source Stamp: 32690 Blamelist: etxrab,jake BUILD FAILED: failed nmake all sincerely, -The Buildbot ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] What type should I use for 12 byte field in my dissector??
Hi,
What data type can I use when the proprietary protocol says that the field is
12 bytes (96 Bit)
{ hf_myproto_timedate,{ PDU Time Date, myproto.timedate,FT_UINT??,
BASE_DEC,NULL, 0x0,NULL, HFILL }}
Regards,
Craig
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] buildbot failure in Wireshark (development) on Solaris-10-SPARC
The Buildbot has detected a new failure of Solaris-10-SPARC on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Solaris-10-SPARC/builds/144 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: solaris-10-sparc Build Reason: Build Source Stamp: 32707 Blamelist: gerald,guy BUILD FAILED: failed test.sh sincerely, -The Buildbot ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
