OmniPeek Enterprise
OmniEngine Enterprise
OmniPeek Professional
OmniPeek Basic
OmniEngine Desktop
OmniVirtual
Omnipliance
Support FAQ
Tech Tips
Supported Hardware
Omnipliance Portable
Omni Wireless Sensor

Omnipliance

Return to top of page Is the LCD utility supported on Windows 2000?

The Omnipliance and the LCD utility is designed to run on Windows Server 2003.

Return to top of page Does the Omnipliance support 10 Gig networks?

Yes, Omnipliance does support 10 Gigabit capture and analysis. Please visit http://www.wildpackets.com/products/analysis_cards/10GbE for more information.

Return to top of page Why aren’t my Statistics Output Reports being output when I set them to?

When doing Statistics Output, setting the output interval too low may cause some reports to not be output when intended. If reports are not being output at the desired time, you may wish to increase the output interval.

Return to top of page Can I change my adapter buffer size?

Adapter buffer size in the Adapters view does not apply to the OmniEngine Linux. The default buffer size for all installed adapters is set to “0”.

Return to top of page Can I make changes to the built in WildPackets Gigabit card?

Making changes to WildPackets Gigabit capture cards is not recommended unless using OmniPeek or the OmniEngine Manager.

Return to top of page Why am I receiving bad checksum messages on some outgoing packets?

This problem may be caused by the network card’s ability to offload the calculation of IP, TCP, and/or UDP checksums from the TCP/IP protocol stack. If the OmniEngine Linux is sending the packets, the checksums may appear incorrect if the hardware is calculating the checksums. A work around is to disable this feature on the network card. The following command will turn off the feature for the specified adapter in the OmniEngine Linux computer:

ethtool –K eth# tx off (where # is the adapter index)

Note: The adapter must be in a ‘down’ state for the change to take effect. The change will not persist across a reboot.

Return to top of page Why are some of my outgoing packets unusually large?

This problem may be caused by the network card’s ability to offload TCP/IP protocol stack. If the OmniEngine Linux is sending the TCP packets, some of these packets may be unusually large if the hardware is doing the segmentation. A work around is to disable this feature on the network card. The following command will turn off the feature for the specified adapter in the OmniEngine Linux computer:

ethtool –K eth# tso off (where # is the adapter index)

Note: The adapter must be in a ‘down’ state for the change to take effect. The change will not persist across a reboot.

Return to top of page Can I change the VoIP region settings?

Yes, you can edit the omni.conf file (/etc/omni) to change the VoIP region. The omni.conf file lists the possible values. Restart the OmniEngine Service for the changes to take effect.

Download a demo of OmniPeek
Custom Integration & Engineering
WildPackets understands that one size does not fit all. Moreover, we all face new challenges every day. WildPackets Custom Engineering performs software development and systems integration, complementing WildPackets products and enhancing the capabilities of Network Operations Centers.
Learn more...

Network Analysis & Consulting
WildPackets offers a full spectrum of professional services, available remote and on-site. Our network engineers provide expertise for your network troubleshooting, capacity planning, or baseline performance analysis needs.
Learn more...

Tip of the Month
Don’t Lose The Tags
WildPackets’ Technical Support Team regularly receives questions about capturing VLAN (Virtual LAN) tags in packets. Some customers report that they cannot see VLAN tags when capturing packets from their switches. The tags are usually missing because the capture configuration or the location of OmniPeek (or Omni Engine) is incorrect. So, this tip is aimed at understanding VLAN tags and how they can be captured using OmniPeek Product Family.