Hi. I need to publish a HTTPS endpoint (which will be consumed by an AWS Lambda function). My ISP uses CGNAT for IPv4, but publishing over IPv6 only is fine. All the posts about IPv6 port forwarding that I've found in the forum end either with suggestions that don't work or "you don't need port forwarding with IPv6". I know with IPv6, devices usually get a publicly routable IP address. I opened the port in the router and this works, but the problem is that i also have a dynamic IPv6 prefix. So it only works until the prefix changes and then I have to reconfigure everything.
Configure a ddns client on the client or a ddns client for the whole prefix. Doing NAT would be the worst solution you can have.
Thanks for the reply.
I have now modified the firewall rule that opens the port to use negative netmask notation. The port is still open, so I assume it will keep working when my prefix changes (I haven't tested yet). I tried to use the same notation for an IPv6 port forwarding rule (following section in the previous link) and it didn't work. Is it not supported?
Why would NAT be the worst solution? With port forwarding and the router's builtin DDNS client. So I wouldn't need a DDNS client in every server I want to publish services from, which seems simpler.