IETF Logo Mail Archive

Re: Getting error ioctl SIOCSARP: Network is unreachable

boris@hal2000.law.columbia.edu Mon, 20 May 1996 15:45 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16511; 20 May 96 11:45 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa16507; 20 May 96 11:45 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa08700; 20 May 96 11:45 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA15895; Mon, 20 May 1996 11:42:07 -0400
Date: Mon, 20 May 1996 11:42:07 -0400
Message-Id: <9605201534.AA11905@hal2000.law.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: boris@hal2000.law.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

Nancy:

Did you get warning messages like "illegal pointer combination" and even
syntax errors (some source files from snmplib directory) while compiling
with cc instead of gcc?
I guess the code written especially for gcc.

Boris

> >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
>

v2.8.7 | Report a Bug | By Email