wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: nekochan@tuta.io
To: wireguard@lists.zx2c4.com
Subject: Re: Wireguard massive amount data
Date: Fri, 24 Sep 2021 12:23:16 +0200 (CEST)	[thread overview]
Message-ID: <MkMK9M9--3-2@tuta.io> (raw)
In-Reply-To: <EBVVZQ.U9BF94AEV1NE@dumke.me>

This is sending telemetry to Fedora.


Sep 23, 2021, 13:47 by daniel@dumke.me:

> Hi,
>
> I am trying to connect to a Mullvad Wireguard Host with my Fedora Linux using nmcli, as soon as I up the connection (nmcli con up Mullvad) massive amounts of data are sent through the tunnel (according to wg 1.4 GiB in the first 20 secs).
>
> Any hints on why this huge amount of data is transfered?
>
> Daniel
>
> '''
> root@lenovo# wg
> interface: wg1
>  public key: zr0q0pxcOfSoiKWjXEfuHqM58GMjE4HBLr8FzQIHYxM=
>  private key: (hidden)
>  listening port: 40360
>  fwmark: 0xcbdf
>
> peer: C2TUHPoZlT08iceLM2coBDTbcfg9tTKrUt7tRBWP0nk=
>  endpoint: 45.8.223.195:51820
>  allowed ips: 0.0.0.0/0, ::/0
>  latest handshake: 20 seconds ago
>  transfer: 4.23 KiB received, 1.39 GiB sent
>  persistent keepalive: every 33 seconds
>
>
> root@lenovo# route
> Kernel IP Routentabelle
> Ziel            Router          Genmask         Flags Metric Ref    Use Iface
> default         _gateway        0.0.0.0         UG    50     0        0 wg1
> default         _gateway        0.0.0.0         UG    600    0        0 wlp0s12f0
> _gateway        0.0.0.0         255.255.255.255 UH    20050  0        0 wg1
> 10.0.2.0        0.0.0.0         255.255.255.0   U     600    0        0 wlp0s12f0
> 192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0
>
>
> '''
>


      parent reply	other threads:[~2021-09-24 20:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23 10:47 Wireguard massive amount data Daniel Dumke
2021-09-23 16:00 ` Jason A. Donenfeld
2021-09-24 10:23 ` nekochan [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=MkMK9M9--3-2@tuta.io \
    --to=nekochan@tuta.io \
    --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).