DPDK usage discussions
 help / color / mirror / Atom feed
From: Andrew Wang <andrw.wng@gmail.com>
To: roszenrami@gmail.com
Cc: users@dpdk.org
Subject: Re: [dpdk-users] AF_PACKET pmd and linux networking stack
Date: Sat, 25 Aug 2018 10:43:39 -0400	[thread overview]
Message-ID: <CANEosPB39FjBb0LakRRQBmnJ8zFWAGtkgA1wGeODvOQFUSHELQ@mail.gmail.com> (raw)
In-Reply-To: <CAKoUArk_aXANSNCKkJ=ujbH8m6KPHjfB9yo_CgzqRbhKsLUWuw@mail.gmail.com>

Rami

Thank you for the suggestion. Later I found it was a problem with the dpdk
app (setting incorrect mac address).

Andrew

On Fri, Aug 17, 2018 at 5:15 PM Rami Rosen <roszenrami@gmail.com> wrote:

> Hi Andrew,
> I am not sure at all that there is a way of achieving it, because of the
> way AF_PACKET works.
> But couldn't you achieve your goal with running DPDK L2FWD or DPDK L3FWD
> application ? In such a case, when not working in promiscuous mode, it
> seems that this will avoid processing of the packets by the kernel. See the
> l2fwd and l3fwd sections in DPDK samples guide.
>
> Regards,
> Rami Rosen
>
>
>
> בתאריך יום ד׳, 8 באוג׳ 2018, 19:57, מאת Andrew Wang ‏<andrw.wng@gmail.com
> >:
>
>> Hi
>>
>> Is there a way of preventing the linux kernel networking stack from
>> handling packets when using the AF_PACKET pmd?
>>
>> Our DPDK app is running on a node that is attracting traffic for a VIP and
>> for which it has a blackhole routing rule (to drop all the incoming
>> packets
>> for that VIP).
>>
>> The intention was to have our DPDK app (running on AF_PACKET pmd for now -
>> we're still developing the app) grab those packets, process and send them
>> out (with a different address).
>>
>> Right now we can actually see those packets in our dpdk app, we process
>> them, give them a different address, but it seems that the linux kernel
>> networking stack is still dropping them.
>>
>> When the blackhole rule is removed we see the outgoing packet with correct
>> header, but also a destination unreachable message is sent out, suggesting
>> the kernel is also handling the packet. We see the same behavior when
>> using
>> iptables to drop packets (instead of blackhole route).
>>
>> Any suggestions appreciated.
>>
>> Thanks
>> Andrew
>>
>

      reply	other threads:[~2018-08-25 14:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08 16:57 Andrew Wang
2018-08-17 21:15 ` Rami Rosen
2018-08-25 14:43   ` Andrew Wang [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=CANEosPB39FjBb0LakRRQBmnJ8zFWAGtkgA1wGeODvOQFUSHELQ@mail.gmail.com \
    --to=andrw.wng@gmail.com \
    --cc=roszenrami@gmail.com \
    --cc=users@dpdk.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 NNTP newsgroup(s).