Re: [tcpdump-workers] Release schedule?

On Apr 1, 2010, at 10:24 PM, Peter Volkov wrote: > Hi. It looks like tests directory is missed tcpdump-4.1.0.tar.gz. Do you > suggest to avoid running tests for tcpdump or was tarball corrupted > somehow? The Makefile didn't include the tests in the list of files to distribute. I've changed Ma

Re: [tcpdump-workers] Fix ./configure --without-chroot for tcpdump

On Apr 1, 2010, at 10:44 PM, Peter Volkov wrote: > ./configure --without-chroot will configure tcpdump with "no" as the > value of chroot directory and cause tcpdump to fail with: > > tcpdump: Couldn't chroot/chdir to 'no': No such file or directory > > Patch in attachment fixes this issue. Ple

Re: [tcpdump-workers] Release schedule?

Hi. It looks like tests directory is missed tcpdump-4.1.0.tar.gz. Do you suggest to avoid running tests for tcpdump or was tarball corrupted somehow? Thanks. -- Peter. - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.

[tcpdump-workers] Fix ./configure --without-chroot for tcpdump

./configure --without-chroot will configure tcpdump with "no" as the value of chroot directory and cause tcpdump to fail with: tcpdump: Couldn't chroot/chdir to 'no': No such file or directory Patch in attachment fixes this issue. Please apply. -- Peter. >From 7ec07e4815965dd31b85e56ac823249bfb

Re: [tcpdump-workers] Raw USB capturing with libpcap 1.1?

On Apr 1, 2010, at 1:04 PM, Chris Maynard wrote: > I was under the impression that libpcap allowed one to capture raw USB traffic > (See http://wiki.wireshark.org/CaptureSetup/USB). However, with libpcap 1.1, > this doesn't seem to work as I get an error from pcap_compile() with > pcap_geterr(

[tcpdump-workers] Raw USB capturing with libpcap 1.1?

I was under the impression that libpcap allowed one to capture raw USB traffic (See http://wiki.wireshark.org/CaptureSetup/USB). However, with libpcap 1.1, this doesn't seem to work as I get an error from pcap_compile() with pcap_geterr() returning, "USB link-layer type filtering not implemented

Re: [tcpdump-workers] Release schedule?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > "Chris" == Chris Morgan writes: Chris> I've got a couple of Oss projects that I release and ended up Chris> writing some bash scripts that I keep in a subdir of the code Chris> repo that build source and release packages given a ver

Re: [tcpdump-workers] Release schedule?

I've got a couple of Oss projects that I release and ended up writing some bash scripts that I keep in a subdir of the code repo that build source and release packages given a version number. They even use git log to build the release notes from a tag. I can share if interested since I had the sam

Re: [tcpdump-workers] Release schedule?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > "Darren" == Darren Reed writes: >> >> The links on http://www.tcpdump.org are broken. Guy> The tarballs are libpcap-1.1.tar.gz and tcpdump-4.1.tar.gz, Guy> rather than libpcap-1.1.0.tar.gz and tcpdump-4.1.0.tar.gz. Are Guy> we

Re: [tcpdump-workers] Problem with libpcap

Guy Harris alum.mit.edu> writes: > Odd - it compiled on my Ubuntu 9.10 virtual machine, with a 2.6.31-19-generic kernel. What kernel does your > RHEL5 system have? "uname -a" reveals: Linux harley 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:14 EST 2007 x86_64 x86_64 x86_64 GNU/Linux - This is the tc

Re: [tcpdump-workers] Problem with libpcap

On Mar 31, 2010, at 1:10 PM, Chris Maynard wrote: > I encountered the same problem trying to compile the latest libpcap-1.1 > sources > on a RHEL5 system. Odd - it compiled on my Ubuntu 9.10 virtual machine, with a 2.6.31-19-generic kernel. What kernel does your RHEL5 system have? > I fixed

Re: [tcpdump-workers] Release schedule?

On 03/31/10 11:39, Michael Richardson wrote: "Guy" == Guy Harris writes: Guy> On Mar 30, 2010, at 1:55 PM, Wesley Shields wrote: >> The links on http://www.tcpdump.org are broken. Guy> The tarballs are libpcap-1.1.tar.gz and tcpdump-4.1.tar.gz, Guy> rather than li