Upgraded to 23.01 release no IPV6

SteveITS

@nighthawk1967 Is it still an issue after reboot? What are your firewall max table entries set to?

https://forum.netgate.com/topic/45603/cannot-define-table-bogonsv6-cannot-allocate-memory

nighthawk1967

@steveits How about the no ipv6 just says unknown and pending all worked fine on version 22

maverickws

I'm having the same issue of no IPv6 since upgraded to 23.01 no IPv6

Gateway monitor "Pending" and Status "Unknown"
Rebooted to see if that would solve it, it didn't.

I noticed on the firewall that the LAN IPv6 Network was being blocked. I added an allow rule for the /40 IPv6 subnet, but IPv6 traffic is dead anyway.

P.S. - Just noticed I don't have any memory error logged. So it's just no ipv6 after upgrade, I'm creating a new topic for this.

defunct78

I just did a few more tests, and discovered the same issue.

SG-1100
HE Tunnel Broker - Works perfectly on 22.05
Upgraded to 23.01 and I am no longer able to route IPv6 through. Rebooted back into 22.05 and again, no issues.

Since Tunnel Broker uses a GIF interfaces, I checked for the symptoms found in the following bug, and saw none. Attempted the manual fix and even applied patch and rebooted. No luck
https://redmine.pfsense.org/issues/13963

I do have a /48 allocated from HE, though not sure that would make any difference. I am do not see any errors about the GIF interface in the logs.

From pfSense I can ping google 2607:f8b0:4007:803::200e Successfully while running 22.05. When I switch back to 23.01, I am unable to ping 2607:f8b0:4007:803::200e

PING6(56=40+8+8 bytes) xxxx:xx:x:xx::x --> 2607:f8b0:4007:803::200e
ping6: wrote 2607:f8b0:4007:803::200e 16 chars, ret=-1
ping6: wrote 2607:f8b0:4007:803::200e 16 chars, ret=-1
ping6: wrote 2607:f8b0:4007:803::200e 16 chars, ret=-1

--- 2607:f8b0:4007:803::200e ping6 statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss

I will call out, that my Gateway Monitor is successful through the GIF interface to HE on either 22.05 or 23.01

defunct78

@defunct78 To add to my comment.

The PING to Google (2607:f8b0:4007:803::200e) over the WANv6 interface which worked under 22.05 and not over 23.01, I attempted a packet capture on the WANv6 interface. No packets were seen on the WANv6 interface.

lacoppoc

I followed the instructions found in https://redmine.pfsense.org/issues/13963 and IPv6 has been working just fine after I rebooted.

Considering that this was a pretty major upgrade, this was the only issue I've come across (so far) so I'm feeling pretty lucky. You might want to try it again in a a bit.

nighthawk1967

@lacoppoc Does not help me .Still have the same problem .Nothing has helped i am using a hp 360 12 core 32gig server for pfsense

Bob.Dig

@nighthawk1967 Maybe 32 Gigs is to much...

lacoppoc

@nighthawk1967 - That's not good. That's decent hardware you're working with there. What Gen is it?

maverickws

My pfSense is not an HP, (it's a Qotom mini-pc with 6GB ethernet ports) has 4GB of memory, and has the same problem of no IPv6 after upgrading to 2301. Don't focus on ONE hardware config for an issue that is hardware agnostic. Thank you.

defunct78

After more troubleshooting, I found my problem. Had nothing to due with the bug posted.

After the upgrade, IPv6 default gateway was set to "Automatic". And in doing so, it wasn't able to route my IPv6 traffic. Forced the IPv6 Gateway (WANv6_TUNNEL) to be the "Default gateway IPv6", and now traffic is flowing.

Side note, boot environments are awesome! Thank you devs for adding that feature as it made it really easy to go back and forth to find the issue.

SteveITS

@defunct78 good find and now that you’ve said that I have seen that issue posted occasionally over the years.

maverickws

@defunct78 unfortunately that is not my issue. I have a IPv6 Gateway Group selected the same as before.