From owner-freebsd-hackers Tue Nov 26 14:25:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA01198 for hackers-outgoing; Tue, 26 Nov 1996 14:25:37 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA01182 for ; Tue, 26 Nov 1996 14:25:29 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id NAA13714 for ; Tue, 26 Nov 1996 13:24:51 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA24839; Tue, 26 Nov 1996 22:22:50 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA15958; Tue, 26 Nov 1996 22:22:49 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id WAA14440; Tue, 26 Nov 1996 22:18:35 +0100 (MET) From: J Wunsch Message-Id: <199611262118.WAA14440@uriah.heep.sax.de> Subject: Re: Inappropriate/inconsistent EEXIST from ioctl(sockfd, SIOCAIFADDR,...) To: freebsd-hackers@FreeBSD.org (FreeBSD hackers) Date: Tue, 26 Nov 1996 22:18:35 +0100 (MET) Cc: john@starfire.mn.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199611261423.IAA02686@starfire.mn.org> from "john@starfire.mn.org" at "Nov 26, 96 08:23:01 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk 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. ;-)