Re: libnet.dll under win2k

Herman Hsu <[email protected]>
Newsgroups gmane.comp.security.libnet
Message-ID <[email protected]>
In-Reply-To: <[email protected]>

Hi, Thanks for the prompt reply.

I'm still a novice at libnet, but I dont think there's anything wrong with the program (tcp1 or tcp2).  I've tested them under Linux, and their functions have been veried with Ethereal also.

However, I'm skeptical about the Libnet.dll and Libnet.lib that were generated from the libnet 1.1.1 source with my build environment.  I wonder if it has something to do with it:

Windows 2000 SP3
VC++ 6.0 SP5
WinPCAP 3.0 Binary
WinPCAP 3.0 Dev

Everything seems to compile/link right, just not sure why some things are not being called.  The interesting thing is that I do see an ARP request, so something IS being sent to the wire, just that it's not sending the rest of the TCP Packet.

This is the only Windows Dev. environment I have.  Are there any pre-compiled Libnet.dll and Libnet.lib available?  Would they help to diagnose my problem?


Thanks,
Herman


>Received: (qmail 22526 invoked from network); 11 Mar 2004 03:21:05 -0000
>Received: from outgoing3.securityfocus.com (205.206.231.27)
>  by mail.securityfocus.com with SMTP; 11 Mar 2004 03:21:05 -0000
>Received: from lists.securityfocus.com (lists.securityfocus.com [205.206.231.19])
>	by outgoing3.securityfocus.com (Postfix) with QMQP
>	id E48E6A330C; Wed, 10 Mar 2004 20:08:59 -0700 (MST)
>Mailing-List: contact [email protected]; run by ezmlm
>Precedence: bulk
>List-Id: <libnet.list-id.securityfocus.com>
>List-Post: <mailto:[email protected]>
>List-Help: <mailto:[email protected]>
>List-Unsubscribe: <mailto:[email protected]>
>List-Subscribe: <mailto:[email protected]>
>Delivered-To: mailing list [email protected]
>Delivered-To: moderator for [email protected]
>Received: (qmail 4148 invoked from network); 10 Mar 2004 16:59:29 -0000
>Message-Id: <[email protected]>
>Reply-To: <[email protected]>
>From: "Kirby Kuehl" <[email protected]>
>To: "'Herman Hsu'" <[email protected]>
>Cc: <[email protected]>
>Subject: RE: libnet.dll under win2k
>Date: Wed, 10 Mar 2004 15:13:36 -0800
>Organization: Cisco Systems, Inc.
>MIME-Version: 1.0
>Content-Type: text/plain;
>	charset="us-ascii"
>Content-Transfer-Encoding: 7bit
>X-Mailer: Microsoft Office Outlook, Build 11.0.5510
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>In-Reply-To: <[email protected]>
>Thread-Index: AcQG9APfAhURDeaYS6etUlKFmRtNRwAAP4Mw
>
> 
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Just tested tcp1.exe with VC++ .NET 2003 and XP and it works fine
>(verified with Ethereal).
>Set some breakpoints and let us know what is happening.
>- -Kirby 
>
>- -----Original Message-----
>From: Herman Hsu [mailto:[email protected]] 
>Sent: Wednesday, March 10, 2004 12:01 PM
>To: [email protected]
>Subject: libnet.dll under win2k
>
>
>
>Hi,  I'm trying to get libnet.dll to work under win2k.  I believe I
>followed the instructions precisely, but it still doesn't work. 
>Here's an overview of my setup:  Windows 2000 SP3 VC++ SP5 WinPCAP
>3.0 binary from http://winpcap.polito.it/ WinPCAP 3.0 dev pack from
>http://winpcap.polito.it/ MS SDK libnet 1.1.1 src from
>http://www.packetfactory.net/Projects/Libnet/  I got everything to
>compile, built Libnet.dll and Libnet.lib with no problems at all. 
>Now, I'm just trying to get it to run.  I compiled one of the sample
>progams: tcp2.  Everything compiles fine and runs with no error. 
>But, nothing is written to the wire.  Using a sniffer, all I see is a
>ARP request whenever I do something like: >tcp2 -s 192.168.10.9.456
>- -d 192.168.10.10.567 -p "hello"  I've also tried it under Linux and
>it works fine, but I need it to work under Windows.  I'm basically
>stuck at this moment.  Any suggestions???
>
>-----BEGIN PGP SIGNATURE-----
>Version: PGP 8.0.3
>
>iQA/AwUBQE+hIPJlWu/m+KZxEQIKdACfRnHIrj1HIpYLjzwjn0Eh1zQ3cp0AmwYx
>ZcZXpHHd+qSyKcKAYpXmXx6X
>=M8OB
>-----END PGP SIGNATURE-----
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.