Hi, I am using WireGuard on an OpenWRT VM as server for clients basically to reach the server's internal LAN at 10.5.44.0/24
As clients I currently use different WireGuard implementations like: - Ubiquiti EdgeRouter (EdgeOS v2 based on Debian/stretch) with package from: https://github.com/WireGuard/wireguard-vyatta-ubnt/releases - Mikrotik RouterOS v7.1 with Mikrotik own (at the moment beta) implementation - Windows 10 Client using https://download.wireguard.com/windows-client/wireguard-installer.exe Server config looks like this: config interface 'wg0' option proto 'wireguard' option private_key 'cNT...8Hc=' option listen_port '51820' list addresses '172.27.0.1/16' config wireguard_wg0 option description 'router-test' option public_key 'qT5...YGo=' option preshared_key 'Dle...ozI=' option persistent_keepalive '25' option route_allowed_ips '1' list allowed_ips '172.27.34.28/32' list allowed_ips '10.34.28.0/24' Client config looks like this: [Interface] PrivateKey = mDk...uVs= Address = 172.27.34.28 [Peer] PublicKey = 1sy...IkU= PresharedKey = Dle...ozI= AllowedIPs = 172.27.0.1/32,10.5.44.0/24 Endpoint = server.mydomain.at:51820 PersistentKeepalive = 25 Clients should just be able to reach the server's 10.5.44.0/24 subnet and this subnet should be able to reach clients at (in this one example) 10.34.28.0/24 Now this works all well as expected but I would like to omit using the 172.27.* addresses/linknet if possible because I dont really need/use this as it is only defined for the WireGuard tunnel itself. On the EdgeRouter this also works perfectly fine if I remove the 172.27.* address on both sides. It is still possible to reach the other end repestively. On the Mikrotik device and on the Windows client (using exact same configuration) it does not work as soon as I remove just the 172.27. address/linknet from configuration. (I didn't test other clients yet) I guess on the EdgeRouter this works because I set: set interfaces wireguard wg0 **route-allowed-ips true** - so the corresponding routes are added. The Mikrotik device and the Windows client do not offer such an option, so those routes have to be added manually I guess? But why does that work "out of the box" as soon as I add any linknet (172.27.* in my example) for the tunnel itself to the configuration? Is this a fault in the implementation and I should file a bug report or is that expected that way? (it's not a big issue using the linknet, I am just curious and would like avoid using it if it is not neccessarily required) Thanks for any thoughts and kind regards, Christoph
