Edegerouter X e50v2.deb latest. The command line doesn't seem to give an option to set a DNS = statement on the wireguard interface. DNS can be set via edgeos dhcp-server or local nameserver but the WG interface itself can't set dns via the cli. (As other implementations of wireguard can) Clients behind the VPN are unable to resolve dns names. ( For example, an xbox on a subnet whose traffic is being forwarded via modified table through the WG interface to an endpoint providing a masquerade) Also I don't see a way to refer to a config file and can only hardset configuration via edgeos WG interface. Is there another way to resolve dns for clients going through wireguard?
Disregard on the dns resolving. Found an oversight. Though I do still wonder about not being able to set DNS under the interface like the other wireguard implementations.
Edegerouter X e50v2.deb latest. The command line doesn't seem to give an option to set a DNS = statement on the wireguard interface. DNS can be set via edgeos dhcp-server or local nameserver but the WG interface itself can't set dns via the cli. (As other implementations of wireguard can) Clients behind the VPN are unable to resolve dns names. ( For example, an xbox on a subnet whose traffic is being forwarded via modified table through the WG interface to an endpoint providing a masquerade) Also I don't see a way to refer to a config file and can only hardset configuration via edgeos WG interface. Is there another way to resolve dns for clients going through wireguard?