Re: [Wireshark-dev] U3 package fails to install

2007-04-09 Thread Graham Bloice
Clifford Thrasher wrote: > Graham Bloice wrote: >> Graeme Lunt wrote: >> >>> Hi, >>> >>> Graham Bloice wrote: > I built a U3 version from SVN 20915, but the resulting .u3p fails to > install on my SanDisk MicroCruzer. > >>> Does the package downloaded f

[Wireshark-dev] Dissecting sua info string

2007-04-09 Thread durgabhavani.uppuluru
Hi, How to dissect the (proprietary) information present in SUA 'info string' part? Should I create a separate dissector handle for that? Please provide your inputs. Thanks in advance. Regards, Bhavani. The information contained in this electronic message and any attachments to this mess

Re: [Wireshark-dev] Questions about IEEE 802.11 dissector

2007-04-09 Thread Stig Bjørlykke
Den 3. apr. 2007 kl. 01.09 skrev Guy Harris: > What type of AirPort adapter do you have? I'm using a iMac 24" which identifies a Broadcom BCM43xx firmware. > I think at least some of them are using (yay!) radiotap headers rather > than AVS headers, although some older ones might've used AVS head

[Wireshark-dev] [PATCH] Adding option to IEEE 802.11 to ignore wep bit with IV

2007-04-09 Thread Stig Bjørlykke
Hi. This patch adds an option to IEEE 802.11 to ignore the wep bit with IV, as mentioned in http://www.wireshark.org/lists/wireshark-dev/ 200704/msg00021.html I also fixed a bug where the packet is dissected different in the Packet List with and without "Colorize Packet List" (actually whe

Re: [Wireshark-dev] Dissecting sua info string

2007-04-09 Thread Michael Tuexen
Hi Bhavani, not sure what you want to achieve. The parameter is defined as a character string and is displayed as a string. So you can not analyze more. And it should be pretty readable right now. From an SUA implementation point of view, you can not assume that the receiver does anything wi

[Wireshark-dev] How to avoid the OS X error dyld: Symbol not found: __cg_jpeg_resync_to_restart

2007-04-09 Thread Stephen Fisher
I've found the fix for the MacOS X error below when running Wireshark from the build directory: -- dyld: Symbol not found: __cg_jpeg_resync_to_restart Referenced from: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO Expected

Re: [Wireshark-dev] Wireshark 0.99.5 "makerpm-package"problemsonRHEL3

2007-04-09 Thread Maynard, Chris
I think I've found out what's going wrong, and it doesn't appear to be specific to RHEL3. You obviously can't run "make rpm-package" until after both the autogen.sh and configure scripts are run in order to generate the Makefile in the first place. In my case, I run configure with lots of options

Re: [Wireshark-dev] Wireshark 0.99.5 "makerpm-package"problemsonRHEL3

2007-04-09 Thread Maynard, Chris
I figured out the problem with the /usr/lib conflict. The default location specified by "prefix" in packaging/rpm/SPECS/wireshark.spec.in is set to /usr, rather than to /usr/local. Changing it allowed me to create an .rpm and install it without conflicting with the wiretap library already install

[Wireshark-dev] Controlling the location of plugins directory

2007-04-09 Thread Bob Doolittle
Hi, Can wireshark handle env-variable control of the location of the plugins directory (similar to LD_LIBRARY_PATH etc)? I haven't found it, and desperately need it. I work in an environment where I commonly use several platforms, including Solaris sparc and x86 as well as various Linux distros.

Re: [Wireshark-dev] Wireshark 0.99.5 "makerpm-package"problemsonRHEL3

2007-04-09 Thread Thomas Anders
Maynard, Chris wrote: > I can't create an svn diff at the moment (proxy troubles), but consider > this one-line change to the file, packaging/rpm/SPECS/wireshark.spec.in: > > =[FROM]= > %define prefix /usr > > =[TO]= > %define prefix /usr/local I'm not convinced this change s

[Wireshark-dev] A Study on Free/Open Source Software Defect Management

2007-04-09 Thread Anu Gupta DCSA
Dear Sir/Madam, I am really thankful to Free/Open Source Software development community for their overwhelming response to the survey on practices and problems of defect management in Free/Open Source Software projects. If you have not participated ealier, you may spend a few minutes now too.