From owner-freebsd-net@FreeBSD.ORG  Sun Aug 30 02:14:28 2009
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id F363D106566B;
	Sun, 30 Aug 2009 02:14:27 +0000 (UTC)
	(envelope-from qing.li@bluecoat.com)
Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28])
	by mx1.freebsd.org (Postfix) with ESMTP id D644A8FC15;
	Sun, 30 Aug 2009 02:14:27 +0000 (UTC)
Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95])
	by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n7U2EQEU008222;
	Sat, 29 Aug 2009 19:14:27 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 29 Aug 2009 19:08:19 -0700
Message-ID: <B583FBF374231F4A89607B4D08578A4305277CDC@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <38B715CC-9C82-4D8D-97CC-134A9CB01A0C@lurchi.franken.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: routing message problem
Thread-Index: AcooECTrPp9whvmMQ+OaAD/RddsvTwBBoYKg
References: <BFC746D7-9E88-43AD-8320-96928633C532@lurchi.franken.de>
	<B583FBF374231F4A89607B4D08578A4305277931@bcs-mail03.internal.cacheflow.com>
	<38B715CC-9C82-4D8D-97CC-134A9CB01A0C@lurchi.franken.de>
From: "Li, Qing" <qing.li@bluecoat.com>
To: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
Cc: qingli@freebsd.org, "Bjoern A. Zeeb" <bz@freebsd.org>,
	Randall Stewart <rrs@lakerest.net>, net@freebsd.org
Subject: RE: routing message problem
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Aug 2009 02:14:28 -0000

Hi Michael,
>=20
> your patch fixes the issue.
> Will it find its way into 8.0?
> Will it find its way into 7.3?
>=20

Yes, the patch will make its way into 8.0 Release and 7.3, too.

Thanks,

-- Qing


>=20
> On Aug 28, 2009, at 7:24 PM, Li, Qing wrote:
>=20
> >>
> >> Dear all,
> >>
> >> via a bug report from Preethi I figured out that there are no
> >> RTM_NEWADDR
> >> routing messages generated when an IP address is added to an
> >> interface
> >> and there is already an address in the same network configured.
> >> This is a problem for the SCTP stack.
> >>
> >> To reproduce the problem you can
> >> sudo ifconfig em0 192.168.1.1
> >> sudo ifconfig em0 192.168.1.2 alias
> >>
> >> and use the attached problem. It will only show the first address
> >> being added. This problem applies to FreeBSD 9.0 CURRENT and 7.2
> >> RELEASE.
> >>
> >> Any idea how to fix the problem?
> >>
> >
> >
> >  Please try my patch (not the final version) at
> >
> > 	http://people.freebsd.org/~qingli/patch-8-28-rtmsg.diff
> >
> >
> >  I have tested it and seems to work as expected. You should
> >  get the notifications for both address insertion ("alias")
> >  and deletion ("-alias").
> >
> >  Let me know if it's to your satisfaction.
> >
> >  I found a couple of other issues while looking over the code.
> >
> >  1. in_scrubprefix() is called unnecessarily in 2 locations
> >  2. the loopback host route is not removed for an alias
> >
> >  On a related note, in.c can use some code cleanup. I think
> >  I will do that post 8.0 release.
> >
> >  Thanks,
> >
> >  -- Qing
> >
> >