delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2001/03/14/10:07:14

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Subject: protocol parameter in socket call.
To: cygwin AT cygwin DOT com
X-Mailer: Lotus Notes Release 5.0.6 December 14, 2000
Message-ID: <OFBF27A266.6A4377D5-ON85256A0F.0052349D@tavve.com>
From: Matt DOT Brozowski AT tavve DOT com
Date: Wed, 14 Mar 2001 10:12:05 -0500
X-MIMETrack: Serialize by Router on hercules/Tavve(Release 5.0.6 |December 14, 2000) at
03/14/2001 10:12:14 AM
MIME-Version: 1.0

I've been trying to port a ping application to cygwin that works by opening
a RAW IP Socket and passing IPPROTO_ICMP (1) as the protocol parameter and
then constructing ICMP Echo packets and sending them to the destination
host.  (In other words, The usual way of pinging.)  While this application
works just find on , AIX, Solaris, HPUX and Linux it is NOT working using
Cygwin.  Using tcpdump ( a packet sniffer ) on Linux I found out that
packets where getting sent with a protocol number of 0 rather then
IPPROTO_ICMP (1).  Looking through the Cygwin sources I found that the
cygwin_socket call takes the protocol parameter (3rd parameter) but does
NOT pass it to the windows version of the socket call.  Instead the call is
hardcoded to take a zero (0).  Does anyone know if this is intentional?

Matt Brozowski
Tavve Software Company


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019