Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 May 1997 08:30:18 +0200
From:      j@uriah.heep.sax.de (J Wunsch)
To:        freebsd-current@FreeBSD.ORG (FreeBSD-current users)
Subject:   Re: All zeros still recognized as broadcast??
Message-ID:  <19970521083018.CB14886@uriah.heep.sax.de>
In-Reply-To: <199705201443.KAA22975@khavrinen.lcs.mit.edu>; from Garrett Wollman on May 20, 1997 10:43:25 -0400
References:  <19970519170904.LV61260@uriah.heep.sax.de> <199705191619.MAA20016@khavrinen.lcs.mit.edu> <19970519183606.JC27358@uriah.heep.sax.de> <199705191656.MAA20128@khavrinen.lcs.mit.edu> <19970519192709.LI31727@uriah.heep.sax.de> <199705201443.KAA22975@khavrinen.lcs.mit.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
As Garrett Wollman wrote:

> > Anyway (and not only to Garrett), what's up with the ``File exists''
> > messages when configuring an interface?  They are benign as it seems
> > but annoying.
> 
> They are indicative of a particular sort of configuration error where
> you are attempting to add an interface address which is already in the
> routing table as belonging to someone else (or some other interface).

As i showed in my mails, there was just nothing in the routing table,
yet all my attempts to ifconfig an interface yield a ``File exists''.
(I wouldn't have asked otherwise, trust me. :) It is totally benign,
in that the correct routes are being added nevertheless.

Probably i need to CVS update again.

uriah # netstat -ran
Routing tables

Internet:
Destination        Gateway            Flags     Refs     Use     Netif Expire

uriah # netstat -rAn
Routing tables

Internet:
Address  Destination        Gateway            Flags     Refs     Use     Netif Expire
f076154c   (32) f0761534 : f0761564
f0761534 (root node)
f0761564 (root node)

uriah # ifconfig vx0 192.168.0.1

(OK)

uriah # ifconfig bppp0
bppp0: flags=2811<UP,POINTOPOINT,SIMPLEX,LINK1> mtu 1500
uriah # ifconfig bppp0 193.101.57.{162,161}
ifconfig: ioctl (SIOCAIFADDR): File exists

(Surprise)

I think it happens for all p2p interfaces only, never for ethernet-
type interfaces.  It regularly happens when setting up a SLIP
interface, that's where i noticed it first.

-- 
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?19970521083018.CB14886>