WireGuard does not assign dynamic IP addresses, which may be a privacy risk.
It is known that while WireGuard may offer advantages in terms of performance, by design it is not ideal for privacy, because it doesn't allocate VPN IP Addresses (10.*) dynamically like OpenVPN does; instead WireGuard requires fixed ones in .conf files deployed on devices.
I keep reading there are certain scenarios in which these IP addresses can be exposed, namely with WebRTC leaks. I'd like to know if my scenario is among the scenarios at risk of leaking this fixed (internal) VPN IP address.
On my OpenWrt router I have installed WireGuard, which connects to my VPN provider and provides internet access (tunneled through the VPN) for all my LAN clients. The LAN clients themselves are in this sense 'unaware' of the VPN connection. The public IP address reported by sites such as ipleak.net when visited in the browser on one of my LAN clients reports only the VPN public IP address, not the public IP from my ISP, nor does it report the fixed (internal) WireGuard IP address which can allegedly leak by means of WebRTC or STUN.
My question is: is it possible for LAN clients in this scenario to obtain, somehow, the fixed (internal) WireGuard IP address (assuming they can't login to the router)? Should I be concerned about the risk of WebRTC in this case, or not?