[Winpcap-bugs] Re: Unable to list devices for interfaces
containingmany IPv6 addresses
Bhairav
stan2k08 at gmail.com
Wed Oct 22 22:30:13 GMT 2008
Hi GV,
Thanks for responding and confirming my emails are getting there :).
Just wanted to let you know that I had looked at the code a little and think
that part of the reason I am running into the issue is because there is a
very low number IPv6 addresses being allowed, signified by the value of
MAX_NETWORK_ADDRESSES. Currently, that is set to 16. So, it seems winpcap
will only look up 16 IPv6 addresses before it decides to quit due to
insufficient storage.
HTH,
Bhairav
On Wed, Oct 22, 2008 at 12:26 PM, Gianluca Varenni <
gianluca.varenni at cacetech.com> wrote:
> Your message has been correctly received on the mailing list, but I
> haven't found time to look at the WinPcap source code and understand exactly
> what the problem is.
>
> Have a nice day
> GV
>
> ----- Original Message -----
> *From:* Bhairav <stan2k08 at gmail.com>
> *To:* winpcap-bugs at winpcap.org
> *Sent:* Tuesday, October 21, 2008 6:02 PM
> *Subject:* [Winpcap-bugs] Re: Unable to list devices for interfaces
> containingmany IPv6 addresses
>
> Hello All,
> I had sent the previous email(s) for the very first time. Wondering if it
> was even received by the list. If so, any responses would be really
> appreciated.
>
> Thanks,
> Bhairav
>
> On Sat, Oct 18, 2008 at 5:20 PM, Bhairav <stan2k08 at gmail.com> wrote:
>
>> Ooops ... apologies -- forgot to attach the file. Attached now.
>> Thanks,
>> Bhairav
>>
>>
>> On Sat, Oct 18, 2008 at 5:13 PM, Bhairav <stan2k08 at gmail.com> wrote:
>>
>>> Hello,
>>> I have captured debug information for an issue I am seeing according to
>>> the bug page on the WinPcap page. Here are the details as requested on the
>>> page:
>>>
>>> 1) WinPcap version is 4.1 beta4. Please note, I was seeing the issue
>>> with 4.0.2 previously and decided to try out this beta version before
>>> reporting the problem. The debug file created is with this beta version
>>> 2) The output of windump -D is blank (the debug file will make it clear
>>> why this is the case)
>>> 3) Win2k3
>>> 4) 2 Network adapters installed - both HP NC324i PCIe Dual Port Gigabit
>>> Server, but I think the issue is independent of the adapters themselves
>>> 5) The issue is this: I have about 500 IPv4 and 500 IPv6 virtual
>>> addresses on one (out of 2) interfaces. At the application level (wireshark
>>> and windump) I am not able to list the interfaces with these numbers of
>>> addresses. I could have 1000 IPv4 addresses without a problem (in listing
>>> the interfaces) -- but whenever I get to a higher number of IPv6 (eg 1000
>>> IPv4 + 14 IPv6), there becomes a problem listing the interfaces (a few IPv6
>>> addresses is not a problem though). Looking at the debug file, I see the
>>> following error:
>>> [000005B4] 2008-10-18 16:34:23 The space in
>>> AdInfo->NNetworkAddresses is not large enough, failing
>>>
>>> Ideally, I wanted to use 1000 IPv4 + 1000 IPv6 addresses. But, perhaps
>>> winpcap is not able to get enough space for all the IPs?
>>>
>>> Is it possible to increase the available storage space to accommodate
>>> these numbers of IP addresses.
>>>
>>> Thanks,
>>> Bhairav
>>>
>>>
>>
> ------------------------------
>
> _______________________________________________
> Winpcap-bugs mailing list
> Winpcap-bugs at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-bugs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winpcap.org/pipermail/winpcap-bugs/attachments/20081022/d275edda/attachment.htm
More information about the Winpcap-bugs
mailing list