Wireshark 2.1 开发者指南

需积分: 10 158 浏览量更新于2024-07-19 收藏 1.11MB PDF 举报

"Wireshark Developer's Guide 是一本针对Wireshark 2.1版本的开发者指南，由Ulf Lamping、Luis E. Ontanon和Graham Bloice撰写。这本书详细介绍了如何进行Wireshark的二次开发和编写插件，涵盖了Wireshark的构建环境、编程语言、支持平台等内容，并遵循GNU General Public License V2或更高版本的开源协议。" Wireshark是一款强大的网络封包分析软件，对于网络诊断、协议开发以及网络安全分析等任务至关重要。《Wireshark Developer's Guide For Wireshark 2.1》是开发者深入理解并定制Wireshark功能的重要参考资料。该书首先介绍了Wireshark的基础信息，包括Wireshark的作用（例如，它能捕获和分析网络流量，帮助用户理解网络协议的工作原理）以及支持的平台，如Unix、Linux和Microsoft Windows。书中强调了Wireshark在多个操作系统上的兼容性，使其成为跨平台网络分析的首选工具。在Wireshark的开发与维护部分，书中指出Wireshark使用多种编程语言，如C、C++和Lua，这使得开发者可以根据自己的专长来贡献代码。此外，作为开源软件，Wireshark遵循开放源代码的原则，鼓励社区成员参与开发和改进。接下来的内容可能涉及如何配置Wireshark的构建环境，包括安装必要的依赖库、设置编译器选项以及构建和调试过程。这对于开发者来说是至关重要的，因为他们需要能够在本地环境中构建和测试自定义的Wireshark模块和插件。书中还可能涵盖Wireshark的数据包处理模型，解释了如何解析和显示不同协议的数据包。这涉及到Wireshark的Dissector机制，通过编写dissector代码，开发者可以添加对新协议的支持或者增强现有协议的解析能力。除此之外，指南可能会涉及Wireshark的UI设计，如如何扩展图形用户界面以添加新的视图或功能。开发者也可能需要学习如何利用Wireshark的框架来编写插件，这些插件可以实现特定的分析任务，或者与外部应用程序集成。书中还可能包含错误报告和调试技巧，帮助开发者有效地解决问题并提升Wireshark的性能。最后，作者可能会提供获取最新文档和反馈文档问题的途径，以便持续改进Wireshark的开发资源。《Wireshark Developer's Guide For Wireshark 2.1》是一本详尽的开发者手册，对于想要深入Wireshark内部、开发新功能或优化现有功能的程序员来说，是不可或缺的参考资料。

Introduction

1.6.2. What does the Buildbot do?

The Buildbot will do the following (to a different degree on the different platforms):

• Check out from the source repository

• Build

• Create binary packages and installers

• Create source packages and run distribution checks

• Run regression tests

Each step is represented at the status page by a rectangle, green if it succeeded or red if it failed. Most

steps provide a link to the corresponding console logfile, to get additional information.

The Buildbot runs on a platform collection that represents the different "platform specialties" quite well:

• Windows 8.1 x86 (Win32, little endian, Visual Studio 2013)

• Windows Server 2012 R2 x86-64 (Win64, little endian, Visual Studio 2013)

• Ubuntu x86-64 (Linux, little endian, gcc, Clang)

• OS X x86-64 (BSD, little endian, Clang)

and two buildslaves that run static code analysis to help spot coding issues:

• Visual Studio Code Analysis (Win64, little endian, VS 2013)

• Clang Code Analysis (Linux, little endian, Clang)

Each platform is represented at the status page by a single column, the most recent entries are at the top.

1.7. Reporting problems and getting help

If you have problems, or need help with Wireshark, there are several places that may be of interest to you

(well, beside this guide of course).

1.7.1. Website

You will find lots of useful information on the Wireshark homepage at https://www.wireshark.org/.

1.7.2. Wiki

The Wireshark Wiki at https://wiki.wireshark.org/ provides a wide range of information related to

Wireshark and packet capturing in general. You will find a lot of information not part of this developer’s

guide. For example, there is an explanation how to capture on a switched network, an ongoing effort to

build a protocol reference and a lot more.

And best of all, if you would like to contribute your knowledge on a specific topic (maybe a network

protocol you know well), you can edit the Wiki pages by simply using your webbrowser.

1.7.3. FAQ

The "Frequently Asked Questions" will list often asked questions and the corresponding answers.

Introduction

Before sending any mail to the mailing lists below, be sure to read the FAQ, as it will often answer any

questions you might have. This will save yourself and others a lot of time. Keep in mind that a lot of people

are subscribed to the mailing lists.

You will find the FAQ inside Wireshark by clicking the menu item Help/Contents and selecting the FAQ

page in the upcoming dialog.

An online version is available at the Wireshark website: https://www.wireshark.org/faq.html. You might

prefer this online version as it’s typically more up to date and the HTML format is easier to use.

1.7.4. Other sources

If you don’t find the information you need inside this book, there are various other sources of information:

• The file doc/README.developer and all the other README.xxx files in the source code. These are

various documentation files on different topics

Read the README

README.developer is packed full with all kinds of details relevant to the developer of

Wireshark source code. Its companion file README.dissector advises you around common

pitfalls, shows you basic layout of dissector code, shows details of the APIs available to the

dissector developer, etc.

• The Wireshark source code

• Tool documentation of the various tools used (e.g. manpages of sed, gcc, etc.)

• The different mailing lists. See Section 1.7.5, “Mailing Lists”

1.7.5. Mailing Lists

There are several mailing lists available on specific Wireshark topics:

wireshark-announce

This mailing list will inform you about new program releases, which usually appear about every 4-8

weeks.

wireshark-users

This list is for users of Wireshark. People post questions about building and using Wireshark, others

(hopefully) provide answers.

wireshark-dev

This list is for Wireshark developers. People post questions about the development of Wireshark,

others (hopefully) provide answers. If you want to start developing a protocol dissector, join this list.

wireshark-bugs

This list is for Wireshark developers. Every time a change to the bug database occurs, a mail to this

mailing list is generated. If you want to be notified about all the changes to the bug database, join this

list. Details about the bug database can be found in Section 1.7.6, “Bug database (Bugzilla)”.

wireshark-commits

This list is for Wireshark developers. Every time a change to the GIT repository is checked in, a mail to

this mailing list is generated. If you want to be notified about all the changes to the GIT repository, join

this list. Details about the GIT repository can be found in Section 3.2, “The Wireshark Git repository”.

Introduction

You can subscribe to each of these lists from the Wireshark web site: https://www.wireshark.org/lists/.

From there, you can choose which mailing list you want to subscribe to by clicking on the Subscribe/

Unsubscribe/Options button under the title of the relevant list. The links to the archives are included on

that page as well.

The archives are searchable

You can search in the list archives to see if someone previously asked the same question

and maybe already got an answer. That way you don’t have to wait until someone answers

your question.

1.7.6. Bug database (Bugzilla)

The Wireshark community collects bug reports in a Bugzilla database at https://bugs.wireshark.org/. This

database is filled with manually filed bug reports, usually after some discussion on wireshark-dev, and

automatic bug reports from the Buildbot tools.

1.7.7. Q&A Site

The Wireshark Q and A site at https://ask.wireshark.org/ offers a resource where questions and answers

come together. You have the option to search what questions were asked before and what answers were

given by people who knew about the issue. Answers are graded, so you can pick out the best ones easily.

If your issue isn’t discussed before you can post one yourself.

1.7.8. Reporting Problems

Test with the latest version

Before reporting any problems, please make sure you have installed the latest version of

Wireshark. Reports on older maintenance releases are usually met with an upgrade request.

If you report problems, provide as much information as possible. In general, just think about what you

would need to find that problem, if someone else sends you such a problem report. Also keep in mind that

people compile/run Wireshark on a lot of different platforms.

When reporting problems with Wireshark, it is helpful if you supply the following information:

1. The version number of Wireshark and the dependent libraries linked with it, e.g. Qt, GTK+, etc. You

can obtain this with the command wireshark -v.

2. Information about the platform you run Wireshark on.

3. A detailed description of your problem.

4. If you get an error/warning message, copy the text of that message (and also a few lines before and

after it, if there are some), so others may find the build step where things go wrong. Please don’t give

something like: "I get a warning when compiling x" as this won’t give any direction to look at.

Don’t send large files

Do not send large files (>100KB) to the mailing lists, just place a note that further data

is available on request. Large files will only annoy a lot of people on the list who are not

interested in your specific problem. If required, you will be asked for further data by the

persons who really can help you.

Chapter 2. Quick Setup

2.1. UNIX: Installation

All the tools required are usually installed on a UNIX developer machine.

If a tool is not already installed on your system, you can usually install it using the package in your

distribution: aptitude, yum, Synaptic, etc.

If an install package is not available or you have a reason not to use it (maybe because it’s simply too

old), you can install that tool from source code. The following sections will provide you with the webpage

addresses where you can get these sources.

2.2. Win32/64: Step-by-Step Guide

A quick setup guide for Win32 and Win64 with recommended configuration.

Warning

Unless you know exactly what you are doing, you should strictly follow the recommendations

below. They are known to work and if the build breaks, please re-read this guide carefully.

Known traps are:

1. Not using the correct (x86 or x64) version of the Visual Studio command prompt.

2. Not copying/downloading the correct version of vcredist_xYY.exe.

2.2.1. Install PowerShell

PowerShell 2.0 or later is required for building Wireshark and the NSIS package. Windows 7 and later

include compatible versions. It is also required by Chocolatey.

If you are running Windows Vista and have thus far managed to not install PowerShell 2.0, either directly

or via anything that requires it, you must now install PowerShell 2.0. You can download it from https://

www.microsoft.com/powershell

2.2.2. Optional: Install Chocolatey

Chocolatey is a native package manager for Windows. There are packages for most of the software listed

below. Along with traditional Windows packages it supports Cygwin and the Python Package Index.

2.2.3. Install Microsoft C compiler and SDK

You need to install, in exactly this order:

1. C compiler: Download and install "Microsoft Visual Studio 2013 Community Edition." This is a small

download that then downloads all the other required parts (which are quite large).

Uncheck all the optional components (unless you want to use them for purposes other than Wireshark).

剩余213页未读，继续阅读

feng1gb

粉丝: 0
资源: 2

Wireshark 2.1 开发者指南

Wireshark Developer's Guide

Wireshark Developer’s Guide For Wireshark 2.1

WireShark 开发者指南（developer-guide）

Wireshark Developer’s Guide 2.9

Wireshark Developer's Guide.pdf

Wireshark Developer’s Guide.pdf

WireShark developer guide

wireshark-developer-guide.rar

wireshark-developer-guide.pdf

Wireshark-developer-guide.chm

最新资源