Bug #15096
closedInterface subnet aliases do not contain IPv6 VIPs
100%
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
Updated by JohnPoz _ about 1 year 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.
Updated by gwab ber about 1 year ago
I fixed it temporarely by adding separate allow rule for the ULA.
Updated by Marcos M about 1 year 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.
Updated by Marcos M about 1 year ago
- % Done changed from 0 to 100
Applied in changeset 1c4ca20d3d5910f126f11221f23e1fa21197f225.
Updated by Lev Prokofev about 1 year 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
Updated by Jim Pingle 11 months ago
- Status changed from Resolved to New
- % Done changed from 100 to 90