|
|
||
|
|
||
|
|
||
|
|
||
![]()
OmniPeek Enterprise
OmniEngine Enterprise
Support FAQs
Tech Tips
Supported Hardware
System Requirements
Getting Started Guide
OmniPeek Professional
OmniPeek Basic
OmniEngine Desktop
OmniVirtual
Omnipliance
Omnipliance Portable
Omni Wireless Sensor
|
Capturing of 802.11n packets
At the present time, we support the Buffalo Nfiniti, Model # WLI-CB-AG300N and Netgear WN511T, both using the Marvell driver that is supplied with Omni 5.1.
This is because Omni 5.1 is reporting the actual speed of the adapter’s connection, not its maximum data rate.
These channels have been added to the Network Policy screen in OmniPeek 5.1.
Since all WildPackets products make use of the underlying Operating System for all time computations, no patch will be necessary for our products to operate correctly with the new Daylight Saving Time Change.
There are two possible causes of this:
OmniEngine is not compatible with User Account Control (UAC) under Windows Vista. In order to run OmniEngine under Windows Vista, you must disable UAC
OmniPeek will load and run on 64 bit operating systems in 32 bit compatibility mode and supports AMD and Intel x86 processors including the 64 bit capable Pentium and Xeon processors.
Yes, Omni has fully integrated the Application Performance Index (Apdex).
Apdex is an attempt to represent user satisfaction with application performance as a numeric score from 0.00 (horrible) to 1.00 (perfect). Calculations are based on how long it takes to complete each measured task.
Each individual task gets an Apdex score of 1.00, 0.50, or 0.00, depending on task duration relative to a user-defined threshold duration "T":
If an individual task completes within a user-defined threshold duration, the user is considered "satisfied" with application performance, and the task gets an Apdex score of 1.00. If an individual task takes between one and four times the user-defined threshold duration, the user is considered "tolerating" application performance, and the task gets an Apdex score of 0.50. If an individual task takes more than four times the user-defined threshold duration, the user is considered "frustrated" with application performance, and the task gets an Apdex score of 0.00. For example, if you set the threshold for web applications at 3 seconds, then any time you can completely load a web page within 3 seconds, you are "satisfied" and score 1.00. If it takes more than 3 seconds, but no more than 12 seconds (4 times 3 seconds), you are merely "tolerating" performance, and score 0.50. If it ever takes more than 12 seconds, you are frustrated, and get an Apdex score of 0.00.
The OmniEngine Manager is included with both OmniPeek and OmniEngine. It provides an interface for connecting to, configuring and updating remote OmniEngines. See the OMC Readme or the OMC Help for more information on OmniEngine Manager.
Forensics Capturing provides the means to easily organize, filter, and pinpoint the data of interest. Captures are indexed and can be searched across multiple data collection files using specific area of interest, start time, end time and any available filters.
OmniEngine supports RADIUS and TACACs + authentication as well as Windows domain spaces to maintain logon credentials.
G.711 µ-law |
|
||||||
| COPYRIGHT © 2008 WILDPACKETS, INC — PRIVACY STATEMENT · CONTACT US | CORPORATE · PRODUCTS · SOLUTIONS · SERVICES · SUPPORT · PARTNERS · BUY NOW |
|
All registered and unregistered trademarks are the sole property of their respective owners |
|
United States
UK





