@mystic330 said in IPv6 over Starlink:
It’s gone from bad to worse now…
I hit release /renew on the WAN, gave it several mins and neither v6 or v4 worked - got no addresses on either. I was hard down.
I had to reboot the Starlink router - once it came back I have v4 connectivity but I’m still not getting any v6 address - routable or link-local…
The two are not related.
The dhcpc (IPv4 !) will emit a request for IPv4lease - you can see this happening in the DHCP log, just locate (Ctrl-F) all the lines with the 'dhcpc' lines.
If there is no answer from the upstream dhcp IPv4 server .... well ... that's an issue on its own. If you need to reboot the upstream starlink stuff, that's pretty lame.
To get more info : use the search button at the top, enter 'Starlink' and you'll find many posts about startlink and WAN issues.
This :
0887889e-d094-4d12-b589-0f3aa99845bd-image.png
and the absence of log lines from dhcp6c (the DHCP client IPv6 process) where you can see (see my example) that the dhcp6c is asking for a lease, and get one (one at lease) means that
you get an IPv6 address for your LAN :
66c781ff-6434-4581-aa50-bc239709ee8f-image.png
Btw : this option is somewhat strange :
976662aa-bce2-456d-b327-2d25369abbe0-image.png
You don't want just prefix(es), you want also an IPv6 address for your WAN .... right ( ? )
Try this : Hook up on the starlink router another device, like a PC.
When connected : check the starlink router GUI for Ipv6 leases it handed over, or type
ipconfig /all
on your PC.
Did it get an IPv6 like 2605:59c8:5200;bbb0:a.b.c.d ?
If so, the DHCP6 starlink server (in your router, or further upstream) hands over IPv6 addresses, but ...
no prefixes ?
The thing is, your pfSense is not a normal end device like a PC, its a router.
It needs a IPv6 for it's WAN needs, like a PC.
But it has also, on the other side, a LAN interface, and on this interface you can connect many devices.
Hence the need of a 'pool' of IPv6 addresses that it, pfSense, can hand over to these end user devices, exactly like the upstream router to which pfSense is connected.
These 'pools' are the prefixes. One is needed per pfSense LAN.
If Starlink doesn't give you a prefix, pfSense can't hand over IPv6 lease on the LAN side, as it has no FHCPv6 pool to do so.
Again : this means :
f48ee447-1fe7-4fac-bb92-5f66c268b088-image.png
that pfSense did not obtain a prefix for that LAN.
It is very possible that the starlink router can only give IPv6 addresses for devices connected, like PCs, phones etc.
But if it does not support to 'lease' IPv6 prefixes : this means you can't use a down stream router like pfSense, and propagate IPv6 addresses on its LAN.