-
Not sure if this is a bug somewhere but when I connect to the VPN then I can access all network and services over the VPN but I can't seem to ssh to the VPN/Wag server. I have to hop to another server and then ssh to the wag server from there. But I can't ssh directly from my laptop/client computer to the wag server. I can do this when I setup the original Wireguard (without Wag). I'm not sure if this is a security feature to prevent clients from accessing the wag server? The weird thing is I can ping the Wag server on both the private wireguard network and LAN network from my client but port 22 is inaccessible to the wag server. Is there a setting in the config to enable this access? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I found the solution to my own problem. After reviewing the user guide more I noticed the setting ExposePorts so I set it up with "22/tcp" and its working now ExposePorts: Expose ports on the VPN server to the client (adds rules to IPtables) example: [ "443/tcp", "100-200/udp" ] |
Beta Was this translation helpful? Give feedback.
I found the solution to my own problem. After reviewing the user guide more I noticed the setting ExposePorts so I set it up with "22/tcp" and its working now
ExposePorts: Expose ports on the VPN server to the client (adds rules to IPtables) example: [ "443/tcp", "100-200/udp" ]