From: Roman Mamedov <rm@romanrm.net>
To: zrm <zrm@trustiosity.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: idle traffic considerations
Date: Sat, 30 Nov 2019 12:33:39 +0500 [thread overview]
Message-ID: <20191130123339.255a3424@natsu> (raw)
In-Reply-To: <86ffb110-50f2-de38-ec25-698b0232b09b@trustiosity.com>
On Fri, 29 Nov 2019 16:18:52 -0500
zrm <zrm@trustiosity.com> wrote:
> 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.
And read the small-print of mobile carrier plans, at least in our country[1]
they love so much to tally-up the user transferred data every hour, while also
rounding that up to nearest 250 KB, or even 1 MB. So even in the above
scenario they would bill for at least 250 KB/hour.
[1] http://tyumen.megafon.ru/tariffs/all/megafon-online.html
--
With respect,
Roman
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-11-30 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 10:29 idle traffic considerations Knuth
2019-11-29 21:18 ` zrm
2019-11-29 22:32 ` Lonnie Abelbeck
2019-11-30 7:33 ` Roman Mamedov [this message]
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=20191130123339.255a3424@natsu \
--to=rm@romanrm.net \
--cc=wireguard@lists.zx2c4.com \
--cc=zrm@trustiosity.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).