Public IPv6 on the LAN side

New to MikroTik, I’ll try to explain the situation and hopefully it’s easy.
Model: PowerBox Pro
Clean build v6.47.1 (stable)
Firewall configuration basic (factory) NAT mode
Internet = ether1
LAN = bridge1
IPv4 enabled, and static IP assigned to the MikroTik
IPv6 enabled, and static IP assigned to the MikroTik
MikroTik can ping all IPv4 and IPv6 public IP addresses

Issue:
No computer on the LAN side can ping IPv6 addresses. Even if the PC or Apple enters the static IPv6 address manually it will not ping any IPv6 addresses

Solution:?

You should share a little more (preferably everything) about what IPv6 config you got from ISP. You can anonymize it (mask some numbers), but don’t overdo it.

I have my own ASN and registered public IPv6
Our fibre provider has allocated this to our network:
Network is XXXX:2e40:1::/64
Gateway is XXXX:2e40:1::1
I have a MikroTik attached to the switch and everything works at the router.
If I attach a PC to the fibre switch bypassing the MikroTik and assign a static IPv6 address it works.
IPv6 does not work at all if the PC is attached to the LAN ports of the MikroTik.
That’s the issue, hope that helps.

So you have additional subnet(s) of your own, or just this one /64 from ISP?

If it’s just this one, then it’s not good, because it’s not enough. If ISP’s router has gateway IP, then it expects whole /64 directly reachable.

It’s like if you got e.g. x.x.x.0/24 IPv4 subnet from ISP, but they kept gateway x.x.x.1/24 on their router. You wouldn’t be able to use any of x.x.x.y behind router with regular config (you could do it with the help of proxy ARP, but it’s not the most correct way). IPv6 is similar, it has ND proxy, but RouterOS doesn’t support it and it’s not the right way either.

Proper config requires another subnet. Ask ISP to route at least another /64 to your router, and that’s what you can use in LAN. But better get even larger subnet (popular choices are /48 or /56), because /64 is default size for SLAAC (autoconfiguration) and you can’t easily divide it, when you need e.g. one private subnet for yourself, another for guests, next one for IoT things, etc.