I'll have to check on a system where glibc was not updated since install.
I get the same errors on a Slackware box with an unupgraded libc version 2.3.4.
Best regards,
Michal
-
This is the tcpdump-workers list.
Visit https://lists.sandelman.ca/ to unsubscribe.
CVS log entries from 02.10.2005 (Sun) 09:06:57 - 03.10.2005 (Mon) 09:07:18 GMT
=
Summary by authors
=
Author: mcr
File: tcpdump/tests/print-flags.puu; Revisions: 1.1.2.1
File:
-BEGIN PGP SIGNED MESSAGE-
tcpdump 3.9.4 and libpcap 0.9.4 have been tagged, tar'ed, signed and
put on the web site.
lox-[/tcpdump/htdocs/release] mcr 824 %md5 *9.4.tar.gz
MD5 (libpcap-0.9.4.tar.gz) = 79025766e8027df154cb1f32de8a7974
MD5 (tcpdump-3.9.4.tar.gz) =
I'm using libnet 1.1.1 and pcaplib 0.8.3 (I believe).
Linux 2.4.20 / 2.6.11 (and later, FreeBSD 5.2).
GCC 3.3
Apologies if this is too off-topic an application for this list.
I'm attempting to use libnet and pcap together to write a client using raw
sockets so that I can gain explicit control
I'm failing at connection establishment. I can squirt the packet out using
libnet and get a reply using pcap, but the connection-initiating TCP seems
to be generating a RST on my behalf before I can transmit the third packet
of the handshake.
[ ... ]
The libnet code to transmit packets
- Original Message -
From: Guy Harris [EMAIL PROTECTED]
To: tcpdump-workers@lists.tcpdump.org
Sent: Monday, October 03, 2005 6:49 PM
Subject: Re: [tcpdump-workers] pcap: prob w/libnet making raw socket client
rh wrote:
I'm using libnet 1.1.1 and pcaplib 0.8.3 (I believe).
Linux
rh wrote:
Sounds like it's unavoidable. libnet and libpcap seem like they'd
complement each other so well.
libpcap is a low-level library, in that
1) it works at the link layer
and
2) it doesn't deal with dissecting or constructing packets.
As of 0.9.x, it *does* deal