|
|
||
|
|
||
|
|
||
|
|
||
![]()
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
|
First be sure the analyzer is placed where the tagged frames exist, this is generally on a switch trunk (a link that connects switch-to-switch). Second verify that your switch is not stripping the VLAN tags, you may need to contact your switch manufacturer. Lastly, the network interface card may strip 802.1q tags at the adapter/driver level. By default, Intel adapters strip the VLAN tag before passing it up the stack. Some Broadcom adapters also exhibit this behavior. Possible fixes for Intel and Broadcom adapters can be found below, for other adapters please contact your NIC manufacturer. Unsupported Fix for Broadcom Adapters: ** Please backup your registry before making these modifications. ** Please look for the following registry key and follow the steps listed below. This fix is not supported by WildPackets. HKEY_LOCAL_MACHINE-->SYSTEM-->CurrentControlSet
Unsupported Fix for Intel Adapters: http://support.intel.com/support/network/sb/CS-009720.htm Another solution is to purchase a tap. TAPs are passive and independent of the network. Please call (925) 937-3200 or write to sales@wildpackets.com to find out more about TAPs.
OmniEngine uses port 6367/TCP/UDP.
Start a Monitoring Capture or a New Capture -> Select the Statistics Output View. Reports can be saved in CSV, TEXT, or XML, HTML.
Right-click on any Expert event and choose EventFinder Settings. Click the Show Info button for a description of the event and possible causes and remedies.
If the "Client for Microsoft Networks" driver is not installed, the service "Workstation" is also not installed, which may cause OmniEngine to not start up.
Click the Peer Map view and click Open. The supported file types are *.BMP, *.JPEG, *.GIF, *.EMF, *.WMF, *.TIFF, *.PNG, *.ICO.
Jitter is independent either direction. If both end VoIP devices send out periodic RTCP report packets, then the expert is checking jitter from the perspective of both endpoints, i.e. both ways. If only one device is sending RTCP packets, then it's the direction TO that device. Not all VoIP devices send RTCP reports. To measure data at the point of capture, OmniPeek analyzes the RTP stream independently of RTCP reports. This is not necessarily the jitter as received by an end-point (unless OmniPeek Professional is on the end segment), but rather gives you a reading for jitter for some intermediate path.
Yes, here’s how:
You will need an additional adapter to use for network services or use a multi-port adapter like the Intel dual or quad port adapters. These cards could connect via one port and capture on the additional, available ports.
The summary statistics feature allows you to monitor key network statistics in real time and save these statistics for later comparison. Use this feature to baseline “normal” network activity, save the data, then compare saved statistics with those observed during periods of erratic network behavior to help pinpoint the cause of the problem. Summary statistics are also extremely valuable in comparing the performance of two different network segments. For example, a field support engineer could compare the real-time statistics on a client’s network with a saved “healthy” router snapshot and easily diagnose or eliminate the source of inconsistent or poor router performance. To baseline with summary statistics: Choose Monitor > Summary. The Summary Statistics window appears.
Be sure you have clicked the yellow bar "Click here to send changes".
Communications between nodes is indicated with line segments. The line between nodes can be color-coded to show which protocol is used. The thickness of the line indicates the volume of traffic between nodes. For more information see the OmniPeek User Guide or the online Help.
To start a Forensics Capture:
Be sure the modules are enabled. Start a new Monitoring Capture or New Capture -> Click the Performance View -> Traffic History and Top Talker Statistics should be checked. Please also note that the Dashboard view is available only when Monitoring and Capturing. Forensic Captures by default have all Performance Statistics unchecked.
Yes, with the use of a supported Atheros chipset-based adapter and the WildPackets 3.0.1.12 and 4.2.2.9 Atheros driver.
The OmniEngine supports WPA-PSK and WEP encryption.
The only console that was designed to work simultaneously with an engine is OmniPeek Connect. OmniPeek Connect provides the ability to locally configure and view the engine’s analysis as the engine is capturing packets and performing analysis.
In the Capture/Monitor Options, select Performance. For peak performance, right click on one of the features and choose Disable All. This way, the OmniEngine will function at peak performance, but the features are still available when needed. When you need a particular feature, you can always enable it. As you enable/disable individual features, the performance bar at the bottom of the Performance Options dialog will move to show you an estimate of the impact of each feature. Here are a few more tips to improve the performance of the OmniEngine:
The following component is an additional module (not included in the standard package):
If you need one of the other features, you can enable it when you are actually viewing the capture file. Also if you're on a switched network, you can try using the switch's mirroring or monitoring capability to zero-in on the traffic you're looking for. Try only mirroring ports one by one to avoid overloading the analyzer with traffic. For more information, please see our whitepaper which also applies to the OmniEngine product: Applying EtherPeek to Switched and Gigabit Ethernet Network Management.
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 Windows XP/Windows Server 2003: Please use the following steps to configure the system:
In order to capture wireless traffic with the OmniEngine, you must install a custom WildPackets driver. A list of supported cards and the WildPackets drivers can be found here: Please find your card from the list and download the appropriate driver. ***First install and test the adapter with the OEM driver. Do not install the WildPackets driver until the adapter is functioning properly on your network using the OEM driver.*** Also, be sure to follow the ReadMe carefully; you must choose 'Don't search. I will choose the driver to install.'
The Profile tab lets you save Peer Map configurations settings into a single profile that controls the appearance and layout of the Peer Map. The Configuration tab lets you control what part of the traffic in the Capture window’s buffer is displayed in Peer Map. The Node Visibilities tab displays node counts, and nodes that are both shown and hidden in the Peer Map. For example, if this option is set to Always Hide, then all nodes that have not had their visibility assigned by the user will be hidden. This is useful if, during a live capture, the user doesn’t want new nodes to appear on the Peer Map as they are discovered.
Peek *must* capture the complete (EAPOL) key exchange to successfully decrypt WPA-PSK encrypted traffic. This exchange consists of the 4 packet Pairwise Master key (PMK) and the 2 packet Group Temporal Key (GTK). The below is an example of a successful EAPOL capture. |
|
||||||||||||
| 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 |
|
China
Japan
UK
United States





