Wireshark · Ethereal-dev: Re: [ethereal-dev] Probable serious bug in ethereal 0.7.8 and 0.7.9 under Linux

[Aleksander Adamowski <olo@xxxxxxxxxxxxxxxxxxxxxxxxxx>]

Guy Harris wrote:
> (Sigh, a simple reply bounced with:
>         <olo@xxxxxxxxxxxxxxxxxxxxxxxxxx>:
>         No host named karpaty.arka.altkom.com.pl. (#5.1.2)
> 
> so I'm resending, using Aleksander's address from his signature.  He
> should complain to whoever manages mail at Altkom Akademia about this -

actally, our DNS's UTP cable got wronged...

> > I'd like to point out that I'm just a Linux newbie and I'm not able to
> > find the problem's cause here on my own, but I'm sure that it's something
> > that changed in Ethereal itself, between versions 0.7.7 and 0.7.8,
> > because 0.7.7 works fine.
> 
> Have you built 0.7.7 with the *exact same version of the "libpcap"
> library* as the one with which 0.7.9 was built?  If not, it could be a

Yes, it was the same version in both cases, I didn't touch the libpcap
at all. It's the original package that was within my Mandrake 6.1
distro. It seems that it's not libpcap's fault.

> "libpcap" difference - which, again, strikes me as far more likely.  If

Yes, it seemed likely to me too, but I didn't change libpcap between
builds of 0.7.7 and 0.7.9.

> the 0.7.7 Ethereal were built with a version of "libpcap" that contained
> the patch to make timeouts work, but the 0.7.8 and 0.7.9 ones were built
> with a vanilla "libpcap" not containing that patch, that would produce
> the behavior you see.
> What happens if you apply the attached patch to the "libpcap" source?

Currently I'm a bit too busy to do that, and I'm still a newbie, but
I'll try ASAP.

By the way, maybe that has been fixed, but Ethereal 0.7.7 segfaults when
I select a "LPD response" packet in the packet list. Looks like some bug
in the LPD packet disassembler. It happens with every LPD response
packet. I didn't catch any other lpd packets though.

----
Aleksander Adamowski
	the_olo@xxxxxxxxxxxxx