Re: [Wireshark-dev] Portability issue of capture files.

2006-09-21 Thread Stephen Fisher
On Thu, Sep 07, 2006 at 10:19:22AM +0200, Andreas Fink wrote: > Ok. so we spotted a real bug. is this one in libwiretap? I don't > think so as libwiretrap is the same as when I tried it before. I am experiencing a variation of this zlib problem on OS X. I first posted about the problem in Jul

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-07 Thread LEGO
On 9/7/06, Guy Harris <[EMAIL PROTECTED]> wrote: > Gak. Any idea what package installed its own private libz? It probably > shouldn't be doing that, unless it needs 1.2.3 or later and can't work > with earlier versions. Darwinports does use its own dependencies for a *lot* of things even if unne

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-07 Thread Guy Harris
LEGO wrote: > there's libz.1.2.3 in both /usr/lib and /opt/local/lib Gak. Any idea what package installed its own private libz? It probably shouldn't be doing that, unless it needs 1.2.3 or later and can't work with earlier versions. > as soon as I removed that in /opt/local/lib I solved the

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-07 Thread Andreas Fink
Oh thats interesting. I think my wireshark was built with the source of libz as well but really what whould have been needed was a export LDFLAGS -lz for most of the tools. I'm rebuilding it currently on a new MacPro. Will report if that fixes it too. On 07.09.2006, at 13:57, LEGO wrote: >

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-07 Thread LEGO
Found! there's libz.1.2.3 in both /usr/lib and /opt/local/lib as soon as I removed that in /opt/local/lib I solved the issue... diferent library same mis-bahaviour as I used to have with open-ssl "Solved" by [pociccio:~/src/trunk] lego% sudo mv /opt/local/lib/libz.1.2.3.dylib /opt/local/lib/=libz

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-07 Thread Guy Harris
Andreas Fink wrote: > I'm capturing data on a linux machine (fedora5) with tcpdump -s0 > -wdumpfile.cap. Transfer the file to the mac and try to open it with > wireshark. I get weird errors saying it couldnt open it because packet > size is bigger than 65k or something like that. Same is if I c

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-07 Thread Guy Harris
LEGO wrote: > I just tried to open some files with my intel > based minimac and they do not work... Where were the capture files created, and what application wrote them? > oddly enough capture works only > if you are seeing packets in real-time, if instead you try to capture > without it fails

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-07 Thread Jeff Morriss
Andreas Fink wrote: >>> >>> Most frequently that's due to using FTP and not setting binary mode. >>> Does the file's checksum change from machine to machine after copying it? > > no. iIuse scp to copy from machine to machine. Well, you know, had to ask. Just in case... :-) >> The issue here

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-07 Thread Andreas Fink
Most frequently that's due to using FTP and not setting binary mode.Does the file's checksum change from machine to machine after copying it?no.  iIuse scp to copy from machine to machine.The PCAP/Wiretap library is supposed to figure out the endianism of thehost where the file was generated automa

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-06 Thread LEGO
On 9/7/06, Jeff Morriss <[EMAIL PROTECTED]> wrote: > > > Andreas Fink wrote: > > I recently compiled wireshark under MacOS X 10.4.7 on a intel machine. > > This time I succeeded even with GTK+2 after fiddling with a lot of options. > > I'm preparing an installer for it for users without "fink" or "

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-06 Thread Jeff Morriss
Andreas Fink wrote: > I recently compiled wireshark under MacOS X 10.4.7 on a intel machine. > This time I succeeded even with GTK+2 after fiddling with a lot of options. > I'm preparing an installer for it for users without "fink" or "darwin > ports". > > But while using it, I find out a stra

Re: [Wireshark-dev] Portability issue of capture files.

2006-09-06 Thread LEGO
On 9/7/06, Andreas Fink <[EMAIL PROTECTED]> wrote: > > I recently compiled wireshark under MacOS X 10.4.7 on a intel machine. This > time I succeeded even with GTK+2 after fiddling with a lot of options. > I'm preparing an installer for it for users without "fink" or "darwin > ports". > > But while

[Wireshark-dev] Portability issue of capture files.

2006-09-06 Thread Andreas Fink
I recently compiled wireshark under MacOS X 10.4.7 on a intel machine. This time I succeeded even with GTK+2 after fiddling with a lot of options.I'm preparing an installer for it for users without "fink" or "darwin ports".But while using it, I find out a strange behaviour.I'm capturing data on a l