nodes with same subnet in cluster

[andypeng2015]

Hi,
Thanks for the great work on kilo. I added a new backend to work with VM instead of pod.

And I try to setup 2 nodes with same subnet 192.168.130/0/24 in one cluster, but I cannot ping VM behind the bridge, any suggestion? Thanks.

WireGuard subnet 192.168.2.0/24
Node subnet 192.168.130.0/24

# Node-X
# Private IP 192.168.130.2/32
# wireguard
[Interface]
ListenPort = 51820
PrivateKey = xxx

[Peer]
PublicKey = xxx
AllowedIPs = 192.168.130.5/32, 192.168.2.1/32, 192.168.130.15/32
Endpoint = 10.0.0.5:51820
PersistentKeepalive = 30
# ip route
default via 10.0.0.251 dev ens0 proto dhcp src 10.0.0.2 metric 101
10.0.0.0/24 dev ens0 proto kernel scope link src 10.0.0.2 metric 101
192.168.2.0/24 dev wg0 proto kernel scope link src 192.168.2.2
192.168.130.0/24 dev brq0 proto kernel scope link src 192.168.130.2
192.168.130.5 via 192.168.2.1 dev wg0 proto static onlink
192.168.130.15 via 192.168.2.1 dev wg0 proto static onlink


# Node-Y
# Private IP 192.168.130.5/32
# wireguard
[Interface]
ListenPort = 51820
PrivateKey = xxx

[Peer]
PublicKey = xxx
AllowedIPs = 192.168.130.2/32, 192.168.130.1/32, 192.168.2.2/32, 192.168.130.12/32, 192.168.130.20/32
Endpoint = 10.0.0.2:51820
PersistentKeepalive = 30
# ip route
default via 10.0.0.251 dev ens0 proto dhcp src 10.0.0.5 metric 101
10.0.0.0/24 dev ens0 proto kernel scope link src 10.0.0.5 metric 101
192.168.2.0/24 dev wg0 proto kernel scope link src 192.168.2.1
192.168.130.0/24 dev brq0 proto kernel scope link src 192.168.130.5
192.168.130.1 via 192.168.2.2 dev wg0 proto static onlink
192.168.130.2 via 192.168.2.2 dev wg0 proto static onlink
192.168.130.12 via 192.168.2.2 dev wg0 proto static onlink
192.168.130.20 via 192.168.2.2 dev wg0 proto static onlink

Thanks @squat