@kirby @menherahair

> No it's not my fault

you can't be certain of that if you can't explain what's actually happening under the hood to cause this :puniko_shrug:

> other devices

what other devices? I've had stuff like this happen with shitty WiFi connections where the wireless device puts the hardware to sleep and can't be reached until it instigates outgoing traffic

> on the network

you mean the wireguard network?

> unless something communicates with it first

that sounds like a firewall on the remote network to me HOWEVER given that you can establish an outgoing connection from you -> them in the first place it doesn't seem to add up

basically for an incoming (not outgoing) connection to be allowed to be established initially but then to get killed *while still active* would basically constitute an active measure AGAINST keepalive mechanisms on the part of the remote firewall