OmniPeek Enterprise
OmniEngine Enterprise
OmniPeek Professional
OmniPeek Basic
OmniEngine Desktop
Support FAQs
Tech Tips
Supported Hardware
OmniVirtual
Omnipliance
Omnipliance Portable
Omni Wireless Sensor

Supported Hardware

OmniEngine Desktop

Ethernet

OmniEngine Desktop will run with any NDIS 3 or higher compatible Ethernet promiscuous mode network adapter. Almost all Ethernet adapters on the market today meet this requirement. For example, we are compatible with adapters from 3Com, Intel, Xircom, SMC, and many others.

Traffic from wireless NICs is stripped of 802.11 headers and treated as 802.3 Ethernet traffic.

Error capture using OmniEngine Desktop

Wireless

For wireless packet capture, OmniEngine requires the installation of a special driver corresponding to the supported wireless network adapter. WildPackets has tested Marvell-based, Atheros-based and Intel Centrino 3945-based cards for wireless capture. Other wireless cards may work with this version to the same degree that they worked in prior versions; however, these cards are not recommended. For more information and to download wireless drivers, please visit: OmniPeek Enterprise Wireless Drivers Page.

Download a demo of OmniPeek
Custom Integration & Engineering
WildPackets understands that one size does not fit all. Moreover, we all face new challenges every day. WildPackets Custom Engineering performs software development and systems integration, complementing WildPackets products and enhancing the capabilities of Network Operations Centers.
Learn more...

Network Analysis & Consulting
WildPackets offers a full spectrum of professional services, available remote and on-site. Our network engineers provide expertise for your network troubleshooting, capacity planning, or baseline performance analysis needs.
Learn more...

Tip of the Month
Don’t Lose The Tags
WildPackets’ Technical Support Team regularly receives questions about capturing VLAN (Virtual LAN) tags in packets. Some customers report that they cannot see VLAN tags when capturing packets from their switches. The tags are usually missing because the capture configuration or the location of OmniPeek (or Omni Engine) is incorrect. So, this tip is aimed at understanding VLAN tags and how they can be captured using OmniPeek Product Family.