From owner-freebsd-bugs  Sat Oct 21  7:10:10 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 9B6D937B4D7
	for <freebsd-bugs@FreeBSD.org>; Sat, 21 Oct 2000 07:10:01 -0700 (PDT)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id HAA73349;
	Sat, 21 Oct 2000 07:10:01 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from yar.chem.msu.su (yar.chem.msu.ru [195.208.208.25])
	by hub.freebsd.org (Postfix) with ESMTP id 3601837B479
	for <FreeBSD-gnats-submit@freebsd.org>; Sat, 21 Oct 2000 07:02:13 -0700 (PDT)
Received: (from yar@localhost)
	by yar.chem.msu.su (8.11.0/8.11.0) id e9LDxqf00443;
	Sat, 21 Oct 2000 17:59:52 +0400 (MSD)
	(envelope-from yar)
Message-Id: <200010211359.e9LDxqf00443@yar.chem.msu.su>
Date: Sat, 21 Oct 2000 17:59:52 +0400 (MSD)
From: yar@comp.chem.msu.su
Reply-To: yar@comp.chem.msu.su
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.2
Subject: kern/22185: Identical IP addresses on two broadcast interfaces
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         22185
>Category:       kern
>Synopsis:       Identical IP addresses on two broadcast interfaces
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Oct 21 07:10:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     Yar Tikhiy
>Release:        FreeBSD 4.1-STABLE i386
>Organization:
Moscow State University
>Environment:

	The bug seems to exist in all branches.

>Description:

	It's possible to add two absolutely identical IP addresses
	to two different broadcast interfaces.

	I guess it would be possible to add different addresses from
	the same network, too.

	The problem arises from in_control()/in_ifinit() leaving the
	address installed even if adding the link-layer route fails.

>How-To-Repeat:

yar# ifconfig fxp0 10.1.1.1
yar# ifconfig fxp1 10.1.1.1
ifconfig: ioctl (SIOCAIFADDR): File exists
yar# ifconfig fxp0 
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 10.1.1.1 netmask 0xff000000 broadcast 10.255.255.255
        ether 00:d0:b7:60:63:da 
        media: autoselect (100baseTX) status: active
        supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UT
P <full-duplex> 10baseT/UTP
yar# ifconfig fxp1 
fxp1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 10.1.1.1 netmask 0xff000000 broadcast 10.255.255.255
        ether 00:a0:c9:66:67:4d 
        media: autoselect (100baseTX) status: active
        supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UT
P <full-duplex> 10baseT/UTP

>Fix:

	Maybe, the code should try to add the link layer route first,
	and assign the address to the interface only if adding
	the route succeeded?

>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message