IETF Logo Mail Archive

Re: Getting error ioctl SIOCSARP: Network is unreachable

"Philip A. Prindeville" <philipp@erols.com> Fri, 17 May 1996 20:42 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa25649; 17 May 96 16:42 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa25642; 17 May 96 16:42 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa16116; 17 May 96 16:42 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA03434; Fri, 17 May 1996 16:33:37 -0400
Date: Fri, 17 May 1996 16:33:37 -0400
Message-Id: <199605171936.PAA00518@erols.erols.com>
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: "Philip A. Prindeville" <philipp@erols.com>
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.

Just a shot in the dark...  I haven't looked at the sources.  Make
sure you are passing the address of a struct and not the struct
itself to ioctl().  Some compilers handle passing structs differently.
Some create a copy, and then pass the address of the copy when passing
structs by value.  Some just push the whole struct on the stack.

-Philip

v2.8.7 | Report a Bug | By Email