the
NdisSend(&Status, Open->AdapterHandle, pPacket); function.
I would like that Loris Degioanni add this as a function of winpcap, because
if you can write a bridge, you can also write a transparent firewall.
Regards
David Rodriguez
- Original Message -
From: "Ben Gre
windows 2000 and xp, I built several nice applications
with this.
David Rodriguez
- Original Message -
From: "Bowers, Rick" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, February 22, 2005 06:50 PM
Subject: RE: [WinPcap-users] PROBLEM WITH BUILDING A BRIDGE
Thanks for the su
I can read arp packets with winpcap that are 48 bytes size, Winpcap cannot
read erroneus packets but smaller it can read.
David.
Regards.
- Original Message -
From: "Rob Henningsgard" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 24, 2004 10:42 AM
Subject: [WinPcap
Hello
I have a transparent application for voip built
with winpcap,
it works as a bridge and uses 2 threads similar
your app,
only once a year the pc where is installed hang up. I did not
find the reason.
how many times your app or your server lock ups
?
David
- Original Mess
p the packet?
>
> I can recommend using ethereal on the receiving computer, to see if the
> packet alteration are good enough. By doing this, i've been able to
> distinquish between WinpCap initialization errors, and my own packet
editing
> errors..
>
> Hope this help,
ts or truncated packets
> You could try publishing the relevant code parts, and see what the
response
> is. I'll be glad to browse through it and se if I can see something you've
> missed. I've been through most aspects of the library about know...
>
> - Jesper
>
>
ybe i'm of track. Just a thought...
>
> - Jesper
>
> -Original Message-
> From: David Rodriguez [mailto:[EMAIL PROTECTED]]
> Sent: 8. august 2002 15:06
> To: [EMAIL PROTECTED]
> Subject: Re: [WinPcap-users] Loosing Packets or truncated packets
>
&g
hat the increase of the buffer produce this error, does the driver copy
> all
> >
> > the content of the kernel memory to the user memory even the memory has
> >
> > little information ?
> >
> > Note:
