You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I want to access services on my NAS and my home network (192.168.0.0/24) remotely using a wireguard tunnel from my NAS to my VPS running k3s.
I have installed the operator on my VPS and successfully set up the wireguard server and the client/peer on my NAS and established the tunnel. I can access my NAS remotely using the wireguard IP (10.8.0.XXX).
However, I can't access my NAS using the IP from my home network (192.168.0.XXX). According to the guide I used, the server configuration also needs AllowedIPs for the NAS peer so that the wireguard server knows to route packets for 192.168.0.0/24 to this peer.
As far as I can tell, there currently is no way to set this part of the configuration.
Describe the solution you'd like
I'd like to set AllowedIPs directly in the spec of the WireguardPeer.
Describe alternatives you've considered
Not sure if any other way would make sense.
Thanks for opening this issue. Would you be interested in contributing to this project and implementing this feature? Otherwise I'll try to work on this the next time I touch this repo.
Is your feature request related to a problem? Please describe.
I want to access services on my NAS and my home network (
192.168.0.0/24
) remotely using a wireguard tunnel from my NAS to my VPS running k3s.I have installed the operator on my VPS and successfully set up the wireguard server and the client/peer on my NAS and established the tunnel. I can access my NAS remotely using the wireguard IP (
10.8.0.XXX
).However, I can't access my NAS using the IP from my home network (
192.168.0.XXX
). According to the guide I used, the server configuration also needsAllowedIPs
for the NAS peer so that the wireguard server knows to route packets for192.168.0.0/24
to this peer.As far as I can tell, there currently is no way to set this part of the configuration.
Describe the solution you'd like
I'd like to set
AllowedIPs
directly in thespec
of theWireguardPeer
.Describe alternatives you've considered
Not sure if any other way would make sense.
Additional context
Explanation how
AllowedIPs
also sets up routing: https://techoverflow.net/2021/07/09/what-does-wireguard-allowedips-actually-do/The text was updated successfully, but these errors were encountered: