wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Knuth <knuth@ethergeist.de>
To: wireguard@lists.zx2c4.com
Subject: idle traffic considerations
Date: Thu, 17 Oct 2019 12:29:39 +0200	[thread overview]
Message-ID: <48f2826293c5cf93d123d8789b6afc15@ethergeist.de> (raw)

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

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply	other threads:[~2019-11-27  9:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17 10:29 Knuth [this message]
2019-11-29 21:18 ` idle traffic considerations zrm
2019-11-29 22:32   ` Lonnie Abelbeck
2019-11-30  7:33   ` Roman Mamedov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48f2826293c5cf93d123d8789b6afc15@ethergeist.de \
    --to=knuth@ethergeist.de \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).