IPv6 over Starlink
-
Hello - I have gone through most threads here trying to get v6 working out through Starlink with no joy.
I think the starlink part is working fine however:- I get a local-link GW - and can ping it
- It seems like I'm getting delegated /64s through DHCPv6 (LAN hosts are getting non local-link addresses)
- Pfsense can ping public v6 addresses
I just can't get any hosts on my LAN to get out via v6 - which I'm thinking is a pfsense issue....
Couple of questions:- How do you see what the delegated prefix is? (If I pull up DHCPv6 config under Primary Pool Prefix I just see " Delegated Prefix: WAN1_STARLINK/0/64 "
- If I have the v6 config on the LAN set to Track (ID=0), shouldn't I see an address from that prefix be assigned to the LAN interface? All I see is a local-link address.
- I think my LAN hosts are getting v6 addresses from the /64 prefix via RA (not sure how to verify)
- I have nothing in my DHCPv6 leases table....
I don't think v6 is being routed and DHCPv6 isn't working because there's no routable v6 address assigned to my LAN interface..... ??? But I'm not sure...
Any ideas?
-
For answers, you have to ask them to show up.
Easy :
From this moment, the answers will be shown here : Status > System Logs > DHCP
When you see this part (can exists multiple times, as many as you have LAN interfaces with "IPv6 : Tracking" activated ) :
Here you can see I received one prefix.
As I have my LAN using IPv6 Tracking :
together with, on the same LAN Interface settings page :
Note the "from 0 to 0" which means that there is one (with index 0) available
Now, goto DHCPv6 Server page for my LAN interface :
You can see the prefix again, and the available network.
I've created a pool, from ::2 to ::86.I've set the Router Advertisement to Managed (because : why not) :
and from now on my DHCP6 server starts to receive IPv6 lease requests.
Because I can see it happen in the ...... DHCP Logs :
and the DHCP6 Leases pages starts to fill up :
Note that most if not every DHCP6 lease are not taken from the pool.
I've set up Static DHCP6 Leases, like the IPv4 equivalent :
Last, but not least : My DHCP6 WAN settings :
and I'm not sure that the one and only option I've checked is even needed.
Note : all this is valid for my setup, using my ISP router (not modem), and it it my router that gives to pfSense an IPv6 on the WAN side, and a prefix (just one !! or the ISP router says it has /56 == 256 prefixes avaible). So, I have Ipv6 working on one pfSense LAN.
And things get even better : impossible to open ports to this prefix so i can access IPv6 to access a device (my NAS) using IPv6.
Very few ISPs are fully IPv6 compliant, many have implementation issues, they do thing 'their way'. And they are not documenting their miss-interpretation. There is still a "IPv4 works, and IPv6 maybe, if you can make it work" culture.I've been using this IPv6 ISP for nearly a decade https://tunnelbroker.net/, it is free, you have your own /48, so your good for 65535 LANs, each with its own /64. They handled IPv6 as it is written in the book. They actually wrote that book (RFC).
There was one condition, though : you had to go through https://ipv6.he.net/certification/ : they ware actually asked that you learned how to use IPv6 before using it.
-
Thanks.
I'm not seeing much in the DHCP log:
I do have an IP on the WAN interface however:
I have the requisite config on the DHCPv6 for the WAN:
As I said, my LAN hosts are getting IPv6 addresses, so I'm assuming RA is working and it's possibly from the delegated /64 - but I can't verify.
Do you have an actual IPv6 address assigned to your LAN interface based on the "track" function??
(Status -> Interfaces)
I only see a link-local address:
-
Adding....
My DHCPv6 config screen doesn't show the actual delegated /64 like yours (and others) show - but instead just "WAN1_STARLINK/0/64"
I don't think delegation is working on my setup.... Although my LAN hosts are getting IPv6 addresses from somewhere....
-
@mystic330 said in IPv6 over Starlink:
My DHCPv6 config screen doesn't show the actual delegated /64 like yours (and others) show - but instead just "WAN1_STARLINK/0/64"
I had the same problem once after adding a new LAN with IPv6 tracking the WAN. It was solved by doing a Release / Renew on the WAN interface (under Status / Interfaces). Once the WAN had reconnected the DHCPv6 config screen showed the correct prefix.
-
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…
I don’t think this v6 code is ready for prime time
-
The log indicates a “ transmit failed: Can't assign requested address”
Is there some cache that needs to be cleared?
-
@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 :
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 :
Btw : this option is somewhat strange :
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 typeipconfig /allon 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 :
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. -
They are related in that I had both v4 and v6 addresses on my WAN interface - just delegation wasn’t working - and I clicked “release” based on a suggestion here, and both v4 and v6 DHCP stopped working altogether.
I not worried about the v4 issue - just found it odd - this is a v6 troubleshooting thread and I’m specifically looking at/posting logs from the “dhcp6c” processes and help on how to troubleshoot v6 on pfsense. I’m way beyond the router vs end-node, ip addressing, etc stage (CCIE for 15 years)I was previously getting a v6 address on my WAN interface, so I know Starlink is handing out/supports DHCPv6 and I was also getting a gateway so I know RA was working. (Now I need to troubleshoot why it suddenly stopped)
(I didn't realize the Only send prefix checkbox was checked - as I was trying different options it must've gotten checked - Thanks, I'll uncheck that).What wasn’t working is delegation of a /56 from Starlink and the first /64 (with ID 0) to my LAN interface. My LAN interface never reported a routable v6 address (which I believe is keeping my dhcpv6 server on the LAN interface from working). For those of you that have v6 delegation working from your ISP, do you have a routable v6 address from the delegated block assigned to your LAN interface?? I know this is not required as a link-local address as the gateway on the LAN will allow routing to work, but I never see any dhcpv6 leases being handed out and I believe not having a v6 address on the LAN interface is the reason….
-
This is from starlink's web site. They claim they delegate a /56.
-
OK - When in doubt - REBOOT!
With all the standard v6 settings as shown in other posts, a reboot brought everything into a working as expected state!
I have a routable v6 address on my LAN interface:
...which allows the DHCPv6 server to work on the LAN interface as I now have v6 leases showing:
Here's my config for others to reference:
WAN interface - v6 address set to DHCPv6
LAN interface - v6 address set to "Track interface":
...with the track interface set to the WAN interface getting the v6 delegation and the prefix ID set (0 in this case refers to the first /64 within the delegation (/56 in the case of Starlink):
Then enable DHCPv6 server on the LAN interface:
Thanks for everybody's help!
-
-
@Gertjan Hi I just joined this forum for this thread.
After registering and logging in all of the images of screen captures are showing as "UUID-string.png" clicking on them displays "Not Found".What do I need to do to see the embedded images?
-
@timg_11 said in IPv6 over Starlink:
@Gertjan Hi I just joined this forum for this thread.
After registering and logging in all of the images of screen captures are showing as "UUID-string.png" clicking on them displays "Not Found".What do I need to do to see the embedded images?
A few months ago the forum software experienced a serious crash and many links to images in posts were irreparably broken. Unfortunately, the links you seek were among those broken.
-
@mystic330 said in IPv6 over Starlink:
It seems like I'm getting delegated /64s through DHCPv6 (LAN hosts are getting non local-link addresses)
Does Starlink provide a prefix through DHCPv6-PD? Or just the one /64? My cell phone does the latter.
-
@timg_11 The images are available on the Wayback machine at archive.org.
I just did the same thing as you, but I'm trying to route IPv6 on Linux
