Development discussion of WireGuard
 help / color / mirror / Atom feed
* 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
@ 2021-06-11  6:23 Dimitar Vassilev
  2021-06-14  7:51 ` Dimitar Vassilev
  0 siblings, 1 reply; 2+ messages in thread
From: Dimitar Vassilev @ 2021-06-11  6:23 UTC (permalink / raw)
  To: WireGuard mailing list

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: 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
  2021-06-11  6:23 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 Dimitar Vassilev
@ 2021-06-14  7:51 ` Dimitar Vassilev
  0 siblings, 0 replies; 2+ messages in thread
From: Dimitar Vassilev @ 2021-06-14  7:51 UTC (permalink / raw)
  To: WireGuard mailing list

На пт, 11.06.2021 г. в 9:23 ч. Dimitar Vassilev
<dimitar.vassilev@gmail.com> написа:
>
> 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

For the record - this is a cosmetics issue in my case. Once I put the
uplink cable all came good. Disconnecting the VPN interface to avoid
greater worries also helps [tm]
Thanks,
Dimitar

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-06-14  7:53 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-11  6:23 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 Dimitar Vassilev
2021-06-14  7:51 ` Dimitar Vassilev

Development discussion of WireGuard

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.vuxu.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ http://inbox.vuxu.org/wireguard \
		wireguard@lists.zx2c4.com
	public-inbox-index wireguard

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.wireguard


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git