-
Notifications
You must be signed in to change notification settings - Fork 34
Open
Description
Hello,
I'm having issue with this chart.
From what I see, the keys present in the POD are different from those specified in the yaml file.
kubectl get logs reports
wgrs-wireguard-xqvv9 sysctls net.ipv4.ip_forward = 1
wgrs-wireguard-xqvv9 sysctls net.ipv4.conf.all.forwarding = 1
wgrs-wireguard-xqvv9 wireguard [#] ip link add wg0 type wireguard
wgrs-wireguard-xqvv9 wireguard [#] wg setconf wg0 /dev/fd/63
wgrs-wireguard-xqvv9 wireguard [#] ip -4 address add 172.32.32.1/24 dev wg0
wgrs-wireguard-xqvv9 wireguard [#] ip link set mtu 1290 up dev wg0
wgrs-wireguard-xqvv9 wireguard [#] wg set wg0 private-key /etc/wireguard/privatekey && iptables -t nat -A POSTROUTING -s 172.32.32.0/24 -o eth0 -j MASQUERADE
wgrs-wireguard-xqvv9 wireguard Public key 'dRH4Ms/h+H3BmT/J.....'
But in the yaml file, I specified:
wireguard:
serverAddress: 172.32.32.1/24
serverCidr: 172.32.32.0/24
natAddSourceNet: true
allowWan: false
clients:
- AllowedIPs: 172.32.32.2/32
PublicKey: cbrG5zpfV1BIZZk...
PresharedKey: KmkotoRaR1B...
wg show wg0 shows
interface: wg0
public key: cbrG5zpfV1BIZZkJNb3OYIilOg4Xdvp/juMNS27/6zA=
private key: (hidden)
listening port: 35008
Another things I note, is that the pod is very hard to debug, I can't get to any shell and kubectl exec gives errors in reading /etc/wireguard
The project seems promising but more focus should be put into documentation (also a way to debug)
--
Roberto
Metadata
Metadata
Assignees
Labels
No labels