Re: Getting error ioctl SIOCSARP: Network is unreachable

Nancy Lee <nancy@watsun.cc.columbia.edu> Fri, 17 May 1996 18:33 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa21650; 17 May 96 14:33 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa21646; 17 May 96 14:33 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa13960; 17 May 96 14:33 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA25071; Fri, 17 May 1996 14:30:02 -0400
Date: Fri, 17 May 1996 14:30:02 -0400
Message-Id: <CMM.0.90.4.832354789.nancy@pongo.cc.columbia.edu>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
X-Orig-Sender: dhcp-v4@bucknell.edu
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Nancy Lee <nancy@watsun.cc.columbia.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Getting error ioctl SIOCSARP: Network is unreachable
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4

>Recently, I've ported dhcp-3.3.7 but the same problem remains. This
>server gives the msg

>ioctl SIOCSARP: Operation not supported on socket

I also got these messages.  Chris Davis suggested I recompile with cc
instead of gcc and the messages went away.  He couldn't explain why
cc worked and gcc didn't.  But in his next release he is going to
compensate for this.

                  Nancy