parent
9ab5bc5713
commit
155ee76ad8
77
FAQ
77
FAQ
|
@ -47,7 +47,7 @@ Building Ethereal:
|
|||
dftest_DEPENDENCIES was already defined in condition TRUE, which
|
||||
implies condition HAVE_PLUGINS_TRUE
|
||||
|
||||
when I try to build Ethereal from CVS or a CVS snapshot?
|
||||
when I try to build Ethereal from SVN or a SVN snapshot?
|
||||
|
||||
4.3 The link fails with a number of "Output line too long." messages
|
||||
followed by linker errors.
|
||||
|
@ -57,9 +57,6 @@ Building Ethereal:
|
|||
4.5 The build fails on Windows because of conflicts between winsock.h
|
||||
and winsock2.h.
|
||||
|
||||
4.6 I'm trying to build Ethereal 0.10.0a on Windows; why is the the
|
||||
build failing with an error saying it can't find "Makefile.nmake"?
|
||||
|
||||
Using Ethereal:
|
||||
|
||||
5.1 When I use Ethereal to capture packets, I see only packets to and
|
||||
|
@ -215,7 +212,7 @@ General Questions
|
|||
|
||||
Q 1.2: What protocols are currently supported?
|
||||
|
||||
A: There are currently 512 supported protocols and media, listed
|
||||
A: There are currently 518 supported protocols and media, listed
|
||||
below. Descriptions can be found in the ethereal(1) man page.
|
||||
|
||||
3GPP2 A11
|
||||
|
@ -367,10 +364,12 @@ cies
|
|||
Distance Vector Multicast Routing Protocol
|
||||
Distcc Distributed Compiler
|
||||
Distributed Checksum Clearinghouse Protocol
|
||||
Distributed Network Protocol 3.0
|
||||
Domain Name Service
|
||||
Dynamic DNS Tools Protocol
|
||||
Echo
|
||||
Encapsulating Security Payload
|
||||
Endpoint Name Resolution Protocol
|
||||
Enhanced Interior Gateway Routing Protocol
|
||||
EtherNet/IP (Industrial Protocol)
|
||||
Ethernet
|
||||
|
@ -409,6 +408,7 @@ cies
|
|||
Generic Security Service Application Program Interface
|
||||
Gnutella Protocol
|
||||
H225
|
||||
H235-SECURITY-MESSAGES
|
||||
H245
|
||||
H4501
|
||||
HP Extended Local-Link Control
|
||||
|
@ -416,7 +416,6 @@ cies
|
|||
Hummingbird NFS Daemon
|
||||
HyperSCSI
|
||||
Hypertext Transfer Protocol
|
||||
IAX2
|
||||
ICQ Protocol
|
||||
IEEE 802.11 Radiotap Capture header
|
||||
IEEE 802.11 wireless LAN
|
||||
|
@ -446,6 +445,7 @@ cies
|
|||
Intel ANS probe
|
||||
Intelligent Platform Management Interface
|
||||
Inter-Access-Point Protocol
|
||||
Inter-Asterisk eXchange v2
|
||||
InterSwitch Message Protocol
|
||||
Interbase
|
||||
Internet Cache Protocol
|
||||
|
@ -589,6 +589,7 @@ cies
|
|||
PPP-over-Ethernet Session
|
||||
PPPMux Control Protocol
|
||||
Packed Encoding Rules (ASN.1 X.691)
|
||||
PacketCable
|
||||
Point-to-Point Protocol
|
||||
Point-to-Point Tunnelling Protocol
|
||||
Portmap
|
||||
|
@ -659,6 +660,7 @@ cies
|
|||
Session Initiation Protocol
|
||||
Session Initiation Protocol (SIP as raw text)
|
||||
Short Message Peer to Peer
|
||||
Signaling Compression
|
||||
Signalling Connection Control Part
|
||||
Signalling Connection Control Part Management
|
||||
Simple Mail Transfer Protocol
|
||||
|
@ -729,6 +731,7 @@ cies
|
|||
Zebra Protocol
|
||||
Zone Information Protocol
|
||||
eDonkey Protocol
|
||||
giFT Internet File Transfer
|
||||
iSCSI
|
||||
iSNS
|
||||
|
||||
|
@ -813,8 +816,8 @@ cies
|
|||
According to the book "Computer Networks" by Andrew Tannenbaum,
|
||||
Ethernet was named after the "luminiferous ether" which was once
|
||||
thought to carry electromagnetic radiation. Taking that into
|
||||
consideration, Ethereal seemed like an appropriate name for an
|
||||
Ethernet analyzer.
|
||||
consideration, Ethereal seemed like an appropriate name for something
|
||||
that started out as an Ethernet analyzer.
|
||||
|
||||
Downloading Ethereal
|
||||
|
||||
|
@ -881,7 +884,7 @@ Building Ethereal
|
|||
dftest_DEPENDENCIES was already defined in condition TRUE, which
|
||||
implies condition HAVE_PLUGINS_TRUE
|
||||
|
||||
when I try to build Ethereal from CVS or a CVS snapshot?
|
||||
when I try to build Ethereal from SVN or a SVN snapshot?
|
||||
|
||||
A: You probably have automake 1.5 installed on your machine (the
|
||||
command automake --version will report the version of automake on your
|
||||
|
@ -932,16 +935,6 @@ Building Ethereal
|
|||
Note that the installed version of the developer's pack should be the
|
||||
same version as the version of WinPcap you have installed.
|
||||
|
||||
Q 4.6: I'm trying to build Ethereal 0.10.0a on Windows; why is the the
|
||||
build failing with an error saying it can't find "Makefile.nmake"?
|
||||
|
||||
A: There was a bug in the 0.10.0a distribution that caused
|
||||
"tools\Makefile.nmake" not to be in the source code release. You can
|
||||
download it with the URL
|
||||
http://www.ethereal.com/cgi-bin/viewcvs.cgi/*checkout*/ethereal/tools/
|
||||
Makefile.nmake?rev=1.5. Put it into "tools\Makefile.nmake" and try the
|
||||
build again.
|
||||
|
||||
Using Ethereal
|
||||
|
||||
Q 5.1: When I use Ethereal to capture packets, I see only packets to
|
||||
|
@ -1159,11 +1152,28 @@ Using Ethereal
|
|||
|
||||
If the attempt to capture on it succeeds, the interface is somehow not
|
||||
being reported by the mechanism Ethereal uses to get a list of
|
||||
interfaces; please report this to ethereal-dev@ethereal.com giving
|
||||
full details of the problem, including
|
||||
interfaces. Try listing the interfaces with WinDump; see the WinDump
|
||||
Web site or the local mirror of the WinDump Web site for information
|
||||
on using WinDump.
|
||||
|
||||
You would run WinDump with the -D flag; if it lists the interface,
|
||||
please report this to ethereal-dev@ethereal.com giving full details of
|
||||
the problem, including
|
||||
* the operating system you're using, and the version of that
|
||||
operating system;
|
||||
* the type of network device you're using.
|
||||
* the type of network device you're using;
|
||||
* the output of WinDump.
|
||||
|
||||
If WinDump does not list the interface, this is almost certainly a
|
||||
problem with one or more of:
|
||||
* the operating system you're using;
|
||||
* the device driver for the interface you're using;
|
||||
* the WinPcap library and/or the WinPcap device driver;
|
||||
|
||||
so first check the WinPcap FAQ, the local mirror of that FAQ, or the
|
||||
Wiretapped.net mirror of that FAQ, to see if your problem is mentioned
|
||||
there. If not, then see the WinPcap support page (or the local mirror
|
||||
of that page) - check the "Submitting bugs" section.
|
||||
|
||||
If you are having trouble capturing on a particular network interface,
|
||||
first try capturing on that device with WinDump; see the WinDump Web
|
||||
|
@ -1476,22 +1486,21 @@ Using Ethereal
|
|||
error "** ERROR **: file print.c: line 691 (print_line): should not be
|
||||
reached".
|
||||
|
||||
A: This is a bug in Ethereal 0.10.0a, which is fixed in the Ethereal
|
||||
CVS tree and will thus be fixed in the next release. To work around
|
||||
the bug, don't use "-x" unless you're also using "-V"; note that "-V"
|
||||
produces a full dissection of each packet, so you might not want to
|
||||
use it.
|
||||
A: This is a bug in Ethereal 0.10.0a, which is fixed in 0.10.1 and
|
||||
later releases. To work around the bug, don't use "-x" unless you're
|
||||
also using "-V"; note that "-V" produces a full dissection of each
|
||||
packet, so you might not want to use it.
|
||||
|
||||
To get a fixed version, either build the current CVS version from
|
||||
anonymous CVS or a nightly CVS snapshot, or apply to tethereal.c in
|
||||
To get a fixed version, either build the current SVN version from
|
||||
anonymous SVN or a nightly SVN snapshot, or apply to tethereal.c in
|
||||
the 0.10.0a source tarball the changes between the broken and the
|
||||
fixed versions, which you can download with the URL
|
||||
http://www.ethereal.com/cgi-bin/viewcvs.cgi/ethereal/tethereal.c.diff?
|
||||
r2=1.211&r1=1.210&diff_format=u and (re-)build from source. It might
|
||||
be easier to get the CVS version than to get the patch and apply it to
|
||||
be easier to get the SVN version than to get the patch and apply it to
|
||||
the 0.10.0a source tarball, but it's probably easier to build from the
|
||||
source tarball than from the CVS version, as you'll need to have more
|
||||
tools and make more steps to generate from the CVS version some files
|
||||
source tarball than from the SVN version, as you'll need to have more
|
||||
tools and make more steps to generate from the SVN version some files
|
||||
that are bundled with the source tarball.
|
||||
|
||||
Note that to build from the 0.10.0a source tarball on Windows with
|
||||
|
@ -1810,7 +1819,7 @@ echo "Mode: y">/proc/driver/aironet/ethN/Config
|
|||
echo "Mode: ess">/proc/driver/aironet/ethN/Config
|
||||
|
||||
On Linux with the driver in the 2.4.20 or later kernel, or with the
|
||||
CVS drivers from the airo-linux SourceForge site, you will have to
|
||||
SVN drivers from the airo-linux SourceForge site, you will have to
|
||||
capture on the wifiN interface if your Aironet card is ethN, after
|
||||
running the commands listed above.
|
||||
|
||||
|
@ -2099,4 +2108,4 @@ echo "Mode: ess">/proc/driver/aironet/ethN/Config
|
|||
For corrections/additions/suggestions for this web page (and not
|
||||
Ethereal support questions), please send email to
|
||||
ethereal-web[AT]ethereal.com .
|
||||
Last modified: Thu, May 13 2004.
|
||||
Last modified: Fri, July 16 2004.
|
||||
|
|
77
help/faq.txt
77
help/faq.txt
|
@ -47,7 +47,7 @@ Building Ethereal:
|
|||
dftest_DEPENDENCIES was already defined in condition TRUE, which
|
||||
implies condition HAVE_PLUGINS_TRUE
|
||||
|
||||
when I try to build Ethereal from CVS or a CVS snapshot?
|
||||
when I try to build Ethereal from SVN or a SVN snapshot?
|
||||
|
||||
4.3 The link fails with a number of "Output line too long." messages
|
||||
followed by linker errors.
|
||||
|
@ -57,9 +57,6 @@ Building Ethereal:
|
|||
4.5 The build fails on Windows because of conflicts between winsock.h
|
||||
and winsock2.h.
|
||||
|
||||
4.6 I'm trying to build Ethereal 0.10.0a on Windows; why is the the
|
||||
build failing with an error saying it can't find "Makefile.nmake"?
|
||||
|
||||
Using Ethereal:
|
||||
|
||||
5.1 When I use Ethereal to capture packets, I see only packets to and
|
||||
|
@ -215,7 +212,7 @@ General Questions
|
|||
|
||||
Q 1.2: What protocols are currently supported?
|
||||
|
||||
A: There are currently 512 supported protocols and media, listed
|
||||
A: There are currently 518 supported protocols and media, listed
|
||||
below. Descriptions can be found in the ethereal(1) man page.
|
||||
|
||||
3GPP2 A11
|
||||
|
@ -367,10 +364,12 @@ cies
|
|||
Distance Vector Multicast Routing Protocol
|
||||
Distcc Distributed Compiler
|
||||
Distributed Checksum Clearinghouse Protocol
|
||||
Distributed Network Protocol 3.0
|
||||
Domain Name Service
|
||||
Dynamic DNS Tools Protocol
|
||||
Echo
|
||||
Encapsulating Security Payload
|
||||
Endpoint Name Resolution Protocol
|
||||
Enhanced Interior Gateway Routing Protocol
|
||||
EtherNet/IP (Industrial Protocol)
|
||||
Ethernet
|
||||
|
@ -409,6 +408,7 @@ cies
|
|||
Generic Security Service Application Program Interface
|
||||
Gnutella Protocol
|
||||
H225
|
||||
H235-SECURITY-MESSAGES
|
||||
H245
|
||||
H4501
|
||||
HP Extended Local-Link Control
|
||||
|
@ -416,7 +416,6 @@ cies
|
|||
Hummingbird NFS Daemon
|
||||
HyperSCSI
|
||||
Hypertext Transfer Protocol
|
||||
IAX2
|
||||
ICQ Protocol
|
||||
IEEE 802.11 Radiotap Capture header
|
||||
IEEE 802.11 wireless LAN
|
||||
|
@ -446,6 +445,7 @@ cies
|
|||
Intel ANS probe
|
||||
Intelligent Platform Management Interface
|
||||
Inter-Access-Point Protocol
|
||||
Inter-Asterisk eXchange v2
|
||||
InterSwitch Message Protocol
|
||||
Interbase
|
||||
Internet Cache Protocol
|
||||
|
@ -589,6 +589,7 @@ cies
|
|||
PPP-over-Ethernet Session
|
||||
PPPMux Control Protocol
|
||||
Packed Encoding Rules (ASN.1 X.691)
|
||||
PacketCable
|
||||
Point-to-Point Protocol
|
||||
Point-to-Point Tunnelling Protocol
|
||||
Portmap
|
||||
|
@ -659,6 +660,7 @@ cies
|
|||
Session Initiation Protocol
|
||||
Session Initiation Protocol (SIP as raw text)
|
||||
Short Message Peer to Peer
|
||||
Signaling Compression
|
||||
Signalling Connection Control Part
|
||||
Signalling Connection Control Part Management
|
||||
Simple Mail Transfer Protocol
|
||||
|
@ -729,6 +731,7 @@ cies
|
|||
Zebra Protocol
|
||||
Zone Information Protocol
|
||||
eDonkey Protocol
|
||||
giFT Internet File Transfer
|
||||
iSCSI
|
||||
iSNS
|
||||
|
||||
|
@ -813,8 +816,8 @@ cies
|
|||
According to the book "Computer Networks" by Andrew Tannenbaum,
|
||||
Ethernet was named after the "luminiferous ether" which was once
|
||||
thought to carry electromagnetic radiation. Taking that into
|
||||
consideration, Ethereal seemed like an appropriate name for an
|
||||
Ethernet analyzer.
|
||||
consideration, Ethereal seemed like an appropriate name for something
|
||||
that started out as an Ethernet analyzer.
|
||||
|
||||
Downloading Ethereal
|
||||
|
||||
|
@ -881,7 +884,7 @@ Building Ethereal
|
|||
dftest_DEPENDENCIES was already defined in condition TRUE, which
|
||||
implies condition HAVE_PLUGINS_TRUE
|
||||
|
||||
when I try to build Ethereal from CVS or a CVS snapshot?
|
||||
when I try to build Ethereal from SVN or a SVN snapshot?
|
||||
|
||||
A: You probably have automake 1.5 installed on your machine (the
|
||||
command automake --version will report the version of automake on your
|
||||
|
@ -932,16 +935,6 @@ Building Ethereal
|
|||
Note that the installed version of the developer's pack should be the
|
||||
same version as the version of WinPcap you have installed.
|
||||
|
||||
Q 4.6: I'm trying to build Ethereal 0.10.0a on Windows; why is the the
|
||||
build failing with an error saying it can't find "Makefile.nmake"?
|
||||
|
||||
A: There was a bug in the 0.10.0a distribution that caused
|
||||
"tools\Makefile.nmake" not to be in the source code release. You can
|
||||
download it with the URL
|
||||
http://www.ethereal.com/cgi-bin/viewcvs.cgi/*checkout*/ethereal/tools/
|
||||
Makefile.nmake?rev=1.5. Put it into "tools\Makefile.nmake" and try the
|
||||
build again.
|
||||
|
||||
Using Ethereal
|
||||
|
||||
Q 5.1: When I use Ethereal to capture packets, I see only packets to
|
||||
|
@ -1159,11 +1152,28 @@ Using Ethereal
|
|||
|
||||
If the attempt to capture on it succeeds, the interface is somehow not
|
||||
being reported by the mechanism Ethereal uses to get a list of
|
||||
interfaces; please report this to ethereal-dev@ethereal.com giving
|
||||
full details of the problem, including
|
||||
interfaces. Try listing the interfaces with WinDump; see the WinDump
|
||||
Web site or the local mirror of the WinDump Web site for information
|
||||
on using WinDump.
|
||||
|
||||
You would run WinDump with the -D flag; if it lists the interface,
|
||||
please report this to ethereal-dev@ethereal.com giving full details of
|
||||
the problem, including
|
||||
* the operating system you're using, and the version of that
|
||||
operating system;
|
||||
* the type of network device you're using.
|
||||
* the type of network device you're using;
|
||||
* the output of WinDump.
|
||||
|
||||
If WinDump does not list the interface, this is almost certainly a
|
||||
problem with one or more of:
|
||||
* the operating system you're using;
|
||||
* the device driver for the interface you're using;
|
||||
* the WinPcap library and/or the WinPcap device driver;
|
||||
|
||||
so first check the WinPcap FAQ, the local mirror of that FAQ, or the
|
||||
Wiretapped.net mirror of that FAQ, to see if your problem is mentioned
|
||||
there. If not, then see the WinPcap support page (or the local mirror
|
||||
of that page) - check the "Submitting bugs" section.
|
||||
|
||||
If you are having trouble capturing on a particular network interface,
|
||||
first try capturing on that device with WinDump; see the WinDump Web
|
||||
|
@ -1476,22 +1486,21 @@ Using Ethereal
|
|||
error "** ERROR **: file print.c: line 691 (print_line): should not be
|
||||
reached".
|
||||
|
||||
A: This is a bug in Ethereal 0.10.0a, which is fixed in the Ethereal
|
||||
CVS tree and will thus be fixed in the next release. To work around
|
||||
the bug, don't use "-x" unless you're also using "-V"; note that "-V"
|
||||
produces a full dissection of each packet, so you might not want to
|
||||
use it.
|
||||
A: This is a bug in Ethereal 0.10.0a, which is fixed in 0.10.1 and
|
||||
later releases. To work around the bug, don't use "-x" unless you're
|
||||
also using "-V"; note that "-V" produces a full dissection of each
|
||||
packet, so you might not want to use it.
|
||||
|
||||
To get a fixed version, either build the current CVS version from
|
||||
anonymous CVS or a nightly CVS snapshot, or apply to tethereal.c in
|
||||
To get a fixed version, either build the current SVN version from
|
||||
anonymous SVN or a nightly SVN snapshot, or apply to tethereal.c in
|
||||
the 0.10.0a source tarball the changes between the broken and the
|
||||
fixed versions, which you can download with the URL
|
||||
http://www.ethereal.com/cgi-bin/viewcvs.cgi/ethereal/tethereal.c.diff?
|
||||
r2=1.211&r1=1.210&diff_format=u and (re-)build from source. It might
|
||||
be easier to get the CVS version than to get the patch and apply it to
|
||||
be easier to get the SVN version than to get the patch and apply it to
|
||||
the 0.10.0a source tarball, but it's probably easier to build from the
|
||||
source tarball than from the CVS version, as you'll need to have more
|
||||
tools and make more steps to generate from the CVS version some files
|
||||
source tarball than from the SVN version, as you'll need to have more
|
||||
tools and make more steps to generate from the SVN version some files
|
||||
that are bundled with the source tarball.
|
||||
|
||||
Note that to build from the 0.10.0a source tarball on Windows with
|
||||
|
@ -1810,7 +1819,7 @@ echo "Mode: y">/proc/driver/aironet/ethN/Config
|
|||
echo "Mode: ess">/proc/driver/aironet/ethN/Config
|
||||
|
||||
On Linux with the driver in the 2.4.20 or later kernel, or with the
|
||||
CVS drivers from the airo-linux SourceForge site, you will have to
|
||||
SVN drivers from the airo-linux SourceForge site, you will have to
|
||||
capture on the wifiN interface if your Aironet card is ethN, after
|
||||
running the commands listed above.
|
||||
|
||||
|
@ -2099,4 +2108,4 @@ echo "Mode: ess">/proc/driver/aironet/ethN/Config
|
|||
For corrections/additions/suggestions for this web page (and not
|
||||
Ethereal support questions), please send email to
|
||||
ethereal-web[AT]ethereal.com .
|
||||
Last modified: Thu, May 13 2004.
|
||||
Last modified: Fri, July 16 2004.
|
||||
|
|
120
manuf
120
manuf
|
@ -506,7 +506,7 @@
|
|||
00:01:C8 ThomasConr # THOMAS CONRAD CORP.
|
||||
00:01:C9 Cisco # Cisco Systems, Inc.
|
||||
00:01:CA GeocastNet # Geocast Network Systems, Inc.
|
||||
00:01:CB Netgame # NetGame, Ltd.
|
||||
00:01:CB Evr
|
||||
00:01:CC JapanTotal # Japan Total Design Communication Co., Ltd.
|
||||
00:01:CD Artem
|
||||
00:01:CE CustomMicr # Custom Micro Products, Ltd.
|
||||
|
@ -3245,7 +3245,7 @@
|
|||
00:0C:A2 ScopusNetw # Scopus Network Technologies Ltd
|
||||
00:0C:A3 RanchoTech # Rancho Technology, Inc.
|
||||
00:0C:A4 PrompttecP # Prompttec Product Management GmbH
|
||||
00:0C:A5 Private
|
||||
00:0C:A5 NamanNz # Naman NZ LTd
|
||||
00:0C:A6 Mintera # Mintera Corporation
|
||||
00:0C:A7 MetroSuzho # Metro (Suzhou) Technologies Co., Ltd.
|
||||
00:0C:A8 GarudaNetw # Garuda Networks Corporation
|
||||
|
@ -3550,7 +3550,7 @@
|
|||
00:0D:D3 SamwooTele # SAMWOO Telecommunication Co.,Ltd.
|
||||
00:0D:D4 Revivio # Revivio Inc.
|
||||
00:0D:D5 O'RiteTech # O'RITE TECHNOLOGY CO.,LTD
|
||||
00:0D:D6 Private
|
||||
00:0D:D6 Iti # ITI LTD
|
||||
00:0D:D7 Bright
|
||||
00:0D:D8 Bbn
|
||||
00:0D:D9 AntonPaar # Anton Paar GmbH
|
||||
|
@ -4253,7 +4253,7 @@
|
|||
00:10:92 Netcore # NETCORE INC.
|
||||
00:10:93 CmsCompute # CMS COMPUTERS, LTD.
|
||||
00:10:94 Performanc # Performance Analysis Broadband, Spirent plc
|
||||
00:10:95 ThomsonMul # Thomson Multimedia, Inc.
|
||||
00:10:95 Thompson # Thompson Inc.
|
||||
00:10:96 Tracewell # TRACEWELL SYSTEMS, INC.
|
||||
00:10:97 WinnetMetr # WinNet Metropolitan Communications Systems, Inc.
|
||||
00:10:98 StarnetTec # STARNET TECHNOLOGIES, INC.
|
||||
|
@ -4526,6 +4526,110 @@
|
|||
00:11:A4 JstreamTec # JStream Technologies Inc.
|
||||
00:11:A5 FortunaEle # Fortuna Electronic Corp.
|
||||
00:11:A6 SypixxNetw # Sypixx Networks
|
||||
00:11:A7 InfilcoDeg # Infilco Degremont Inc.
|
||||
00:11:A8 QuestTechn # Quest Technologies
|
||||
00:11:A9 Moimstone # MOIMSTONE Co., LTD
|
||||
00:11:AA UniclassTe # Uniclass Technology, Co., LTD
|
||||
00:11:AB TrustableT # TRUSTABLE TECHNOLOGY CO.,LTD.
|
||||
00:11:AC SimtecElec # Simtec Electronics
|
||||
00:11:AD ShanghaiRu # Shanghai Ruijie Technology
|
||||
00:11:AE MotorolaBc # Motorola BCS
|
||||
00:11:AF Medialink- # Medialink-i,Inc
|
||||
00:11:B0 Fortelink # Fortelink Inc.
|
||||
00:11:B1 Blueexpert # BlueExpert Technology Corp.
|
||||
00:11:B2 2001Techno # 2001 Technology Inc.
|
||||
00:11:B3 Yoshimiya # YOSHIMIYA CO.,LTD.
|
||||
00:11:B4 WestermoTe # Westermo Teleindustri AB
|
||||
00:11:B5 ShenzhenPo # Shenzhen Powercom Co.,Ltd
|
||||
00:11:B6 OpenIntern # Open Systems International
|
||||
00:11:B7 MelexisNed # Melexis Nederland B.V.
|
||||
00:11:B8 Liebherr-E # Liebherr - Elektronik GmbH
|
||||
00:11:B9 InnerRange # Inner Range Pty. Ltd.
|
||||
00:11:BA ElexolPty # Elexol Pty Ltd
|
||||
00:11:BB Cisco # Cisco Systems
|
||||
00:11:BC Cisco # Cisco Systems
|
||||
00:11:BD Bombardier # Bombardier Transportation
|
||||
00:11:BE AgpTelecom # AGP Telecom Co. Ltd
|
||||
00:11:BF AesysSPA # AESYS S.p.A.
|
||||
00:11:C0 AdayTechno # Aday Technology Inc
|
||||
00:11:C1 4pMobileDa # 4P MOBILE DATA PROCESSING
|
||||
00:11:C2 UnitedFibe # United Fiber Optic Communication
|
||||
00:11:C3 Transceivi # Transceiving System Technology Corporation
|
||||
00:11:C4 Terminales # Terminales de Telecomunicacion Terrestre, S.L.
|
||||
00:11:C5 TenTechnol # TEN Technology
|
||||
00:11:C6 SeagateTec # Seagate Technology LLC
|
||||
00:11:C7 RaymarineG # RAYMARINE Group Ltd.
|
||||
00:11:C8 Powercom # Powercom Co., Ltd.
|
||||
00:11:C9 Mtt # MTT Corporation
|
||||
00:11:CA LongRange # Long Range Systems, Inc.
|
||||
00:11:CB JacobsonsR # Jacobsons RKH AB
|
||||
00:11:CC GuangzhouJ # Guangzhou Jinpeng Group Co.,Ltd.
|
||||
00:11:CD AxsunTechn # Axsun Technologies
|
||||
00:11:CE Ubisense # Ubisense Limited
|
||||
00:11:CF ThraneThra # Thrane & Thrane A/S
|
||||
00:11:D0 TandbergDa # Tandberg Data ASA
|
||||
00:11:D1 SoftImagin # Soft Imaging System GmbH
|
||||
00:11:D2 Perception # Perception Digital Ltd
|
||||
00:11:D3 Nextgentel # NextGenTel Holding ASA
|
||||
00:11:D4 Netenrich # NetEnrich, Inc
|
||||
00:11:D5 HangzhouSu # Hangzhou Sunyard System Engineering Co.,Ltd.
|
||||
00:11:D6 Handera # HandEra, Inc.
|
||||
00:11:D7 Ewerks # eWerks Inc
|
||||
00:11:D8 AsustekCom # ASUSTek Computer Inc.
|
||||
00:11:D9 Tivo
|
||||
00:11:DA VivaasTech # Vivaas Technology Inc.
|
||||
00:11:DB Land-Cellu # Land-Cellular Corporation
|
||||
00:11:DC GlunzJense # Glunz & Jensen
|
||||
00:11:DD FromusTec # FROMUS TEC. Co., Ltd.
|
||||
00:11:DE Eurilogic
|
||||
00:11:DF Arecont # Arecont Systems
|
||||
00:11:E0 U-MediaCom # U-MEDIA Communications, Inc.
|
||||
00:11:E1 BekoElectr # BEKO Electronics Co.
|
||||
00:11:E2 HuaJungCom # Hua Jung Components Co., Ltd.
|
||||
00:11:E3 BroadbandA # Broadband Access Products
|
||||
00:11:E4 DanelecEle # Danelec Electronics A/S
|
||||
00:11:E5 Kcodes # KCodes Corporation
|
||||
00:11:E6 Scientific # Scientific Atlanta
|
||||
00:11:E7 Worldsat-T # WORLDSAT - Texas de France
|
||||
00:11:E8 TixiCom # Tixi.Com
|
||||
00:11:E9 Starnex # STARNEX CO., LTD.
|
||||
00:11:EA Iwics # IWICS Inc.
|
||||
00:11:EB Innovative # Innovative Integration
|
||||
00:11:EC Avix # AVIX INC.
|
||||
00:11:ED 802Global # 802 Global
|
||||
00:11:EE Estari # Estari, Inc.
|
||||
00:11:EF ConitecDat # Conitec Datensysteme GmbH
|
||||
00:11:F0 Wideful # Wideful Limited
|
||||
00:11:F1 Qinetiq # QinetiQ Ltd
|
||||
00:11:F2 InstituteO # Institute of Network Technologies
|
||||
00:11:F3 GavitecAg- # Gavitec AG- mobile digit
|
||||
00:11:F4 Woori-Net
|
||||
00:11:F5 AskeyCompu # ASKEY COMPUTER CORP.
|
||||
00:11:F6 AsiaPacifi # Asia Pacific Microsystems , Inc.
|
||||
00:11:F7 ShenzhenFo # Shenzhen Forward Industry Co., Ltd
|
||||
00:11:F8 Airaya # AIRAYA Corp
|
||||
00:11:F9 NortelNetw # Nortel Networks
|
||||
00:11:FA Rane # Rane Corporation
|
||||
00:11:FB Heidelberg # Heidelberg Engineering GmbH
|
||||
00:11:FC HartingEle # HARTING Electric Gmbh & Co.KG
|
||||
00:11:FD Korg # KORG INC.
|
||||
00:11:FE KeiyoSyste # Keiyo System Research, Inc.
|
||||
00:11:FF DigitroTec # Digitro Tecnologia Ltda
|
||||
00:12:00 Cisco
|
||||
00:12:01 Cisco
|
||||
00:12:02 AudioInter # Audio International Inc.
|
||||
00:12:03 ActivNetwo # Activ Networks
|
||||
00:12:04 U10Network # u10 Networks, Inc.
|
||||
00:12:05 TerrasatCo # Terrasat Communications, Inc.
|
||||
00:12:06 IquestNz # iQuest (NZ) Ltd
|
||||
00:12:07 HeadStrong # Head Strong International Limited
|
||||
00:12:08 GantnerEle # Gantner Electronic GmbH
|
||||
00:12:09 Fastrax # Fastrax Ltd
|
||||
00:12:0A EmersonEle # Emerson Electric GmbH & Co. OHG
|
||||
00:12:0B ChinasysTe # Chinasys Technologies Limited
|
||||
00:12:0C Ce-Infosys # CE-Infosys Pte Ltd
|
||||
00:12:0D AdvancedTe # Advanced Telecommunication Technologies, Inc.
|
||||
00:12:0E Abocom
|
||||
00:17:00 Kabel
|
||||
00:1C:7C Perq # PERQ SYSTEMS CORPORATION
|
||||
00:20:00 LexmarkInt # LEXMARK INTERNATIONAL, INC.
|
||||
|
@ -4554,7 +4658,7 @@
|
|||
00:20:17 Orbotech
|
||||
00:20:18 CisTechnol # CIS TECHNOLOGY INC.
|
||||
00:20:19 Ohler # OHLER GmbH
|
||||
00:20:1A N-BaseSwit # N-BASE SWITCH COMMUNICATIONS
|
||||
00:20:1A MrvCommuni # MRV Communications, Inc.
|
||||
00:20:1B NorthernTe # NORTHERN TELECOM/NETWORK
|
||||
00:20:1C Excel # EXCEL, INC.
|
||||
00:20:1D KatanaProd # KATANA PRODUCTS
|
||||
|
@ -6314,7 +6418,7 @@
|
|||
00:91:D6 CrystalGro # Crystal Group, Inc.
|
||||
00:9D:8E CardiacRec # CARDIAC RECORDERS, INC.
|
||||
00:A0:00 Centillion # CENTILLION NETWORKS, INC.
|
||||
00:A0:01 Watkins-Jo # WATKINS-JOHNSON COMPANY
|
||||
00:A0:01 DrsSignalS # DRS Signal Solutions
|
||||
00:A0:02 LeedsNorth # LEEDS & NORTHRUP AUSTRALIA PTY LTD
|
||||
00:A0:03 StaefaCont # STAEFA CONTROL SYSTEM
|
||||
00:A0:04 Netpower # NETPOWER, INC.
|
||||
|
@ -6378,7 +6482,7 @@
|
|||
00:A0:3E AtmForum # ATM FORUM
|
||||
00:A0:3F ComputerSo # COMPUTER SOCIETY MICROPROCESSOR & MICROPROCESSOR STANDARDS C
|
||||
00:A0:40 AppleCompu # APPLE COMPUTER
|
||||
00:A0:41 Leybold-In # LEYBOLD-INFICON
|
||||
00:A0:41 Inficon
|
||||
00:A0:42 SpurProduc # SPUR PRODUCTS CORP.
|
||||
00:A0:43 AmericanTe # AMERICAN TECHNOLOGY LABS, INC.
|
||||
00:A0:44 NttIt # NTT IT CO., LTD.
|
||||
|
@ -7052,7 +7156,7 @@
|
|||
00:D0:B5 IpricotFor # IPricot formerly DotCom
|
||||
00:D0:B6 CrescentNe # CRESCENT NETWORKS, INC.
|
||||
00:D0:B7 Intel # INTEL CORPORATION
|
||||
00:D0:B8 Iomega # IOMEGA CORP.
|
||||
00:D0:B8 Iomega # Iomega Corporation
|
||||
00:D0:B9 MicrotekIn # MICROTEK INTERNATIONAL, INC.
|
||||
00:D0:BA Cisco # CISCO SYSTEMS, INC.
|
||||
00:D0:BB Cisco # CISCO SYSTEMS, INC.
|
||||
|
|
Loading…
Reference in New Issue