Project

General

Profile

Actions

Bug #16965

open

pfSense Plus doesn't start using a new IPv6 gateway via SLAAC without expired lifetime notification

Added by Kris Phillips 3 days ago. Updated 3 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
IPv6 Router Advertisements (RADVD)
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
Affected Architecture:

Description

In the event a WAN is using SLAAC for IPv6 and the router upstream for the default gateway sends a "Valid Lifetime=0" message to immediately expire the gateway, then starts advertising a new gateway, pfSense Plus will pick up the new gateway and start using it.

However, if the upstream gateway does not expire the gateway, it will keep trying to use it. This is the case even when the lifetime value reaches 0 and the upstream provider starts advertising a new router via RAs.

While it's expected that an upstream provider will gracefully terminate the old gateway's validity and "push" the client to use a new gateway, pfSense should try and at least get a new gateway and refresh the routing table when that lifetime expires.


Files

Screenshot_20260721_160851.png (198 KB) Screenshot_20260721_160851.png Kris Phillips, 07/21/2026 09:09 PM
Actions #1

Updated by Kris Phillips 3 days ago

Attached is a screenshot of the pcap file showing the Router Advertisements coming through. At packet 46647, you can see the RAs change addresses without a expiration of the old gateway, but pfSense never tries to use the new gateway even after days of sitting this way.

The default gateway from netstat shows this:

Destination Gateway Flags Nhop# Mtu Netif Expire
default fe80::10:18ff:fe0d:be5%igb3 UGS 16 1500 igb3

Customer ticket 46692678936 contains the actual pcap file, but it cannot be attached here due to file size limits.

Actions

Also available in: Atom PDF