Thanks Lonnie and yes I will be using the new option.
I realised afterwards that I already had fixed this problem in the new release
but had just forgotten about it.
Its basic routing and I am kicking myself. Old age ☹
Regards
Michael Knill
On 13/3/19, 12:25 am, "Lonnie Abelbeck" wrote:
Yes, if 172.30.253.0/24 was the OpenVPN subnet on the remote WG peer, what you
did would have made sense, assuming your OpenVPN subnets across peers are
unique.
Think of the WireGuard "AllowedIPs" setting as AllowedIPs_into_this_peer . The
corresponding figurative "AllowedIPs_out_of_this_peer"
Damn it I found the problem.
When using OpenVPN and Wireguard, I added this to the Wireguard config:
AllowedIPs = 172.29.253.1/32, 172.30.253.0/24 (wg peer,openvpn subnet)
This was done to allow OpenVPN to Wireguard connectivity however it ended up
putting a route into the routing table for the op
