Date: Tue, 26 Nov 1996 22:18:35 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-hackers@FreeBSD.org (FreeBSD hackers) Cc: john@starfire.mn.org Subject: Re: Inappropriate/inconsistent EEXIST from ioctl(sockfd, SIOCAIFADDR,...) Message-ID: <199611262118.WAA14440@uriah.heep.sax.de> In-Reply-To: <199611261423.IAA02686@starfire.mn.org> from "john@starfire.mn.org" at "Nov 26, 96 08:23:01 am"
next in thread | previous in thread | raw e-mail | index | archive | help
As john@starfire.mn.org wrote: (Inconsistency: the network code has `recycled' a bunch of errno's, giving them a different meaning. I always thought that this has been a very silly idea, given the frequent use of utilities like perror(). Wrt. routing, EEXIST basically means ``This route does already exist.'') > Then, > for reasons I have not been able to nail down, after several cycles of > connecting and disconnecting (sometimes as few as two, sometimes several) > PPPD will start getting EEXIST from the ioctl call mentioned above. > I have been working with ppp-2.3b3. My system is largely 2.1-R, but I > have gotten some significant networking components from 2.1.5-R,... Are you sure you haven't missed /sys/net/route.c? I remember that problems like you're describing have been very `popular' way back, in particular (but not only) when proxarp was also in use. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611262118.WAA14440>