print

Error Capture

Error Packet Capture with OmniPeek Basic

OmniPeek Basic has the ability to capture error packets on the network. These errors include: Runt, Oversize, Frame Alignment, and CRC Errors. To capture errors on Wireless, supported wireless cards with a special WildPackets driver must be installed. To capture errors on Ethernet or Fast Ethernet, you must use one of the supported cards and a special WildPackets driver.

For information on Wireless Cards, Please visit OmniPeek Basic Wireless Drivers Page.

If you are not using one of the supported cards and the WildPackets driver, you will not be able to capture error packets. If your NIC reports error statistics, OmniPeek Basic will record those statistics, but it will not actually capture error packets. If your NIC does not report error statistics, the error statistics in OmniPeek Basic won't change. The only way to capture error packets is to use a supported card and a WildPackets driver.

Error packets can be captured, filtered on, triggered for and displayed in various windows in OmniPeek Basic.

For error packet capture, a WildPackets driver must be used in conjunction with one of the following cards.

Please note that WildPackets does not resell these cards and as most are legacy cards, they can be difficult to procure.

Ethernet Network PC Card/CardBus Cards*

* The CreditCard Ethernet (CE3B-100) does not work with the WildPackets Xircom driver. The following two cards have not been tested, but the WildPackets Xircom driver may work: RealPort Ethernet (RE-100), RealPort2 Ethernet (R2E-100).

**Instructions for installing the WildPackets special Digital driver (Dc21x4) for error packet capture can be found in the Readme.txt file located in the Driver\Dc21x4 directory where OmniPeek Basic is installed. Please note that the special driver is supported for PCI adapters on Windows 98, ME, Windows NT 4.0, Windows 2000, and Windows XP.