wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: John <graysky@archlinux.us>
To: Kalin KOZHUHAROV <me.kalin@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Syntax for iperf3 to use over pair wireguard interfaces on a LAN?
Date: Tue, 18 Dec 2018 17:45:48 -0500	[thread overview]
Message-ID: <CAO_nJAaxt5TmkVe1JJf1c1Aw2fD0_ya4TcSPyT1D3RNtHrn=+g@mail.gmail.com> (raw)
In-Reply-To: <CAKXLc7ewkUKnVLugQAzqWbRxb8w1NaDBV4_DtAJeBSVyggveOA@mail.gmail.com>

My mistake... I opened 500/udp for both sides... a quick fix was to
allow all from 10.0.9.0/24 and it works. Thank you for the reply.

On foo:
% iperf3 -s
                                     :(
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 10.0.9.16, port 54812
[  5] local 10.0.9.15 port 5201 connected to 10.0.9.16 port 54814
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec   102 MBytes   854 Mbits/sec
[  5]   1.00-2.00   sec  98.1 MBytes   823 Mbits/sec
[  5]   2.00-3.00   sec   107 MBytes   901 Mbits/sec
[  5]   3.00-4.00   sec   107 MBytes   894 Mbits/sec
[  5]   4.00-5.00   sec   104 MBytes   870 Mbits/sec
[  5]   5.00-6.00   sec   101 MBytes   848 Mbits/sec
[  5]   6.00-7.00   sec   107 MBytes   899 Mbits/sec
[  5]   7.00-8.00   sec   107 MBytes   901 Mbits/sec
[  5]   8.00-9.00   sec   107 MBytes   901 Mbits/sec
[  5]   9.00-10.00  sec  98.1 MBytes   823 Mbits/sec
[  5]  10.00-10.04  sec  4.50 MBytes   901 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-10.04  sec  1.02 GBytes   872 Mbits/sec                  receiver

On bar:
% iperf3 -c 10.0.9.15
Connecting to host 10.0.9.15, port 5201
[  5] local 10.0.9.16 port 54814 connected to 10.0.9.15 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   107 MBytes   898 Mbits/sec    0    361 KBytes
[  5]   1.00-2.00   sec  98.0 MBytes   822 Mbits/sec    0    361 KBytes
[  5]   2.00-3.00   sec   107 MBytes   901 Mbits/sec    0    361 KBytes
[  5]   3.00-4.00   sec   107 MBytes   898 Mbits/sec    0    442 KBytes
[  5]   4.00-5.00   sec   100 MBytes   840 Mbits/sec    0    465 KBytes
[  5]   5.00-6.00   sec   105 MBytes   880 Mbits/sec    0    488 KBytes
[  5]   6.00-7.00   sec   107 MBytes   897 Mbits/sec    0    513 KBytes
[  5]   7.00-8.00   sec   107 MBytes   900 Mbits/sec    0    513 KBytes
[  5]   8.00-9.00   sec   107 MBytes   901 Mbits/sec    0    513 KBytes
[  5]   9.00-10.00  sec  98.2 MBytes   823 Mbits/sec    0    513 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  1.02 GBytes   876 Mbits/sec    0             sender
[  5]   0.00-10.04  sec  1.02 GBytes   872 Mbits/sec                  receiver

iperf Done.

On Tue, Dec 18, 2018 at 4:49 PM Kalin KOZHUHAROV <me.kalin@gmail.com> wrote:
>
>
>
> On Tue, 18 Dec 2018, 20:50 John <graysky@archlinux.us wrote:
>>
>> On bar:
>> % iperf3 -c 10.0.9.15 -B 10.0.9.16
>> iperf3: error - unable to connect to server: Connection timed outa
>
> iperf -c 10.0.9.15
>
> Also for the server, omit ipaddr, it listens to all interfaces by default.
>
> Kalin.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      parent reply	other threads:[~2018-12-18 22:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 19:49 Syntax for iperf3 to use over pair wireguard interfaces on a LAN? John
2018-12-18 21:48 ` Kalin KOZHUHAROV
2018-12-18 22:42   ` John
2018-12-18 22:45   ` John [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='CAO_nJAaxt5TmkVe1JJf1c1Aw2fD0_ya4TcSPyT1D3RNtHrn=+g@mail.gmail.com' \
    --to=graysky@archlinux.us \
    --cc=me.kalin@gmail.com \
    --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).