From: Dimitar Vassilev <dimitar.vassilev@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: openwrt interface does not have a public key after upgrade from librecmc 1.4.8 to openwrt 21.02-rc2 to openwrt 21.02-rc2 ath79
Date: Fri, 11 Jun 2021 09:23:40 +0300 [thread overview]
Message-ID: <CAF+AZZXLYQtMA7j2ks2uk3SO5NnvSEW3VJ6zxwFG3SUGB736Ew@mail.gmail.com> (raw)
Greetings,
I upgraded an WNDR3800 from librecmc 1.4.8/ath71 to openwrt 21.02-rc2
ath79 and reapplied the librecmc 1.4.8 configuration. I'm seeing now
the interface configuration in the CLI and in Luci with all the keys,
but when I click on Status->Wireguard I get a message interface does
not have a public key.
I did have a look on
https://forum.openwrt.org/t/wireguard-interface-does-not-have-a-public-key/37549
and the other threads, but even when after applying the work-arounds
for DNS rebind protection still the same. My Luci is using self-signed
certs as well.
Any clues where to look further? I will be testing the device today to
see how it really works. I do have some overlapping IP ranges in the
configs that make me reluctant to test how site A machine works as a
client of site B, while the actual site A is running remotely over the
VPN.
Thanks,
Dimitar
next reply other threads:[~2021-06-11 6:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 6:23 Dimitar Vassilev [this message]
2021-06-14 7:51 ` Dimitar Vassilev
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=CAF+AZZXLYQtMA7j2ks2uk3SO5NnvSEW3VJ6zxwFG3SUGB736Ew@mail.gmail.com \
--to=dimitar.vassilev@gmail.com \
--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).