From owner-freebsd-current Sun Aug 13 14:30:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id OAA05549 for current-outgoing; Sun, 13 Aug 1995 14:30:21 -0700 Received: from Wit401402.student.utwente.nl (Wit401402.student.utwente.nl [130.89.236.162]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id OAA05524 ; Sun, 13 Aug 1995 14:30:14 -0700 Received: (from alain@localhost) by Wit401402.student.utwente.nl (8.6.11/8.6.9) id XAA00537; Sun, 13 Aug 1995 23:29:30 +0200 Date: Sun, 13 Aug 1995 23:29:29 +0200 (MET DST) From: Alain Kalker Reply-To: A.C.P.M.Kalker@student.utwente.nl To: current@FreeBSD.org, Joerg Wunsch cc: FreeBSD-current users Subject: ifconfig(8) / route(8): File exists: Routing problem? In-Reply-To: <199508131944.VAA02331@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Sun, 13 Aug 1995, J Wunsch wrote: > Another problem... > > ... every invocation of ifconfig from the sliplogin > script causes > > ioctl(SIOCAIFADDR): File exists > > Very useful :-/ The `File exists' looks like it's from the routing > code. Sounds familliar to me... I have been running FreeBSD-current (last 'make world' Aug 9) with few problems when suddenly it started acting weird during startup: -- part of startup messages -- ed1: flags=8863 mtu 1500 inet 130.89.236.162 netmask 0xffff0000 broadcast 130.89.255.255 ether b4:66:c8:96:98:81 lo0: flags=8009 mtu 16384 inet 127.0.0.1 netmask 0xff000000 add net default: gateway 130.89.220.1 add net 224.0.0.0: gateway Wit401402 add host Wit401402: gateway localhost: File exists starting routing daemons: routed. -- end -- I tried several times to delete then re-add the routes manually, which _sometimes_ succeeded, but mostly led to the same error message... When I was trying to delete and add the local route repeatedly the kernel suddenly panicked and shot me into a reboot... Anybody have any idea what's wrong here? Alain.