search

jpr5 / ngrep

ngrep is like GNU grep applied to the network layer. It's a PCAP-based tool that allows you to specify an extended regular or hexadecimal expression to match against data payloads of packets. It understands many kinds of protocols, including IPv4/6, TCP, UDP, ICMPv4/6, IGMP and Raw, across a wide variety of interface types, and understands BPF filter logic in the same fashion as more common packet sniffing tools, such as tcpdump and snoop.
https://github.com/jpr5/ngrep
Other
889 stars 99 forks source link

ngrep on windows #17

Open avi301 opened 5 years ago

avi301 commented 5 years ago

i'm tryin to compile the solution with visual studio and getting multiple error messages: image windows versions: 8.1 and server 2016 winpcap installed and also the dev pack. trying to lock for same errors and cannot find anything. thanks

jpr5 commented 5 years ago

FYI ngrep is an old product, been around almost 20 years now. I don't use it regularly on the Windows platform, but every few years I update it to keep up with the different things MSFT does. Keeping up has been challenging however, so if you discover how to work past these things, I'd love a patch FWIW.

I think the root problem you've encountered is probably due to me not updating for additions I made on the nix side in the last major release (i.e. USE_VLAN_HACK). Most of the messages look like warnings, which probably can be effectively ignored (though I'd guess they'll be easy to fix by #defineing any renamed/deprecated functions. Under win32/support is a file called config.h (usually autogenerated on nix by a configure script). The fix for what you've identified here is probably to just put in any of the missing #defines manually from config.h.in FYI I'd set USE_VLAN_HACK to 0.

LMK how it goes! Thanks for the report.

kejkillviruss commented 1 month ago

'termux-change-repo'