[Winpcap-users] Winpcap and Sockets

[Gianluca Varenni]

----- Original Message ----- 
From: "Ian Basham" <ianb at proconex.com>
To: <winpcap-users at winpcap.org>
Sent: Thursday, March 29, 2007 12:26 PM
Subject: Re: [Winpcap-users] Winpcap and Sockets


> Gianluca,
>
> Thanks for your help.
>
> I took a while to respond because I had to install and figure out MS 
> Visual Studio .NET 2003 (I assume that is what you meant by VC 2003).  I 
> unzipped your files into "C:\Program Files\WpdPack\Examples-pcap\iflist", 
> after renaming the existing iflist folder.  I got a clean compile right 
> away.  BTW, I am using WinPcap 4.0.
>
> Unfortunately, I am still getting the exact same problem, that is the bind 
> is failing.
> A couple of questions for you please,
>
> 1) Am I using the right compiler, and

Yes.

> 2) did you use my sample 'Machine B' code as well?
>

No. From what you said the sample Machine B runs on another machine, so it 
should not have anything to do with the problems you have on machine A. Does 
sample Machine A run ok if sample B is not used at all?

Have a nice day
GV


> Sincerely,
>
> Ian Basham
>
> Gianluca Varenni wrote:
>> Ian,
>>
>> I briefly tried your application (machine A) on my machine, and it worked 
>> without any problem. The call to bind didn't fail. Attached you can find 
>> the Visual Studio project I used (i just modified one of the samples of 
>> the WpdPack). I used VC 2003 to compile it.
>>
>> Can you please try the attached project and see if it works?
>>
>> GV
>>
>>
>>
>> ----- Original Message ----- From: "Ian Basham" <ianb at proconex.com>
>> To: <winpcap-users at winpcap.org>
>> Sent: Wednesday, March 21, 2007 7:28 AM
>> Subject: [Winpcap-users] Winpcap and Sockets
>>
>>
>>> Here are 2 programs that demonstrate a problem I am having.
>>>
>>> In a nutshell, normally the program on Machine B can be run over and 
>>> over without any problems.  However, if the program on Machine A calls 
>>> pcap_open and pcap_close, then the program on Machine B can never 
>>> re-establish the socket, because the program on Machine A fails on the 
>>> call to bind.
>
>>> snip...
>
>>> _______________________________________________
>>> Winpcap-users mailing list
>>> Winpcap-users at winpcap.org
>>> https://www.winpcap.org/mailman/listinfo/winpcap-users
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Winpcap-users mailing list
>> Winpcap-users at winpcap.org
>> https://www.winpcap.org/mailman/listinfo/winpcap-users
>>
>
> _______________________________________________
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-users