wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Christoph Loesch <wireguard-mail@chil.at>
To: <wireguard@lists.zx2c4.com>
Subject: WireGuard connection without interface-address / linknet
Date: Wed, 3 Nov 2021 14:45:58 +0100	[thread overview]
Message-ID: <1da52141-2cca-9ebb-e415-af471b14e74e@chil.at> (raw)


(mail resent without URLs, because it got filtered by moderation)

I am using WireGuard on an OpenWRT VM as server for clients basically to reach the server's internal LAN at

As clients I currently use different WireGuard implementations like:
- Ubiquiti EdgeRouter (EdgeOS v2 based on Debian/stretch) with package from github/WireGuard/wireguard-vyatta-ubnt
- Mikrotik RouterOS v7.1 with Mikrotik own (at the moment beta) implementation
- Windows 10 Client from wireguard website

Server config looks like this:

config interface 'wg0'
         option proto 'wireguard'
         option private_key 'cNT...8Hc='
         option listen_port '51820'
         list addresses ''
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 ''
         list allowed_ips ''

Client config looks like this:

PrivateKey = mDk...uVs=
Address =
PublicKey = 1sy...IkU=
PresharedKey = Dle...ozI=
AllowedIPs =,
Endpoint = server.mydomain.at:51820
PersistentKeepalive = 25

Clients should just be able to reach the server's subnet and this subnet should be able to reach clients at (in this one example)
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,

             reply	other threads:[~2021-11-03 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 13:45 Christoph Loesch [this message]
2021-11-03 16:03 ` WireGuard connection without interface-address / linknet Christoph Loesch
2021-11-03 16:18   ` Jason A. Donenfeld
2021-11-03 16:39     ` Christoph Loesch
  -- strict thread matches above, loose matches on Subject: below --
2021-11-02 22:15 Christoph Loesch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1da52141-2cca-9ebb-e415-af471b14e74e@chil.at \
    --to=wireguard-mail@chil.at \
    --cc=wireguard@lists.zx2c4.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).