IPv6 not working after IP change

AndyRH

ATT had the great idea of changing my IP addresses. IPv4, no problem, IPv6 problem.

I restarted my PC (needed it anyway) and got the new address, but it does not work. I have poked around and cannot find anything that does not match the new address.
It worked fine before the change, so I know in general it is correct.
I can ping my PiHole server (ClearPi) by IPv6, but they are on the same LAN and I can ping the GW.

Where should I look?

pfSense:

 WAN (wan)          -> ix1     -> v4/DHCP4: 999.9.204.54/23
                                  v6/DHCP6: 2001:506:xxxx:yyyy::1/128
 LAN (lan)          -> igc0    -> v4: 192.168.129.1/24
                                  v6/t6: 2600:1702:865b:xxxx:92ec:77ff:fe86:ed65/64

My PC

Ethernet adapter USBEthernet:

   Connection-specific DNS Suffix  . : home.arpa
   IPv6 Address. . . . . . . . . . . : 2600:1702:865b:xxxx::1000
   Link-local IPv6 Address . . . . . : fe80::9f87:ae0f:2ab7:2da2%9
   IPv4 Address. . . . . . . . . . . : 192.168.129.33
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : fe80::92ec:77ff:fe86:ed65%9
                                       192.168.129.1

LAN rules

LAN interface

Bob.Dig

@AndyRH Does IPv6 work on pfSense itself to the outside? If not, go to interface WAN, click save and apply and try again.
In general, dynamic IPv6 with pfSense is a mess. I look that I get a new IPv6 at night time, two hours before I actually have to use it.

AndyRH

@Bob.Dig I should have thought of pinging from pfSense... It did not work and the save action on WAN did not help. I pinged Cloudflares DNS server. 2606:4700:4700::1111

Bob.Dig

@AndyRH You are using PPPoE? Then maybe look there, reboot pfSense and disable IPv6 on WAN or PPPoE and then re-enable it.

AndyRH

@Bob.Dig It is ATT fiber. I should have pointed out that pfSense was restarted twice for the upgrade. There was no change.
Also, there is no ATT modem involved.

SteveITS

@AndyRH try a traceroute out and see how far it gets. I’d guess not past the ISP router implying a routing problem there.

Bob.Dig

And disable gateway monitoring for some test.

AndyRH

Sometimes I hate IT stuff. I did nothing as I was out of ideas, now it works.

Thanks for the advice.

SteveITS

@AndyRH "any sufficiently advanced technology is indistinguishable from magic"

Gertjan

That doesn't look magic to me.
a /128 ... just doesn't feel right.

When I see a IPv6 .../128 it makes me think of a 1.2.3.4/32 IP-network.
I mean : try settings an up IPv4 like this :

and see what happens ...

JKnott

@Gertjan

A /128 is entirely normal. It means an assigned address, but it cannot be used for routing. The link local address is normally used for routing.

stephenw10

Yeah as long as that address or some larger subnet containing it is being routed to pfSense via the link-local address that should work fine. Though it's more common to see some transport subnet on WAN for a DHCP connection.

Gertjan

Thanks you both for getting my v6Mind straight.
I tend to forget about these two :

Note : green : the more common case : a /64

stephenw10

Yup route over link-local in IPv6 takes some mindset change.