style="display:inline-block;width:728px;height:90px"
data-ad-client="ca-pub-7505528228218001"
data-ad-slot="1225241371">

Support Guidelines

No replies
Mark Bednarczyk
Offline
Joined: 03/22/2008

The jNetPcap community welcomes all of your questions and issues. No question is too small or to complex.

We do ask is that you provide all the relevant information we will need to help you solve your particular issue and follow few simple guide lines. Please provide the following information if applicable to your problem:

  1. Which version of jnetpcap are you using (jnetpcap-1.3.b0006 for example)
  2. Which operating system does the problem occur on (fedora core 10, ubuntu 9.04, etc.)
    • On linux systems please also provide output from: uname -a, lsb_release -a
    • On linux, if possible also provide version of libpcap installed
  3. Which hardware architecture, especially 32-bit or 64-bit
  4. When describing networking problems and multiple devices, protocols or applications are involved, simple graphics would be greatly appreciated and helpful. See guidelines below on graphics.

Guidelines

A few guide lines which will ensure that our forums organized and easier to search:

  1. Search the forum archives to see if your question has been answered before
  2. Do not post unrelated replies to already existing topics. Please start a new topic.
  3. Only post replies to topics if you have more questions about that particular topic or if you can contribute to the discussion.

Graphics

Graphics are always very helpful. When dealing with multiple network nodes, interfaces, protocols and applications, it is usually helpful to show setup of your network using simple graphics. This can be as simple as some ASCII characters enclosed between <pre>/</pre> html tags. You will find many people on this forum, including myself utilize a lot of ASCII graphics.

You may also attached graphic files to your post (attachment menu is accessible from the "first" topic edit tag). Any graphic format is acceptable as long as we can open it.

Attaching capture files

You may also attach small capture files with specific packets you would like to discuss. Please make sure that the capture files you are attaching have no confidential information such as password, confidential IP addresses and hostnames. Also please note that any attached capture file either in its entirety or in individual packets, may be posted and viewed publicly.

If there is confidential information, please contact the site admin before hand and make arrangements on how to transmit the file for private viewing or analysis. You may also scramble confidential information with various public capture file scramblers, which substitute or map IP ranges to private space as to masquerade the original information.

We all can save time and effort with this basic information with these few basic guidelines.

Sly Technologies, Inc.
http://slytechs.com