Re: [Wireshark-dev] U3 package fails to install
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 from: http://prdownloads.sourceforge.net/wireshark/wireshark-0.99.5.u3p install OK? Yes it does, without an icon as has been discussed previously. When I run the U3 add programs applet, it reports: U3 Launchpad failed to install U3 program, due to a possible error in the program package. Try downloading and installing the program again. If the problem persists, contact the program software vendor. The version of U3 Launchpad in use is 1.4.0.2 I'm also unable to install either a home built version from the latest SVN (20933) or the buildbot version of the same. I have seen this sort of error when the manifest.u3i file is corrupt. Have a look at the file in packaging/u3/win32/manifest - or extract it from the u3p using a zip tool. Does it look OK? The one in my working copy looks fine, it seems to be well formed XML, I assume the actual content is correct. Hi Graham, I know its been over a month, but I tried to build a U3 package myself and ran into the same error. I fixed it by going into the packaging\u3\win32 directory once the u3p file is complete, from there I created my own archive. I added the data, device, host and manifest directories to a zip archive with zero compression. Then I renamed that zip archive to the desired u3p filename. The U3 program took the handmade archive with no problems. I think Graeme L checked in a fix, as I subsequently did manage to build a u3p package. I haven't tried for a month or so though. -- Regards, Graham Bloice ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
[Wireshark-dev] Dissecting sua info string
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 message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] Questions about IEEE 802.11 dissector
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 headers. There might be a driver bug wherein the SSI type isn't big-endian, although with older adapters that'd arguably be somewhat stoopid, given that Which driver is used to capture wireless traffic? Builtin in OSX, or pcap? I really don't know where to start looking for this... -- Stig Bjørlykke ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
[Wireshark-dev] [PATCH] Adding option to IEEE 802.11 to ignore wep bit with IV
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 when dissecting with and without tree). Try toggling Colorize Packet List with my previous posted ieee80211-wep.pcap without this patch to see the bug. The patch is tested on OSX. -- Stig Bjørlykke packet-ieee80211.patch.gz Description: GNU Zip compressed data ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] Dissecting sua info string
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 with it. Best regards Michael On Apr 9, 2007, at 1:17 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: 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 message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] Wireshark 0.99.5 makerpm-packageproblemsonRHEL3
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, including --disable-gtk2. If you then run make, it works fine ... compiling Wireshark w/out gtk2. However, if you then run make rpm-package, all the sources are copied to wireshark-0.99.5/packaging/rpm/BUILD/wireshark-0.99.5/, then from what I gather, autogen.sh and configure are then re-run automatically, but, this time configure is run WITHOUT the options originally selected before. So that's why the rpm-package fails because RHEL3 does not have gtk2.4, and even though I tried to disable it, the configure options are not used. To work around that problem, I manually edited configure.in to set all the options I wanted, then re-ran autogen.sh and configure, then make rpm-package. This successfully built an rpm without gtk2 (or any of the other packages I didn't need). Unfortunately, I ran into another problem when trying to install the rpm: =[START]= rpm -ivh wireshark-0.99.5-2.i386.rpm Preparing...### [100%] file /usr/lib/libwiretap.so.0.0.1 from install of wireshark-0.99.5-2 conflicts with file from package ethereal-0.99.0-EL3.2 =[END]= I know I can force the installation, but why should there be a conflict at all? The wiretap used with ethereal-0.99.0 is installed in /usr/lib/, but the wiretap used with Wireshark should be installing in /usr/local/lib/. The default installation is /usr/local/lib, and I've verified that in both the Wireshark and wiretap configure scripts. Any ideas on this one? And rather than having to manually edit configure.in in order to create an .rpm with your desired packages optional components, is there a better way to do this? - Chris (I have updated bug 1509 in the bugzilla database to reflect these latest findings.) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maynard, Chris Sent: Saturday, March 31, 2007 1:48 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Wireshark 0.99.5 makerpm-packageproblemsonRHEL3 I just noticed my post and that somewhere in transition, what I typed was not exactly what was posted. The scripts are obviously run from the current directory ./, not from the upper-level ../ directory. The buildrpm.sh script I actually run is attached. - Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maynard, Chris Sent: Friday, March 30, 2007 5:23 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Wireshark 0.99.5 make rpm-packageproblemsonRHEL3 Right. I run a buildrpm.sh script that essentially encapsulates the following: .../autogen.sh .../conf.sh make clean make rpm-package The conf.sh script is attached. It disables almost everything (including gtk2), again as I'm primarily only interested in tshark for this particular rpm. I attached the output of the configuration in a prior post, but that is attached again here as well. Anyway, I still get the undefined reference failure, so my feeling is that this function is incorrectly being used in all cases and not taking into account whether gtk2 is actually enabled or not. But even if it is enabled, shouldn't there be a check somewhere for 2.4 or greater? Regardless, for my purposes, I'd be happy to get it working with gtk1 only, but as I said, it still fails with the same error. Regards, Chris P.S. In case the conf.sh script gets mangled in transit for some reason, here's the basic contents: /configure --disable-gtk2 --enable-wireshark=no --enable-tshark=yes --enable-editcap=yes --enable-dumpcap=yes --enable-capinfos=no --enable-mergecap=yes --enable-text2pcap=no --enable-idl2wrs=no --enable-dftest=no --enable-randpkt=no --enable-ipv6=no --enable-threads=no --without-ssl --without-net-snmp --without-adns --without-lua --without-portaudio --without-pcre --without-krb5 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Fisher Sent: Friday, March 30, 2007 5:00 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Wireshark 0.99.5 make rpm-package problemsonRHEL3 On Fri, Mar 30, 2007 at 08:23:08PM +0200, Ulf Lamping wrote: You may try GTK 1.2 which should still work. Don't ask me how to do (configure) this, I'm currently Win32 only ;-) /configure --disable-gtk2 :) Steve - This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, retention, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the
[Wireshark-dev] Controlling the location of plugins directory
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. So I need to build architecture-dependent versions of a plugin, and currently can't find a way to deploy this in an easy fashion in the $HOME directory. I've arranged my shell rc files so that I set my executable $PATH to include a platform-dependent $HOME/bin type of directory during login[1]. It would be reasonable to do something similar for some variable that specified my wireshark plugin directory for the current platform. Thanks, Bob [1] Specifically, it adds $HOME/bin/$(uname -s).$(uname -p), e.g. $HOME/bin/SunOS.sparc or $HOME/bin/Linux.i386 ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] Wireshark 0.99.5 makerpm-packageproblemsonRHEL3
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 should be committed. A prefix of /usr is perfectly reasonable for a (public) wireshark rpm package per most RPM Packaging Guidelines, no matter if it matches the default configure prefix or not. +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
