From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Rene Vrolijk <rrvrolijk@gmail.com>, xdp-newbies@vger.kernel.org
Subject: Re: XDP use for data diodes
Date: Thu, 31 Aug 2023 11:43:03 +0200 [thread overview]
Message-ID: <878r9rv97c.fsf@toke.dk> (raw)
In-Reply-To: <0CF95803-5B47-4793-9FE4-F20F3312D075@gmail.com>
Rene Vrolijk <rrvrolijk@gmail.com> writes:
> Hi,
>
> I have a question about the use of XDP. A little warning upfront, i’m
> not a programmer or network manager so my question could be strange.
> Sorry for that.
>
> I created a Github to teach people about the basics of data diodes on
> https://github.com/vrolijk/osdd Via this git i explain student in 2
> hours the basics and how to to get their hands on a data diode,
> insight in UDP packetloss with normal operating systems, setup Ubuntu
> to use as a proxy and send data with three different use cases. All
> with publicly available hard and software and with complicated
> scripting.
>
> My (noob) question:
> There is a major issue when using Ubuntu and packetloss in the
> Linuxkernel. Is it possible to use XDP to prevent packetloss when
> sending data over an unidirectional connection between 2 Ubuntu
> machines via a data diode? Is it possible to help me (and the
> students) via an example how to configure this on the 2 machines?
While XDP can help alleviate some causes of packet loss, it is always
possible to overwhelm a receiver. And XDP is certainly not noob
friendly, so I'm not sure I'd recommend it as a tool for people who are
just starting out experimenting with network programming.
The XDP tutorial is probably still the best resource we have for getting
started with XDP, so I'd suggest you take a look at that:
https://github.com/xdp-project/xdp-tutorial
-Toke
prev parent reply other threads:[~2023-08-31 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 14:03 XDP use for data diodes Rene Vrolijk
2023-08-31 9:43 ` Toke Høiland-Jørgensen [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=878r9rv97c.fsf@toke.dk \
--to=toke@redhat.com \
--cc=rrvrolijk@gmail.com \
--cc=xdp-newbies@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).