[Solved] Wireguard blocks ssh/smb :(
[Solved] Wireguard blocks ssh/smb :(
In this tutorial, you will set up WireGuard on an Ubuntu 22.04 server, and then configure another machine to connect to it as a peer using both IPv4 and IPv6…
This was manually solved, I didn't check any other comment till the issue was fixed.
Take a look at my comment.
Thank you all for helping!
Hello.
I have wireguard set but the second it runs, services like ssh (22) and smb (455/445?) stop working.
nmap thinks my system is down.
Here is my config, I followed debian's guide since my server is Deb12:
[Interface]
Address = 192.168.1.120/24
SaveConfig = true
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -t nat -A POSTROUTING -o wlp1s0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -t nat -D POSTROUTING -o wlp1s0 -j MASQUERADE
ListenPort = 51820
PrivateKey = XXX
[Peer]
PublicKey = xxx
AllowedIPs = 192.168.1.230/32
Endpoint = 192.168.1.230:50104
No extra config was made.
Solved:
IP Table: Server : 192.168.1.120 / wg0 : 10.0.0.1 Client : 192.168.1.230 / wg0 :10.0.0.2
Server:
[Interface] Address = 10.0.0.1/24 SaveConfig = true PostUp = iptables -t nat -I POSTROUTING -o wlp1s0 -j MASQUERADE PostUp = ip rule add table 200 from 192.168.1.230 PostUp = ip route add table 200 default via 192.168.1.1 PreDown = iptables -t nat -D POSTROUTING -o wlp1s0 -j MASQUERADE PreDown = ip rule delete table 200 from 192.168.1.230 PreDown = ip route delete table 200 default via 192.168.1.1 ListenPort = 51820 PrivateKey = XXX [Peer] PublicKey = yyy AllowedIPs = 0.0.0.0/0Client:
[Interface] Address = 10.0.0.2/24 PrivateKey = YYY [Peer] AllowedIPs = 10.0.0.0/24 Endpoint = 192.168.1.120:51820 PublicKey = xxxCould be your routing rules? Here's what I use and it routes to anything inside my home network:
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADEJust be sure to replace
eth0with the name of your adapter before you try it.Edit:
Almost forgot, I've also enabled routing on my server as well; here are the steps I took to enable that:
To configure forwarding, open the /etc/sysctl.conf file on your Wireguard Server using nano or your preferred editor:
sudo nano /etc/sysctl.confIf you are using IPv4 with WireGuard, add the following line at the bottom of the file:
net.ipv4.ip_forward=1If you are using IPv6 with WireGuard, add this line at the bottom of the file:
net.ipv6.conf.all.forwarding=1If you are using both IPv4 and IPv6, ensure that you include both lines. Save and close the file when you are finished.
To read the file and load the new values for your current terminal session, run:
sudo sysctl -pOutput:
net.ipv6.conf.all.forwarding = 1 net.ipv4.ip_forward = 1Now your WireGuard Server will be able to forward incoming traffic from the virtual VPN ethernet device to others on the server and its LAN (if the LAN subnet is included in the
AllowedIPsin the Wireguard config)Unfortunely that didn't work.
The WG server is also servicing SSH and SMB.
are your services accessible through the wg interface on the server ? Try with nmap -Pn -A -T4 -p CHANGEME_TO_SSH_OR_SMB IPADDR_OF_WG_NIC
I am not sure but your AllowedIPs and Endpoint should be in separate subdomain right?
Perhaps your samba system isn't listening on your Wireguard IP?