From: Erik Kazandjian <erik.kazandjian@accelleran.com>
To: xdp-newbies@vger.kernel.org
Subject: XDP soxkets over loopback
Date: Wed, 9 Feb 2022 17:29:07 +0100 [thread overview]
Message-ID: <83a47cc3-8199-cd59-9b22-c084b19dd90b@accelleran.com> (raw)
Hi,
I've implemented an XDP socket that sends a simple UDP message to a
server that listens on a specific port. I therefore create the packet
with ethernet header, ip header, udp header and payload. This all works
fine on an interface which is not the loopback interface, however if I
try to use the loopback interface I see that my packet is send (I can
see it in wireshark, all checksum are correct ), however the program the
server never receives that packet. If I use netcat as a client to send
to the server I see exactly the same data in wireshark as when I send it
with XDP but in that case the packet arrives in the server.
My question is can you send over the loopback interface XDP TX to a
standard udp socket or is this not possible ?Do I have to configure my
loopback interface in a spacial way ?
All tips are welcome
Erik
reply other threads:[~2022-02-09 16:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=83a47cc3-8199-cd59-9b22-c084b19dd90b@accelleran.com \
--to=erik.kazandjian@accelleran.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).