Project

General

Profile

Actions

Bug #15906

closed

IPv6 delegated prefix changes upstream do not immediately update track6 interfaces

Added by Uwe Verwey 4 months ago. Updated 10 days ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
IPv6 Router Advertisements (radvd/rtsold)
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.7.2
Affected Architecture:
All

Description

After an IPv6 prefix and IP change on the WAN interface the LAN interface IPs and delegated IPv6 prefixes don’t get updated.
This mens the client devices on the LAN networks are not getting an updated IPv6 IP via SLAAC and communication stops.

This situation resolves only after 1.5 to 2 hours. Then the LAN IPs get updated. This is taking too long.
Log:
/rc.newwanipv6: Netgate pfSense Plus package system has detected an IP change or dynamic WAN reconnection - 2003:e2:8700:ae00:2e0:edff:febe:dacf -> 2003:e2:8701:3a00:2e0:edff:febe:dacf - Restarting packages.

Scenario:
IPv6 with dynamic IPv6 prefix advertised by upstream router via DCHPv6 to WAN Interface.
WAN IPv6 Configuration Type: DHCP6
DHCPv6 Prefix Delegation size: 61
Send IPv6 prefix hint: yes
Request only an IPv6 prefix: no
LAN Interfaces: Track Interface

Clients are configured "unmanaged" (Stateless Address Auto-Configuration (SLAAC)).

Steps to reproduce:
Initiate a IPv6 prefix change on the upstream router.


Related issues

Related to Bug #12947: Old IPv6 addresses may continue to be used after DHCP or RA changesFeedbackMarcos M

Actions
Actions

Also available in: Atom PDF