Cisco AP Adapter for the OmniEngine

You must be a MyPeek member to download our extensibility solutions. Click here to learn more about the benefits of membership and find out how to sign up for free.

Download Remote Adapter

You must have a valid maintenance contract to download this file.
If you are not a WildPackets Maintenance Customer but would like to purchase a Maintenance contract for your WildPackets product please click here for sales information.
Downloaded : 299 Times
Rating : Not Yet Rated

View Comments (2)

Cisco AP Adapter for the OmniEngine

Category : Remote Adapters

Submitted By : SpacePacket


Breaking News
We have just released a new version of the Cisco AP Adapter for the OmniEngine that allows each capture to filter on packets from a particular Cisco AP.

Background
A few years ago, even before the OmniEngine was available, WildPackets introduced the Cisco AP Adapter for the OmniPeek Console. With this tool, engineers could use one or more Cisco AP's, either from a wireless mesh in a store or warehouse, or in a lab environment, to capture and analyze traffic in the area on one or more channels. This solution increased the ROI for our customers who could use the Cisco AP's they already owned as probes. This solution also changed the rules of the game for our customers, who previously had to either scan multiple channels and as a result only see part of the picture, or manually concatenate files from different channels together. With the Cisco AP Adapter, our customers could easily aggregate packets from multiple AP's listening on different channels into a single capture. Aggregating these channels made it possible to do roaming analysis. This Cisco AP Adapter became so popular with our customers that we integrated into the core product. Now this functionality is available right out of the box.

Fast Forward
Jump ahead a few years, and now our customers are quickly realizing the many benefits of distributed network monitoring and analysis with the OmniEngine. By deploying OmniEngines into different segments of the network, engineers have greater, more readily accessible, visibility into those network segments. The migration to OmniEngines is easy, since the console most of our customers already use for local capture and analysis is the same console used to connect and perform remote capture and analysis on OmniEngines. And unlike the Cisco AP Adapter, the OmniEngine does not stream packets all the way back to the console. With the OmniEngine, all of the capture and analysis is done locally, and the console is used to view the results.

Jump to now
So here we are, and WildPackets has just revolutionized the world of wireless capture and aggregation again, by porting the Cisco AP Adapter to the OmniEngine. By integrating these two products, the Cisco AP Adapter and the distributed OmniEngine, our customers are able to capture and aggregate packets from multiple Cisco AP's directly into a local OmniEngine, without having to stream the packets all the way back to the console. The console is then used through a secure and compressed connection to view the results. Huge I say, huge!

Be a hero!
Why wait? If you already have a Cisco AP mesh deployment, and you want to achieve the highest level of ROI possible, then buy an OmniEngine today and download the Cisco AP Adapter for the OmniEngine. You will then be able to more easily troubleshoot the wireless mesh with the equipment you already have, remotely. The CFO loves ROI. Your CFO will be very happy.

Configuration
To install and use the Cisco AP Adapter for the OmniEngine, first download the plug-in, and install it onto the machine running OmniEngine. After restating the OmniEngine, create a new capture and select the CiscoServer Adapter as shown below.



Filtering
With the Cisco AP Server Adapter for the OmniEngine, each capture can be configured to either accept packets from all Cisco AP's, or from only a particular AP. The default is to collect from all AP's.

To configure a capture to collect packets from a particular Cisco AP, you must install the Cisco Server Adapter on the machine running the OmniPeek Console. The plug-in that runs on the console side is the same ciscoserver.dll and ciscoserver.he files that run on the engine side.

The IP address of the Cisco AP for each capture is configured from the CiscoServer Analysis entry in the capture options dialog when you are creating the capture.



To create and configure these captures from a script, you will have to create a capture template from the OmniEngine Captures tab, and configure it with the desired settings.



Once you have created this capture template and closed OmniPeek, it will be saved to “C:Users[YOUR ACCOUNT]Application DataWildPacketsOmniPeek” in the file RemoteCaptureTemplates.xml. Below is a sample of the the section describing the IP address of the Cisco AP looks like this:
<obj name="PluginsConfig" clsid="{862E83A1-BC76-479A-A7FD-06CD6451815A}">
     <plugins>
             <plugin name="CiscoServer Analysis" clsid="{BB04608A-EDC1-42C0-8AA5-C0CB6510B3FC}">
                       <ip enabled="1">1.2.3.4</ip>
              </plugin>
      </plugins>
</obj>


History

Version 1.0.0.2 11/11/2009
- Add AP filtering


Version 1.0.0.1
- First release to MyPeek

Comments

Only works on 32Bit engine versions.
Posted by: Joe Habib on Thursday, December 5th, 2013 at 11:40 AM
I'm still not clear how this works. Do there have to be wireless adapters connected to the OmniEngine that are receiving the wireless signals for this to work, or is the OmniEngine connecting to the AP's through the network to get packets?
Posted by: DG NOC on Wednesday, August 15th, 2012 at 7:53 AM