this post was submitted on 30 Dec 2023
1 points (100.0% liked)

WireGuard

3 readers
1 users here now

WireGuard - a fast, modern, secure VPN Tunnel.

founded 1 year ago
MODERATORS
 
This is an automated archive.

The original was posted on /r/wireguard by /u/departet on 2023-12-30 01:26:03+00:00.


Hi!

i have the following setup which worked until yesterday when one client got rebootet (pi shutdown, turned on again). I'm not quite sure what broke my setup because i didn't change anything at all.

Network 1 ( Raspberry Pi Client) - 192.168.178.0/24 10.0.20.5

Root Server working as the Server 10.0.20.1

Network 2 (Proxmox LXC container Client) - 192.168.20.1/24 10.0.20.2

I can ping any client in network 2 from network 1 and vice versa. I can also connect via ssh without any issue (connection feels sluggish/slow but i don't know if this was the case before already). I read about the mtu in such cases. As i said i didn't change any config and it was workign before hand. All clients and the server have an mtu as the following - 1420 on wg0 (wireguard) and 1500 on the main (and only connected) other interface. Would i need to change this on every device? Which setting should i try?

Trying to curl the router (both AVM Fritz!Box) webpage from one network to the other (same result on both directions):

root@plex:~# curl -v 192.168.178.1
*   Trying 192.168.178.1:80...
* Connected to 192.168.178.1 (192.168.178.1) port 80 (#0)
> GET / HTTP/1.1
> Host: 192.168.178.1
> User-Agent: curl/7.74.0
> Accept: */*
>
* Recv failure: Connection reset by peer
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer

If any addictional info is needing just hit me up!

no comments (yet)
sorted by: hot top controversial new old
there doesn't seem to be anything here