From: hyung@twg.com (Henry Yung (The Last In Line))
Subject: Re: icmp_input() Error Message
Keywords: WIN/TCP
Reply-To: hyung@twg.com
Organization: The Wollongong Group, West Coast Operations
Date: Wed, 13 Jan 1993 01:01:15 GMT


In article <657@msd.measurex.com>, bobml@msd.measurex.com (Bob LaGesse) writes:
|>Path: twg.com!eco.twg.com!uunet!mxmsd!msd.measurex.com!bobml
|>From: bobml@msd.measurex.com (Bob LaGesse)
|>Newsgroups: vmsnet.networks.tcp-ip.wintcp
|>Subject: icmp_input() Error Message
|>Keywords: WIN/TCP
|>Message-ID: <657@msd.measurex.com>
|>Date: 6 Jan 93 22:07:04 GMT
|>Sender: news@msd.measurex.com
|>Organization: Measurex/MSD, Cincinnati, OH 45240, USA
|>Lines: 34
|>Nntp-Posting-Host: mxmsd.msd.measurex.com
|>
|>I know that this newsgroup is supposed to be for VMS but I believe that
|>these two problems may be platform independent.
|>I'm running WIN/TCP Release 4.1.3 under Interactive UNIX Version 2.0.2.
|>The ethernet cards which we're using are the Western Digital WD8013EP and
|>the 3Com 3C503-16; the problems described below happen on both cards.
|>
|>1)  We keep getting the following message on all of our UNIX PCs running
|>    WIN/TCP anywhere from 5 to 30 times a day:
|>
|>    [-1]: icmp_input() default: badtype 10, code 0
|>		- OR -
|>    [4294967295]: icmp_input() default: badtype 10, code 0
|>
|>    These just stared appearing within the last month.  We've been running this
|>    version of WIN/TCP for 6 months prior without this error.  Can anyone
|>    give more details as to what this message really means?  I do know that it
|>    is generated from within the "ip(7)" device driver.
|> 

Although I am no UNIX guru (or for that matter, not even a protocol person),
let me take a shot at this problem.  RFC 1256, ICMP Router Discovery Messages
specifies that an ICMP message with a type of 10 and a code of 0 is a
"ICMP Router Solicitation Message".  It is possible that the WIN/TCP
you are running on Interactive does not recognize the newer ICMP
message type specified by RFC 1256 (released in Sept/1991).  I believe
you have a host on your network that is sending this ICMP request
repeatedly.  Consequently, this "debug" message is displayed on your
console every time this ICMP message is received.

I believe there is a way for you to turn off icmp_printfs under
WIN/TCP for Streams.  I don't know much about WIN/TCP for Streams
but I suspect you may need to rebuild the TCP kernel on your PC
in order to eliminate this message.  Or perhaps there is a way
to patch the icmp_printfs variable in the WIN/TCP kernel for Streams.

Or you may want to set up a Sniffer and see where this ICMP message
is originated from and try to turn it off on the client side.

|>2)  I've been trying to execute the following with no success:
|>
|>    struct icmpstat is;
|>    ioctl(fd, IPIOC_GETICMPSTAT, &is);
|>
|>    It always fails with errno=EINVAL.  I've tried opening fd
|>    with "open("/dev/ip", O_RDWR, 0)" and "socket(AF_INET, ..., 0)"
|>    with the same negative results.  What gives here?
|>

Sorry, I don't have an answer for this one (yet).

|>Any help, pointers, tips, etc, would be greatly appreciated.
|>
|>------------------------------------------------------------------------
|>Domain: bobml@msd.measurex.com    Bob LaGesse, Senior Software Engineer
|>  UUCP: ...!uunet!mxmsd!bobml     Measurex/Management Systems Division
|> Voice: (513) 825-3931 X303       1280 Kemper Meadow Drive
|>   Fax: (513) 825-5393            Cincinnati, Ohio 45240, USA
|>

Hank

-------------------------------------------------------------------------- 
  __  __/  |      /    _____/  Henry Yung	Email: hyung@twg.com
     /     |     /    /        VMS Software Engineering
    /        /  /    / -- /    The Wollongong Group, Inc.
  _/       _/ _/   ______/     Voice: (415)962-7100 FAX: (415)969-5547