From owner-freebsd-current@FreeBSD.ORG Wed Sep 10 14:48:30 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1E85AAFC for ; Wed, 10 Sep 2014 14:48:30 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id CFAC71D53 for ; Wed, 10 Sep 2014 14:48:29 +0000 (UTC) Received: from [192.168.1.2] (senat1-01.HML3.ScaleEngine.net [209.51.186.5]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id E2F5146449 for ; Wed, 10 Sep 2014 14:48:22 +0000 (UTC) Message-ID: <541064BD.9060509@freebsd.org> Date: Wed, 10 Sep 2014 10:48:29 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: ipv6 network aliases not set after upgrade to 9.3 References: <20140904141624.GA66403@hydra.pix.net> <541023A0.8000509@yandex.ru> <54105AB2.6020206@pix.net> In-Reply-To: <54105AB2.6020206@pix.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tR60JWfTx179kv5tcEqTV44tcuQCPvkrs" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 14:48:30 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --tR60JWfTx179kv5tcEqTV44tcuQCPvkrs Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2014-09-10 10:05, Kurt Lidl wrote: > On 9/10/14, 6:10 AM, Andrey V. Elsukov wrote: >> On 04.09.2014 18:16, Kurt Lidl wrote: >>> Greetings all: >>> >>> I have a host that recently was upgraded from FreeBSD 9.1 >>> to FreeBSD 9.3. After the upgrade, the IPv6 aliases that >>> I was setting on vlan'd interfaces, no longer get set: >>> >>> The section of my /etc/rc.conf, which worked under 9.1: >>> >>> # inside network (gigabit connected) >>> ifconfig_bce1=3D"up" >>> vlans_bce1=3D"16 17" >>> ifconfig_bce1_16=3D"192.168.16.4/24" >>> ifconfig_bce1_16_ipv6=3D"inet6 accept_rtadv" >>> ifconfig_bce1_16_alias0=3D"inet6 2001:470:e254:0010::4 prefixlen 64 a= lias" >>> ifconfig_bce1_17=3D"192.168.17.4/24" >>> ifconfig_bce1_17_ipv6=3D"inet6 accept_rtadv" >>> ifconfig_bce1_17_alias0=3D"inet6 2001:470:e254:0011::4 prefixlen 64 a= lias" >>> >>> When I use the same configuration file under 9.3, I get the >>> vlan'd interfaces created, and they get an auto-assigned >>> IPv6 interface, but the aliases do not get assigned. >>> >>> If I manually run: >>> >>> ifconfig bce1.16 inet6 2001:470:e254:0010::4 prefixlen 64 alias >>> ifconfig bce1.17 inet6 2001:470:e254:0011::4 prefixlen 64 alias >>> >>> Then the aliased addresses get assigned. Did the syntax for >>> specifying aliases on vlan'd interfaces change subtly for 9.3 vs 9.1?= >>> >>> I did not see anything calling out this change in either the 9.2 or 9= =2E3 >>> release notes. >> >> Hi, >> >> I can confirm this, please, fill a bug report. >> >=20 > This bug has already been fixed in stable/9, apparently: >=20 > -----------------------------------------------------------------------= - > r269028 | dteske | 2014-07-23 18:10:34 -0400 (Wed, 23 Jul 2014) | 7 lin= es >=20 > MFC r267812 (hrs): Fix ifname normalization. ifconfig_IF_alias{es,N} di= d > not > work if ifname has any of [.-/+]. >=20 > PR: conf/191961 > Spotted by: jhay > MFC after: 3 days >=20 > -----------------------------------------------------------------------= - >=20 > Personally, given that this a regression of prior behavior, > I'd love to see it go into a patch release of 9.3. Since its > not a security concern, I think this is unlikely to happen. >=20 > I have tested the patch in that revision (kindly send to me by > Hiroki Sato), and it resolves the issue I was seeing. >=20 > -Kurt >=20 >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" I think at least an Errata notice is called for. So users will more easily be able to find out what the problem is, and stand a reasonable chance of being aware of the issue before they upgrade, so they can either include the patch, or rename their interfaces. --=20 Allan Jude --tR60JWfTx179kv5tcEqTV44tcuQCPvkrs Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJUEGTAAAoJEJrBFpNRJZKf3hQQAILebcuuQeo74JXwXZW+3AH4 7BtrxAiQdVSLzuJ6+aCY1f8V/0LxQzI/6bBVGx5oR3PVSw0Mb72nKdpkyG1tMpTI JAYkbk7EYPlu9ba4YCPg2mXQSKn4YQLdeClpyZTUSyLJxpvZehcS1CNlNXCpepPa PVoLTvSY2kFm4ExOqiBv0QH6TnPm4XijD+BEYllm9PIliHsdJErrEDrYIXDixkbA CAhieb8zQoj8Qw027Qt1UUjLIPFfwrjfXauAVqbji9PZlVlNC/tg7kJ1r02JDZDb NNWDGX0qw7ynewpzkmXUMqzinbyKprHBqMTf9c1S6cEDnZxf3eRGD4LBCli9Dh1v XUIOLP5N0/+W3giumSGcaYgCKG7ear6wdS6/yLOfzBwAELMnUYpZzEO4Livh9zuS QTBkVYH+bebSEzqp95Owyb1nGfXAz0nSSiFYxJ3AspAofwSwkRiEhdklVuFdxckC gi7faSSQHUvffXsdMRWgZKXkMSCts+9awMB67PQnEXsAbFj+2RWHyW6O2fcpr25T 88RRosOLFalTexnNhqYq2M111bIetupn9PXKyz6D/WHFs5F1UMFwiXsIy4uXGu21 0Vl0kiYwuC186HMSQGfb8nSo6iotEhFcREpRvT1rrEk+DRM0VpPVP0qYGCl0Vi7g WRVfyIsiS505woIHN7DD =nP7V -----END PGP SIGNATURE----- --tR60JWfTx179kv5tcEqTV44tcuQCPvkrs--