When I connected a host to the app’s private network via fly.io’s wireguard endpoint, I notice that the host receives keepalive packet every second. This might be necessary for some highly-aggressive NAT scenarios but it’s killing my use case of connecting a low-bandwidth IoT device: the keepalive packets alone is consuming 6MB (74 bytes * 86400) of data every day.
Can we consider making the server->peer keepalive interval configurable when the tunnel is created, or increase the current interval to something less aggressive? A moderate increase to 5 seconds would mean my project can be feasible to run on fly.io.