|
Are you running Windows Vista?
If so, try to execute Wireshark with
elevated privileges i.e. right-click on the wireshark link and use "Run as
administrator"
GV
----- Original Message -----
Sent: Sunday, September 20, 2009 3:45
PM
Subject: Re: [Wireshark-users]
Wireshark-users Digest, Vol 40, Issue 44
when i installed WS(wireshark) last verison of
WinPcap is already installed automatically.but WS can not dedect my NIC
(Marvell Yukon 88E8056)
2009/9/20 <wireshark-users-request@xxxxxxxxxxxxx>
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. no eth interface (M.Emin.Ba?)
2. Re: no eth interface (Martin
Visser)
----------------------------------------------------------------------
Message:
1
Date: Sun, 20 Sep 2009 13:40:56 +0300
From: M.Emin.Ba? <tespara@xxxxxxxxx>
Subject:
[Wireshark-users] no eth interface
To: wireshark-users@xxxxxxxxxxxxx
Message-ID:
<aabd96730909200340i2bed62bfka3c77c57e8848fb3@xxxxxxxxxxxxxx>
Content-Type:
text/plain; charset="iso-8859-1"
my NIC is "Marvell Yukon
88E8056 PCI-E Gigabit Ethernet Controller" but
wireshark does not
recognize it
-------------- next part --------------
An HTML
attachment was scrubbed...
URL: http://www.wireshark.org/lists/wireshark-users/attachments/20090920/e85a345d/attachment.html
------------------------------
Message:
2
Date: Sun, 20 Sep 2009 22:54:07 +1000
From: Martin Visser <martinvisser99@xxxxxxxxx>
Subject:
Re: [Wireshark-users] no eth interface
To: Community support list for
Wireshark
<wireshark-users@xxxxxxxxxxxxx>
Message-ID:
<b3739b0c0909200554q290c73ael300ef702926a4a14@xxxxxxxxxxxxxx>
Content-Type:
text/plain; charset="utf-8"
It is more likely that the issue with not
seeing the NIC is due to
permissions rather than the chipset. You really
need to provide at least the
platform you are running on (Windows/Linux)
and version. (Paste the output
from the Wireshark "About" box). (Also if
you are running on Windows make
sure you installed WinPcap when you
installed).
MartinVisser99@xxxxxxxxx
On
Sun, Sep 20, 2009 at 8:40 PM, M.Emin.Ba? <tespara@xxxxxxxxx> wrote:
>
my NIC is "Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller"
but
> wireshark does not recognize it
>
>
___________________________________________________________________________
>
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
>
-------------- next part
--------------
An HTML attachment was scrubbed...
URL: http://www.wireshark.org/lists/wireshark-users/attachments/20090920/7f0d96e6/attachment.htm
------------------------------
_______________________________________________
Wireshark-users
mailing list
Wireshark-users@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-users
End
of Wireshark-users Digest, Vol 40, Issue
44
***********************************************
--
Çatık kaş hükümet dedikleri zat
Beni Allah tutmuş kim
eder azat
___________________________________________________________________________
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
|