-
Notifications
You must be signed in to change notification settings - Fork 844
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Win32 and Endace DAG card support. #1366
Comments
It would be interesting to see what it looks like in Linux, but I do not have their hardware or the SDK. |
PS. The NapaTech SmartNICs seems to support Windows via some WinPcap-NT driver. These (or some?) can even transmit via WinPcap-NT. |
@sfd: for which platforms is it useful to support DAG cards? |
The specs from the page you linked to say that the supported OSes are "Linux and Windows" - and that they support "libpcap, WinPcap and DPDK". According to https://www.napatech.com/products/link-capture-software/ their "Link-Capture™ Software" is supported by:
with the supported APIs being:
The page at https://www.napatech.com/support/resources/data-sheets/link-capture-software-for-napatech/ updates that to
with
|
1.
The only modification made to libpcap is the addition of the Napatech support files. No modification to libpcap itself has been made. Our libpcap is not placed on github, but can be downloaded as a part of our driver package on our website.
2.
Yes WinPCAP is no longer supported, but is still available as a part of our driver. Npcap could easily be supported, but has not been done yet as there is not customer request for the support.
…________________________________
From: Guy Harris ***@***.***>
Sent: Thursday, October 10, 2024 13:39
To: the-tcpdump-group/libpcap ***@***.***>
Cc: Bent Kuhre ***@***.***>; Mention ***@***.***>
Subject: Re: [the-tcpdump-group/libpcap] Win32 and Endace DAG card support. (Issue #1366)
The NapaTech SmartNICs seems to support Windows via some WinPcap-NT driver.
The specs from the page you linked to say that the supported OSes are "Linux and Windows" - and that they support "libpcap, WinPcap and DPDK".
According to https://www.napatech.com/products/link-capture-software/<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.napatech.com%2fproducts%2flink-capture-software%2f&c=E,1,zTN5sPS9GhVt8ciokXvylGUjHeQWiYccCDTpbboWEjl8IbWvMkDCGE8yT2nyiBh1KmbfsFu4pjZIWEDBoAJv7FdU8QXUX68S83VAwzdlgE2u-ydIhNL2ouSkisc,&typo=1> their "Link-Capture™ Software" is supported by:
* Linux kernel 3.0 – 3.19, 4.0 – 4.18, 5.0 – 5.11 (64-bit)
* Windows Server 2016 and 2019 (64-bit)
with the supported APIs being:
* libpcap v. 1.7.3, 1.8.1, 1.9.0 and WinPcap v. 4.1.3
* DPDK v. 20.11
* NTAPI (Napatech API)
The page at https://www.napatech.com/support/resources/data-sheets/link-capture-software-for-napatech/<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.napatech.com%2fsupport%2fresources%2fdata-sheets%2flink-capture-software-for-napatech%2f&c=E,1,dl5JESBhdtGTNdkZx2XSmIe3PDHvEAwHk_G8HJYW9ZT-sBkdXA1SBwxmmNhMcozchjCT8zg-LKydTC8gJosaAXcyMHJQEpgO9nGZy-BSBK8q7wpg&typo=1> updates that to
* Linux kernel 3.x, 4.x and 5.x (64-bit)
* Windows server 2022 (64-bit) and Windows 11 (64-bit)
with
* libpcap v. 1.8.1, 1.9.1, 1.10.0 and WinPcap v. 4.1.3
* DPDK v. 21.11 LTS
* NTAPI (Napatech API)
@napafc<https://github.com/napafc>, @bkuhre<https://github.com/bkuhre>:
1. Have you modified libpcap to support your adapters? If so, are the modifications available in some repository?
2. WinPcap is no longer supported, and is based on an older version of libpcap; Npcap<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fnpcap.com%2f&c=E,1,Ddxh5UXAiVuE2ZtS16_gV5CdVOjfM50JXzhdifRXy0Gab5DKJpq0eEm9MPDXB0B8N7Tv5rP0p7hfXxpnWWJvJ_puGiPnEoJ-6kwv2THROLQhF60oKoWUDhEP5RE,&typo=1> is actively being developed and is currently based on, I think, libpcap 1.10.4 (Npcap 1.80 might be based on the recently-released 1.10.5). Would it be possible to support Npcap?
—
Reply to this email directly, view it on GitHub<#1366 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGQDL4FHKRRIJKA5WIZDM63Z2ZRNJAVCNFSM6AAAAABPUOWAN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBUHA2TOMZRGY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
Disclaimer: This email and any files transmitted with it may contain confidential information intended for the addressee(s) only. The information is not to be surrendered or copied to unauthorized persons. If you have received this communication in error, please notify the sender immediately and delete this e-mail from your system.
|
Trying to build with
-DHAVE_DAG_API
on Windows has lot of problems.First, with Camio's
dagapi.h(61):
fatal error C1189: #error: Could not detect CPU endianness. Please contact <[email protected]> for assistance.
(which I faked with a
-D__x86_64__
).The needed
pcap-dag.c
file misses apid_t
type for MSVC/clang-cl.Missing definition:
Lots of warnings on mixing
char*
andu_char*
.And finally:
So what is the point to support DAG cards in
pcap-npf.c
?I'm not even sure an Endance/DAG card is even supported on Windows. Not here AFAICS
Time to remove this
HAVE_DAG_API
code?The text was updated successfully, but these errors were encountered: