Quote from: meyergru on April 17, 2025, 04:21:19 PMMany routers tend to hand out only a /64 range, because they usually "think" that it is only one LAN connected to them - I mean that is in itself not a sure sign that your ISP does not hand out a larger prefix like /56 or /48 as per IA-PD. You would probably see that if you use the ISP router in brige/modem mode and try bringing up the connection with OpnSense as the only router.
I cannot provide any specific instructions, because IDK that provider.
Hi @meyergru yes you are right, apparently this ISP is indeed locking out domestic/home users to just one IPv6 lan prefix and the thing in Bridge or DMZ does not work as intended either, hence why the ISP in bridge or DMZ didn't worked on the IPv6 side as expected when testing, and the user can't modify prefix nor to disable IPv6 in the ISP router.
To make things worse found that this ISP company is nothing more than a [Carrier-Grade-NAT] "cgnat.libertypr.net" with a dynamic/dynamic connection setup.
This boils down that no matter what firewall/router is connected in between it will not work as intended for the IPv6 stuff, and since more and more heavily loaded content-delivery-networks websites/apps are using IPv6 it is not recommended disabling it completely like two decades ago.
I've confirmed this by completely disabling the IPv6 only on my workstation/client and all of this websites/apps loaded partially/broken even when connected directly to the CGN ISP.
I will try contact my ISP and ask if they can change this IPv6 prefix limitation though, and if not possible then wait patiently for further resolutions regarding CGN users with OPNsense.
For now I will enable the `ufw` firewall on my workstation and strict my current `pf` settings on my FreeBSD server, even if is a headache working with this stuff by hand, but at least is better than nothing.
Again thanks a lot for the suggestions @meyergru @cookiemonster @Seimus
Regards