> > > > Support FAQ

Support FAQ

GigaPeek NX

Hardware

Does GigaPeek NX support any Ethernet adapters?

Absolutely! All Ethernet NICs that are supported by EtherPeek are also supported by GigaPeek NX. We recommend a GigaPeek NX portable solution that comes with a Intel Ethernet NIC on the motherboard. This configuration has been fully tested with GigaPeek NX.

See Supported Ethernet Interfaces for EtherPeek.

Does GigaPeek NX support gigabit over copper?

Yes, please contact sales@wildpackets.com for a quote.

OS Related

Do you support Windows Server 2003 for GigaPeek NX?

Yes. Complete support for GigaPeek NX is available for Windows Server 2003. To download the driver for Windows Server 2003 please go to http://www.wildpackets.com/support/downloads/.

Note: This driver will not be available on the GigaPeek NX CD

Filtering

I know you can use a wildcard to specify a class C space when setting up an address IP filter, such as 192.216.124.*. Is there any way to easily specify my space when my subnet mask is 255.255.255.192?

Yes, you can use CIDR notation to specify a subnet. In GigaPeek, that class C space can be identified as 192.216.124.* or 192.216.124.0/24. Customers who have applied subnetting to their IP address space can now use the CIDR notation in the IP address filter. For your address space based on a subnet mask of 255.255.255.192, which provides for 64 host addresses, you can specify the particular subnet in the filter as, for example, 192.216.124.128/26. This will filter all IP addresses in the range 192.216.124.128 to 192.216.124.191. Note that this range includes the subnet ID (192.216.124.128) and the subnet broadcast address (192.216.124.191) as well as the 62 valid host addresses (192.216.124.129 to 192.216.124.190).

Troubleshooting

NetSense, ProConvert and my third-party applications can't read the trace file that I saved with GigaPeek NX 1.0. Is this a bug?

GigaPeek NX 1.0 use a new packet file format when they save out a .pkt trace file. If you have applications that cannot read this new format, open the file in GigaPeek NX 1.0 and choose Save All Packets..., change the 'Save as type' field on the 'Save As' dialogue to 'EtherPeek Classic Packet File (.pkt)'. Doing this will save out a packet file in the older format, which should be readable in NetSense, ProConvert, and third-party applications.

When I use GigaPeek NX to monitor my high speed network, the application tends to slow down. Are there any tips to optimize performance?

Capturing data at Gigabit speeds can put heavy traffic loads on the hardware.

Here are a few optimization tips to improve the performance of GigaPeek NX:

set hardware filters on all channels
Use packet slicing on all channels
Use RAID 0 on 10k RPM or faster hard drives
In the Capture Options, select Performance. For peak performance, right click on one of the features and choose Disable All. As you enable/disable features, the performance bar at the bottom of the Performance Options dialog will move to show you an estimate of the impact of each action.

If you need one of the features, you can enable it while capturing or when you are actually viewing the capture file. This way, GigaPeek NX will function at peak performance while you are capturing traffic and the features are available when you need them.

All registered and unregistered trademarks are the sole property of their respective owners