Project

General

Profile

Actions
Copy link

Bug #15096

closed

Interface subnet aliases do not contain IPv6 VIPs

Added by Bob Dig 4 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Marcos M
Category:
Aliases / Tables
Target version:
2.8.0
Start date:
Due date:
% Done:

100%

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

Description

While the tables NETWORK not reflecting any IPv6 ULA as VIP at all, an ULA IPv6 connection from LAN is working while a connection from other Subnets isn't working as long as there is a rule with subnets as source. It is working with source any with every subnet, not only LAN.
Also see this forum post.
https://forum.netgate.com/topic/184867/ula-routing-broke-after-2-7-2-update/2?=1702635139798

CE and Plus are affected.

Files

clipboard-202312152349-amahq.png (41.9 KB) clipboard-202312152349-amahq.png Lev Prokofev, 12/15/2023 04:49 PM
Actions
Copy link
 #1

Updated by JohnPoz _ 4 months ago

I just looked, created gua and ula on one of my interfaces - and while the gua is shown, the ula is missing.

I created a IPv4 vip on the same interface the ula is on, and the IPv4 is shown, the gua IPv6 is shown, but not the ula.

Actions
Copy link
 #2

Updated by gwab ber 4 months ago

I fixed it temporarely by adding separate allow rule for the ULA.

Actions
Copy link
 #3

Updated by Marcos M 4 months ago

  • Project changed from pfSense Plus to pfSense
  • Subject changed from built-in subnets not containing ULA IPv6 VIP to Interface subnet aliases do not contain IPv6 VIPs
  • Category changed from Aliases / Tables to Aliases / Tables
  • Status changed from New to Feedback
  • Assignee set to Marcos M
  • Target version set to 2.8.0
  • Affected Plus Version deleted (23.09)
  • Plus Target Version set to 24.03
  • Affected Version set to 2.7.2

Fixed in commit 1c4ca20d3d5910f126f11221f23e1fa21197f225.

Actions
Copy link
 #4

Updated by Marcos M 4 months ago

  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by Lev Prokofev 4 months ago

Patch is woring, table now contain the IPV6 alias IP
tested on

23.09.1-RELEASE (amd64)
built on Wed Dec 6 23:22:00 MSK 2023
FreeBSD 14.0-CURRENT

Actions
Copy link
 #6

Updated by Bob Dig 4 months ago

Patch working great, thanks.

Actions
Copy link
 #7

Updated by gwab ber 4 months ago

Works like a charm! cheers!

Actions
Copy link
 #8

Updated by Marcos M 4 months ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #9

Updated by Bob Dig 3 months ago

Turns out the patch is only working momentarily. It will prevent you from enabling IPv6 GUA (tested via Track Interface) on another interface.
First you have to disable the patch, turn IPv6 on on another interface, as desired, and then re-enable the patch (for ULA).

Actions
Copy link
 #10

Updated by Jim Pingle 3 months ago

  • Status changed from Resolved to New
  • % Done changed from 100 to 90
Actions
Copy link
 #11

Updated by Marcos M 3 months ago

  • Status changed from New to Resolved
  • % Done changed from 90 to 100

This issue/fix is only related to the alias; if an IPv6 address does not get added to the interface, that would need its own redmine issue.

Actions
Copy link
 #12

Updated by Bob Dig 3 months ago

The reason it is not working anymore is this patch, so it looks counter-intuitive to me to open another redmine issue.

Actions
Copy link

Also available in: Atom PDF