From owner-freebsd-net@freebsd.org Wed Mar 21 20:50:28 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A7FBF65E76 for ; Wed, 21 Mar 2018 20:50:28 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 08ACA87359 for ; Wed, 21 Mar 2018 20:50:27 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id AAEB53AEF8 for ; Wed, 21 Mar 2018 13:50:26 -0700 (PDT) From: "Ronald F. Guilmette" To: FreeBSD Net Subject: Re: Raw Sockets: Two Questions In-Reply-To: <5AB2C0B1.3020709@grosbein.net> Date: Wed, 21 Mar 2018 13:50:26 -0700 Message-ID: <4802.1521665426@segfault.tristatelogic.com> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 20:50:28 -0000 In message <5AB2C0B1.3020709@grosbein.net>, Eugene Grosbein wrote: >It does not mean you need to stick with raw sockets API. >libpcap can be used too, as I've shown in previous letter. Thank you. If zmap ends up not suiting my needs, I will definitely look into libpcap.