|
|
||
|
|
||
|
|
||
|
|
||
![]()
OmniPeek Enterprise
OmniEngine Enterprise
OmniPeek Professional
OmniPeek Basic
OmniEngine Desktop
OmniVirtual
Omnipliance Portable
Omni Wireless Sensor
|
The Omnipliance and the LCD utility is designed to run on Windows Server 2003.
Yes, Omnipliance does support 10 Gigabit capture and analysis. Please visit http://www.wildpackets.com/products/analysis_cards/10GbE for more information.
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.
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”.
Making changes to WildPackets Gigabit capture cards is not recommended unless using OmniPeek or the OmniEngine Manager.
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.
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.
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. |
|
||||||
| COPYRIGHT © 2008 WILDPACKETS, INC — PRIVACY STATEMENT · CONTACT US | CORPORATE · PRODUCTS · SOLUTIONS · SERVICES · SUPPORT · PARTNERS · BUY NOW |
|
All registered and unregistered trademarks are the sole property of their respective owners |
|
United States
UK





