From: Peter Libassi <peter@libassi.se>
To: wireguard@lists.zx2c4.com
Subject: FreeBSD wireguard wg-quick remote IP address assignment is incorrect
Date: Sun, 23 Feb 2020 09:00:33 +0100 [thread overview]
Message-ID: <01F8520D-6F1E-4DFB-BC07-80D9838EF35D@libassi.se> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1109 bytes --]
local wg interface does not respond due to the wg-quick script sets up the interface by reusing the local address as the remote address in the ifconfig command:
root@bsd2:~ # wg-quick up wg0
[#] wireguard-go wg0
INFO: (wg0) 2020/02/20 09:45:16 Starting wireguard-go version 0.0.20200121
[#] wg setconf wg0 /tmp/tmp.87viEAsK/sh-np.YdRfI6
[#] ifconfig wg0 inet 192.168.2.2 192.168.2.2 alias
On linux setting up an IP address on a tun interface does not require a remote address:
[root@vpn2 wireguard]# wg-quick up wg0
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add 192.168.2.2/24 dev wg0
In the wg-quick script function add_addr() is where the assignment is made:
cmd ifconfig "$INTERFACE" inet "$1" "${1%%/*}" alias
I verifed this by replacing remote address with localhost:
cmd ifconfig "$INTERFACE" inet "$1" "127.0.0.1" alias
Now local ping works. You can give any address I suppose since the ”remote address” of the ifconfig of a tun interface is not really used by wireguard.
I also filed this as FreeBSD bug 244330.
/Peter
[-- Attachment #1.2: Type: text/html, Size: 1619 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2020-02-23 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 8:00 Peter Libassi [this message]
2020-02-23 11:37 ` Jason A. Donenfeld
2020-02-23 13:25 ` Peter Libassi
2020-02-23 15:32 ` Jason A. Donenfeld
2020-02-25 6:07 ` Peter Libassi
[not found] <4c6af2b0-62bc-84bd-f1ec-ce11a152d348@gmail.com>
2020-02-25 13:08 ` Peter Libassi
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01F8520D-6F1E-4DFB-BC07-80D9838EF35D@libassi.se \
--to=peter@libassi.se \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).