Re: Extending Npcap

--===============2494438765050672807==
Content-Type: multipart/alternative; boundary="0000000000006771e40591fc3a3e"

--0000000000006771e40591fc3a3e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 5, 2019 at 11:51 PM Holger Pfrommer <[email protected]>
wrote:

> Cheers,
>
>
>
> I=E2=80=99d like to extend Npcap library to support an additional capture=
 device.
> Goal is to contribute the code to your nice project so it=E2=80=99ll be a=
vailable
> to the whole public in future.
>
> I already have an (up-to-date) running libpcap implementation for Linux
> and also (an older implementation) for WinPcap.
>
>
>
> As far as I understood, Npcap is based in libpcap and thus would not
> require any separate implementation for Windows?
>
>
>
> So what would be the best way to get my code into an upcoming release of
> Npcap?
>

Hi Holger.  I'm glad to hear it!  If your changes are all to libpcap
itself, your best bet is to work with them toward adoption.  Npcap includes
the latest libpcap (1.9.0) now, and we are usually pretty fast to update to
newer libpcap releases as they are made.  They are great maintainers, so we
try to avoid maintaining our own separate changesets wherever possible.

What kind of "additional capture device" does your extension enable?  We
would love to see a link to the changesets when you submit them to the
tcpdump/libpcap group.

Cheers,
Fyodor

--0000000000006771e40591fc3a3e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Thu, Sep 5, 2019 at 11:51 PM Holge=
r Pfrommer &lt;<a href=3D"mailto:[email protected]">HPfrommer@hilscher=
.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">





<div lang=3D"DE">
<div class=3D"gmail-m_-6826144199527138662WordSection1">
<p class=3D"MsoNormal">Cheers,<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I=E2=80=99d like to extend Npca=
p library to support an additional capture device. Goal is to contribute th=
e code to your nice project so it=E2=80=99ll be available to the whole publ=
ic in future.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I already have an (up-to-date) =
running libpcap implementation for Linux and also (an older implementation)=
 for WinPcap.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">As far as I understood, Npcap i=
s based in libpcap and thus would not require any separate implementation f=
or Windows?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">So what would be the best way t=
o get my code into an upcoming release of Npcap?</span></p></div></div></bl=
ockquote><div><br></div><div>Hi Holger.=C2=A0 I&#39;m glad to hear it!=C2=
=A0 If your changes are all to libpcap itself, your best bet is to work wit=
h them toward adoption.=C2=A0 Npcap includes the latest libpcap (1.9.0) now=
, and we are usually pretty=C2=A0fast to update to newer libpcap releases a=
s they are made.=C2=A0 They are great maintainers, so we try to avoid maint=
aining our own separate changesets wherever possible.</div><div><br></div><=
div>What kind of &quot;additional capture device&quot; does your extension =
enable?=C2=A0 We would love to see a link to the changesets when you submit=
 them to the tcpdump/libpcap group.</div><div><br></div><div>Cheers,</div><=
div>Fyodor</div><div><br></div></div></div>

--0000000000006771e40591fc3a3e--

--===============2494438765050672807==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/
--===============2494438765050672807==--