Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Antonio Quartulli <a@unstable.cc>
To: Germano Massullo <germano.massullo@gmail.com>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Mini PCIE HW accelerator for ChaCha20
Date: Mon, 17 Jun 2024 13:42:50 +0200	[thread overview]
Message-ID: <8f366adc-89a5-4b81-9a4f-8bcb1d08aad3@unstable.cc> (raw)
In-Reply-To: <ef44089b-1060-458f-906b-45fe682c6a10@gmail.com>

Hi,

On 17/06/2024 13:08, Germano Massullo wrote:
> Il 17/06/24 11:45, Antonio Quartulli ha scritto:
>> Have you tried running the test between a client, behind the omnia 
>> turris and the wg server?
> 
> Do you mean a configuration where the Turris Omnia is not acting as 
> Wireguard peer/gateway? I could do it but I prefer not

No no. Sorry I might have used the wrong words.

Basically you should keep the wg setup as it is, but instead of running 
the iperf client on the turris, you run it on another host that uses the 
turris as gateway (as if the turris was the gateway of a LAN).

This way the tunnel is still established between the turris and the 
server (which is what you want to test), but you move the traffic 
generation to a different host (which is most likely what you will have 
in a real scenario).

I hope I clarified your doubt.

Regards,


-- 
Antonio Quartulli

  reply	other threads:[~2024-06-17 11:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 14:11 Germano Massullo
2024-06-16 13:47 ` Max Schulze
2024-06-16 14:59   ` Germano Massullo
2024-06-16 19:00     ` Max Schulze
2024-06-17  9:21       ` Germano Massullo
2024-06-17  9:45         ` Antonio Quartulli
2024-06-17 11:08           ` Germano Massullo
2024-06-17 11:42             ` Antonio Quartulli [this message]
2024-06-17 12:32               ` Germano Massullo
2024-06-17 12:41                 ` Roman Mamedov
2024-06-17 14:31                   ` Germano Massullo

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=8f366adc-89a5-4b81-9a4f-8bcb1d08aad3@unstable.cc \
    --to=a@unstable.cc \
    --cc=germano.massullo@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).