Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 6 Jul 2005 10:14:52 -0500 (CDT) From: "L. D. Marks" X-X-Sender: ldm AT risc4 DOT numis DOT northwestern DOT edu DOT edu Reply-To: "L. D. Marks" To: cygwin AT cygwin DOT com Subject: Application sending Router Solicitation packet Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I've seen a couple of times a fortran program (g77 compilation under cygwin) attempting to send (according to my Sygate Firewall) an ICMP Type 10 (Router Solicitation) packet. The latest case wants to send to 224.0.0.2 -- I did not keep a record of previous cases. The code contains no system calls (certainly nothing tcp or router related), is stable and has worked for years compiled on a range of systems. If I ignore what the firewall is saying I get another attempt, one from c:\cygwin\bin\sh.exe and another from another fortran code. 1) There are arrays going out of bounds (always possible) which is somehow triggering one of the cygwin dll's to send the signal. However, this should not happen with two different programs & sh.exe. 2) This is an internal bug somewhere in cygwin (I would not know where to look), perhaps X. 3) There is a conflict between cygwin dll's & sygate (I probably don't know what I'm talking about). I'd appreciate any suggestions. N.B., the program runs to completion without problem, so the Router Solicitation packet seems to be completely irrellevant. N.N.B., the information that the firewall gives is: File Version : File Description : C:\cygwin\bin\sh.exe File Path : C:\cygwin\bin\sh.exe Process ID : 0xB04 (Heximal) 2820 (Decimal) Connection origin : local initiated Protocol : ICMP Local Address : 10.0.0.18 ICMP Type : 10 (Router Solicitation) ICMP Code : 0 Remote Name : Remote Address : 224.0.0.2 Ethernet packet details: Ethernet II (Packet Length: 56) Destination: 01-00-5e-00-00-02 Source: 00-06-5b-31-85-14 Type: IP (0x0800) Internet Protocol Version: 4 Header Length: 20 bytes Flags: .0.. = Don't fragment: Not set ..0. = More fragments: Not set Fragment offset:0 Time to live: 64 Protocol: 0x1 (ICMP - Internet Control Message Protocol) Header checksum: 0xb3a2 (Correct) Source: 10.0.0.18 Destination: 224.0.0.2 Internet Control Message Protocol Type: 10 (Router Solicitation) Code: 0 Data (4 bytes) Binary dump of the packet: 0000: 01 00 5E 00 00 02 00 06 : 5B 31 85 14 08 00 45 00 | ..^.....[1....E. 0010: 00 1C EE 19 00 00 40 01 : A2 B3 0A 00 00 12 E0 00 | ......@......... 0020: 00 02 0A 00 F5 FF 00 00 : 00 00 82 B3 29 10 00 01 | ............)... 0030: 00 00 00 00 00 01 20 45 : | ...... E ----------------------------------------------- Laurence Marks Department of Materials Science and Engineering MSE Rm 2036 Cook Hall 2220 N Campus Drive Northwestern University Evanston, IL 60201, USA Tel: (847) 491-3996 Fax: (847) 491-7820 email: L - marks @ northwestern . edu http://www.numis.northwestern.edu ----------------------------------------------- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/