From: nick black <dankamongmen@gmail.com>
To: Vitali Lovitch <vlovich@qualcomm.com>,
Johann Baudy <johann.baudy@gnu-log.net>,
David Miller <davem@redhat.com>
Cc: linux-net@vger.kernel.org
Subject: is PACKET_TX_RING expected to work on loopback?
Date: Thu, 6 Oct 2011 14:37:32 -0400 [thread overview]
Message-ID: <20111006183732.GA24014@qemfd.net> (raw)
Hey there. I'm developing an application which makes use of PACKET_TX_RING
(http://dank.qemfd.net/dankwiki/index.php/Omphalos), one mmap'd RX and TX
socket per interface. When I transmit on wireless/ethernet devices, the
packets flow out fine, and I get responses.
When I transmit on loopback, I can see the packets using tcpdump -i lo,
send() returns 0, and the frame is set back to TP_STATUS_AVAILABLE.
Checksums are properly set and the packets appear well-formed in Wireshark.
I can't seem to read the packets, however; neither the intended DNS server
(verified via dnsmasq -d and strace) nor my own socat udp-listen process
seem to get the packets.
Is PACKET_TX_RING expected to work on loopback?
Thanks!
--
nick black <nblack@nvidia.com>
"A main cause of the Roman Empire's fall was that–lacking zero–they had
no way to indicate successful termination of their C programs."
reply other threads:[~2011-10-06 19:04 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=20111006183732.GA24014@qemfd.net \
--to=dankamongmen@gmail.com \
--cc=davem@redhat.com \
--cc=johann.baudy@gnu-log.net \
--cc=linux-net@vger.kernel.org \
--cc=vlovich@qualcomm.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).