From owner-freebsd-bugs  Tue Oct 17 12:00:03 1995
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id MAA03720
          for bugs-outgoing; Tue, 17 Oct 1995 12:00:03 -0700
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id MAA03712
          ; Tue, 17 Oct 1995 12:00:02 -0700
Resent-Date: Tue, 17 Oct 1995 12:00:02 -0700
Resent-Message-Id: <199510171900.MAA03712@freefall.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, tech@Ieunet.ie
Received: from pop.Ieunet.ie (zadok.Ieunet.ie [192.111.39.34])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id LAA03429
          for <FreeBSD-gnats-submit@freebsd.org>; Tue, 17 Oct 1995 11:51:45 -0700
Received: by pop.Ieunet.ie (Smail3.1.29.1 #2)
	id m0t5H6d-000IFbC; Tue, 17 Oct 95 19:51 WET DST
Message-Id: <m0t5H6d-000IFbC@pop.Ieunet.ie>
Date: Tue, 17 Oct 95 19:51 WET DST
From: aj@Ieunet.ie (Alan Judge)
Reply-To: tech@Ieunet.ie
To: FreeBSD-gnats-submit@freebsd.org
Cc: tech@Ieunet.ie
X-Send-Pr-Version: 3.2
Subject: kern/785: 2.0.5-950622-SNAP Various ifconfig alias problems
Sender: owner-bugs@freebsd.org
Precedence: bulk


>Number:         785
>Category:       kern
>Synopsis:       Various ifconfig alias problems
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 17 12:00:01 PDT 1995
>Last-Modified:
>Originator:     Alan Judge
>Organization:
Ieunet Ltd
>Release:        FreeBSD 2.0-BUILT-19950612 i386
>Environment:

	2.0.5-950622-SNAP running busy web server.  10 virtual interfaces
	running using ifconfig alias.

>Description:

	Several, possibly related problems:
	      - ifconfig ed0 xxx.yyy.zzz.123 alias
		returns error:
			ifconfig: ioctl (SIOCAIFADDR): File exists

		If run a second time, there is no error and everything seems
		to be OK.

	      - In order for the new address to be reachable from the
		host itself, you need to do
			ifconfig lo0 xxx.yyy.zzz.123 alias
		as well.  I don't know if this is intentional, but
		it's certainly necessary.

		This usually results in a kernel error message like:
			arp_rtrequest: bad gateway value
			rtinit: wrong ifa (0xf06b2600) was (0xf0746d80)

		And again sometimes must be redone.

	      - Some of this may be related to the fact that the
		presence of an arp entry for the host being aliased
		(even an incomplete one) seems to break everything.
		So I've been doing arp -d first.

>How-To-Repeat:

>Fix:
	
	Unknown.  Current workaround is to do:
		$i=xxx.yyy.zzz.aaa
		arp -d $i > /dev/null 2>&1
		ifconfig ed0 $i alias > /dev/null 2>&1
		ifconfig ed0 $i alias
		ifconfig lo0 $i alias > /dev/null 2>&1
		ifconfig lo0 $i alias
>Audit-Trail:
>Unformatted: