Therefore client-to-server is the only solution. Site-2-site solution was my goal but I don't really have a choice due to lack of external IP or port forwarding on Mikrotik side Some things to take care of, place the mikrotiks subnet in the allowed IP's (and enable routing) so that the ddwrt server knows how to reach the mikrotiks subnet ( you maybe did already as I suspect that 192.168.88.0/24 is the mikrotiks subnet), take care of the mikrotiks firewall to enable traffic, take care of the mikrotiks WG client to also route the subnet of the DDWRT server via the WG tunnel and lastly the clients of the mikrotik subnet (your Windows PC's) must allow traffic from other subnets, clients itself also have a firewall. How to setup for ddwrtddwrt is described in the Advanced setup guide: that might give you some pointers how to setup the mikrotik router. What you want is a site-to-site setup so not only from the client to the server but also the other way around. Posted: Tue 7:26 Post subject: Re: WireGuard - one way communication between LAN networks

It looks like routing is being set automatically by dd-wrt(?) I can reach PC's sitting on Mikrotik LAN from dd-wrt ssh console I can't reach PC's sitting on Mikrotik LAN from dd-wrt LAN PC's I can reach PC's sitting on dd-wrt LAN from Mikrotik LAN PC's I have set up static routing on MikrotikĪfter a long battle I was able to configure VPN connection although having following issue: dd-wrt R44809 acting as a Wireguard server Mikrotik router with Wireguard support 7beta acting as a WireGuard client Posted: Tue 2:24 Post subject: WireGuard - one way communication between LAN networks

Mikrotik wireguard firewall