Re: ipv6 network aliases not set after upgrade to 9.3

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="up"
>>> vlans_bce1="16 17"
>>> ifconfig_bce1_16="192.168.16.4/24"
>>> ifconfig_bce1_16_ipv6="inet6 accept_rtadv"
>>> ifconfig_bce1_16_alias0="inet6 2001:470:e254:0010::4 prefixlen 64 alias"
>>> ifconfig_bce1_17="192.168.17.4/24"
>>> ifconfig_bce1_17_ipv6="inet6 accept_rtadv"
>>> ifconfig_bce1_17_alias0="inet6 2001:470:e254:0011::4 prefixlen 64 alias"
>>>
>>> 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.3
>>> release notes.
>>
>> Hi,
>>
>> I can confirm this, please, fill a bug report.
>>
> 
> This bug has already been fixed in stable/9, apparently:
> 
> ------------------------------------------------------------------------
> r269028 | dteske | 2014-07-23 18:10:34 -0400 (Wed, 23 Jul 2014) | 7 lines
> 
> MFC r267812 (hrs): Fix ifname normalization. ifconfig_IF_alias{es,N} did
> not
> work if ifname has any of [.-/+].
> 
> PR:             conf/191961
> Spotted by:     jhay
> MFC after:      3 days
> 
> ------------------------------------------------------------------------
> 
> 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.
> 
> I have tested the patch in that revision (kindly send to me by
> Hiroki Sato), and it resolves the issue I was seeing.
> 
> -Kurt
> 
> 
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"

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.

-- 
Allan Jude