On Mon, Jan 25, 2016 at 3:10 AM, Guy Harris wrote:
> On Jan 24, 2016, at 8:30 AM, Yang Luo wrote:
>
> > I forgot about one most important thing that libpcap seemingly doesn't
> > compile under Windows, even if there's a Win32\Prj in it. Actually I got
> > many errors when I build libpcap under V
On Jan 24, 2016, at 8:30 AM, Yang Luo wrote:
> I forgot about one most important thing that libpcap seemingly doesn't
> compile under Windows, even if there's a Win32\Prj in it. Actually I got
> many errors when I build libpcap under VS2005.
>
> I am quite confused with some lines like this in p
On Jan 24, 2016, at 6:46 AM, Yang Luo wrote:
> I have implemented a loopback adapter called "Npcap Loopback Adapter" on
> Windows. It's like lo in linux. I know that libpcap recognizes "lo" by just
> matching the adapter name with "lo".
...*if* the OS doesn't helpfully provide, as one of the int
Hi,
I forgot about one most important thing that libpcap seemingly doesn't
compile under Windows, even if there's a Win32\Prj in it. Actually I got
many errors when I build libpcap under VS2005.
I am quite confused with some lines like this in pcap-int.h:
typedef int (*activate_op_t)(pcap_t *);
Hi list,
I am a developer for Npcap, a fork for WinPcap (
https://github.com/nmap/npcap). My libpcap code is still some very old
version 1.0 branch 1_0_rel0b (20091008). And I want to update to the latest
release. But before that happens, I need to handle some updates of mine to
the libpcap folder
