["Gianluca Varenni" <gianluca.varenni@xxxxxxxxxxxx>]

It's one of those things I want to look at, but probably it won't happen for the next release of WinPcap (4.1).

Consider that the only devices affected by this problem are the wireless devices using a native wi-fi driver.

 

Have a nice day

GV

 

 

----- Original Message -----

From: Joshua (Shiwei) Zhao

To: Developer support list for Wireshark

Sent: Friday, July 24, 2009 4:13 PM

Subject: Re: [Wireshark-dev] Wireshark on vista

Are we going to fix it? There should be a way to get the device name/description.

If there are multiple WiFi devices (or other network devices showing same problem) on a same machine, currently it's hard to tell which one is which.

 

Thanks,

Joshua

On Fri, Jul 24, 2009 at 12:05 PM, Gianluca Varenni <gianluca.varenni@xxxxxxxxxxxx> wrote:

Microsoft is the wireless adapter.

 

Native wifi adapters on Vista/Win7 have an Intermediate driver (from MS) between their miniport driver and winpcap itself, and such IM driver traps the request that WinPcap uses to get the name, returning just "Microsoft".

 

Have a nice day

GV

 

 

----- Original Message -----

From: Joshua (Shiwei) Zhao

To: Developer support list for Wireshark

Sent: Friday, July 24, 2009 11:46 AM

Subject: Re: [Wireshark-dev] Wireshark on vista

Yes, I do have one listed as "Microsoft: \Device\NPF_{7D4C2BA0-BCB3-47D6-8E5C-5D30946E8150}".

What does this tell? Is it the wifi card I have? Then why there is no descriptive name like what we get on xp?

 

Thanks,

Joshua

 

On Fri, Jul 24, 2009 at 11:36 AM, Gianluca Varenni <gianluca.varenni@xxxxxxxxxxxx> wrote:

What is the list of adapters returned by Wireshark? Do you have an adapter just called "Microsoft"?

 

GV

----- Original Message -----

From: Joshua (Shiwei) Zhao

To: Developer support list for Wireshark

Sent: Friday, July 24, 2009 11:18 AM

Subject: [Wireshark-dev] Wireshark on vista

With Wireshark 1.0.4 running on vista, I cannot see my WiFi card as a capture interface though I can see my Ethernet card.

Is this a known issue? Or I might be doing sth wrong?

 

Many thanks,

Joshua

---

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

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

---

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

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

---

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