It seems Wireguard is unexpectedly redirecting traffic to certain ports.
It seems Wireguard is unexpectedly redirecting traffic to certain ports.
Hello! Your WireGuard is up and functioning properly for basic tasks like pinging and speed testing. However, web browsing isn't working and several services have stopped responding. You're using it mainly to tunnel traffic for Minecraft servers, but local connections aren't reaching the authentication servers. Port forwarding seems to be missing—when you try to connect from your host's IP, nothing appears, while locally the client can reach the server. You mentioned port forwarding settings in both sysctl.conf and iptables, but they don't seem to apply correctly. I'm here to help clarify how to set up forwarding properly.
I'm uncertain about the multiple entries. Each guide appears to combine them into one statement. It seems only the first command is running, opening the port for connection but skipping the rest. This would block access to the server on enp3s0 and cut off internet. Can you verify if traffic reaches 10.66.66.1 after connecting? Also check if your host OS has a firewall service like firewalld instead of iptables directly. If it does, using that is usually safer as it handles rule changes more smoothly.
Thanks! Your system has the firewall enabled but permits port 51820 for TCP/UDP traffic across both IPv4 and IPv6. You’re able to reach your host via WireGuard and even access Google through it, which confirms the connection is functional. Your base Ubuntu server runs a minimal setup with no firewall, so the issue likely lies in the specific configuration or service settings.
Server config: [Interface] PostUp = iptables -t nat -A POSTROUTING -s 10.0.0.0/24 -o eth0 -j MASQUERADE Address = 10.66.66.1/24,fd42:42:42::1/64 ListenPort = 58120 PrivateKey = x
Client info: ga1 [Peer] PublicKey = x PresharedKey = x AllowedIPs = 10.66.66.2/32,fd42:42:42::2/128