From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f41.google.com (mail-pg0-f41.google.com [74.125.83.41]) by dpdk.org (Postfix) with ESMTP id 35CBE44C3 for ; Sun, 14 Jan 2018 06:25:11 +0100 (CET) Received: by mail-pg0-f41.google.com with SMTP id j2so6638959pgv.3 for ; Sat, 13 Jan 2018 21:25:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=QXRZCFMmgpclk2w9rOn0zES4JnoxcMdHbna3aWaU2rY=; b=Z+4kGNLSdKMX/uDpqLwtGO5XZQpDbnvyCWmSwrvWiwyFSO0yJCbjKk4721PiZM+ZjC q0805q1F3Z/TD7c5CHTO+9EgjlaMO3ulneRBDTSU1iOUjgu5uVGp8f9LbexGOlS4fglH I0oyy5/eJ+XZULjxtm89MYMWxBBHgmhBX6HS/myY+c1oqOEkm3lKtCzKYJvsdCdx3jyZ dm83XOT4Qjj/26dRIqjoE+lOJx+d4+5O7GFviNHzitbndTPK4xOQq+6PB2Xf35K9O/tP K06thYaC35OfrPsuqeroS6xjshqMtjumAgOtuL4prT7Fp8aBJGGg6hJ/8esA1QCf3Bv2 0xVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=QXRZCFMmgpclk2w9rOn0zES4JnoxcMdHbna3aWaU2rY=; b=OmvdLyvF7SHe4hO8EK5KsXh5Hw2UfeFboEDof6y5zasrP4+uqvqGqz8W2rAktI0uuX A+jfAB22B7M5PetOnd+PF8Y6VViqpho54n4pvMA1UclfyfCoDxrvckesFZ+Oe7CHHWdI QIW8ETe1bq3zCP0QoR5zt974F844X6qE+OtY0Ur4yXuLze8ujwJ0deJvVzXVbQjH3INV rUXfu0n16A5yUN29+WUaEAL0ROj8UELguji/3PSLJ3SU3yMksQcfgCc7cCvxD2VQN3sq MOk3ZoiIiSmbtBWU1YYIFfTqILTphrb1CTiJnJZsVlRahP53g2BApwYn9N0FUi69tYsh QBIw== X-Gm-Message-State: AKwxyteY2APjlQBVAh29qGnRg2H99ixuHDl8vFWtPzi2fcDaY0jAe3G+ fsPIBJciy7bXb7+aWipQWatsBJ2Jf4A= X-Google-Smtp-Source: ACJfBouBxZXH0e1hQqG59Qk1G4+KY3R0lTN5/88ZN4J6D3nFgaOYYE1Labvn9+feuKq2/2NJYBvS4Q== X-Received: by 10.101.68.199 with SMTP id g7mr1678017pgs.21.1515907510240; Sat, 13 Jan 2018 21:25:10 -0800 (PST) Received: from xeon-e3 (204-195-18-133.wavecable.com. [204.195.18.133]) by smtp.gmail.com with ESMTPSA id v126sm21429709pfv.160.2018.01.13.21.25.09 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 13 Jan 2018 21:25:09 -0800 (PST) Date: Sat, 13 Jan 2018 21:25:06 -0800 From: Stephen Hemminger To: Adrian Duralia Cc: users@dpdk.org Message-ID: <20180113212506.03497509@xeon-e3> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] middlebox using dkdp X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jan 2018 05:25:11 -0000 On Sat, 13 Jan 2018 22:10:55 +0200 Adrian Duralia 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.