IPv6, SLAAC, DHPv6 and Port Forward

[Azuriye]

@elbertmai

This is correct if Plex and all the other services are running on the router itself. But since they're running on another host in the network, the AAAA record needs to point to the IPv6 address of that host, not the router.

Huh, that's odd, but thanks for letting me know. I feel like I might need to have two sub-domains with AAAA records pointing to my Router and the other to my Desktop?

Also, I've just rebooted my Router and deleted my Wireguard Traffic Rule as well as the Port Forward but for some reason my Wireguard clients can still access it. How is that possible? Does it possibly auto-configure the ports when setting up the interface?

EDIT: Okay I found out the issue was this.

Left it disabled and it no longer accepts any Wireguard traffic.

I've been setting this up in an attempt to have IPv6 access through my Wireguard tunnel with Selective IPv6 NAT.

NAT examples

But that didn't seem to work.

I'm not sure if I'm allowed to cross-reference another post...

How to setup Wireguard with IPv6-PD?

Don't use ULAs as @mikma said most endpoint OS don't consider a ULA valid to originate a connection to a GUA on the v6 Internet. To NAT you need to issue the LAN clients local IPs which look like GUAs but are never going to actually exist on the Internet, as trying to reach a site that has a public IP in the same subnet as your LAN IP will not route properly. There is no officially reserved block of GUAs for this purpose. I have used "documentation" block this way: 2001:db8:<16 random bits>::…

I guess maybe you would've witnessed how my wg0 interface was using a ULA address... but with how many threads there are regarding setting up Wireguard with IPv6 access and so many NAT options which people try I'm puzzled as to how to get my things sorted...