Project

General

Profile

Actions
Copy link

Bug #14725

closed

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

Added by Marcos M about 1 year ago. Updated about 1 year ago.

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

100%

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

Description

The previous behavior of using the first IPv6 non-LL address as the primary interface address was restored with https://redmine.pfsense.org/issues/14623. Now, the inverse situation is broken - that is, when the ULA is set before the GUA. 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 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>

Instead of arbitrarily choosing the first non-LL address, the first GUA address should be used.

Related issues

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

Actions
Related to Regression #11570: Gateway monitoring services is not always restarted on interface events, which may prevent a WAN from recovering back to an online stateClosed

Actions
Actions
Copy link
 #1

Updated by Marcos M about 1 year ago

  • Related to Regression #14623: Primary interface address is incorrectly set to the last address on the interface added
Actions
Copy link
 #2

Updated by Marcos M about 1 year ago

  • Status changed from New to In Progress
  • Assignee set to Marcos M
Actions
Copy link
 #3

Updated by Marcos M about 1 year ago

  • Status changed from In Progress to Pull Request Review
  • Target version set to 2.8.0
  • Plus Target Version set to 23.09
Actions
Copy link
 #4

Updated by Marcos M about 1 year ago

  • Status changed from Pull Request Review to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by Marcos M about 1 year ago

  • Status changed from Feedback to Resolved
  • Release Notes changed from Default to Force Exclusion
Actions
Copy link
 #6

Updated by Marcos M about 1 year ago

  • Related to Regression #11570: Gateway monitoring services is not always restarted on interface events, which may prevent a WAN from recovering back to an online state added
Actions
Copy link
 #7

Updated by Jim Pingle about 1 year ago

  • Target version changed from 2.8.0 to 2.7.1
Actions
Copy link

Also available in: Atom PDF