idle traffic considerations

Lonnie Abelbeck lists at
Fri Nov 29 23:32:48 CET 2019

> On Nov 29, 2019, at 3:18 PM, zrm <zrm at> wrote:
> On 10/17/19 06:29, Knuth wrote:
>> Hey,
>> we are planning to deploy certain devices with an embedded sim cards in different countries across the globe, for maintenance we need to be able to connect to the devices with ssh.
>> Since the sim cards only provide us with a private IPv4 behind NAT (because apparently IPv6 is still hard...) we need to reverse the connection process to our control system,
>> at the moment we consider doing this with wireguard (we are aware of the "pre" release status), since we had good experiences with it on other similar setups.
>> To calculate some rough estimated costs for the mobile connection traffic volume, i'd love to know if there is a way to calculate the amount of traffic caused by an idle wireguard connection kept alive since we would be charged per MByte transferred.
>> Or do we simply have to setup a few test subjects and monitor it over a longer time, which in itself could be error prone.
>> Thanks for your time
>> Knuth
> Ballpark estimate, round a keepalive packet to about a hundred bytes. You're also going to get a re-keys, call those two hundred bytes. If you have a keepalive every 30 seconds and a re-key every 120 seconds, that's around 18KB per hour per peer in each direction.

I had a similar use case as Knuth described, zrm's estimate is right on target.

Using a Netgear LB1121 as a 4G/LTE Endpoint, native IPv4-only behind NAT to a static IPv4 public server.

## 4G/LTE Endpoint
PersistentKeepalive = 25

## Static Endpoint
PersistentKeepalive = 0

When idle the WireGuard VPN consumes less than 0.5 MB/day of data.


More information about the WireGuard mailing list