Support FAQs

• What is the extent of 802.11n support in Omni5?
• What adapters do you support for 802.11 n captures?
• When I configure a capture with my Buffalo card, it reports a speed of 1Mbps instead of 54Mbps in the Capture Options. Why?
• Why are the 40Mhz 802.11n channels missing from the Expert Network Policy screen?
• Are you going to release a patch for WildPackets Products in order to make them compatible with the new 2007 Daylight Savings Time changes?
• I installed my OmniEngine on my Vista laptop, but the application will not run. What is the problem here?
• Will OmniEngine run on 64 bit Operating Systems?
• What type of authentication is supported on the engine?
• Can I use both the OmniEngine and OmniPeek Analyzer at the same time on the same machine?
• When trying to connect to the engine, why do I receive the following error? "An error occurred: The login attempt failed (Error code: 0x8009030C)".
• What is happening when I enable compression on my engine?
• When I start a capture I do not see packets showing up in the Packets view. The "Packets received" and "Packets filtered" counters are both incrementing so why don’t I see packets?

What is the extent of 802.11n support in Omni5?

Capturing of 802.11n packets
Fully decode all 802.11n specific information elements in packets.
Provide 802.11n-specific statistics, analyses and expert diagnoses.

What adapters do you support for 802.11 n captures?

At the present time, we support the Buffalo Nfiniti, Model # WLI-CB-AG300N adapter using the Marvell driver that is supplied with Omni 5.

When I configure a capture with my Buffalo card, it reports a speed of 1Mbps instead of 54Mbps in the Capture Options. Why?

This is because Omni 5 is reporting the actual speed of the adapter’s connection, not its maximum data rate.

Why are the 40Mhz 802.11n channels missing from the Expert Network Policy screen?

We apologize for any inconvenience. These channels will be added to the Network Policy screen in a subsequent version of OmniPeek.

Are you going to release a patch for WildPackets Products in order to make them compatible with the new 2007 Daylight Savings Time changes?

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.

Important Vista Note:

Vista Operating System has a facility for dynamic Daylight Saving Time calculations that takes into account the fact that different years may have different DST dates. The next release of the OmniPeek Product Family (available end of Jan. 2007) will include the code to use this new operating system facility.

The end result is that everything will work correctly with Vista, but if a user has XP with the DST hotfix installed, the duration of captures that span the actual time change in past years may be incorrect since XP does not have the facility to understand that different years may have different DST dates.

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.

The Omni Management Console (OMC) 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 Omni Management Console.

OmniEngine supports RADIUS and TACACs + authentication.

The only console that was designed to work simultaneously with an engine is OmniPeek Enterprise Connect. OmniPeek Enterprise Connect provides the ability to locally configure and view the engine’s analysis as the engine is capturing packets and performing analysis.

The OmniEngine will not allow logins with a blank password. Please add a password to your account and try logging in again. If you are not logging in with a blank password, please see the instructions below.

OmniEngine supports authentication using Windows authentication services. In order to allow remote users to connect to an engine, the system administrator must configure the computer where the engine is to be installed.

Security Note: Users allowed to use OmniEngine are NOT required to have Administrative privileges and we recommend restricting their rights to minimize potential security risks, especially if the engine is accessed from outside of a firewall.

Disable Guest Network Logins
By default a network login will give each user "guest" credentials. This must be changed so that network logins will provide credentials based on the user's identity. Note: If your network uses a domain to control access, you must disable the Guest account on the domain controller.

Windows XP/Windows Server 2003: Please use the following steps to configure the system:

• Open the "Local Security Policy" editor from the "Start | Settings | Control Panel | Administrative Tools" menu. Alternatively, launch the "Administrative Tools" from the Control panel window.
• Under the "Local Policies" heading, click on "Security Options".
• Ensure the following settings are set:
• Accounts: Guest Account Status - Disabled
• Network Access: Sharing and security model for local accounts - Classic

When compression is turned on, all communications other than the initial setup between a console and engine are compressed. The ZIP format is used for run-time compression. Compression rates will vary based on the data being compressed. If you transfer a saved capture file from the engine to a console, it will be compressed on the engine side and uncompressed on the console before saving locally.

Running captures are not transferred en-mass from engine to console. The console asks the engine for various information required to update a capture's UI, and the engine supplies the information. Both the request and the reply are compressed.