https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3687
Summary: Wireshark 1.2 wont start up when connected to SPAN port
on switch
Product: Wireshark
Version: 1.2.0
Platform: x86
OS/Version: Windows XP
Status: NEW
Severity: Major
Priority: Medium
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: rnutter@xxxxxxxx
Created an attachment (id=3291)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=3291)
Microsoft error report file giving specific details
Build Information:
Version 1.2.0 (SVN Rev 28753)
Copyright 1998-2009 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled with GTK+ 2.16.2, with GLib 2.20.3, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with c-ares 1.6.0, with Lua 5.1, with GnuTLS 2.8.1, with Gcrypt 1.4.4, with MIT
Kerberos, with GeoIP, with PortAudio V19-devel (built Jun 15 2009), with
AirPcap.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1
beta5
(packet.dll version 4.1.0.1452), based on libpcap version 1.0.0, GnuTLS 2.8.1,
Gcrypt 1.4.4, without AirPcap.
Built using Microsoft Visual C++ 9.0 build 30729
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
I was trying to do some captures of an access point on startup. Wireshark and
tshark both kept crashing and complaining about some problem that had to be
reported to microsoft. I was connected to a span port on a cisco 3750 switch.
I even tried to assign a static ip address and still received the error. I
uninstalled and reinstalled Wireshark 1.2 with no resolution in the problem.
If I downgraded to 1.0.8, the problem no longer occurs. Screen captures and
other info attached.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
