I'll try to make an example
cluster 1 node 1 has private IP1 and VIP1
cluster 2 node 2 has private IP2 and VIP2
each node uses it's private ip for outbound connections.
each node can receive inbound connection on its VIP.
so the wireguard config file for node1 is going to look like:
[peer]
I'm not sure of the proper way to resolve this issue with systemd-resolved, but
I was able to get to a more comfortable position in my case by disabling
systemd-resolved and manually configuring my DNS servers in /etc/resolv.conf.
Since the machine in question always sends all traffic over the
Since this is a home setup and my /56 might (will) change at some point, I
don't want to have to reconfigure my router, server, and clients. Unless
there's a way to dynamically reconfigure these devices in such a situation?
Original Message
On Sep 16, 2018, 12:47 PM, Toke
Hi,
I am trying to build an encrypted tunnel between two Kubernetes clusters.
The distribution of Kubernetes that I use is OpenShift, so I'll make my
examples in OpenShift although the problem that I'm seeing is really more
general.
The nodes that comprise the cluster in OpenShift have an IP in
Lane Russell writes:
> Since this is a home setup and my /56 might (will) change at some
> point, I don't want to have to reconfigure my router, server, and
> clients. Unless there's a way to dynamically reconfigure these devices
> in such a situation?
Ah, right; renumbering is a PITA. Hmm, you
Ivan,
I tried the SNAT idea, and still have issue.
here is an example configuration of one of the nodes:
[Interface]
ListenPort =
PrivateKey = ---
[Peer]
PublicKey = H09cwQeUUly2AIdTAhyr5zvzFK9bED0NYiKgJultYwE=
AllowedIPs = 10.128.2.0/23
Endpoint = 192.168.99.12:31112
PersistentKeepalive =
