The modem provided by the ISP is a cable modem, put in bridge mode, the ISP only provided a /64 subnet
I successfully get an ipv6 address on WAN and LAN, but I can't ping anything on internet, here the details:

2. Is your machine on the LAN side getting an IPv6 in the same subnet as your LAN interface, and does it have the correct default gateway? Since pfSense is broadcasting router advertisements, you'll probably see fe80::1:1 as the default gateway.

2. Is your machine on the LAN side getting an IPv6 in the same subnet as your LAN interface, and does it have the correct default gateway? Since pfSense is broadcasting router advertisements, you'll probably see fe80::1:1 as the default gateway.

If both the above are good, I suspect that your ISP's modem or something upstream isn't creating a route for the delegated prefix on their side.
When you plug directly into the ISP modem you are not using a delegated prefix, you are using the subnet of modem.

If both the above are good, I suspect that your ISP's modem or something upstream isn't creating a route for the delegated prefix on their side.
When you plug directly into the ISP modem you are not using a delegated prefix, you are using the subnet of modem.

Your assumption about the subnet on the modem makes sense. I thought that a modem in bridge mode was enough :-/
Anything I could try to replicate manually on pfsense or do you think is worthless at this point and I should back to use the tunnel (which is a shame since I've finally got a native ipv6 support:-)) ?

Cable one, and this was the saddest point :-) I could try different ways to distribute the addresses to the LAN, but even the WAN doesn't work, looks like it just gets the IP address, but no routes were being set :-/

… Finally my ISP has managed to release the native ipv6 for their customers ...

I guess they need to un-release native IPv6 until they can get it working properly. As many others have stated on this forum, just stick with the HE.NET (or equivalent) free tunnel. I predict that it is still going to take years before IPv6 is working well for everyone.

… Finally my ISP has managed to release the native ipv6 for their customers ...

I guess they need to un-release native IPv6 until they can get it working properly. As many others have stated on this forum, just stick with the HE.NET (or equivalent) free tunnel. I predict that it is still going to take years before IPv6 is working well for everyone.

News

Resources

Company

Our Mission

We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.