Project

General

Profile

Actions

Bug #14785

closed

Primary IPv6 interface address may be incorrect when a VIP is set

Added by Marcos M 7 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Interfaces
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.09
Release Notes:
Force Exclusion
Affected Version:
Affected Architecture:
All

Description

If a compressed IPv6 VIP exists, the interface's primary IPv6 address will be set to the VIP even when a non-VIP GUA exists. Example (partially redacted):

vmx1.98: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
    description: ISP2
    options=4000000<MEXTPG>
    ether 00:50:56:b2:b1:89
    inet 192.168.1.253 netmask 0xfffffffc broadcast 192.168.1.255
    inet6 fe80::250:56ff:feb2:b189%vmx1.98 prefixlen 64 scopeid 0xf
    inet6 VIP:VIP:VIP:VIP:5:5:0:1 prefixlen 128
    inet6 ULA:ULA:ULA:ULA:250:56ff:feb2:b189 prefixlen 64 autoconf pltime 3600 vltime 86400
    inet6 GUA:GUA:GUA:GUA:250:56ff:feb2:b189 prefixlen 64 autoconf pltime 2592000 vltime 2592000
    groups: vlan
    vlan: 98 vlanproto: 802.1q vlanpcp: 0 parent interface: vmx1
    media: Ethernet autoselect
    status: active
    nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>

Here, the primary address should be GUA:GUA:GUA:GUA:250:56ff:feb2:b189, but instead Status > Interfaces shows it's VIP:VIP:VIP:VIP:5:5:0:1.


Related issues

Related to Regression #14623: Primary interface address is incorrectly set to the last address on the interfaceResolvedMarcos M

Actions
Actions

Also available in: Atom PDF