This looks like VyOS 1.3 config nodes. Can you probably try using the default keypair over a named one here? Maybe there is a config bug in non default keypairs.
@Viacheslav There’s not much of a network diagram. It is client (ubuntu) <–> sever (vyos). IPs and ports are per the above provided configs.
Regarding nat, the above is referenced in the standard wireguard setup and I do not necessarily need to do that at this time. Right now, the client and server will not even ping one another so there is something more fundamentally wrong. Are the config files correct? Is there anything additional that needs to be set in the vyos config, e.g. iptables?
Not without going through and stripping out the confidential information; most of the config will be irrelevant. Is the configuration above correct to configure wireguard? Is there anything additional that needs to be set in the vyos config, e.g. iptables? Where are the logs for wireguard?
well no idea if you having something blocked at the firewall for example. I believe that should all be set up automatically, but I explicitly open the listening ports up.
What is your default route and how are you pushing traffic down the tunnels, I use PBR to push certain address ranges through my wg tunnels for example.
show configuration commands | strip-private
show configuration | strip-private
It should log to syslog,however I believe you need to turn on debugging first before you would see any messages. There are easier ways to check what’s going wrong.
Can you share your config and explain your setup, I can test it in a lab then and check what’s going wrong.