> Date: Sun, 3 Feb 2002 15:11:21 -0800 > From: Guy Harris <[EMAIL PROTECTED]> > Subject: Re: [tcpdump-workers] libpcap 0.7.1 & Linux 2.0.39 little tweak ;)
> [ ... ] > You might want to send patches as attachments; it appears your > mail program "helpfully" converted tabs to spaces, so the patch > didn't apply directly - sending them as attachments may make your > mail program leave them as is. OK, pine was probably trying to be userfriendly ;) > I've checked it into the main CVS branch and the x.7 CVS branch > (so that it should appear in the next 0.7.x release). Thanks ! > > I couldn't find anything in CVS about this, but did see a more similar > > one concerning an ARPHRD_FDDI (IIRC) which didn't exist in Linux 2.2.x > > but did in Linux 2.4.x ... It used a similar workaround... > No, ARPHRD_FDDI did exist at least as of 2.2.13 (the oldest > 2.2[.x]kernel whose sources I have handy); however, it didn't > exist in 2.0, so I put in a workaround for that. (It presumably > existed in later 2.0[.x] releases, as nobody's reported a problem > with it, as far as I know - but one might as well be prepared for > it anyway, and put in a workaround>) :) Well, the first problem with libpcap 0.7 versus 0.6 has surfaced for me, on Linux 2.0.39 sniffing ppp0 will make tcpdump crash (+core sometimes), giving a notice that it couldn't set SIOC*-flags back to their original value... After it has crashed once (note: it sets promisc *and* multicast on a ppp device !), libpcap will fail telling that it doesn't support the ppp-device... Sniffing on normal eth* devices still works. I'm guessing my problem might lie in the fact that I've upgraded my PPP support, in order to have working PtPP support for my ADSL connection... Libpcap 0.6 works without a hitch, in combination with tcpdump 3.6 ... Although I still see some weirdness when sniffing 'ippp'-devices (syncppp devices created by ISDN4Linux), especially with fragments... > There are some other workarounds for ARPHRD_ values that didn't exist in > all 2.2[.x] kernels, as well as some for ARPHRD_ values that didn't > exist until 2.4[.x], e.g. ARPHRD_IEEE802_TR (which the Token Ring > drivers started using in 2.4[.x], causing older libpcaps, including the > ones shipped with many Linux distributions, to stop supporting Token > Ring, grumble grumble), ARPHRD_IEEE80211, and ARPHRD_SIT. :) I think I'm spending the coming weekend tweaking similar stuff to get libpcap 0.7 and my PPP-setup working nicely... I'll also try and see, if I can boot a 'stock' 2.0.39 kernel, although the PPP API's haven't changed between 'my' 2.0.39 and stock... It's mostly GRE stuff... Well, it'll keep me off the streets ;) Regards, JP Velders - This is the TCPDUMP workers list. It is archived at http://www.tcpdump.org/lists/workers/index.html To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
