From owner-freebsd-questions Mon Aug 4 16:36:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA05613 for questions-outgoing; Mon, 4 Aug 1997 16:36:21 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA05606 for ; Mon, 4 Aug 1997 16:36:17 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id JAA24708; Tue, 5 Aug 1997 09:06:03 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id JAA18709; Tue, 5 Aug 1997 09:06:02 +0930 (CST) Message-Id: <199708042336.JAA18709@freebie.lemis.com> Subject: Re: ifconfig: ioctl (SIOCAIFADDR): File exists In-Reply-To: <199708040650.CAA02850@radford.i-plus.net> from Troy Settle at "Aug 4, 97 02:48:53 am" To: rewt@i-Plus.net (Troy Settle) Date: Tue, 5 Aug 1997 09:06:02 +0930 (CST) Cc: questions@FreeBSD.ORG, ktsin@acm.org Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Troy Settle writes: > From: Sin Key Teck >> Every time I add an alias to the fxp interface I would get the following >> message: >> >> ifconfig: ioctl (SIOCAIFADDR): File exists >> >> What does it mean? How to get rid of it? > > How are you adding the alias? what netmask are you using? should be > 0xffffffff ('255.255.255.255' if you can't read hex :) Did you try this solution? It doesn't work: + # ifconfig tun0 freebie 139.130.136.129 netmask 255.255.255.255 alias + ifconfig: ioctl (SIOCAIFADDR): File exists In fact, it works anyway: + # ifconfig tun0 + tun0: flags=8151 mtu 1500 + inet 139.130.136.133 --> 139.130.136.129 netmask 0xffffffff + inet 192.109.197.137 --> 139.130.136.129 netmask 0xffffffff I think this is a bug. Greg