From: Adrian Duralia <adrian.duralia@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] middlebox using dkdp
Date: Sun, 14 Jan 2018 13:53:01 +0200 [thread overview]
Message-ID: <CANOA3aB-WuQOyUCb-iPHrApx=a8n8yb-FDTr4aHMLXt3A4Ktdg@mail.gmail.com> (raw)
In-Reply-To: <20180113212506.03497509@xeon-e3>
Thank you for the response!
While I'm not scared to add a lot of code in the app side, I wouldn't like
to reinvent the wheel. So, is there any framework or library that you think
it would be more appropiate to create a middlebox?
Thank you,
Adrian
On Sunday, January 14, 2018, Stephen Hemminger <stephen@networkplumber.org>
wrote:
> On Sat, 13 Jan 2018 22:10:55 +0200
> Adrian Duralia <adrian@techexpress.ro> wrote:
>
> > Hello,
> >
> > I'm curious if it would be possible to implement a middlebox device using
> > dpdk, that can filter & sign all traffic.
> > My goal is to be able to filter some packets and also to secure the
> > communication between a few computers (that cannot be updated/modified)
> on
> > the same LAN and I'm thinking to place such device in front on each
> > computer, leaving current network topology untouched.
> > I had a look at the existing samples in dpdk and l2fwd-crypto seems to
> be a
> > good place to start.
> >
> > Thank you,
> > Adrian
>
> DPDK is about sending and receiving packets. It has pieces that could be
> used
> to handle IP etc, but really 95% of the work would have to be in the
> application.
> So yes, you could build a middlebox; but lots left to do.
>
--
Adrian Duralia
Tel. +40723698531
Email: adrian.duralia@gmail.com
next prev parent reply other threads:[~2018-01-14 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 20:10 Adrian Duralia
2018-01-14 5:25 ` Stephen Hemminger
2018-01-14 11:53 ` Adrian Duralia [this message]
2018-01-14 17:12 ` Stephen Hemminger
2018-01-14 18:51 ` tom.barbette
2018-01-15 17:55 ` Adrian Duralia
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='CANOA3aB-WuQOyUCb-iPHrApx=a8n8yb-FDTr4aHMLXt3A4Ktdg@mail.gmail.com' \
--to=adrian.duralia@gmail.com \
--cc=stephen@networkplumber.org \
--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).