



|
|
Yes, here’s how: APeek.exe [/autoload |/autostart ] [template1] [templateN] The /autoload switch loads the specified Capture Template (*.ctf) file(s). The /autostart switch loads the specified template(s) and begins capture. Multiple templates may be listed, separated by a space. You can use the * (asterisk) character or the ? (question mark) character as wildcards in specifying template names, following standard Windows wildcard usage.In a default installation of AiroPeek, the command line would be started from:
To automatically load template file capture1.ctf, for example, the command would be:
The Peek Country setting in the driver would need to be set to ‘ Japan’ to support these frequencies. In order to capture packets in a regulatory domain (i.e. country) different than the one the adapter was bought in originally, you must change the "Peek Country" code being used by the adapter. The "Peek Country" code is only used by Peek and does not have any effect on the country code used for network services. To change the adapter's "Peek Country" code on Windows XP, follow these steps:
To change the adapter's "Peek Country" code on Windows 2000, follow these steps:
You can create an Advanced or Simple filter to span multiple ports. Ports can be entered and separated by commas and/or semicolons. Here’s how:
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.
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, AiroPeek analyzes the RTP stream independently of RTCP reports. This is not necessarily the jitter as received by an end-point (unless AiroPeek is on the end segment), but rather gives you a reading for jitter for some intermediate path.
Yes, here’s how:
The Visual Expert shows pictures of what is happening in a selected conversation, or flow. Click on the Expert View. There are 6 tabs of the Visual Expert:
Open the captures you would like to compare.
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:
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).
The <CondSwitch> tag will define a port number. The example is using port number 1234. You can add additional ports by adding additional <CondSwitch></CondSwitch> tags. See example below.
For more information on ProtoSpecs, please visit our The WildPackets Developer Network (WPDN) and under the documentation section take a look at the ProtoSpecs XML Writing Guidelines.
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 <CondSwitch> tag will define a port number. The example is using port number 1234. You can add additional ports by adding additional <CondSwitch></CondSwitch> tags. See example below.
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 AiroPeek will choose a color for the protocol. CondSwitch tells AiroPeek 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 visit our The WildPackets Developer Network (WPDN) and under the documentation section take a look at the ProtoSpecs XML Writing Guidelines.
You can use the Locate Node feature if you are using AiroPeek on a laptop. Under the Wireless View, select WLAN. Right-click the source and choose Locate Node. AiroPeek will create a live signal strength graph for this node in the Graphs tab, and then switch your display to the new graph automatically. The higher the signal strength, the closer you have moved to the source node. Please also see our white paper on Identifying and Locating Rogue Access Points. http://www.wildpackets.com/elements/tutorials/RogueAccessPoints.pdf
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.
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.
Yes, you can play up to 5000 voice packets.
Hold down <Ctrl> + <E>
Yes, you can automate captures based on an alarm, here’s how: In this example we will use “Average Utilization”.
Instructions Either time/date or packets passing through the filters activate triggers. Alarm messages create a signal that is acted upon by the notifications module, which causes an action to occur (Log, Email, Sound, Execute, log to syslog server or send SNMP traps).
Yes, this is possible. For instance, if I have the vendor ID of the MAC (00:04:75 for 3Com), your filter would like look this 00:04:75:*:*:* First, confirm Capture Options/General/Continuous capture is checked. If you are using Windows XP, you will need to turn off "Wireless Zero Configuration". This service sometimes tries to take control of the wireless adapter, when you are capturing packets. If this happens, AiroPeek will stop capturing. You can go to properties on your wireless card, select the wireless networks tab, and uncheck the "Use Windows to config my wireless network settings" box, or go into services to stop the wireless zero config service.
This is a known issue with the driver. Please go to http://www.wildpackets.com/support/hardware/ap_atheros5001plus_driver for more information and an updated driver.
AiroPeek uses RF monitor mode to capture packets from the network. RF monitor mode is superior because it allows AiroPeek to capture all of the packets it sees on a single channel, no matter what Access Point they are going to, what vendor's equipment sent the packets, or who the packets are addressed to. Unfortunately, as you have noticed, when the wireless NIC is placed into RF monitor mode, it cannot be used for normal data transfer. This is not a limitation of AiroPeek, the drivers, or even the wireless NIC; it is simply a physical limitation of the RF technology. Some customers have gotten around this limitation by placing two wireless cards into their laptops simultaneously. One card is used for data transmission and the other card is used for capturing with AiroPeek. This depends on whether the NICs' form factor allows it. For example, the Cisco cards are relatively thin and will fit into the bottom PCMCIA slot with an Agere card on top, but Agere cards are thicker and probably won't fit in the bottom slot with a Cisco card on top. In order to keep the drivers separate, the cards should be from different vendors- this is very important! So, for example, you might use a Cisco 340 card for AiroPeek and an Agere card for sending data.
We use the maximum link speed of the wireless card which would be 11Mbits/s.
First, make certain that your adapter card is working normally on your network. Are you associated with an Access Point? Can you browse the internet? Verify you have installed a supported driver. Next, make sure you capturing on the correct channel, Go to Capture/Capture Options/802.11. If you have checked these two things and still can't capture, contact us via our Technical Support Form.
Unfortunately, Atheros does not support this usage so the WildPackets driver also does not support the simultaneous use of multiple Atheros-based adapters. One of the Atheros-based cards would need to be disabled for the other Atheros-based card to function. If you must connect to the network and also use AiroPeek, you will need to obtain another card with a different chipset, i.e. Realtek, Agere, Symbol, please check our list of supported adapters: http://www.wildpackets.com/support/product_support/airopeek/hardware
AiroPeek recognizes the type of preamble from the Capability Info field contained in management and control frames from the AP.
You will need to create a VoIP Analysis Module .ini file.
Example *.gst file
To add custom ports to Peek VX, click on the VoIP tab.
Yes. To ignore signaling:
(Note: After this, you will not see signaling on the VoIP view.)
In order to capture wireless traffic with AiroPeek, 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/product_support/airopeek/hardware 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.'
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). Below is an example of a successful EAPOL capture.
Note: If the initial key exchange is not captured, you will have to wait for your access point to re-key, or force a re-key by re-association. |
MyPeekCommunity Portal
Training / Courses
Product Tips & Tricks
|
Lawful Intercept
Deploying & Testing Applications
Distributed Networks
Network Baselining
Network Forensics
Network Performance Analysis
- NetFlow
Network Performance Management
Network Security
Network Troubleshooting
Product Development Support
VoIP Monitoring and Analysis
Video Monitoring and Analysis
Wireless Network Analysis
10 Gigabit Networks
Industry Specific Solutions
OmniFlow Collector
NetFlow Collector
sFlow Collector
OmniPeek Network Analyzer
Compass Live
OmniEngine Software Probe
OmniVirtual VMware Probe
TimeLine Network Recorder
Omnipliance Network Recorder
OmniAdapter Analysis Cards
Omnipliance Portable
Product Activation FAQs
Maintenance Programs
Product Versions
Contact Tech Support
Downloads
Training / Courses
Consulting
Custom Engineering
WildPackets Forums
MyPeek Community Portal
Information Kits
Video How-To's
Product Tips and Tricks
Networking Glossary
Networking Links
Free Utilities
Media Coverage
Media Kit
Blog
Peeks Newsletter
Success Stories
Reviews & Awards
Upcoming Events
Webinars & Webcasts
Software Upgrades
Hardware
Training
Maintenance Renewal
Per Incident Support
Sales Policies
Contact Sales






Germany
Japan
Korea
UK
United States
















