WildPackets

Tech Tips

OmniPeek Basic

  • When upgrading to OmniPeek 6.8, should I uninstall my older version of OmniPeek first?
  • I have entered the correct key or passphrase but the encrypted packets are not being decrypted. Can you please tell me what's wrong?
  • How do I create a filter to span multiple ports?
  • How do I capture VLAN packets?
  • Is there a way to only capture the header of a packet?
  • What do the colors of the globes represent in the WLAN view?
  • How do I change port numbers for an existing protocol?
  • How do I add port numbers for an existing protocol?
  • How do I add a custom protocol to OmniPeek?
  • How can OmniPeek Basic help me baseline my network?
  • What are some of the keyboard shortcuts?
  • Can I use the Peek analyzer to assist with firewall rules?
  • How do I use port numbers instead of port names?
  • How accurate are the Delta and Relative times in the Packet view?
  • How secure is OmniPeek?
  • Are there any tips to optimize performance?
  • I am unable to start a wireless capture. When I select 'OK' in the Capture Options I receive the error 'The adapter "Wireless Network Connection" is not supported by this product.' What am I missing?

    • Return to top of page When upgrading to OmniPeek 6.8, should I uninstall my older version of OmniPeek first?

    When you run the OmniPeek installation it will automatically prompt you that it has found an older version. Just select Remove and it will unintall your old version before it begans to install the new.

    Return to top of page I have entered the correct key or passphrase but the encrypted packets are not being decrypted. Can you please tell me what's wrong?

    OmniPeek *must* capture the complete (EAPOL) key exchange to successfully decrypt WPA/WPA2 encrypted traffic.

    Return to top of page

    Return to top of page How do I create a filter to span multiple ports?

    You can create an Advanced or Simple filter to span individual ports. Ports can be entered and separated by commas and/or semicolons.

    Here is how:

    1. Click View/Filters to bring up the filters window.
    2. Click the Insert button (Green).
    3. Select Simple or Advanced for Filter Type.
    4. Select Port Filter and add the port numbers. Use commas and semicolons to separate the port numbers.

    Return to top of page How do I capture VLAN packets?

    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

    1. You need to find the right instance of the driver in the registry.
    2. Run Regedit.
    3. Search for "TxCoalescingTicks" and ensure this is the only instance that you have.
    4. Right-click on the instance number (eg. 0008) and add new string value.
    5. Enter "PreserveVlanInfoInRxPacket" and give it value "1".

    Unsupported Fix for Intel Adapters:

    http://www.intel.com/support/network/sb/cs-005897.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.

    Return to top of page Is there a way to only capture the header of a packet?

    Yes, here's how:

    1. Click View/Filters to bring up the filters window.
    2. Click the Insert button (Green )
    3. Select Simple or Advanced for Filter Type.
    4. Select Protocol Filter.
    5. Select the Protocol and check Slice to Header.

    Return to top of page What do the colors of the globes represent in the WLAN view?
    • Blue - ESSID
    • Pink - Access Point or Ad Hoc Equivalent
    • Orange - STA or Client
    • Gray - Admin or otherwise unknown
    • Gray with (?) - Indications for a particular node are contradictory or unexpected

    Return to top of page How do I change port numbers for an existing protocol?

    For example, maybe you want all traffic on port 80 and port 8000 to show up under HTTP in the Packet view, Protocol statistics, etc. In that case, you will need to modify the following file with a Text Editor:

    C:Program FilesWildPacketsOmniPeek1033pspecs.xml

    You can search for your protocol's PSpec Name (i.e. HTTP) and when you find the protocol, you can modify the existing port number(s).

    For more information on ProtoSpecs, please log into MyPeek and under the Resources section go to Developer Documentation and take a look at the ProtoSpecs XML Writing Guidelines.

    http://mypeek.wildpackets.com/

    Return to top of page How do I add port numbers for an existing protocol?

    The tag will define a port number. The example is using port number 1234. You can add additional ports by adding additional tags. See example below.

    1234
    1235
    1236

    For more information on ProtoSpecs, please log into MyPeek and under the Resources section go to Developer Documentation and take a look at the ProtoSpecs XML Writing Guidelines.

    http://mypeek.wildpackets.com/

    Return to top of page How do I add a custom protocol to OmniPeek?
    1. Exit OmniPeek.
    2. First, make a backup copy of the pspecs.xml file. OmniPeek will not load if the pspecs.xml file is missing or corrupted.
      Note: By default the pspecs.xml file is located in "C:Program FilesWildPacketsOmniPeek1033" for the English- localized version. For other languages, the final subdirectory ("1033") will be equal to the language code for the OmniPeek's localized language.
    3. Open the pspecs.xml file in your favorite text or XML editor.
      Note: Please make sure you add the protocols in the right section (TCP/UDP) and that the higher port numbers go further down in the file.
    4. Create a new entry (see example below).

      1483
      MyProtocol - Long Name
      MyProtocol - Short Name
      This is my protocol.
      color_2
      1234

    Quick Notes:

    The PSpecID is a numerical identifier for the protocol. It must be unique-that is, no two protocols are allowed to have the same PSpecID. You must choose a PSpecID that is not used anywhere else in the file.

    The tag will define a port number. The example is using port number 1234. You can add additional ports by adding additional tags. See example below.

    1234
    1235
    1236

    The PSpec Name will be displayed in the Protocol column of the Packets tab.

    The LName will be displayed in the Protocol Info dialog box (accessed by right-clicking the protocol and choosing Protocol Info).

    The SName will be displayed in the Protocol statistics.

    The Desc will be displayed in the Protocol Info box (Desc is optional. You can delete it if you don't want to write a description for your protocol).

    Color will be the color used for the protocol. Colors are defined at the beginning of the document. Color is optional. You can delete it and OmniPeek will choose a color for the protocol.

    CondSwitch tells OmniPeek how to recognize the protocol. For now, all you have to do is edit the "SrcPort ==" and "DestPort ==" entries to contain the port number that your protocol uses. These two entries should be the same.

    For more information on ProtoSpecs, please log into MyPeek and under the Resources section go to Developer Documentation and take a look at the ProtoSpecs XML Writing Guidelines.

    http://mypeek.wildpackets.com/

    Return to top of page How can OmniPeek Basic help me baseline my network?

    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 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.

    Return to top of page What are some of the keyboard shortcuts?

    Return to top of page Can I use the Peek analyzer to assist with firewall rules?

    The following steps will give you some indication of which ports are open:

    1. Packet slice at 70Bytes (gives you TCP/UDP headers)
    2. Go to the Expert and select Flat
    3. Enable "Port Numbers" optional Column
    4. Disable Resolve Port Names (right click)
    5. Click and sort Port Numbers

    Return to top of page How do I use port numbers instead of port names?

    Right click the column header and select the fields you would like to see. Then right click again and choose Packet List Options > Format tab and deselect "Show port names". You should now see port numbers instead of names.

    Also good to know, the source and port field numbers are always displayed in the 'Summary' field (Src=###,Dst=##) in addition to other packet information.

    Return to top of page How accurate are the Delta and Relative times in the Packet view?

    In regards to wireless, if using an Atheros driver v3.0.1.x and above the accuracy is approximately 1 micro- second as the packets are being time-stamped by the hardware, versions under 3.0.1.x use software timestamps. If using WinXP and other NT based systems packets have an approximate accuracy of .1 milliseconds.

    In regards to Ethernet, non-GAC Ethernet adapters use software timestamps and the accuracy depends on the OS. If using WinXP and other NT based systems packets have an approximate accuracy of .1 milliseconds. The WildPackets Gigabit Analyzer Cards provide hardware timestamps and have an approximate accuracy of 10 nanoseconds.

    Return to top of page How secure is OmniPeek?

    Network analysis tools are powerful and must be protected from misuse. Data captured and sent across the network may be sensitive, so OmniPeek has been designed from the ground up to adhere to strict IT security requirements. By default, all traffic between the Engine and Console is compressed and encrypted and in addition to Windows Security being used for access control to the OmniEngine and application features, TACACs and RADIUS authentication are supported also.

    Return to top of page When I use OmniPeek to monitor my high speed network, the application tends to slow down. Are there any tips to optimize performance?

    In the Capture/Monitor Options, select Performance. For peak performance, right click on one of the features and choose Disable All. This way, OmniPeek 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 OmniPeek:

    Disable the Monitor adapter (Monitor/Select Monitor Adapter/None)

    Turn off scroll during capture. Control K will start/stop scroll.

    Disable passive name resolution. Under Tools/Options/Name Resolution, uncheck enable passive name resolution.

    Turn off any automatic report production for monitor and/or capture. Under Monitor or Capture options, select Statistics Output. Uncheck Save statistics report.

    Return to top of page I am unable to start a wireless capture. When I select 'OK' in the Capture Options I receive the error 'The adapter "Wireless Network Connection" is not supported by this product. What am I missing?

    In order to capture wireless traffic with OmniPeek, you must install a custom WildPackets driver.

    A list of supported cards and the WildPackets drivers can be found here:
    http://www.wildpackets.com/support/downloads/drivers

    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.'

Copyright © 2012 WildPackets, Inc
All registered and unregistered trademarks are the sole property of their respective owners