No GateWay ipv6 Address
-
I have absolutely wracked my brain trying to figure this one out (i'm a newbie) and I'm coming up empty. I have a /64 Prefix delegation on the WAN and I'm using track interface option on a VLAN located inside of my LAN. The LAN interface will show a IPv6 address and devices inside of the network will receive a ipv6 address from that prefix pool, but the default gateway shows up as a fe80 address and I can't actually access any ipv6 sites. The gateway monitoring never actually shows anything other than pending. I've contacted my ISP but they have several other customers online with their ipV6 setup with no issues.
-
Forgot to add a picture of the gateway monitoring section:
-
Just as a update, I connected a regular commercial (Walmart) router unit to this connection to test the ipv6 and it works just fine with no issues so it does appear to be isolated to pfsense.
-
A link local address is entirely normal for the gateway. I have one here. Also, what size prefix do you get from your ISP? I get a /56 from mine, so I have 56 in the prefix delegation size box.
-
@jknott
I only get a /64 from the local ISP. -
@jordanp123
OUCH!!!Why are some ISPs so stingy? While some provide only a /60, some give a /48. Any chance they are new to IPv6 and just starting with it? When my ISP started offering native IPv6, they also provided a /64, but soon moved to /56.
Do they use DHCPv6-PD to provide a local subnet? Or is it only for devices connected directly to them?
You could mention your ISP, so that anyone who might be on them could help.
-
@jknott
lol, yeah you're 100% right their being stingy with it, no doubt. I'm pretty sure after talking with them on the phone they use DHCPv6-PD for the local subnet. Its a fairly local ISP new to ipv6, its a local WISP, I believe their using Mikrotik routers. -
it looks like its just not adding a default gateway or the gateway isn't working. using the ping ipv6 test inside of pfsense just gets me a 100% loss.
-
-
After banging my head into the wall some more I decided to roll back on a VM to test if pfsense 2.6 CE would suffer from the same issue. It doesn't, it pulls up and runs just fine with it, so it appears to be a regression with pf+ 23.01 in some way. I'll be running 2.6CE until it looks what whatever is going on is resolved.
-
@jordanp123 Likely related to this...
