@peuga said in First time using pfsense, went through 3 ISPs. out of all three, only got ipv6 to work with one of them. troubleshooting ideas?:
i have fiber straight to the ISP's device, so it's a ONT, router, AP, Switch, alll the things combo unit. when setting it to bridge mode
My ISP 'combo' (fibre to router, AP, some video/TV facilities and a phone line) shows me this :
ce390da7-9e72-4a8c-9d38-44950889ff25-image.png
This image tells you (should tell you) everything :
That it will propose IPv6 addresses to devices like PC's phones TV's and other stuff like routers etc in the range 2a01:cb19:907:xx00::/64 - the ISP router using itself 2a01:cb19:907:xx00:46d4:54ff:fe2a:3600 - so this networks work on the ISP router LAN.
pfSense is a device on that LAN : so :
7e7ac5b3-c8e5-4cd2-9c05-f6736dec4dfa-image.png
The upstream DNS (not used) = the IPv6 of the ISP box.
The IPv6 WAN of pfSense, ...92ec:77ff:fe29:392a is also on the ISP box LAN.
So, up until there, somewhat comparable with IPv4 scheme.
Now for the other one : 2a01:cb19:907:xx00::/56 - actually NOT 2a01:cb19:907:xx00:: as it is already used, but all the 2a01:cb19:907:xx01:: to 2a01:cb19:907:xxff:: = 256-1 is 255 different networks or prefixes.
Because I have a pfSense LAN interface that wants (tracks) for such a prefix, it will get this one
73d46fe1-276e-4997-8b21-4c0b9bef2b43-image.png
2a01:cb19:907:xxeb:92ec:77ff:fe29:392c
Why not "01", but '"eb", I don't know.
Why not ::1 but "92ec:77ff:fe29:392c", neither.
If your ISP was using DHCP6 to attribute your IPv6, you could do this :
System > Advanced > Networking :
1058370b-d8ec-43dd-ac8f-770184c20969-image.png
and from now one you have DHCP6 client ( pfSense DHCP6 WAN interface activity ).
That is, if your ISP is using "DHCP" to set up your DHCP6 needs.
Keep in mind : like DHCPv4, the WAN interface needs a IPv6
and
your ISP needs to have allocated prefixes for your, so you can assign them to your pfSense LANs (== router after router model)
edit :
I could, technically, decide to not use the ISP router.
I could slide into my Netgate 4100 a FTP module (Fibre to RJ45).
In that case I need to know how my 4100, with the help of the DHCP6 Client, has to ask the DHCP, both for IPv4 and IPv6, server IP information.
My ISP needs specilaly crafted DHCP options for that, with the user ID, password etc encoded into the option. Both for IPv4 and IPv6.
There are sites in France, where I live, who explain how this is done, and these sites will generated the text strings needed to do so. This method is close to rocket sience.
This will work fine, but I will loose video/TV and phone capabilities.