From: creitzel@mediaone.net
To: gnu-win32@cygnus.com
Subject: Re: icmp again..
Date: Tue, 21 Oct 1997 08:54:00 -0000 [thread overview]
Message-ID: <19971021155430.AAA21870@creitzel.ne.highway1.com> (raw)
Check out Chris Becke's page on icmp programing at
http://www.dbn.lia.net/chris/icmp.html . He has hacked the add-on DLL
Windows uses to handle ICMP packets. The page has a .ZIP file containing
source and a decent discussion of what's involved.
Cheers,
Charlie
creitzel@mediaone.net
At 08:39 AM 10/20/97 -1000, you wrote:
>> Hello.
>>
>> I wonder if someone can tell me how to use ICMP with cygnus wunderful
gcc.exe.
>
>You can use winsock functions in the normal (socket) way to write
>icmp packets out. Unfortunately the winsock functions are
>somewhat of a hack for reading back packets. It appears that
>you only get packets back in a recv that are a response to
>a ping icmp packet you sent out. In other words, it's almost
>completely unusable for reading icmps.
>
>> btw, im trying to port the icmpinfo-1.11, which is an excellent
>> icmp-logger. If someone already ported it (or simular) please let me know.
>
>Winsock is incapable of reading arbitrary icmps so you would
>need some other way to read icmps to make an icmp logger.
>
>> IRL : Martin Svenningsson - Helsingborg, SWEDEN
>> MAIL : emmess@triton.tripnet.se - finger for PGP
>-
>For help on using this list (especially unsubscribing), send a message to
>"gnu-win32-request@cygnus.com" with one line of text: "help".
>
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1997-10-21 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-21 8:54 creitzel [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-10-17 8:23 Martin Svenningsson
1997-10-20 14:39 ` Tim Newsham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19971021155430.AAA21870@creitzel.ne.highway1.com \
--to=creitzel@mediaone.net \
--cc=gnu-win32@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).