Wireshark · Wireshark-users: Re: [Wireshark-users] IPv6 Interface

[Brian Daniel <daniel_brian@xxxxxxxxxxxx>]

When I run IPv6, I leave IPv4 enabled also because I still get my IP address from the IPv4 dhcp server. After installing WinPcap_4_1_beta5.exe and wireshark-win32-1.1.2.exe then I have no problems packet capturing everything then filtering on IPv6. I have not experimented with an IPv6 type of capture filter yet.

I hope this helps,

Brian

On Mon, Mar 9, 2009 at 5:59 PM, Michael Margulies <mmargulies@xxxxxxxx> wrote:

I was using the latest stable release of WinPcap - 4.0.2, I updated to
4.1beta5 and am still encountering the same problem.

Thanks,
Mike M

-----Original Message-----
From: wireshark-users-bounces@xxxxxxxxxxxxx
[mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of

wireshark-users-request@xxxxxxxxxxxxx

Sent: Sunday, March 08, 2009 12:00 PM
To: wireshark-users@xxxxxxxxxxxxx

Subject: Wireshark-users Digest, Vol 34, Issue 21

Send Wireshark-users mailing list submissions to
       wireshark-users@xxxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
       https://wireshark.org/mailman/listinfo/wireshark-users
or, via email, send a message with subject or body 'help' to

       wireshark-users-request@xxxxxxxxxxxxx

You can reach the person managing the list at
       wireshark-users-owner@xxxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Wireshark-users digest..."


Today's Topics:

  1. Re: IPv6 Interface (Gianluca Varenni)


----------------------------------------------------------------------

Message: 1
Date: Sat, 7 Mar 2009 17:40:41 -0800
From: "Gianluca Varenni" <gianluca.varenni@xxxxxxxxxxxx>

Subject: Re: [Wireshark-users] IPv6 Interface

To: "Community support list for Wireshark"
       <wireshark-users@xxxxxxxxxxxxx>

Message-ID: <59955923F67C406F8602C3CA7940509F@nelson2>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
       reply-type=original

Which version of WinPcap are you using?

There was a fix related to IPv6 address listing in the latest beta
version
of WinPcap (4.1beta5). Can you please check if the bug shows up in that
version as well?

Have a nice day
GV

----- Original Message -----
From: "Guy Harris" <guy@xxxxxxxxxxxx>
To: "Community support list for Wireshark"
<wireshark-users@xxxxxxxxxxxxx>
Sent: Friday, March 06, 2009 1:53 PM
Subject: Re: [Wireshark-users] IPv6 Interface


>
> On Mar 6, 2009, at 12:27 PM, Michael Margulies wrote:
>
>> Yes, sorry for not being specific, the physical interface is
ethernet.
>> The ethernet card always shows up in the capture interface dialog
box.
>> When the tcp/ipv4 stack is enabled, the ipv4 ip address for my
>> laptop is
>> shown. When the tcp/ipv4 stack is disabled, but the tcp/ipv6 is
>> enabled,
>> the ip address is listed as unknown. I'm interpreting this as
>> Wireshark
>> not recognizing the ipv6 interface for some reason.
>
> Not necessarily.  It could be that, for example, WinPcap can't get the
> IPv6 address for the interface and supply it to Wireshark (Wireshark
> depends on libpcap/WinPcap to do a lot of the work of dealing with
> network adapters).  Gianluca?
>
________________________________________________________________________
___
> Sent via:    Wireshark-users mailing list
<wireshark-users@xxxxxxxxxxxxx>
> Archives:    http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>
> mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe

------------------------------

_______________________________________________
Wireshark-users mailing list
Wireshark-users@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-users

End of Wireshark-users Digest, Vol 34, Issue 21
***********************************************

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
            mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe