diff options
| author | Gerald Combs <gerald@wireshark.org> | 2006-05-30 20:49:45 +0000 |
|---|---|---|
| committer | Gerald Combs <gerald@wireshark.org> | 2006-05-30 20:49:45 +0000 |
| commit | 42300496282018856bd4901496ba4fc27e42b7db (patch) | |
| tree | e5af402de2593906a89b2405a9de868c1d7c8dfc | |
| parent | cfda4eb127247f00333a1d588e9a0a41ac3a4db2 (diff) | |
Ethereal -> Wireshark in the User's Guide. Switch over to the new logo.
We'll probably want to use a vectorized version of the logo (e.g. EPS or
SVG) at some point.
svn path=/trunk/; revision=18257
25 files changed, 666 insertions, 666 deletions
diff --git a/docbook/Makefile b/docbook/Makefile index c55a598c16..b45e4527e2 100644 --- a/docbook/Makefile +++ b/docbook/Makefile @@ -105,9 +105,7 @@ WSUG_GRAPHICS = \ graphics/ethereal-gui-preferences.png \ graphics/ethereal-help-menu.png \ graphics/ethereal-list-pane.png \ - graphics/ethereal-logo.png \ graphics/ethereal-main-toolbar.png \ - graphics/ethereal-main.png \ graphics/ethereal-menu.png \ graphics/ethereal-merge.png \ graphics/ethereal-nameresolution-preferences.png \ @@ -166,7 +164,9 @@ WSUG_GRAPHICS = \ graphics/toolbar/stock_top_24.png \ graphics/toolbar/stock_zoom_1_24.png \ graphics/toolbar/stock_zoom_in_24.png \ - graphics/toolbar/stock_zoom_out_24.png + graphics/toolbar/stock_zoom_out_24.png \ + graphics/wireshark-logo.png \ + graphics/wireshark-main.png EDG_FILES = \ edg_src/EDG_chapter_build_intro.xml \ @@ -188,7 +188,7 @@ EDG_GRAPHICS = \ edg_graphics/ethereal-capture_internals.png \ edg_graphics/ethereal-function-blocks.dia \ edg_graphics/ethereal-function-blocks.png \ - edg_graphics/ethereal-logo.png \ + edg_graphics/wireshark-logo.png \ edg_graphics/note.png \ edg_graphics/tip.png \ edg_graphics/warning.png diff --git a/docbook/developer-guide.xml b/docbook/developer-guide.xml index 54c5f087ba..18c310722f 100644 --- a/docbook/developer-guide.xml +++ b/docbook/developer-guide.xml @@ -68,7 +68,7 @@ FILE SECTION <!-- These refer to graphics files and figures contained in the document --> - <!ENTITY EtherealLogo SYSTEM "./edg_graphics/ethereal-logo.png" NDATA PNG> + <!ENTITY EtherealLogo SYSTEM "./edg_graphics/wireshark-logo.png" NDATA PNG> <!ENTITY EtherealFunctionBlocks SYSTEM "./edg_graphics/ethereal-function-blocks.png" NDATA PNG> <!-- These are the actual files that make up the document --> diff --git a/docbook/edg_graphics/ethereal-logo.png b/docbook/edg_graphics/ethereal-logo.png Binary files differdeleted file mode 100644 index 6f600f708e..0000000000 --- a/docbook/edg_graphics/ethereal-logo.png +++ /dev/null diff --git a/docbook/edg_graphics/wireshark-logo.png b/docbook/edg_graphics/wireshark-logo.png Binary files differnew file mode 100644 index 0000000000..53c0220388 --- /dev/null +++ b/docbook/edg_graphics/wireshark-logo.png diff --git a/docbook/graphics/ethereal-logo.png b/docbook/graphics/ethereal-logo.png Binary files differdeleted file mode 100644 index 6f600f708e..0000000000 --- a/docbook/graphics/ethereal-logo.png +++ /dev/null diff --git a/docbook/graphics/wireshark-logo.png b/docbook/graphics/wireshark-logo.png Binary files differnew file mode 100644 index 0000000000..53c0220388 --- /dev/null +++ b/docbook/graphics/wireshark-logo.png diff --git a/docbook/graphics/ethereal-main.png b/docbook/graphics/wireshark-main.png Binary files differindex 394c1e843a..394c1e843a 100644 --- a/docbook/graphics/ethereal-main.png +++ b/docbook/graphics/wireshark-main.png diff --git a/docbook/user-guide.xml b/docbook/user-guide.xml index e2eb21736d..9fdbb77a4a 100644 --- a/docbook/user-guide.xml +++ b/docbook/user-guide.xml @@ -53,8 +53,8 @@ DOCUMENT SECTION -Use this section to encode all document information --> - <!ENTITY DocumentTitle "<application>Ethereal</application> User's Guide"> - <!ENTITY DocumentSubTitle "&SvnVersion; for Wireshark &EtherealCurrentVersion;"> + <!ENTITY DocumentTitle "<application>Wireshark</application> User's Guide"> + <!ENTITY DocumentSubTitle "&SvnVersion; for Wireshark &WiresharkCurrentVersion;"> <!ENTITY DocumentTitleAbbreviation "WSUG"> <!ENTITY DocumentCopyrightHolder1 "Ulf Lamping "> @@ -71,27 +71,27 @@ DOCUMENT SECTION <!ENTITY DocumentLegalNotice "<para>Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 or any later version published by the Free Software Foundation.</para><para>All logos and trademarks in this document are property of their respective owner.</para>"> <!-- -Ethereal Info +Wireshark Info --> - <!ENTITY EtherealCurrentVersion "0.10.14"> - <!ENTITY EtherealWebSite "http://www.ethereal.com"> - <!ENTITY EtherealUsersGuidePage "&EtherealWebSite;/docs/#usersguide"> - <!ENTITY EtherealDownloadPage "&EtherealWebSite;/download.html"> - <!ENTITY EtherealBinariesPage "&EtherealWebSite;/download.html#releases"> - <!ENTITY EtherealAuthorsPage "&EtherealWebSite;/introduction.html#authors"> - <!ENTITY EtherealProtocolsPage "&EtherealWebSite;/docs/dfref/"> - <!ENTITY EtherealFAQPage "&EtherealWebSite;/faq.html"> - <!ENTITY EtherealFAQPromiscPage "&EtherealWebSite;/faq#promiscsniff"> - <!ENTITY EtherealMediaPage "&EtherealWebSite;/media.html"> - <!ENTITY EtherealWikiPage "http://wiki.ethereal.com"> - <!ENTITY EtherealWikiCaptureFiltersPage "&EtherealWikiPage;/CaptureFilters"> - <!ENTITY EtherealWikiDisplayFiltersPage "&EtherealWikiPage;/DisplayFilters"> - <!ENTITY EtherealWikiPreferencesPage "&EtherealWikiPage;/Preferences"> - <!ENTITY EtherealWikiColoringRulesPage "&EtherealWikiPage;/ColoringRules"> - <!ENTITY EtherealWikiPreferencesPage "&EtherealWikiPage;/Preferences"> - - <!ENTITY EtherealDevMailList "ethereal-dev[AT]ethereal.com"> - <!ENTITY EtherealUsersMailList "ethereal-users[AT]ethereal.com"> + <!ENTITY WiresharkCurrentVersion "0.10.14"> + <!ENTITY WiresharkWebSite "http://www.wireshark.org"> + <!ENTITY WiresharkUsersGuidePage "&WiresharkWebSite;/docs/#usersguide"> + <!ENTITY WiresharkDownloadPage "&WiresharkWebSite;/download.html"> + <!ENTITY WiresharkBinariesPage "&WiresharkWebSite;/download.html#releases"> + <!ENTITY WiresharkAuthorsPage "&WiresharkWebSite;/introduction.html#authors"> + <!ENTITY WiresharkProtocolsPage "&WiresharkWebSite;/docs/dfref/"> + <!ENTITY WiresharkFAQPage "&WiresharkWebSite;/faq.html"> + <!ENTITY WiresharkFAQPromiscPage "&WiresharkWebSite;/faq#promiscsniff"> + <!ENTITY WiresharkMediaPage "&WiresharkWebSite;/media.html"> + <!ENTITY WiresharkWikiPage "http://wiki.wireshark.org"> + <!ENTITY WiresharkWikiCaptureFiltersPage "&WiresharkWikiPage;/CaptureFilters"> + <!ENTITY WiresharkWikiDisplayFiltersPage "&WiresharkWikiPage;/DisplayFilters"> + <!ENTITY WiresharkWikiPreferencesPage "&WiresharkWikiPage;/Preferences"> + <!ENTITY WiresharkWikiColoringRulesPage "&WiresharkWikiPage;/ColoringRules"> + <!ENTITY WiresharkWikiPreferencesPage "&WiresharkWikiPage;/Preferences"> + + <!ENTITY WiresharkDevMailList "wireshark-dev[AT]wireshark.org"> + <!ENTITY WiresharkUsersMailList "wireshark-users[AT]wireshark.org"> <!-- @@ -126,127 +126,127 @@ FILE SECTION --> <!-- These refer to graphics files and figures contained in the document --> <!-- --> - <!ENTITY EtherealLogo SYSTEM "./graphics/ethereal-logo.png" NDATA PNG> + <!ENTITY WiresharkLogo SYSTEM "./graphics/wireshark-logo.png" NDATA PNG> <!-- 1st Chapter --> - <!ENTITY EtherealMain1 SYSTEM "./graphics/ethereal-main.png" NDATA PNG> + <!ENTITY WiresharkMain1 SYSTEM "./graphics/wireshark-main.png" NDATA PNG> <!-- 2nd Chapter --> <!-- Third Chapter --> - <!ENTITY EtherealEmpty SYSTEM "./graphics/ethereal-empty.png" NDATA PNG> - <!ENTITY EtherealThreePane1 SYSTEM "./graphics/ethereal-main.png" NDATA PNG> - <!ENTITY EtherealMenuOnly SYSTEM "./graphics/ethereal-menu.png" NDATA PNG> - <!ENTITY EtherealMainToolbar SYSTEM "./graphics/ethereal-main-toolbar.png" NDATA PNG> - <!ENTITY EtherealFilterToolbar SYSTEM "./graphics/ethereal-filter-toolbar.png" NDATA PNG> - <!ENTITY EtherealListPane SYSTEM "./graphics/ethereal-list-pane.png" NDATA PNG> - <!ENTITY EtherealDetailsPane SYSTEM "./graphics/ethereal-details-pane.png" NDATA PNG> - <!ENTITY EtherealBytesPane SYSTEM "./graphics/ethereal-bytes-pane.png" NDATA PNG> - <!ENTITY EtherealBytesPaneTabs SYSTEM "./graphics/ethereal-bytes-pane-tabs.png" NDATA PNG> - <!ENTITY EtherealStatusbarEmpty SYSTEM "./graphics/ethereal-statusbar-empty.png" NDATA PNG> - <!ENTITY EtherealStatusbarLoaded SYSTEM "./graphics/ethereal-statusbar-loaded.png" NDATA PNG> - <!ENTITY EtherealStatusbarSelected SYSTEM "./graphics/ethereal-statusbar-selected.png" NDATA PNG> - <!ENTITY EtherealSaveAs SYSTEM "./graphics/ethereal-save-as.png" NDATA PNG> - <!ENTITY EtherealOpen SYSTEM "./graphics/ethereal-open.png" NDATA PNG> - <!ENTITY EtherealPacketSelected1 SYSTEM "./graphics/ethereal-packet-selected.png" NDATA PNG> - <!ENTITY EtherealPacketSepView SYSTEM "./graphics/ethereal-packet-sep-win.png" NDATA PNG> - <!ENTITY EtherealFilterTCP SYSTEM "./graphics/ethereal-display-filter-tcp.png" NDATA PNG> - <!ENTITY EtherealColoringRulesDialog SYSTEM "./graphics/ethereal-coloring-rules-dialog.png" NDATA PNG> - <!ENTITY EtherealEditColorDialog SYSTEM "./graphics/ethereal-edit-color-rule-dialog.png" NDATA PNG> - <!ENTITY EtherealChooseColorDialog SYSTEM "./graphics/ethereal-choose-color-rule.png" NDATA PNG> - <!ENTITY EtherealFollowStream SYSTEM "./graphics/ethereal-follow-stream.png" NDATA PNG> - <!ENTITY EtherealFindPacket SYSTEM "./graphics/ethereal-find-packet.png" NDATA PNG> - <!ENTITY EtherealGoToPacket SYSTEM "./graphics/ethereal-goto-packet.png" NDATA PNG> - <!ENTITY EtherealPrint SYSTEM "./graphics/ethereal-print.png" NDATA PNG> - <!ENTITY EtherealGUIPreferences SYSTEM "./graphics/ethereal-gui-preferences.png" NDATA PNG> - <!ENTITY EtherealGUILayoutPreferences SYSTEM "./graphics/ethereal-gui-layout-preferences.png" NDATA PNG> - <!ENTITY EtherealGUIColumnsPreferences SYSTEM "./graphics/ethereal-gui-columns-preferences.png" NDATA PNG> - <!ENTITY EtherealGUIFontPreferences SYSTEM "./graphics/ethereal-gui-font-preferences.png" NDATA PNG> - <!ENTITY EtherealGUIColorsPreferences SYSTEM "./graphics/ethereal-gui-colors-preferences.png" NDATA PNG> - <!ENTITY EtherealCapturePreferences SYSTEM "./graphics/ethereal-capture-preferences.png" NDATA PNG> - <!ENTITY EtherealPrintingPreferences SYSTEM "./graphics/ethereal-printing-preferences.png" NDATA PNG> - <!ENTITY EtherealNameResolutionPreferences SYSTEM "./graphics/ethereal-nameresolution-preferences.png" NDATA PNG> - <!ENTITY EtherealFilters SYSTEM "./graphics/ethereal-filters.png" NDATA PNG> - <!ENTITY EtherealFileMenu SYSTEM "./graphics/ethereal-file-menu.png" NDATA PNG> - <!ENTITY EtherealEditMenu SYSTEM "./graphics/ethereal-edit-menu.png" NDATA PNG> - <!ENTITY EtherealViewMenu SYSTEM "./graphics/ethereal-view-menu.png" NDATA PNG> - <!ENTITY EtherealGoMenu SYSTEM "./graphics/ethereal-go-menu.png" NDATA PNG> - <!ENTITY EtherealCaptureMenu SYSTEM "./graphics/ethereal-capture-menu.png" NDATA PNG> - <!ENTITY EtherealAnalyzeMenu SYSTEM "./graphics/ethereal-analyze-menu.png" NDATA PNG> - <!ENTITY EtherealStatisticsMenu SYSTEM "./graphics/ethereal-statistics-menu.png" NDATA PNG> - <!ENTITY EtherealHelpMenu SYSTEM "./graphics/ethereal-help-menu.png" NDATA PNG> - <!ENTITY EtherealPacketPanePopupMenu SYSTEM "./graphics/ethereal-packet-pane-popup-menu.png" NDATA PNG> - <!ENTITY EtherealDetailsPanePopupMenu SYSTEM "./graphics/ethereal-details-pane-popup-menu.png" NDATA PNG> - <!ENTITY EtherealBytesPanePopupMenu SYSTEM "./graphics/ethereal-bytes-pane-popup-menu.png" NDATA PNG> - <!ENTITY EtherealFilterAddExpression SYSTEM "./graphics/ethereal-filter-add-expression.png" NDATA PNG> - <!ENTITY EtherealFilters2 SYSTEM "./graphics/ethereal-filters-2.png" NDATA PNG> - <!ENTITY EtherealExportPlainDialog SYSTEM "./graphics/ethereal-export-plain.png" NDATA PNG> - <!ENTITY EtherealExportPSDialog SYSTEM "./graphics/ethereal-export-ps.png" NDATA PNG> - <!ENTITY EtherealExportPSMLDialog SYSTEM "./graphics/ethereal-export-psml.png" NDATA PNG> - <!ENTITY EtherealExportPDMLDialog SYSTEM "./graphics/ethereal-export-pdml.png" NDATA PNG> - <!ENTITY EtherealExportSelectedDialog SYSTEM "./graphics/ethereal-export-selected.png" NDATA PNG> - <!ENTITY EtherealCaptureInterfacesDialog SYSTEM "./graphics/ethereal-capture-interfaces.png" NDATA PNG> - <!ENTITY EtherealCaptureOptionsDialog SYSTEM "./graphics/ethereal-capture-options.png" NDATA PNG> - <!ENTITY EtherealCaptureInfoDialog SYSTEM "./graphics/ethereal-capture-info.png" NDATA PNG> - <!ENTITY EtherealMergeDialog SYSTEM "./graphics/ethereal-merge.png" NDATA PNG> - <!ENTITY EtherealPacketRangeFrame SYSTEM "./graphics/ethereal-packet-range.png" NDATA PNG> - <!ENTITY EtherealPacketFormatFrame SYSTEM "./graphics/ethereal-packet-format.png" NDATA PNG> - <!ENTITY EtherealTimeReference SYSTEM "./graphics/ethereal-time-reference.png" NDATA PNG> - <!ENTITY EtherealEnabledProtocols SYSTEM "./graphics/ethereal-enabled-protocols.png" NDATA PNG> - <!ENTITY EtherealDecodeAs SYSTEM "./graphics/ethereal-decode-as.png" NDATA PNG> - <!ENTITY EtherealDecodeAsShow SYSTEM "./graphics/ethereal-decode-as-show.png" NDATA PNG> - <!ENTITY EtherealFileSetDialog SYSTEM "./graphics/ethereal-file-set-dialog.png" NDATA PNG> + <!ENTITY WiresharkEmpty SYSTEM "./graphics/ethereal-empty.png" NDATA PNG> + <!ENTITY WiresharkThreePane1 SYSTEM "./graphics/wireshark-main.png" NDATA PNG> + <!ENTITY WiresharkMenuOnly SYSTEM "./graphics/ethereal-menu.png" NDATA PNG> + <!ENTITY WiresharkMainToolbar SYSTEM "./graphics/ethereal-main-toolbar.png" NDATA PNG> + <!ENTITY WiresharkFilterToolbar SYSTEM "./graphics/ethereal-filter-toolbar.png" NDATA PNG> + <!ENTITY WiresharkListPane SYSTEM "./graphics/ethereal-list-pane.png" NDATA PNG> + <!ENTITY WiresharkDetailsPane SYSTEM "./graphics/ethereal-details-pane.png" NDATA PNG> + <!ENTITY WiresharkBytesPane SYSTEM "./graphics/ethereal-bytes-pane.png" NDATA PNG> + <!ENTITY WiresharkBytesPaneTabs SYSTEM "./graphics/ethereal-bytes-pane-tabs.png" NDATA PNG> + <!ENTITY WiresharkStatusbarEmpty SYSTEM "./graphics/ethereal-statusbar-empty.png" NDATA PNG> + <!ENTITY WiresharkStatusbarLoaded SYSTEM "./graphics/ethereal-statusbar-loaded.png" NDATA PNG> + <!ENTITY WiresharkStatusbarSelected SYSTEM "./graphics/ethereal-statusbar-selected.png" NDATA PNG> + <!ENTITY WiresharkSaveAs SYSTEM "./graphics/ethereal-save-as.png" NDATA PNG> + <!ENTITY WiresharkOpen SYSTEM "./graphics/ethereal-open.png" NDATA PNG> + <!ENTITY WiresharkPacketSelected1 SYSTEM "./graphics/ethereal-packet-selected.png" NDATA PNG> + <!ENTITY WiresharkPacketSepView SYSTEM "./graphics/ethereal-packet-sep-win.png" NDATA PNG> + <!ENTITY WiresharkFilterTCP SYSTEM "./graphics/ethereal-display-filter-tcp.png" NDATA PNG> + <!ENTITY WiresharkColoringRulesDialog SYSTEM "./graphics/ethereal-coloring-rules-dialog.png" NDATA PNG> + <!ENTITY WiresharkEditColorDialog SYSTEM "./graphics/ethereal-edit-color-rule-dialog.png" NDATA PNG> + <!ENTITY WiresharkChooseColorDialog SYSTEM "./graphics/ethereal-choose-color-rule.png" NDATA PNG> + <!ENTITY WiresharkFollowStream SYSTEM "./graphics/ethereal-follow-stream.png" NDATA PNG> + <!ENTITY WiresharkFindPacket SYSTEM "./graphics/ethereal-find-packet.png" NDATA PNG> + <!ENTITY WiresharkGoToPacket SYSTEM "./graphics/ethereal-goto-packet.png" NDATA PNG> + <!ENTITY WiresharkPrint SYSTEM "./graphics/ethereal-print.png" NDATA PNG> + <!ENTITY WiresharkGUIPreferences SYSTEM "./graphics/ethereal-gui-preferences.png" NDATA PNG> + <!ENTITY WiresharkGUILayoutPreferences SYSTEM "./graphics/ethereal-gui-layout-preferences.png" NDATA PNG> + <!ENTITY WiresharkGUIColumnsPreferences SYSTEM "./graphics/ethereal-gui-columns-preferences.png" NDATA PNG> + <!ENTITY WiresharkGUIFontPreferences SYSTEM "./graphics/ethereal-gui-font-preferences.png" NDATA PNG> + <!ENTITY WiresharkGUIColorsPreferences SYSTEM "./graphics/ethereal-gui-colors-preferences.png" NDATA PNG> + <!ENTITY WiresharkCapturePreferences SYSTEM "./graphics/ethereal-capture-preferences.png" NDATA PNG> + <!ENTITY WiresharkPrintingPreferences SYSTEM "./graphics/ethereal-printing-preferences.png" NDATA PNG> + <!ENTITY WiresharkNameResolutionPreferences SYSTEM "./graphics/ethereal-nameresolution-preferences.png" NDATA PNG> + <!ENTITY WiresharkFilters SYSTEM "./graphics/ethereal-filters.png" NDATA PNG> + <!ENTITY WiresharkFileMenu SYSTEM "./graphics/ethereal-file-menu.png" NDATA PNG> + <!ENTITY WiresharkEditMenu SYSTEM "./graphics/ethereal-edit-menu.png" NDATA PNG> + <!ENTITY WiresharkViewMenu SYSTEM "./graphics/ethereal-view-menu.png" NDATA PNG> + <!ENTITY WiresharkGoMenu SYSTEM "./graphics/ethereal-go-menu.png" NDATA PNG> + <!ENTITY WiresharkCaptureMenu SYSTEM "./graphics/ethereal-capture-menu.png" NDATA PNG> + <!ENTITY WiresharkAnalyzeMenu SYSTEM "./graphics/ethereal-analyze-menu.png" NDATA PNG> + <!ENTITY WiresharkStatisticsMenu SYSTEM "./graphics/ethereal-statistics-menu.png" NDATA PNG> + <!ENTITY WiresharkHelpMenu SYSTEM "./graphics/ethereal-help-menu.png" NDATA PNG> + <!ENTITY WiresharkPacketPanePopupMenu SYSTEM "./graphics/ethereal-packet-pane-popup-menu.png" NDATA PNG> + <!ENTITY WiresharkDetailsPanePopupMenu SYSTEM "./graphics/ethereal-details-pane-popup-menu.png" NDATA PNG> + <!ENTITY WiresharkBytesPanePopupMenu SYSTEM "./graphics/ethereal-bytes-pane-popup-menu.png" NDATA PNG> + <!ENTITY WiresharkFilterAddExpression SYSTEM "./graphics/ethereal-filter-add-expression.png" NDATA PNG> + <!ENTITY WiresharkFilters2 SYSTEM "./graphics/ethereal-filters-2.png" NDATA PNG> + <!ENTITY WiresharkExportPlainDialog SYSTEM "./graphics/ethereal-export-plain.png" NDATA PNG> + <!ENTITY WiresharkExportPSDialog SYSTEM "./graphics/ethereal-export-ps.png" NDATA PNG> + <!ENTITY WiresharkExportPSMLDialog SYSTEM "./graphics/ethereal-export-psml.png" NDATA PNG> + <!ENTITY WiresharkExportPDMLDialog SYSTEM "./graphics/ethereal-export-pdml.png" NDATA PNG> + <!ENTITY WiresharkExportSelectedDialog SYSTEM "./graphics/ethereal-export-selected.png" NDATA PNG> + <!ENTITY WiresharkCaptureInterfacesDialog SYSTEM "./graphics/ethereal-capture-interfaces.png" NDATA PNG> + <!ENTITY WiresharkCaptureOptionsDialog SYSTEM "./graphics/ethereal-capture-options.png" NDATA PNG> + <!ENTITY WiresharkCaptureInfoDialog SYSTEM "./graphics/ethereal-capture-info.png" NDATA PNG> + <!ENTITY WiresharkMergeDialog SYSTEM "./graphics/ethereal-merge.png" NDATA PNG> + <!ENTITY WiresharkPacketRangeFrame SYSTEM "./graphics/ethereal-packet-range.png" NDATA PNG> + <!ENTITY WiresharkPacketFormatFrame SYSTEM "./graphics/ethereal-packet-format.png" NDATA PNG> + <!ENTITY WiresharkTimeReference SYSTEM "./graphics/ethereal-time-reference.png" NDATA PNG> + <!ENTITY WiresharkEnabledProtocols SYSTEM "./graphics/ethereal-enabled-protocols.png" NDATA PNG> + <!ENTITY WiresharkDecodeAs SYSTEM "./graphics/ethereal-decode-as.png" NDATA PNG> + <!ENTITY WiresharkDecodeAsShow SYSTEM "./graphics/ethereal-decode-as-show.png" NDATA PNG> + <!ENTITY WiresharkFileSetDialog SYSTEM "./graphics/ethereal-file-set-dialog.png" NDATA PNG> <!-- Third Chapter Toolbar--> - <!ENTITY EtherealToolbarCaptureInterfaces SYSTEM "./graphics/toolbar/capture_interfaces_24.png" NDATA PNG> - <!ENTITY EtherealToolbarCaptureOptions SYSTEM "./graphics/toolbar/capture_options_24.png" NDATA PNG> - <!ENTITY EtherealToolbarCaptureStart SYSTEM "./graphics/toolbar/capture_start_24.png" NDATA PNG> - <!ENTITY EtherealToolbarCaptureStop SYSTEM "./graphics/toolbar/capture_stop_24.png" NDATA PNG> - <!ENTITY EtherealToolbarCaptureRestart SYSTEM "./graphics/toolbar/capture_restart_24.png" NDATA PNG> - <!ENTITY EtherealToolbarCaptureFilters SYSTEM "./graphics/toolbar/capture_filter_24.png" NDATA PNG> - <!ENTITY EtherealToolbarDisplayFilters SYSTEM "./graphics/toolbar/display_filter_24.png" NDATA PNG> - <!ENTITY EtherealToolbarAdd SYSTEM "./graphics/toolbar/stock_add_24.png" NDATA PNG> - <!ENTITY EtherealToolbarGoLast SYSTEM "./graphics/toolbar/stock_bottom_24.png" NDATA PNG> - <!ENTITY EtherealToolbarClose SYSTEM "./graphics/toolbar/stock_close_24.png" NDATA PNG> - <!ENTITY EtherealToolbarColoringRules SYSTEM "./graphics/toolbar/stock_colorselector_24.png" NDATA PNG> - <!ENTITY EtherealToolbarHelp SYSTEM "./graphics/toolbar/stock_help_24.png" NDATA PNG> - <!ENTITY EtherealToolbarGoTo SYSTEM "./graphics/toolbar/stock_jump_to_24.png" NDATA PNG> - <!ENTITY EtherealToolbarGoBack SYSTEM "./graphics/toolbar/stock_left_arrow_24.png" NDATA PNG> - <!ENTITY EtherealToolbarOpen SYSTEM "./graphics/toolbar/stock_open_24.png" NDATA PNG> - <!ENTITY EtherealToolbarPreferences SYSTEM "./graphics/toolbar/stock_preferences_24.png" NDATA PNG> - <!ENTITY EtherealToolbarPrint SYSTEM "./graphics/toolbar/stock_print_24.png" NDATA PNG> - <!ENTITY EtherealToolbarProperties SYSTEM "./graphics/toolbar/stock_properties_24.png" NDATA PNG> - <!ENTITY EtherealToolbarReload SYSTEM "./graphics/toolbar/stock_refresh_24.png" NDATA PNG> - <!ENTITY EtherealToolbarGoForward SYSTEM "./graphics/toolbar/stock_right_arrow_24.png" NDATA PNG> - <!ENTITY EtherealToolbarSave SYSTEM "./graphics/toolbar/stock_save_24.png" NDATA PNG> - <!ENTITY EtherealToolbarSaveAs SYSTEM "./graphics/toolbar/stock_save_as_24.png" NDATA PNG> - <!ENTITY EtherealToolbarFind SYSTEM "./graphics/toolbar/stock_search_24.png" NDATA PNG> - <!ENTITY EtherealToolbarStop SYSTEM "./graphics/toolbar/stock_stop_24.png" NDATA PNG> - <!ENTITY EtherealToolbarGoFirst SYSTEM "./graphics/toolbar/stock_top_24.png" NDATA PNG> - <!ENTITY EtherealToolbarZoom100 SYSTEM "./graphics/toolbar/stock_zoom_1_24.png" NDATA PNG> - <!ENTITY EtherealToolbarZoomIn SYSTEM "./graphics/toolbar/stock_zoom_in_24.png" NDATA PNG> - <!ENTITY EtherealToolbarZoomOut SYSTEM "./graphics/toolbar/stock_zoom_out_24.png" NDATA PNG> - <!ENTITY EtherealToolbarColorize SYSTEM "./graphics/toolbar/colorize_24.png" NDATA PNG> - <!ENTITY EtherealToolbarAutoScroll SYSTEM "./graphics/toolbar/autoscroll_24.png" NDATA PNG> - <!ENTITY EtherealToolbarResizeColumns SYSTEM "./graphics/toolbar/resize_columns_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarCaptureInterfaces SYSTEM "./graphics/toolbar/capture_interfaces_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarCaptureOptions SYSTEM "./graphics/toolbar/capture_options_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarCaptureStart SYSTEM "./graphics/toolbar/capture_start_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarCaptureStop SYSTEM "./graphics/toolbar/capture_stop_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarCaptureRestart SYSTEM "./graphics/toolbar/capture_restart_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarCaptureFilters SYSTEM "./graphics/toolbar/capture_filter_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarDisplayFilters SYSTEM "./graphics/toolbar/display_filter_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarAdd SYSTEM "./graphics/toolbar/stock_add_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarGoLast SYSTEM "./graphics/toolbar/stock_bottom_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarClose SYSTEM "./graphics/toolbar/stock_close_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarColoringRules SYSTEM "./graphics/toolbar/stock_colorselector_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarHelp SYSTEM "./graphics/toolbar/stock_help_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarGoTo SYSTEM "./graphics/toolbar/stock_jump_to_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarGoBack SYSTEM "./graphics/toolbar/stock_left_arrow_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarOpen SYSTEM "./graphics/toolbar/stock_open_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarPreferences SYSTEM "./graphics/toolbar/stock_preferences_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarPrint SYSTEM "./graphics/toolbar/stock_print_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarProperties SYSTEM "./graphics/toolbar/stock_properties_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarReload SYSTEM "./graphics/toolbar/stock_refresh_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarGoForward SYSTEM "./graphics/toolbar/stock_right_arrow_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarSave SYSTEM "./graphics/toolbar/stock_save_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarSaveAs SYSTEM "./graphics/toolbar/stock_save_as_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarFind SYSTEM "./graphics/toolbar/stock_search_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarStop SYSTEM "./graphics/toolbar/stock_stop_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarGoFirst SYSTEM "./graphics/toolbar/stock_top_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarZoom100 SYSTEM "./graphics/toolbar/stock_zoom_1_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarZoomIn SYSTEM "./graphics/toolbar/stock_zoom_in_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarZoomOut SYSTEM "./graphics/toolbar/stock_zoom_out_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarColorize SYSTEM "./graphics/toolbar/colorize_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarAutoScroll SYSTEM "./graphics/toolbar/autoscroll_24.png" NDATA PNG> + <!ENTITY WiresharkToolbarResizeColumns SYSTEM "./graphics/toolbar/resize_columns_24.png" NDATA PNG> <!-- Third Chapter Statistics --> - <!ENTITY EtherealStatsSummary SYSTEM "./graphics/ethereal-stats-summary.png" NDATA PNG> - <!ENTITY EtherealStatsHierarchy SYSTEM "./graphics/ethereal-stats-hierarchy.png" NDATA PNG> - <!ENTITY EtherealStatsEndpoints SYSTEM "./graphics/ethereal-stats-endpoints.png" NDATA PNG> - <!ENTITY EtherealStatsConversations SYSTEM "./graphics/ethereal-stats-conversations.png" NDATA PNG> - <!ENTITY EtherealStatsIOGraphs SYSTEM "./graphics/ethereal-stats-iographs.png" NDATA PNG> - <!ENTITY EtherealStatsSrtDcerpcFilter SYSTEM "./graphics/ethereal-stats-srt-dcerpc-filter.png" NDATA PNG> - <!ENTITY EtherealStatsSrtDcerpc SYSTEM "./graphics/ethereal-stats-srt-dcerpc.png" NDATA PNG> + <!ENTITY WiresharkStatsSummary SYSTEM "./graphics/ethereal-stats-summary.png" NDATA PNG> + <!ENTITY WiresharkStatsHierarchy SYSTEM "./graphics/ethereal-stats-hierarchy.png" NDATA PNG> + <!ENTITY WiresharkStatsEndpoints SYSTEM "./graphics/ethereal-stats-endpoints.png" NDATA PNG> + <!ENTITY WiresharkStatsConversations SYSTEM "./graphics/ethereal-stats-conversations.png" NDATA PNG> + <!ENTITY WiresharkStatsIOGraphs SYSTEM "./graphics/ethereal-stats-iographs.png" NDATA PNG> + <!ENTITY WiresharkStatsSrtDcerpcFilter SYSTEM "./graphics/ethereal-stats-srt-dcerpc-filter.png" NDATA PNG> + <!ENTITY WiresharkStatsSrtDcerpc SYSTEM "./graphics/ethereal-stats-srt-dcerpc.png" NDATA PNG> <!-- Fifth Chapter --> <!-- Sixth Chapter --> <!-- Appendices etc --> - <!ENTITY EtherealFormatError SYSTEM "./graphics/ethereal-error-open.png" NDATA PNG> - <!ENTITY EtherealFormatError SYSTEM "./graphics/ethereal-error-open.png" NDATA PNG> - <!ENTITY EtherealSaveError SYSTEM "./graphics/ethereal-save-error.png" NDATA PNG> + <!ENTITY WiresharkFormatError SYSTEM "./graphics/ethereal-error-open.png" NDATA PNG> + <!ENTITY WiresharkFormatError SYSTEM "./graphics/ethereal-error-open.png" NDATA PNG> + <!ENTITY WiresharkSaveError SYSTEM "./graphics/ethereal-save-error.png" NDATA PNG> <!-- These are the actual files that make up the document --> diff --git a/docbook/wsug_src/WSUG_app_files.xml b/docbook/wsug_src/WSUG_app_files.xml index 05ae129bd7..9dda2e2708 100644 --- a/docbook/wsug_src/WSUG_app_files.xml +++ b/docbook/wsug_src/WSUG_app_files.xml @@ -4,15 +4,15 @@ <appendix id="AppFiles"> <title>Configuration (and other) Files and Folders</title> <para> - Ethereal uses a number of files and folders while it is running. Some + Wireshark uses a number of files and folders while it is running. Some of these reside in the personal configuration folder and are used to - maintain information between runs of Ethereal, while some of them are + maintain information between runs of Wireshark, while some of them are maintained in system areas. </para> <tip><title>Tip</title> - <para>A list of the folders Ethereal actually uses can be found under the + <para>A list of the folders Wireshark actually uses can be found under the <command>Folders</command> tab in the dialog box coming up, when you select - <command>About Ethereal</command> from the <command>Help</command> menu. + <command>About Wireshark</command> from the <command>Help</command> menu. </para> </tip> <para> @@ -39,43 +39,43 @@ <entry><command>preferences</command></entry> <entry>Settings from the Preferences dialog box.</entry> <entry>/etc/ethereal.conf, $HOME/.ethereal/preferences</entry> - <entry>%ETHEREAL%\ethereal.conf, %APPDATA%\Ethereal\preferences</entry> + <entry>%ETHEREAL%\ethereal.conf, %APPDATA%\Wireshark\preferences</entry> </row> <row> <entry><command>recent</command></entry> <entry>Recent GUI settings (e.g. recent files lists).</entry> <entry>$HOME/.ethereal/recent</entry> - <entry>%APPDATA%\Ethereal\recent</entry> + <entry>%APPDATA%\Wireshark\recent</entry> </row> <row> <entry><command>cfilters</command></entry> <entry>Capture filters.</entry> <entry>$HOME/.ethereal/cfilters</entry> - <entry>%ETHEREAL%\cfilters, %APPDATA%\Ethereal\cfilters</entry> + <entry>%ETHEREAL%\cfilters, %APPDATA%\Wireshark\cfilters</entry> </row> <row> <entry><command>dfilters</command></entry> <entry>Display filters.</entry> <entry>$HOME/.ethereal/dfilters</entry> - <entry>%ETHEREAL%\dfilters, %APPDATA%\Ethereal\dfilters</entry> + <entry>%ETHEREAL%\dfilters, %APPDATA%\Wireshark\dfilters</entry> </row> <row> <entry><command>colorfilters</command></entry> <entry>Coloring rules.</entry> <entry>$HOME/.ethereal/colorfilters</entry> - <entry>%ETHEREAL%\colorfilters, %APPDATA%\Ethereal\colorfilters</entry> + <entry>%ETHEREAL%\colorfilters, %APPDATA%\Wireshark\colorfilters</entry> </row> <row> <entry><command>disabled_protos</command></entry> <entry>Disabled protocols.</entry> <entry>$HOME/.ethereal/disabled_protos</entry> - <entry>%ETHEREAL%\disabled_protos, %APPDATA%\Ethereal\disabled_protos</entry> + <entry>%ETHEREAL%\disabled_protos, %APPDATA%\Wireshark\disabled_protos</entry> </row> <row> <entry><command>ethers</command></entry> <entry>Ethernet name resolution.</entry> <entry>/etc/ethers, $HOME/.ethereal/ethers</entry> - <entry>%ETHEREAL%\ethers, %APPDATA%\Ethereal\ethers</entry> + <entry>%ETHEREAL%\ethers, %APPDATA%\Wireshark\ethers</entry> </row> <row> <entry><command>manuf</command></entry> @@ -103,7 +103,7 @@ $HOME/.ethereal/plugins </entry> <entry>%ETHEREAL%\plugins\<version>, - %APPDATA%\Ethereal\plugins</entry> + %APPDATA%\Wireshark\plugins</entry> </row> <row> <entry><command>temp</command></entry> @@ -120,12 +120,12 @@ <filename>C:\Documents and Settings\<username>\Application Data</filename> (for further details, have a look at <xref linkend="ChWindowsProfiles"/>), %ETHEREAL% points to the Wireshark program folder, typically - <filename>C:\Program Files\Ethereal</filename> + <filename>C:\Program Files\Wireshark</filename> </para> </note> <note><title>Unix/Linux folders</title> <para> - The <filename>/etc</filename> folder is the global Ethereal configuration + The <filename>/etc</filename> folder is the global Wireshark configuration folder. The folder actually used on your system may vary, maybe something like: <filename>/usr/local/etc</filename>. </para> @@ -136,7 +136,7 @@ <term><command>preferences/ethereal.conf</command></term> <listitem> <para> - This file contains your Ethereal preferences, + This file contains your Wireshark preferences, including defaults for capturing and displaying packets. It is a simple text file containing statements of the form: <programlisting> @@ -239,7 +239,7 @@ udp addresses to names, it consults the files listed in <xref linkend="AppFilesTabFolders"/>. If an address is not found in /etc/ethers, - Ethereal looks in $HOME/.ethereal/ethers + Wireshark looks in $HOME/.ethereal/ethers </para> <para> Each line in these files consists of one hardware address and @@ -260,7 +260,7 @@ c0-00-ff-ff-ff-ff TR_broadcast <term><command>manuf</command></term> <listitem> <para> - Ethereal uses the files listed in <xref linkend="AppFilesTabFolders"/> + Wireshark uses the files listed in <xref linkend="AppFilesTabFolders"/> to translate the first three bytes of an Ethernet address into a manufacturers name. This file has the same format as the ethers file, except addresses are three bytes long. @@ -281,7 +281,7 @@ c0-00-ff-ff-ff-ff TR_broadcast <term><command>hosts</command></term> <listitem> <para> - Ethereal uses the files listed in <xref linkend="AppFilesTabFolders"/> + Wireshark uses the files listed in <xref linkend="AppFilesTabFolders"/> to translate IPv4 and IPv6 addresses into names. </para> <para> @@ -304,7 +304,7 @@ c0-00-ff-ff-ff-ff TR_broadcast <term><command>ipxnets</command></term> <listitem> <para> - Ethereal uses the files listed in <xref linkend="AppFilesTabFolders"/> + Wireshark uses the files listed in <xref linkend="AppFilesTabFolders"/> to translate IPX network numbers into names. </para> <para> @@ -326,7 +326,7 @@ c0-a8-1c-00 CEO <term><command>plugins</command> folder</term> <listitem> <para> - Ethereal searches for plugins in the directories listed in + Wireshark searches for plugins in the directories listed in <xref linkend="AppFilesTabFolders"/>. They are searched in the order listed. </para> @@ -337,7 +337,7 @@ c0-a8-1c-00 CEO <listitem> <para> If you start a new capture and don't specify a filename for it, - Ethereal uses this directory to place that file in, see + Wireshark uses this directory to place that file in, see <xref linkend="ChCapCaptureFiles"/>. </para> </listitem> @@ -352,7 +352,7 @@ c0-a8-1c-00 CEO </para> <para> As already mentioned, you can find the currently used folders in the - <command>About Ethereal</command> dialog. + <command>About Wireshark</command> dialog. </para> <section id="ChWindowsProfiles"><title>Windows profiles</title> @@ -381,7 +381,7 @@ c0-a8-1c-00 CEO <para> The default in Windows 95/98/ME is: all users work with the same profile, which is located at: - <filename>C:\windows\Application Data\Ethereal</filename> + <filename>C:\windows\Application Data\Wireshark</filename> </para> </listitem> </varlistentry> @@ -391,7 +391,7 @@ c0-a8-1c-00 CEO <para> In Windows 98 and ME you can enable separate user profiles. In that case, something like: - <filename>C:\windows\Profiles\<username>\Application Data\Ethereal</filename> + <filename>C:\windows\Profiles\<username>\Application Data\Wireshark</filename> is used. </para> </listitem> @@ -400,7 +400,7 @@ c0-a8-1c-00 CEO <term><command>NT 4</command></term> <listitem> <para> - <filename>C:\WINNT\Profiles\<username>\Application Data\Ethereal</filename> + <filename>C:\WINNT\Profiles\<username>\Application Data\Wireshark</filename> </para> </listitem> </varlistentry> @@ -443,7 +443,7 @@ c0-a8-1c-00 CEO <section id="ChWindowsTempFolder"> <title>Windows temporary folder</title> <para> - Ethereal uses the folder which is set by the TMPDIR or TEMP environment + Wireshark uses the folder which is set by the TMPDIR or TEMP environment variable. This variable will be set by the windows installer. </para> <para> diff --git a/docbook/wsug_src/WSUG_app_howitworks.xml b/docbook/wsug_src/WSUG_app_howitworks.xml index 25fadb4a5b..b3180db833 100644 --- a/docbook/wsug_src/WSUG_app_howitworks.xml +++ b/docbook/wsug_src/WSUG_app_howitworks.xml @@ -2,11 +2,11 @@ <!-- $Id$ --> <appendix id="AppHowItWorks"> - <title>How Ethereal Works</title> + <title>How Wireshark Works</title> <para> - When using such a complex program like Ethereal, it's sometimes useful to + When using such a complex program like Wireshark, it's sometimes useful to understand the mechanisms and concepts behind the surface. This is an - approach to shed some light on the inner workings of Ethereal. + approach to shed some light on the inner workings of Wireshark. </para> <section><title>Program start</title> @@ -53,16 +53,16 @@ <section><title>Protocol dissectors</title> <para> Each protocol has it's own protocol dissector. A dissector is called from - Ethereal, if the packet data seems to be of that corresponding protocol. The - dissector will then process the packet data and call back Ethereal if it + Wireshark, if the packet data seems to be of that corresponding protocol. The + dissector will then process the packet data and call back Wireshark if it couldn't dissect all the data in that packet to do any further dissections. </para> <para> - So Ethereal will dissect a packet from the lowest to the highest protocol + So Wireshark will dissect a packet from the lowest to the highest protocol layers. </para> <para> - But how does Ethereal know, which dissector to choose? + But how does Wireshark know, which dissector to choose? </para> <para> At program start, the dissector registers itself at the appropriate place(s). @@ -78,7 +78,7 @@ <command>heuristic</command> if no such well known way exists, the dissector can register itself for the heuristic mechanism. If a lower layer dissector has to handle some packet data where no well known way exists, it can - handover the packet to Ethereal's heuristic mechanism. This will ask all + handover the packet to Wireshark's heuristic mechanism. This will ask all registered upper layer dissectors, if they "like" that data. Each of these dissectors will typically look into the first few bytes of the packet, if it contains some characteristic data of that protocol. So the dissector can @@ -87,17 +87,17 @@ </itemizedlist> </para> <para> - Let's look at an example: We'll assume, Ethereal loads a TCP/IP/Ethernet - packet. Ethereal will call the Ethernet dissector, which will dissect the + Let's look at an example: We'll assume, Wireshark loads a TCP/IP/Ethernet + packet. Wireshark will call the Ethernet dissector, which will dissect the Ethernet related data (usually the first 6+6+2 bytes). Then this dissector - calls back into Ethereal and will pass the rest of the data back to - Ethereal. Ethereal in turn will call the next related dissector, in our case + calls back into Wireshark and will pass the rest of the data back to + Wireshark. Wireshark in turn will call the next related dissector, in our case the IP dissector (because of the value 0x800 in the Ethernet type field). This game will continue, until no more data has to be dissected, or the data - is just unknown to Ethereal. + is just unknown to Wireshark. </para> <para> - You can control the way how Ethereal calls it's dissectors, see <xref + You can control the way how Wireshark calls it's dissectors, see <xref linkend="ChAdvProtocolDissectionSection"/> for details. </para> </section> diff --git a/docbook/wsug_src/WSUG_app_messages.xml b/docbook/wsug_src/WSUG_app_messages.xml index 8d2e384acb..298c7d3e65 100644 --- a/docbook/wsug_src/WSUG_app_messages.xml +++ b/docbook/wsug_src/WSUG_app_messages.xml @@ -2,9 +2,9 @@ <!-- $Id$ --> <appendix id="AppMessages"> - <title>Ethereal Messages</title> + <title>Wireshark Messages</title> <para> - Ethereal provides you with additional information generated out of + Wireshark provides you with additional information generated out of the plain packet data or it may need to indicate dissection problems. Messages generated by Wireshark are usually placed in [] parentheses. </para> @@ -20,7 +20,7 @@ <listitem> <para> <command>Wrong dissector</command> - Ethereal errorneously has chosen the wrong protocol dissector for + Wireshark errorneously has chosen the wrong protocol dissector for this packet. This will happen e.g. if you are using a protocol not on it's well known TCP or UDP port. You may try Analyze|Decode As to circumvent this problem. @@ -54,7 +54,7 @@ Any of the above is possible. You'll have to look into the specific situation to determine what it is. You could disable the dissector by disabling the - protocol on the Analyze menu and check how Ethereal displays the packet + protocol on the Analyze menu and check how Wireshark displays the packet then. You could (if it's TCP) enable reassembly for TCP and the specific dissector (if possible) in the Edit|Preferences menu. You could check the packet contents yourself by reading the packet bytes and comparing it to diff --git a/docbook/wsug_src/WSUG_app_protocols.xml b/docbook/wsug_src/WSUG_app_protocols.xml index 6acdf69d94..ce43738bd4 100644 --- a/docbook/wsug_src/WSUG_app_protocols.xml +++ b/docbook/wsug_src/WSUG_app_protocols.xml @@ -4,12 +4,12 @@ <appendix id="AppProtocols"> <title>Protocols and Protocol Fields</title> <para> - Ethereal distinguishes between protocols (e.g. tcp) and protocol fields + Wireshark distinguishes between protocols (e.g. tcp) and protocol fields (e.g. tcp.port). </para> <para> A comprehensive list of all protocols and protocol fields can be found - at: <ulink url="&EtherealProtocolsPage;">&EtherealProtocolsPage;</ulink> + at: <ulink url="&WiresharkProtocolsPage;">&WiresharkProtocolsPage;</ulink> </para> </appendix> <!-- End of WSUG Appendix Protocols --> diff --git a/docbook/wsug_src/WSUG_app_tools.xml b/docbook/wsug_src/WSUG_app_tools.xml index c4bbf48aec..b6be9d893c 100644 --- a/docbook/wsug_src/WSUG_app_tools.xml +++ b/docbook/wsug_src/WSUG_app_tools.xml @@ -16,12 +16,12 @@ <section id="AppToolstcpdump"> <title><command>tcpdump</command>: Capturing with tcpdump for viewing - with Ethereal</title> + with Wireshark</title> <para> There are occasions when you want to capture packets using <command>tcpdump</command> rather than <command>ethereal</command>, especially when you want to do a remote capture and do not want the - network load associated with running Ethereal remotely (not to + network load associated with running Wireshark remotely (not to mention all the X traffic polluting your capture). </para> <para> @@ -50,7 +50,7 @@ tcpdump -i <interface> -s 1500 -w <some-file> </section> <section id="AppToolstethereal"> - <title><command>tethereal</command>: Terminal-based Ethereal</title> + <title><command>tethereal</command>: Terminal-based Wireshark</title> <para> <application>Tethereal</application> is a terminal oriented version of ethereal designed for capturing and displaying packets when an @@ -118,7 +118,7 @@ Usage: editcap [-r] [-h] [-v] [-T <encap type>] [-E <probability>] -E <probability> specifies the probability (between 0 and 1) that a particular byte will will have an error. -F <capture type> specifies the capture file type to write: - libpcap - libpcap (tcpdump, Ethereal, etc.) + libpcap - libpcap (tcpdump, Wireshark, etc.) rh6_1libpcap - RedHat Linux 6.1 libpcap (tcpdump) suse6_3libpcap - SuSE Linux 6.3 libpcap (tcpdump) modlibpcap - modified libpcap (tcpdump) @@ -257,7 +257,7 @@ Usage: editcap [-r] [-h] [-v] [-T <encap type>] [-E <probability>] </para> <para> It is mainly for converting funny captures to something - that Ethereal can deal with. + that Wireshark can deal with. </para> <para> The default frame @@ -463,7 +463,7 @@ Usage: mergecap [-hva] [-s <snaplen>] [-T <encap type>] bacnet-ms-tp - BACnet MS/TP default is the same as the first input file -F <capture type> capture file type to write: - libpcap - libpcap (tcpdump, Ethereal, etc.) + libpcap - libpcap (tcpdump, Wireshark, etc.) rh6_1libpcap - RedHat Linux 6.1 libpcap (tcpdump) suse6_3libpcap - SuSE Linux 6.3 libpcap (tcpdump) modlibpcap - modified libpcap (tcpdump) @@ -608,7 +608,7 @@ Usage: mergecap [-hva] [-s <snaplen>] [-T <encap type>] Text2pcap also allows the user to read in dumps of application-level data, by inserting dummy L2, L3 and L4 headers before each packet. The user can elect to insert Ethernet headers, Ethernet and IP, or - Ethernet, IP and UDP headers before each packet. This allows Ethereal + Ethernet, IP and UDP headers before each packet. This allows Wireshark or any other full-packet decoder to handle these dumps. </para> <example id="AppToolstext2pcapEx"> @@ -723,7 +723,7 @@ where <input-filename> specifies input filename (use - for standard input) </para> <para> For IP packets, instead of generating a fake Ethernet header you - can also use -l 12 to indicate a raw IP packet to Ethereal. Note + can also use -l 12 to indicate a raw IP packet to Wireshark. Note that -l 12 does not work for any non-IP Layer 3 packet (e.g. ARP), whereas generating a dummy Ethernet header with -e works for any sort of L3 packet. @@ -812,7 +812,7 @@ where <input-filename> specifies input filename (use - for standard input) </para> <para> It is also COOL to work on a great Open Source project such as - the case with "Ethereal" ( + the case with "Wireshark" ( <ulink url="http://www.ethereal.com">http://www.ethereal.com</ulink> ) </para> @@ -840,7 +840,7 @@ where <input-filename> specifies input filename (use - for standard input) <para> Of course you need ethereal installed to compile the code and tweak it if required. idl2eth is part of the - standard Ethereal distribution + standard Wireshark distribution </para> </listitem> </orderedlist> diff --git a/docbook/wsug_src/WSUG_chapter_advanced.xml b/docbook/wsug_src/WSUG_chapter_advanced.xml index 9df23cfe37..edf1975cb5 100644 --- a/docbook/wsug_src/WSUG_chapter_advanced.xml +++ b/docbook/wsug_src/WSUG_chapter_advanced.xml @@ -1,13 +1,13 @@ <!-- WSUG Chapter Advanced --> -<!-- $Id:$ --> +<!-- $Id$ --> <chapter id="ChapterAdvanced"> <title>Advanced Topics</title> <section id="ChAdvIntroduction"><title>Introduction</title> <para> - In this chapter some of the advanced features of Ethereal will be described. + In this chapter some of the advanced features of Wireshark will be described. </para> </section> @@ -20,14 +20,14 @@ are trying to make sense of a data stream. Maybe you just need a display filter to show only the packets of that TCP stream. - If so, Ethereal's ability to follow a TCP stream will be useful to you. + If so, Wireshark's ability to follow a TCP stream will be useful to you. </para> <para> Simply select a TCP packet in the packet list of the stream/connection you are interested in and then select the Follow TCP Stream menu item from the Wireshark Tools menu (or use the context menu in the packet list). - Ethereal will set an appropriate display filter and pop up a dialog + Wireshark will set an appropriate display filter and pop up a dialog box with all the data from the TCP stream laid out in order, as shown in <xref linkend="ChAdvFollowStream"/>. </para> @@ -41,7 +41,7 @@ <section><title>The "Follow TCP Stream" dialog box </title> <figure id="ChAdvFollowStream"> <title>The "Follow TCP Stream" dialog box</title> - <graphic entityref="EtherealFollowStream" format="PNG"/> + <graphic entityref="WiresharkFollowStream" format="PNG"/> </figure> <para> The stream content is displayed in the same sequence as it appeared on @@ -141,7 +141,7 @@ <para> Time stamps, their precisions and all that can be quite confusing, this section will provide you with information what's going - on while Ethereal processes time stamps. + on while Wireshark processes time stamps. </para> <para> While packets are captured, each packet is time stamped as it comes in. @@ -150,32 +150,32 @@ </para> <para> So where do these time stamps come from? - While capturing, Ethereal gets the time stamps from the libpcap (WinPcap) + While capturing, Wireshark gets the time stamps from the libpcap (WinPcap) library, which in turn get's them from the operating system kernel. - If the capture data is loaded from a capture file, Ethereal obviously gets + If the capture data is loaded from a capture file, Wireshark obviously gets the data from that file. </para> - <section><title>Ethereal internals</title> + <section><title>Wireshark internals</title> <para> - The internal format that Ethereal uses to keep a packet time stamp consists + The internal format that Wireshark uses to keep a packet time stamp consists of the date (in days since 1.1.1970) and the time of day (in nanoseconds - since midnight). You can adjust the way Ethereal displays the time stamp data + since midnight). You can adjust the way Wireshark displays the time stamp data in the packet list, see the "Time Display Format" item in the <xref linkend="ChUseViewMenuSection"/> for details. </para> <para> - While reading or writing capture files, Ethereal converts the time stamp + While reading or writing capture files, Wireshark converts the time stamp data between the capture file format and the internal format as required. </para> <para> - While capturing, Ethereal uses the libpcap (WinPcap) capture library which + While capturing, Wireshark uses the libpcap (WinPcap) capture library which supports microsecond resolution. Unless you are working with specialized capturing hardware, this resolution should be adequate. </para> </section> <section><title>Capture file formats</title> <para> - Every capture file format that Ethereal knows support time stamps. + Every capture file format that Wireshark knows support time stamps. The time stamp precision supported by a specific capture file format differs widely and varies from one second "0" to one nanosecond "0.123456789". @@ -195,14 +195,14 @@ the capability to store the actual precision will lead to loss of information. Example: If you load a capture file with nanosecond resolution and store the capture data to a libpcap file (with microsecond resolution) - Ethereal obviously must reduce the precision from nanosecond to microsecond. + Wireshark obviously must reduce the precision from nanosecond to microsecond. </para> </note> </section> <section><title>Accuracy</title> <para> It's often asked: "Which time stamp accuracy is provided by Wireshark?". - Well, Ethereal doesn't create any time stamps itself but simply get's them + Well, Wireshark doesn't create any time stamps itself but simply get's them from "somewhere else" and displays them. So accuracy will depend on the capture system (operating system, performance, ...) that you use. Because of this, the above question is difficult to answer in a @@ -353,18 +353,18 @@ You can use the Network Time Protocol (NTP) to automatically adjust your computer to the correct time, by synchronizing it to internet NTP clock servers. NTP clients are available for all operating systems that - Ethereal supports (and for a lot more), for examples see: + Wireshark supports (and for a lot more), for examples see: <ulink url="&NTPSite;">&NTPSite;</ulink>. </para> </tip> </para> </section> - <section><title>Ethereal and Time Zones</title> + <section><title>Wireshark and Time Zones</title> <para> - So what's the relationship between Ethereal and time zones anyway? + So what's the relationship between Wireshark and time zones anyway? </para> <para> - Ethereal's native capture file format (libpcap format), and some + Wireshark's native capture file format (libpcap format), and some other capture file formats, such as the Windows Sniffer, EtherPeek, AiroPeek, and Sun snoop formats, save the arrival time of packets as UTC values. @@ -378,7 +378,7 @@ "Windows 9x based" systems (Windows 95, Windows 98, Windows Me) represent time internally as local time. When capturing, WinPcap has to convert the time to UTC before - supplying it to Ethereal. + supplying it to Wireshark. If the system's time zone is not set correctly, that conversion will not be done correctly. </para> @@ -388,13 +388,13 @@ formats, save the arrival time of packets as local time values. </para> <para> - Internally to Ethereal, time stamps are represented in UTC; this + Internally to Wireshark, time stamps are represented in UTC; this means that, when reading capture files that save the arrival - time of packets as local time values, Ethereal must convert + time of packets as local time values, Wireshark must convert those local time values to UTC values. </para> <para> - Ethereal in turn will display the time stamps always in local + Wireshark in turn will display the time stamps always in local time. The displaying computer will convert them from UTC to local time and displays this (local) time. For capture files saving the arrival time of packets as UTC values, this means @@ -462,17 +462,17 @@ <para> An example: Let's assume that someone in Los Angeles captured a packet with - Ethereal at exactly 2 o'clock local time and sents you this + Wireshark at exactly 2 o'clock local time and sents you this capture file. The capture file's time stamp will be represented in UTC as 10 o'clock. You are located in Berlin and will see 11 - o'clock on your Ethereal display. + o'clock on your Wireshark display. </para> <para> Now you have a phone call, video conference or internet meeting with that one to talk about that capture file. As you are both looking at the displayed time on your local computers, the one in Los Angeles still sees 2 o'clock but you in Berlin will see - 11 o'clock. The time displays are different as both Ethereal displays + 11 o'clock. The time displays are different as both Wireshark displays will show the (different) local times at the same point in time. </para> <para> @@ -505,26 +505,26 @@ </para> <tip><title>Tip!</title> <para> - Ethereal calls this mechanism reassembling, although a specific protocol + Wireshark calls this mechanism reassembling, although a specific protocol specification might use a different term for this (e.g. desegmentation, defragmentation, ...). </para> </tip> </section> - <section><title>How Ethereal handles it</title> + <section><title>How Wireshark handles it</title> <para> - For some of the network protocols Ethereal knows of, a mechanism is + For some of the network protocols Wireshark knows of, a mechanism is implemented to find, decode and display these chunks of data. - Ethereal will try to find the corresponding packets of this chunk, + Wireshark will try to find the corresponding packets of this chunk, and will show the combined data as additional pages in the "Packet Bytes" pane (for information about this pane, see <xref linkend="ChUsePacketBytesPaneSection"/>). </para> <para> - <figure id="ChAdvEtherealBytesPaneTabs"> + <figure id="ChAdvWiresharkBytesPaneTabs"> <title>The "Packet Bytes" pane with a reassembled tab</title> - <graphic entityref="EtherealBytesPaneTabs" format="PNG"/> + <graphic entityref="WiresharkBytesPaneTabs" format="PNG"/> </figure> </para> @@ -542,7 +542,7 @@ <para> An example: In a <command>HTTP</command> GET response, the requested data (e.g. a - HTML page) is returned. Ethereal will show the hex dump of the data in + HTML page) is returned. Wireshark will show the hex dump of the data in a new tab "Uncompressed entity body" in the "Packet Bytes" pane. </para> <para> @@ -585,8 +585,8 @@ a human readable format. There are two possible ways to do this conversations, depending on the resolution to be done: calling system/network services (like the gethostname function) and/or evaluate - from Ethereal specific configuration files. - For details about the configuration files Ethereal uses for name + from Wireshark specific configuration files. + For details about the configuration files Wireshark uses for name resolution and alike, see <xref linkend="AppFiles"/>. </para> <para> @@ -596,7 +596,7 @@ <section><title>Name Resolution drawbacks</title> <para> - Name resolution can be invaluable while working with Ethereal and may + Name resolution can be invaluable while working with Wireshark and may save you even hours of work. Unfortunately, it also has it's drawbacks. </para> <itemizedlist> @@ -623,7 +623,7 @@ <para> <command>DNS may add additional packets to your capture file.</command> You may see packets to/from your machine in your capture file, which are - caused by name resolution network services of the machine Ethereal + caused by name resolution network services of the machine Wireshark captures from. XXX - are there any other such packets than DNS ones? </para> @@ -634,9 +634,9 @@ This is required for acceptable performance. However, if the name resolution information should change while Wireshark is running, - Ethereal won't notice a change to the name resolution information once + Wireshark won't notice a change to the name resolution information once it's get cached. If this information changes while Wireshark is running, - e.g. a new DHCP lease takes effect, Ethereal won't notice it. + e.g. a new DHCP lease takes effect, Wireshark won't notice it. XXX - is this true for all or only for DNS info? </para> </listitem> @@ -659,16 +659,16 @@ something more "human readable". </para> <para><command>ARP name resolution (system service)</command> - Ethereal will ask the operating system to convert an ethernet address + Wireshark will ask the operating system to convert an ethernet address to the corresponding IP address (e.g. 00:09:5b:01:02:03 -> 192.168.0.1). </para> <para><command>Ethernet codes (ethers file)</command> - If the ARP name resolution failed, Ethereal tries to convert the ethernet + If the ARP name resolution failed, Wireshark tries to convert the ethernet address to a known device name, which has been assigned by the user using an ethers file (e.g. 00:09:5b:01:02:03 -> homerouter). </para> <para><command>Ethernet manufacturer codes (manuf file)</command> - If both ARP and ethers didn't returned a result, Ethereal tries to convert + If both ARP and ethers didn't returned a result, Wireshark tries to convert the first 3 bytes of an ethernet address to an abbreviated manufacturer name, which has been assigned by the IEC (e.g. 00:09:5b:01:02:03 -> Netgear_01:02:03). @@ -681,10 +681,10 @@ something more "human readable". </para> <para><command>DNS/ADNS name resolution (system/library service)</command> - Ethereal will ask the operating system (or the ADNS library), + Wireshark will ask the operating system (or the ADNS library), to convert an IP address to the hostname associated with it (e.g. 65.208.228.223 -> www.ethereal.com). The DNS service is using - synchronous calls to the DNS server. So Ethereal will stop responding + synchronous calls to the DNS server. So Wireshark will stop responding until a response to a DNS request is returned. If possible, you might consider using the ADNS library (which won't wait for a network response). </para> @@ -692,7 +692,7 @@ <title>Warning!</title> <para> Enabling network name resolution when your name server is - unavailable may significantly slow down Ethereal while it waits + unavailable may significantly slow down Wireshark while it waits for all of the name server requests to time out. Use ADNS in that case. </para> @@ -715,14 +715,14 @@ a while (several seconds). The ADNS service will work a bit differently. It will also ask the DNS server, but it won't wait for the answer. - It will just return to Ethereal in a very short amount of time. + It will just return to Wireshark in a very short amount of time. The actual (and the following) address fields won't show the resolved name until the ADNS call returned. As mentioned above, the values get cached, so you can use View/Reload to "update" these fields to show the resolved values. </para> <para><command>hosts name resolution (hosts file)</command> - If DNS name resolution failed, Ethereal will try to convert an IP address + If DNS name resolution failed, Wireshark will try to convert an IP address to the hostname associated with it, using an hosts file provided by the user (e.g. 65.208.228.223 -> www.ethereal.com). </para> @@ -740,7 +740,7 @@ something more "human readable". </para> <para><command>TCP/UDP port conversion (system service)</command> - Ethereal will ask the operating system to convert a TCP or UDP port to + Wireshark will ask the operating system to convert a TCP or UDP port to its well known name (e.g. 80 -> http). </para> <para> @@ -811,9 +811,9 @@ <ulink url="http://en.wikipedia.org/wiki/Checksum"/>. </para> </sidebar> - <section><title>Ethereal checksum validation</title> + <section><title>Wireshark checksum validation</title> <para> - Ethereal will validate the checksums of several potocols, e.g.: IP, TCP, ... + Wireshark will validate the checksums of several potocols, e.g.: IP, TCP, ... </para> <para> It will do the same calculation as a "normal receiver" would do, @@ -822,7 +822,7 @@ </para> <para> Checksum validation can be switched off for various protocols in the - Ethereal protocol preferences, e.g. to (very slightly) increase + Wireshark protocol preferences, e.g. to (very slightly) increase performance. </para> <para> @@ -842,7 +842,7 @@ For example: The Ethernet transmitting hardware calculates the Ethernet CRC32 checksum and the receiving hardware validates this checksum. - If the received checksum is wrong Ethereal won't even see the packet, + If the received checksum is wrong Wireshark won't even see the packet, as the Ethernet hardware internally throws away the packet. </para> <para> @@ -859,9 +859,9 @@ <note><title>Note!</title> <para> Checksum offloading often causes confusion as the network packets to be - transmitted are handed over to Ethereal before the checksums are actually + transmitted are handed over to Wireshark before the checksums are actually calculated. - Ethereal gets these "empty" checksums and displays them as + Wireshark gets these "empty" checksums and displays them as invalid, even though the packets will contain valid checksums when they leave the network hardware later. </para> diff --git a/docbook/wsug_src/WSUG_chapter_build_install.xml b/docbook/wsug_src/WSUG_chapter_build_install.xml index f3f5e2f9c1..0be221e450 100644 --- a/docbook/wsug_src/WSUG_chapter_build_install.xml +++ b/docbook/wsug_src/WSUG_chapter_build_install.xml @@ -2,12 +2,12 @@ <!-- $Id$ --> <chapter id="ChapterBuildInstall"> - <title>Building and Installing Ethereal</title> + <title>Building and Installing Wireshark</title> <section id="ChBuildInstallIntro"> <title>Introduction</title> <para> As with all things, there must be a beginning, and so it is with - Ethereal. To use Ethereal, you must: + Wireshark. To use Wireshark, you must: <itemizedlist> <listitem> <para> @@ -16,21 +16,21 @@ </listitem> <listitem> <para> - Obtain the source and build Ethereal for your operating system. + Obtain the source and build Wireshark for your operating system. </para> </listitem> </itemizedlist> </para> <para> - Currently, only two or three Linux distributions ship Ethereal, and + Currently, only two or three Linux distributions ship Wireshark, and they are commonly shipping an out-of-date version. No other versions - of UNIX ship Ethereal so far, and Microsoft does not ship it with any + of UNIX ship Wireshark so far, and Microsoft does not ship it with any version of Windows. For that reason, you will need to know where to - get the latest version of Ethereal and how to install it. + get the latest version of Wireshark and how to install it. </para> <para> This chapter shows you how to obtain source and binary packages, - and how to build Ethereal from source, should you choose to do so. + and how to build Wireshark from source, should you choose to do so. </para> <para> The following are the general steps you would use: @@ -63,7 +63,7 @@ <title>Obtaining the source and binary distributions</title> <para> You can obtain both source and binary distributions from the Wireshark - web site: <ulink url="&EtherealWebSite;">&EtherealWebSite;</ulink>. + web site: <ulink url="&WiresharkWebSite;">&WiresharkWebSite;</ulink>. Simply select the download link, and then select either the source package or binary package of your choice from the mirror site closest to you. @@ -71,9 +71,9 @@ <note> <title>Download all required files!</title> <para> - In general, unless you have already downloaded Ethereal + In general, unless you have already downloaded Wireshark before, you will most likely need to download several source - packages if you are building Ethereal from source. This is + packages if you are building Wireshark from source. This is covered in more detail below. <!-- Make a ref --> </para> </note> @@ -85,7 +85,7 @@ <title>Note!</title> <para> While you will find a number of binary packages available on the - Ethereal web site, you might not find one for your platform, and + Wireshark web site, you might not find one for your platform, and they often tend to be several versions behind the current released version, as they are contributed by people who have the platforms they are built for. @@ -98,9 +98,9 @@ </section> <section id="ChBuildInstallBeforeBuild"> - <title>Before you build <application>Ethereal</application> under UNIX</title> + <title>Before you build <application>Wireshark</application> under UNIX</title> <para> - Before you build Ethereal from sources, or install a binary package, + Before you build Wireshark from sources, or install a binary package, you must ensure that you have the following other packages installed: <itemizedlist> <listitem> @@ -112,7 +112,7 @@ </listitem> <listitem> <para> - libpcap, the packet capture software that Ethereal uses. + libpcap, the packet capture software that Wireshark uses. </para> <para> You can obtain libpcap from @@ -260,7 +260,7 @@ rpm -ivh libpcap-0.4-19.i386.rpm </para> </note> <para> - Under Debian you can install Ethereal using apt-get. apt-get will + Under Debian you can install Wireshark using apt-get. apt-get will handle any dependency issues for you. <xref linkend="Ch02Ex5"/> shows how to do this. <example id="Ch02Ex5"> @@ -273,9 +273,9 @@ apt-get install ethereal </section> <section id="ChBuildInstallUnixBuild"> - <title>Building Ethereal from source under UNIX</title> + <title>Building Wireshark from source under UNIX</title> <para> - Use the following general steps if you are building Ethereal from + Use the following general steps if you are building Wireshark from source under a UNIX operating system: <orderedlist> <listitem> @@ -285,22 +285,22 @@ apt-get install ethereal version of UNIX uses GNU <command>tar</command>, you can use the following command: <programlisting> -tar zxvf ethereal-&EtherealCurrentVersion;-tar.gz +tar zxvf ethereal-&WiresharkCurrentVersion;-tar.gz </programlisting> </para> <para> For other versions of UNIX, You will want to use the following commands: <programlisting> -gzip -d ethereal-&EtherealCurrentVersion;-tar.gz -tar xvf ethereal-&EtherealCurrentVersion;-tar +gzip -d ethereal-&WiresharkCurrentVersion;-tar.gz +tar xvf ethereal-&WiresharkCurrentVersion;-tar </programlisting> <note> <title>Note!</title> <para> The pipeline <command> - gzip -dc ethereal-&EtherealCurrentVersion;-tar.gz | tar xvf - + gzip -dc ethereal-&WiresharkCurrentVersion;-tar.gz | tar xvf - </command> will work here as well. </para> </note> @@ -353,7 +353,7 @@ make install </orderedlist> </para> <para> - Once you have installed Ethereal with <command>make install</command> + Once you have installed Wireshark with <command>make install</command> above, you should be able to run it by entering <command>ethereal</command>. </para> @@ -387,7 +387,7 @@ rpm -ivh ethereal-0.10.5-0.2.2.i386.rpm <section> <title>Installing from deb's under Debian</title> <para> - Use the following command to install Ethereal under Debian: + Use the following command to install Wireshark under Debian: <programlisting> apt-get install ethereal </programlisting> @@ -437,10 +437,10 @@ apt-get install ethereal <title>Building from source under Windows</title> <para> It is recommended to use the binary installer for Windows, - until you want to start developing Ethereal on the Windows platform. + until you want to start developing Wireshark on the Windows platform. </para> <para> - For further information how to build Ethereal for Windows from the + For further information how to build Wireshark for Windows from the sources, have a look at the Development Wiki: <ulink url="http://wiki.ethereal.com/Development">http://wiki.ethereal.com/Development</ulink> for the latest available development documentation. @@ -448,30 +448,30 @@ apt-get install ethereal </section> <section id="ChBuildInstallWinInstall"> - <title>Installing Ethereal under Windows</title> + <title>Installing Wireshark under Windows</title> <para> - In this section we explore installing Ethereal under Windows from the + In this section we explore installing Wireshark under Windows from the binary packages. </para> - <section id="ChBuildInstallEthereal"> - <title>Install Ethereal</title> + <section id="ChBuildInstallWireshark"> + <title>Install Wireshark</title> <para> - You may acquire a binary installer of Ethereal named something like: + You may acquire a binary installer of Wireshark named something like: <filename>ethereal-setup-x.y.z.exe</filename>. </para> <para> Simply download the Wireshark installer from: - <ulink url="&EtherealBinariesPage;">&EtherealBinariesPage;</ulink> + <ulink url="&WiresharkBinariesPage;">&WiresharkBinariesPage;</ulink> and execute it. </para> <note><title>Note!</title> <para> - <command>Since Ethereal Version 0.10.12, the WinPcap installer has become + <command>Since Wireshark Version 0.10.12, the WinPcap installer has become part of the main Wireshark installer, so you don't need to download and install two separate packages any longer!</command> </para> </note> - <section id="ChBuildInstallEtherealCommandLine"> + <section id="ChBuildInstallWiresharkCommandLine"> <title>Command line options</title> <para> You can simply start the Wireshark installer without any command line @@ -539,7 +539,7 @@ ethereal-setup-0.10.13.exe /NCRC /S /desktopicon=yes /quicklaunchicon=no /D=C:\P </tip> <para> The Components - (both Ethereal GTK1 and 2 cannot be installed at the same time): + (both Wireshark GTK1 and 2 cannot be installed at the same time): <itemizedlist> <listitem><para> <command>Etheral GTK1</command> - Wireshark is a GUI network protocol @@ -602,15 +602,15 @@ ethereal-setup-0.10.13.exe /NCRC /S /desktopicon=yes /quicklaunchicon=no /D=C:\P <command>Start Menu Shortcuts</command> - add some start menu shortcuts. </para></listitem> <listitem><para> - <command>Desktop Icon</command> - add an Ethereal icon to the desktop. + <command>Desktop Icon</command> - add an Wireshark icon to the desktop. </para></listitem> <listitem><para> - <command>Quick Launch Icon</command> - add an Ethereal icon to the + <command>Quick Launch Icon</command> - add an Wireshark icon to the Explorer quick launch toolbar. </para></listitem> <listitem><para> - <command>Associate file extensions to Ethereal</command> - Associate - standard network trace files to Ethereal. + <command>Associate file extensions to Wireshark</command> - Associate + standard network trace files to Wireshark. </para></listitem> </itemizedlist> </para> @@ -638,7 +638,7 @@ ethereal-setup-0.10.13.exe /NCRC /S /desktopicon=yes /quicklaunchicon=no /D=C:\P More WinPcap info: <itemizedlist> <listitem><para> - Ethereal related: + Wireshark related: <ulink url="http://wiki.ethereal.com/WinPcap">http://wiki.ethereal.com/WinPcap</ulink> </para></listitem> <listitem><para> @@ -682,16 +682,16 @@ ethereal-setup-0.10.13.exe /NCRC /S /desktopicon=yes /quicklaunchicon=no /D=C:\P </section> </section> - <section id="ChBuildInstallWinEtherealUpdate"> - <title>Update Ethereal</title> + <section id="ChBuildInstallWinWiresharkUpdate"> + <title>Update Wireshark</title> <para> - From time to time you may want to update your installed Ethereal to a more + From time to time you may want to update your installed Wireshark to a more recent version. If you join Wireshark's announce mailing list, you will be - informed about new Ethereal versions, see <xref + informed about new Wireshark versions, see <xref linkend="ChIntroMailingLists"/> for details how to subscribe to this list. </para> <para> - New versions of Ethereal usually become available every 4-8 weeks. + New versions of Wireshark usually become available every 4-8 weeks. Updating Wireshark is done the same way as installing it, you simply download and start the installer exe. A reboot is usually not required and all your personal settings remain unchanged. @@ -716,10 +716,10 @@ ethereal-setup-0.10.13.exe /NCRC /S /desktopicon=yes /quicklaunchicon=no /D=C:\P </section> <section id="ChBuildInstallWinUninstall"> - <title>Uninstall Ethereal</title> + <title>Uninstall Wireshark</title> <para> - You can uninstall Ethereal the usual way, using the "Add or Remove - Programs" option inside the Control Panel. Select the "Ethereal" entry to + You can uninstall Wireshark the usual way, using the "Add or Remove + Programs" option inside the Control Panel. Select the "Wireshark" entry to start the uninstallation procedure. </para> <para> @@ -728,7 +728,7 @@ ethereal-setup-0.10.13.exe /NCRC /S /desktopicon=yes /quicklaunchicon=no /D=C:\P settings, WinPcap and alike. </para> <para> - WinPcap won't be uninstalled by default, as other programs than Ethereal + WinPcap won't be uninstalled by default, as other programs than Wireshark may use it as well. </para> </section> @@ -736,12 +736,12 @@ ethereal-setup-0.10.13.exe /NCRC /S /desktopicon=yes /quicklaunchicon=no /D=C:\P <section id="ChBuildInstallWinPcapUninstall"> <title>Uninstall WinPcap</title> <para> - You can uninstall WinPcap independantly of Ethereal, using the "WinPcap" + You can uninstall WinPcap independantly of Wireshark, using the "WinPcap" entry in the "Add or Remove Programs" of the Control Panel. </para> <note><title>Note!</title> <para> - After uninstallation of WinPcap you can't capture anything with Ethereal. + After uninstallation of WinPcap you can't capture anything with Wireshark. </para> </note> <para> diff --git a/docbook/wsug_src/WSUG_chapter_capture.xml b/docbook/wsug_src/WSUG_chapter_capture.xml index 23a00c13a7..636fc3fb49 100644 --- a/docbook/wsug_src/WSUG_chapter_capture.xml +++ b/docbook/wsug_src/WSUG_chapter_capture.xml @@ -7,7 +7,7 @@ <section id="ChCapIntroduction"> <title>Introduction</title> <para> - Capturing live network data is one of the major features of Ethereal. + Capturing live network data is one of the major features of Wireshark. </para> <para> The Wireshark capture engine provides the following features: @@ -40,7 +40,7 @@ <itemizedlist> <listitem><para> Simultaneous capturing from multiple network interfaces (however, you - can start multiple instances of Ethereal and merge capture files later). + can start multiple instances of Wireshark and merge capture files later). </para></listitem> <listitem><para> Stop capturing (or doing some other action), depending on the captured @@ -52,7 +52,7 @@ <section id="ChCapPrerequisitesSection"><title>Prerequisites</title> <para> - Setting up Ethereal to capture packets for the first time can be tricky. + Setting up Wireshark to capture packets for the first time can be tricky. </para> <tip><title>Tip!</title><para> A comprehensive guide "How To setup a Capture" is available at: @@ -95,12 +95,12 @@ <section id="ChCapCapturingSection"><title>Start Capturing</title> <para> One of the following methods can be used to start capturing packets with - Ethereal: + Wireshark: <itemizedlist> <listitem> <para> You can get an overview of the available local interfaces using the - "<inlinegraphic entityref="EtherealToolbarCaptureInterfaces" format="PNG"/> + "<inlinegraphic entityref="WiresharkToolbarCaptureInterfaces" format="PNG"/> Capture Interfaces" dialog box, see <xref linkend="ChCapCaptureInterfacesDialog"/>. You can start a capture from this dialog box, using (one of) the "Capture" button(s). @@ -109,7 +109,7 @@ <listitem> <para> You can start capturing using the - "<inlinegraphic entityref="EtherealToolbarCaptureOptions" format="PNG"/> + "<inlinegraphic entityref="WiresharkToolbarCaptureOptions" format="PNG"/> Capture Options" dialog box, see <xref linkend="ChCapCaptureOptionsDialog"/>. </para> @@ -118,7 +118,7 @@ <para> If you have selected the right capture options before, you can immediately start a capture using the - "<inlinegraphic entityref="EtherealToolbarCaptureStart" format="PNG"/> + "<inlinegraphic entityref="WiresharkToolbarCaptureStart" format="PNG"/> Capture Start" menu / toolbar item. The capture process will start immediately. </para> @@ -126,11 +126,11 @@ <listitem> <para> If you already know the name of the capture interface, you can start - Ethereal from the command line and use the following: + Wireshark from the command line and use the following: <programlisting> ethereal -i eth0 -k </programlisting> - This will start Ethereal capturing on interface eth0, more details + This will start Wireshark capturing on interface eth0, more details can be found at: <xref linkend="ChCustCommandLine"/>. </para> </listitem> @@ -141,7 +141,7 @@ ethereal -i eth0 -k <section id="ChCapInterfaceSection"> <title>The "Capture Interfaces" dialog box</title> <para> - When you select "Interfaces..." from the Capture menu, Ethereal pops + When you select "Interfaces..." from the Capture menu, Wireshark pops up the "Capture Interfaces" dialog box as shown in <xref linkend="ChCapCaptureInterfacesDialog"/>. <warning><title>Warning!</title> @@ -153,15 +153,15 @@ ethereal -i eth0 -k </warning> <note><title>Note!</title> <para> - This dialog box will only show the local interfaces Ethereal knows - of. As Ethereal might not be able to detect all local interfaces, and it + This dialog box will only show the local interfaces Wireshark knows + of. As Wireshark might not be able to detect all local interfaces, and it cannot detect the remote interfaces available, there could be more capture interfaces available than listed. </para> </note> <figure id="ChCapCaptureInterfacesDialog"> <title>The "Capture Interfaces" dialog box</title> - <graphic entityref="EtherealCaptureInterfacesDialog" format="PNG"/> + <graphic entityref="WiresharkCaptureInterfacesDialog" format="PNG"/> </figure> <variablelist> <varlistentry><term><command>Description</command></term> @@ -174,7 +174,7 @@ ethereal -i eth0 -k <varlistentry><term><command>IP</command></term> <listitem> <para> - The first IP address Ethereal could resolve from this interface. + The first IP address Wireshark could resolve from this interface. If no address could be resolved (e.g. no DHCP server available), "unknown" will be displayed. If more than one IP address could be resolved, only the first is shown (unpredictable which one in that @@ -237,13 +237,13 @@ ethereal -i eth0 -k <title>The "Capture Options" dialog box</title> <para> When you select Start... from the Capture menu (or use the corresponding - item in the "Main" toolbar), Ethereal pops + item in the "Main" toolbar), Wireshark pops up the "Capture Options" dialog box as shown in <xref linkend="ChCapCaptureOptionsDialog"/>. </para> <figure id="ChCapCaptureOptionsDialog"> <title>The "Capture Options" dialog box</title> - <graphic entityref="EtherealCaptureOptionsDialog" format="JPG"/> + <graphic entityref="WiresharkCaptureOptionsDialog" format="JPG"/> </figure> <tip><title>Tip!</title> <para> @@ -261,7 +261,7 @@ ethereal -i eth0 -k <para> This field specifies the interface you want to capture on. You can only capture on one interface, and you can only - capture on interfaces that Ethereal has found on the + capture on interfaces that Wireshark has found on the system. It is a drop-down list, so simply click on the button on the right hand side and select the interface you want. It defaults to the first non-loopback interface that @@ -313,9 +313,9 @@ ethereal -i eth0 -k </term> <listitem> <para> - This checkbox allows you to specify that Ethereal + This checkbox allows you to specify that Wireshark should put the interface in promiscuous mode when capturing. - If you do not specify this, Ethereal will only capture the + If you do not specify this, Wireshark will only capture the packets going to or from your computer (not all packets on your LAN segment). </para> @@ -331,7 +331,7 @@ ethereal -i eth0 -k <title>Note</title> <para> Even in promiscuous mode you still won't necessarily see all packets - on your LAN segment, see <ulink url="&EtherealFAQPromiscPage;"/> for + on your LAN segment, see <ulink url="&WiresharkFAQPromiscPage;"/> for some more explanations. </para> </note> @@ -381,7 +381,7 @@ ethereal -i eth0 -k no filter. </para> <para> - You can also click on the button labelled Capture Filter, and Ethereal + You can also click on the button labelled Capture Filter, and Wireshark will bring up the Capture Filters dialog box and allow you to create and/or select a filter. Please see <xref linkend="ChWorkDefineFilterSection"/> @@ -414,7 +414,7 @@ ethereal -i eth0 -k <varlistentry><term><command>Use multiple files</command></term> <listitem> <para> - Instead of using a single file, Ethereal will automatically switch + Instead of using a single file, Wireshark will automatically switch to a new one, if a specific trigger condition is reached. </para> </listitem> @@ -491,11 +491,11 @@ ethereal -i eth0 -k </term> <listitem> <para> - This option allows you to specify that Ethereal + This option allows you to specify that Wireshark should update the packet list pane in real time. If you - do not specify this, Ethereal does not display any + do not specify this, Wireshark does not display any packets until you stop the capture. When you check this, - Ethereal captures in a separate process + Wireshark captures in a separate process and feeds the captures to the display process. </para> </listitem> @@ -506,10 +506,10 @@ ethereal -i eth0 -k </term> <listitem> <para> - This option allows you to specify that Ethereal + This option allows you to specify that Wireshark should scroll the packet list pane as new packets come in, so you are always looking at the last packet. If you - do not specify this, Ethereal simply adds new packets onto + do not specify this, Wireshark simply adds new packets onto the end of the list, but does not scroll the packet list pane. This option is greyed out if "Update list of packets in real time" is disabled. @@ -536,7 +536,7 @@ ethereal -i eth0 -k <listitem> <para> This option allows you to control whether or not - Ethereal translates MAC addresses into names, see + Wireshark translates MAC addresses into names, see <xref linkend="ChAdvNameResolutionSection"/>. </para> </listitem> @@ -546,7 +546,7 @@ ethereal -i eth0 -k <listitem> <para> This option allows you to control whether or not - Ethereal translates network addresses into names, see + Wireshark translates network addresses into names, see <xref linkend="ChAdvNameResolutionSection"/>. </para> </listitem> @@ -556,7 +556,7 @@ ethereal -i eth0 -k <listitem> <para> This option allows you to control whether or not - Ethereal translates transport addresses into protocols, see + Wireshark translates transport addresses into protocols, see <xref linkend="ChAdvNameResolutionSection"/>. </para> </listitem> @@ -570,7 +570,7 @@ ethereal -i eth0 -k capture, or <command>Cancel</command> to cancel the capture. </para> <para> - If you start a capture, Ethereal allows you to stop capturing when + If you start a capture, Wireshark allows you to stop capturing when you have enough packets captured, for details see <xref linkend="ChCapRunningSection"/>. </para> @@ -602,7 +602,7 @@ ethereal -i eth0 -k <note><title>Note!</title> <para> Using Multiple files may cut context related information. - Ethereal keeps context information of the loaded packet data, so it can + Wireshark keeps context information of the loaded packet data, so it can report context related problems (like a stream error) and keeps information about context related protocols (e.g. where data is exchanged at the establishing phase and only referred to in later packets). @@ -753,7 +753,7 @@ ethereal -i eth0 -k <section id="ChCapCaptureFilterSection"><title>Filtering while capturing</title> <para> - Ethereal uses the libpcap filter language for capture filters. + Wireshark uses the libpcap filter language for capture filters. This is explained in the tcpdump man page, which can be hard to understand, so it's explained here to some extent. </para> @@ -761,7 +761,7 @@ ethereal -i eth0 -k <title>Tip!</title> <para> You will find a lot of Capture Filter examples at <ulink - url="&EtherealWikiCaptureFiltersPage;">&EtherealWikiCaptureFiltersPage;</ulink>. + url="&WiresharkWikiCaptureFiltersPage;">&WiresharkWikiCaptureFiltersPage;</ulink>. </para> </tip> <para> @@ -945,7 +945,7 @@ tcp port 23 and not host 10.0.0.5 While a capture is running, the following dialog box is shown: <figure id="ChCapCaptureInfoDialog"> <title>The "Capture Info" dialog box</title> - <graphic entityref="EtherealCaptureInfoDialog" format="JPG"/> + <graphic entityref="WiresharkCaptureInfoDialog" format="JPG"/> </figure> This dialog box will inform you about the number of captured packets and the time since the capture was started. The selection which protocols @@ -963,7 +963,7 @@ tcp port 23 and not host 10.0.0.5 <orderedlist> <listitem> <para>Using the - "<inlinegraphic entityref="EtherealToolbarStop" format="PNG"/> + "<inlinegraphic entityref="WiresharkToolbarStop" format="PNG"/> Stop" button from the <command>Capture Info dialog box </command>. </para> @@ -976,13 +976,13 @@ tcp port 23 and not host 10.0.0.5 </listitem> <listitem> <para>Using the <command>menu item</command> - "Capture/<inlinegraphic entityref="EtherealToolbarCaptureStop" format="PNG"/> + "Capture/<inlinegraphic entityref="WiresharkToolbarCaptureStop" format="PNG"/> Stop". </para> </listitem> <listitem> <para>Using the <command>toolbar item</command> - "<inlinegraphic entityref="EtherealToolbarCaptureStop" format="PNG"/> + "<inlinegraphic entityref="WiresharkToolbarCaptureStop" format="PNG"/> Stop". </para> </listitem> @@ -1013,13 +1013,13 @@ tcp port 23 and not host 10.0.0.5 <orderedlist> <listitem> <para>Using the <command>menu item</command> - "Capture/<inlinegraphic entityref="EtherealToolbarCaptureRestart" format="PNG"/> + "Capture/<inlinegraphic entityref="WiresharkToolbarCaptureRestart" format="PNG"/> Restart". </para> </listitem> <listitem> <para>Using the <command>toolbar item</command> - "<inlinegraphic entityref="EtherealToolbarCaptureRestart" format="PNG"/> + "<inlinegraphic entityref="WiresharkToolbarCaptureRestart" format="PNG"/> Restart". </para> </listitem> diff --git a/docbook/wsug_src/WSUG_chapter_customize.xml b/docbook/wsug_src/WSUG_chapter_customize.xml index f56a5f3702..f97821be7a 100644 --- a/docbook/wsug_src/WSUG_chapter_customize.xml +++ b/docbook/wsug_src/WSUG_chapter_customize.xml @@ -2,17 +2,17 @@ <!-- $Id$ --> <chapter id="ChapterCustomize"> - <title>Customizing Ethereal</title> + <title>Customizing Wireshark</title> <section id="ChCustIntroduction"><title>Introduction</title> <para> - Ethereal's default behaviour will usually suit your needs pretty well. - However, as you become more familiar with Ethereal, it can be customized + Wireshark's default behaviour will usually suit your needs pretty well. + However, as you become more familiar with Wireshark, it can be customized in various ways to suit your needs even better. In this chapter we explore: <itemizedlist> <listitem> <para> - How to start Ethereal with command line parameters + How to start Wireshark with command line parameters </para> </listitem> <listitem> @@ -34,21 +34,21 @@ </para> </section> - <section id="ChCustCommandLine"><title>Start Ethereal from the command line</title> + <section id="ChCustCommandLine"><title>Start Wireshark from the command line</title> <para> - You can start <application>Ethereal</application> from the command + You can start <application>Wireshark</application> from the command line, but it can also be started from most Window managers as well. In this section we will look at starting it from the command line. </para> <para> - <application>Ethereal</application> supports a large number of + <application>Wireshark</application> supports a large number of command line parameters. To see what they are, simply enter the command <command> ethereal -h</command> and the help information shown in <xref linkend="ChCustEx1"/> (or something similar) should be printed. <example id="ChCustEx1"> - <title>Help information available from Ethereal</title> + <title>Help information available from Wireshark</title> <programlisting> This is ethereal 0.10.13 (C) 1998-2005 Gerald Combs <gerald@wireshark.org> @@ -75,7 +75,7 @@ ethereal [ -vh ] [ -DklLnpQS ] [ -a <capture autostop condition> ] ... <para> The first thing to notice is that issuing the command <command>ethereal</command> by itself will bring up - <application>Ethereal</application>. + <application>Wireshark</application>. However, you can include as many of the command line parameters as you like. Their meanings are as follows ( in alphabetical order ): XXX - is the alphabetical order a good choice? Maybe better task based? @@ -96,7 +96,7 @@ ethereal [ -vh ] [ -DklLnpQS ] [ -a <capture autostop condition> ] ... <listitem><para> Stop writing to a capture file after it reaches a size of value kilobytes (where a kilobyte is 1000 bytes, not 1024 bytes). If - this option is used together with the -b option, Ethereal will + this option is used together with the -b option, Wireshark will stop writing to the current capture file and switch to the next one if filesize is reached. </para></listitem> @@ -114,21 +114,21 @@ ethereal [ -vh ] [ -DklLnpQS ] [ -a <capture autostop condition> ] ... <varlistentry><term><command>-b <capture ring buffer option></command></term> <listitem> <para> - If a maximum capture file size was specified, cause Ethereal to run + If a maximum capture file size was specified, cause Wireshark to run in "ring buffer" mode, with the specified number of files. In "ring - buffer" mode, Ethereal will write to several capture files. Their + buffer" mode, Wireshark will write to several capture files. Their name is based on the number of the file and on the creation date and time. </para> <para> - When the first capture file fills up, Ethereal will switch to writing + When the first capture file fills up, Wireshark will switch to writing to the next file, until it fills up the last file, at which point it'll discard the data in the first file (unless 0 is specified, in which case, the number of files is unlimited) and start writing to that file and so on. </para> <para> - If the optional duration is specified, Ethereal will switch also to + If the optional duration is specified, Wireshark will switch also to the next file when the specified number of seconds has elapsed even if the current file is not completely fills up. </para> @@ -178,7 +178,7 @@ ethereal [ -vh ] [ -DklLnpQS ] [ -a <capture autostop condition> ] ... <varlistentry><term><command>-D</command></term> <listitem> <para> -Print a list of the interfaces on which Ethereal can capture, and +Print a list of the interfaces on which Wireshark can capture, and exit. For each network interface, a number and an interface name, possibly followed by a text description of the interface, is printed. The interface name or the number can be supplied @@ -191,7 +191,7 @@ the number can be useful on Windows 2000 and later systems, where the interface name is a somewhat complex string. </para> <para> -Note that "can capture" means that Ethereal was able to open +Note that "can capture" means that Wireshark was able to open that device to do a live capture; if, on your system, a program doing a network capture must be run from an account with special privileges (for example, as root), then, if Wireshark is run with the <command>-D</command> flag and @@ -218,7 +218,7 @@ is not run from such an account, it will not list any interfaces. <varlistentry><term><command>-h</command></term> <listitem> <para> - The <command>-h</command> option requests Ethereal to print + The <command>-h</command> option requests Wireshark to print its version and usage instructions (as shown above) and exit. </para> </listitem> @@ -237,11 +237,11 @@ Network interface names should match one of the names listed in although not all versions of UNIX support the <command>-a</command> flag to <command>ifconfig</command>. </para> <para> -If no interface is specified, Ethereal searches the list of +If no interface is specified, Wireshark searches the list of interfaces, choosing the first non-loopback interface if there are any non-loopback interfaces, and choosing the first loopback interface if there are no non-loopback interfaces; if there are no interfaces, -Ethereal reports an error and doesn't start the capture. +Wireshark reports an error and doesn't start the capture. </para> <para> Pipe names should be either the name of a FIFO (named pipe) or ``-'' to @@ -253,7 +253,7 @@ standard libpcap format. <varlistentry><term><command>-k</command></term> <listitem> <para> - The <command>-k</command> option specifies that Ethereal + The <command>-k</command> option specifies that Wireshark should start capturing packets immediately. This option requires the use of the <command>-i</command> parameter to specify the interface that packet capture will occur from. @@ -357,7 +357,7 @@ standard libpcap format. <varlistentry><term><command>-Q</command></term> <listitem> <para> - This option forces Ethereal to exit when capturing is + This option forces Wireshark to exit when capturing is complete. It can be used with the <command>-c</command> option. It must be used in conjunction with the <command>-i</command> and <command>-w</command> options. @@ -369,7 +369,7 @@ standard libpcap format. <para> This option provides the name of a capture file for Wireshark to read and display. This capture file can be in one of the - formats Ethereal understands. + formats Wireshark understands. </para> </listitem> </varlistentry> @@ -388,7 +388,7 @@ standard libpcap format. <listitem> <para> This option specifies the snapshot length to use when - capturing packets. Ethereal will only capture + capturing packets. Wireshark will only capture <command><snaplen></command> bytes of data for each packet. </para> </listitem> @@ -396,7 +396,7 @@ standard libpcap format. <varlistentry><term><command>-S</command></term> <listitem> <para> - This option specifies that Ethereal will display packets as + This option specifies that Wireshark will display packets as it captures them. This is done by capturing in one process and displaying them in a separate process. This is the same as "Update list of packets in real time" in the Capture Options @@ -443,7 +443,7 @@ standard libpcap format. <listitem> <para> The <command>-v</command> option requests - Ethereal to print out its version information and exit. + Wireshark to print out its version information and exit. </para> </listitem> </varlistentry> @@ -472,14 +472,14 @@ standard libpcap format. be: </para> <para> - <command>lua_script</command>:lua_script_filename Tell Ethereal to load the given script in addition to the default Lua scripts. + <command>lua_script</command>:lua_script_filename Tell Wireshark to load the given script in addition to the default Lua scripts. </para> </listitem> </varlistentry> <varlistentry><term><command>-z <statistics-string></command></term> <listitem> <para> - Get Ethereal to collect various types of statistics and display the + Get Wireshark to collect various types of statistics and display the result in a window that updates in semi-real time. XXX - add more details here! </para> @@ -492,26 +492,26 @@ standard libpcap format. <section id="ChCustColorizationSection"><title>Packet colorization</title> <para> A very useful mechanism available in Wireshark is packet colorization. - You can set-up Ethereal so that it will colorize packets according to a + You can set-up Wireshark so that it will colorize packets according to a filter. This allows you to emphasize the packets you are usually interested in. </para> <tip> <title>Tip!</title> <para> - You will find a lot of Coloring Rule examples at the <command>Ethereal + You will find a lot of Coloring Rule examples at the <command>Wireshark Wiki Coloring Rules page</command> at <ulink - url="&EtherealWikiColoringRulesPage;">&EtherealWikiColoringRulesPage;</ulink>. + url="&WiresharkWikiColoringRulesPage;">&WiresharkWikiColoringRulesPage;</ulink>. </para> </tip> <para> To colorize packets, select the Coloring Rules... menu item from - the View menu, Ethereal will pop up the "Coloring Rules" + the View menu, Wireshark will pop up the "Coloring Rules" dialog box as shown in <xref linkend="ChCustColoringRulesDialog"/>. </para> <figure id="ChCustColoringRulesDialog"> <title>The "Coloring Rules" dialog box</title> - <graphic entityref="EtherealColoringRulesDialog" format="PNG"/> + <graphic entityref="WiresharkColoringRulesDialog" format="PNG"/> </figure> <para> Once the Coloring Rules dialog box is up, there are a number @@ -535,7 +535,7 @@ standard libpcap format. </para> <figure id="ChCustEditColorDialog"> <title>The "Edit Color Filter" dialog box</title> - <graphic entityref="EtherealEditColorDialog" format="PNG"/> + <graphic entityref="WiresharkEditColorDialog" format="PNG"/> </figure> <para> In the Edit Color dialog box, simply enter a name for the color filter, @@ -548,13 +548,13 @@ standard libpcap format. color for packets that match the filter expression. Click on <command>Foreground color...</command> or <command>Background color...</command> to achieve this and - Ethereal will pop up the Choose foreground/background color for + Wireshark will pop up the Choose foreground/background color for protocol dialog box as shown in <xref linkend="ChCustChooseColorDialog"/>. </para> <figure id="ChCustChooseColorDialog"> <title>The "Choose color" dialog box</title> - <graphic entityref="EtherealChooseColorDialog" format="PNG"/> + <graphic entityref="WiresharkChooseColorDialog" format="PNG"/> </figure> <para> Select the color you desire for the selected packets and click on OK. @@ -573,8 +573,8 @@ standard libpcap format. however, feel free to choose your own. </para> <figure id="ChCustColorFilterMany"> - <title>Using color filters with Ethereal</title> - <graphic entityref="EtherealThreePane1" format="PNG"/> + <title>Using color filters with Wireshark</title> + <graphic entityref="WiresharkThreePane1" format="PNG"/> </figure> </section> @@ -585,24 +585,24 @@ standard libpcap format. </para> <para> Each protocol has its own dissector, so dissecting a complete packet will - typically involve several dissectors. As Ethereal tries to find the + typically involve several dissectors. As Wireshark tries to find the right dissector for each packet (using static "routes" and heuristics "guessing"), it might choose the wrong dissector in your specific - case. For example, Ethereal won't know if you use a common protocol + case. For example, Wireshark won't know if you use a common protocol on an uncommon TCP port, e.g. using HTTP on TCP port 800 instead of the standard port 80. </para> <para> There are two ways to control the relations between protocol dissectors: disable a protocol dissector completely or temporarily - divert the way Ethereal calls the dissectors. + divert the way Wireshark calls the dissectors. </para> <section id="ChAdvEnabledProtocols"><title>The "Enabled Protocols" dialog box</title> <para> The Enabled Protocols dialog box lets you enable or disable specific protocols, all protocols are enabled by default. - When a protocol is disabled, Ethereal stops processing a packet + When a protocol is disabled, Wireshark stops processing a packet whenever that protocol is encountered. </para> <note><title>Note!</title> @@ -619,7 +619,7 @@ standard libpcap format. </note> <figure id="ChAdvEnabledProtocolsFig"> <title>The "Enabled Protocols" dialog box</title> - <graphic entityref="EtherealEnabledProtocols" format="PNG"/> + <graphic entityref="WiresharkEnabledProtocols" format="PNG"/> </figure> <para> To disable or enable a protocol, simply click on it using the @@ -686,13 +686,13 @@ standard libpcap format. <para> <figure id="ChAdvDecodeAsFig"> <title>The "Decode As" dialog box</title> - <graphic scale="100" entityref="EtherealDecodeAs" format="PNG"/> + <graphic scale="100" entityref="WiresharkDecodeAs" format="PNG"/> </figure> The content of this dialog box depends on the selected packet when it was opened. <warning><title>Warning!</title> <para> - The user specified decodes can not be saved. If you quit Ethereal, + The user specified decodes can not be saved. If you quit Wireshark, these settings will be lost. </para> </warning> @@ -748,7 +748,7 @@ standard libpcap format. This dialog box shows the currently active user specified decodes. <figure id="ChAdvDecodeAsShowFig"> <title>The "Decode As: Show" dialog box</title> - <graphic entityref="EtherealDecodeAsShow" format="PNG"/> + <graphic entityref="WiresharkDecodeAsShow" format="PNG"/> </figure> <orderedlist> <listitem> @@ -769,7 +769,7 @@ standard libpcap format. <section id="ChCustPreferencesSection"><title>Preferences</title> <para> There are a number of preferences you can set. Simply - select the Preferences... menu item from the Edit menu, and Ethereal + select the Preferences... menu item from the Edit menu, and Wireshark will pop up the Preferences dialog box as shown in <xref linkend="ChCustGUIPrefPage"/>, with the "User Interface" page as default. On the left side is a tree where you can select the page to be @@ -778,8 +778,8 @@ standard libpcap format. <para> Preference settings are added frequently. For a recent explanation of the preference pages and their settings have a look at the - <command>Ethereal Wiki Preferences page</command> at <ulink - url="&EtherealWikiPreferencesPage;">&EtherealWikiPreferencesPage;</ulink>. + <command>Wireshark Wiki Preferences page</command> at <ulink + url="&WiresharkWikiPreferencesPage;">&WiresharkWikiPreferencesPage;</ulink>. </para> </note> <warning> @@ -818,7 +818,7 @@ standard libpcap format. </para> <figure id="ChCustGUIPrefPage"> <title>The preferences dialog box</title> - <graphic entityref="EtherealGUIPreferences" format="PNG"/> + <graphic entityref="WiresharkGUIPreferences" format="PNG"/> </figure> </section> diff --git a/docbook/wsug_src/WSUG_chapter_introduction.xml b/docbook/wsug_src/WSUG_chapter_introduction.xml index 5edaf7358c..e55c4480f8 100644 --- a/docbook/wsug_src/WSUG_chapter_introduction.xml +++ b/docbook/wsug_src/WSUG_chapter_introduction.xml @@ -5,7 +5,7 @@ <title>Introduction</title> <!-- Introduction --> <section id="ChIntroWhatIs"> - <title>What is <application>Ethereal?</application></title> + <title>What is <application>Wireshark?</application></title> <para> Wireshark is a network packet analyzer. A network packet analyzer will try to capture network packets and tries to display @@ -19,16 +19,16 @@ </para> <para> In the past, such tools were either very expensive, proprietary, or both. - However, with the advent of Ethereal, all that has changed. + However, with the advent of Wireshark, all that has changed. </para> <para> - <application>Ethereal</application> is perhaps one of the best open + <application>Wireshark</application> is perhaps one of the best open source packet analyzers available today. </para> <section id="ChIntroPurposes"><title>Some intended purposes</title> <para> - Here are some examples people use Ethereal for: + Here are some examples people use Wireshark for: <itemizedlist> <listitem><para> network administrators use it to <command>troubleshoot network @@ -46,14 +46,14 @@ internals </para></listitem> </itemizedlist> - Beside these examples, Ethereal can be helpful in many other situations + Beside these examples, Wireshark can be helpful in many other situations too. </para> </section> <section id="ChIntroFeatures"><title>Features</title> <para> - The following are some of the many features Ethereal provides: + The following are some of the many features Wireshark provides: <itemizedlist> <listitem> <para>Available for <command>UNIX</command> and <command>Windows</command>.</para> @@ -98,15 +98,15 @@ However, to really appreciate its power, you have to start using it. </para> <para> - <xref linkend="ChIntroFig1"/> shows <application>Ethereal</application> + <xref linkend="ChIntroFig1"/> shows <application>Wireshark</application> having captured some packets and waiting for you to examine them. <figure id="ChIntroFig1"> <title> - <application>Ethereal</application> captures packets and allows + <application>Wireshark</application> captures packets and allows you to examine their content. </title> - <graphic entityref="EtherealMain1" format="PNG"/> + <graphic entityref="WiresharkMain1" format="PNG"/> </figure> </para> </section> @@ -114,24 +114,24 @@ <section> <title>Live capture from many different network media</title> <para> - Despite its name, Ethereal can capture traffic from + Despite its name, Wireshark can capture traffic from network media other than Ethernet. Which media types are supported, depends on many things like the operating system you are using. An overview of the supported media types can be found at: - <ulink url="&EtherealMediaPage;"/>. + <ulink url="&WiresharkMediaPage;"/>. </para> </section> <section><title>Import files from many other capture programs</title> <para> - Ethereal can open packets captured from a large number of + Wireshark can open packets captured from a large number of other capture programs. For a list of input formats see <xref linkend="ChIOInputFormatsSection"/>. </para> </section> <section><title>Export files for many other capture programs</title> <para> - Ethereal can save packets captured in a large number of formats of + Wireshark can save packets captured in a large number of formats of other capture programs. For a list of output formats see <xref linkend="ChIOOutputFormatsSection"/>. </para> @@ -150,27 +150,27 @@ <para> Wireshark is an open source software project, and is released under the <ulink url="&GPLWebsite;">GNU General Public Licence</ulink> (GPL). - You can freely use Ethereal on any number of computers you like, without + You can freely use Wireshark on any number of computers you like, without worrying about license keys or fees or such. In addition, all source code is freely available under the GPL. Because of that, it is very easy - for people to add new protocols to Ethereal, either as plugins, or built + for people to add new protocols to Wireshark, either as plugins, or built into the source, and they often do! </para> </section> <section id="ChIntroNoFeatures"><title>What Wireshark is not</title> <para> - Here are some things Ethereal does not provide: + Here are some things Wireshark does not provide: <itemizedlist> <listitem><para> - Ethereal isn't an intrusion detection system. It will not warn you when + Wireshark isn't an intrusion detection system. It will not warn you when someone does strange things on your network that he/she isn't allowed to - do. However, if strange things happen, Ethereal might help you figure + do. However, if strange things happen, Wireshark might help you figure out what is really going on. </para></listitem> <listitem><para> - Ethereal will not manipulate things on the network, it will only - "measure" things from it. Ethereal doesn't send packets on the network + Wireshark will not manipulate things on the network, it will only + "measure" things from it. Wireshark doesn't send packets on the network or do other active things (except for name resolutions, but even that can be disabled). </para></listitem> @@ -180,16 +180,16 @@ </section> <section id="ChIntroPlatforms"> - <title>Platforms Ethereal runs on</title> + <title>Platforms Wireshark runs on</title> <para> - Ethereal currently runs on most UNIX platforms and various Windows + Wireshark currently runs on most UNIX platforms and various Windows platforms. It requires GTK+, GLib, libpcap and some other libraries in order to run. </para> <para> If a binary package is not available for your platform, you should download the source and try to build it. Please report your experiences - to <ulink url="mailto:&EtherealDevMailList;">&EtherealDevMailList;</ulink>. + to <ulink url="mailto:&WiresharkDevMailList;">&WiresharkDevMailList;</ulink>. </para> <para> Binary packages are available for at least the following platforms: @@ -254,25 +254,25 @@ <listitem><para>Windows Vista (aka Longhorn)</para></listitem> </itemizedlist> Please provide your experiences about these fresh versions to: - <ulink url="mailto:&EtherealDevMailList;">&EtherealDevMailList;</ulink>. + <ulink url="mailto:&WiresharkDevMailList;">&WiresharkDevMailList;</ulink>. </para> </section> </section> <section id="ChIntroDownload"> - <title>Where to get Ethereal?</title> + <title>Where to get Wireshark?</title> <para> You can get the latest copy of the program from the Wireshark website: - <ulink url="&EtherealDownloadPage;">&EtherealDownloadPage;</ulink>. The + <ulink url="&WiresharkDownloadPage;">&WiresharkDownloadPage;</ulink>. The website allows you to choose from among several mirrors for downloading. </para> <para> - A new Ethereal version will typically become available every 4-8 weeks. + A new Wireshark version will typically become available every 4-8 weeks. </para> <para> - If you want to be notified about new Ethereal releases, you should + If you want to be notified about new Wireshark releases, you should subscribe to the ethereal-announce mailing list. You will find more details in <xref linkend="ChIntroMailingLists"/>. </para> @@ -285,7 +285,7 @@ <emphasis> "A rose by any other name would smell as sweet." </emphasis> - And so it is with Ethereal, as there appears to be two different + And so it is with Wireshark, as there appears to be two different ways that people pronounce the name. </para> <para> @@ -299,16 +299,16 @@ </section> <section id="ChIntroHistory"> - <title>A brief history of Ethereal</title> + <title>A brief history of Wireshark</title> <para> In late 1997, Gerald Combs needed a tool for tracking down networking problems and wanted to learn more about networking, so - he started writing Ethereal as a way to solve both problems. + he started writing Wireshark as a way to solve both problems. </para> <para> - Ethereal was initially released, after several pauses in development, + Wireshark was initially released, after several pauses in development, in July 1998 as version 0.2.0. Within days, patches, bug reports, - and words of encouragement started arriving, so Ethereal was on its + and words of encouragement started arriving, so Wireshark was on its way to success. </para> <para> @@ -318,7 +318,7 @@ <para> In October, 1998, Guy Harris of Network Appliance was looking for something better than tcpview, so he started applying patches and - contributing dissectors to Ethereal. + contributing dissectors to Wireshark. </para> <para> In late 1998, Richard Sharpe, who was giving TCP/IP courses, saw its @@ -328,35 +328,35 @@ dissectors and contributing patches. </para> <para> - The list of people who have contributed to Ethereal has become very long + The list of people who have contributed to Wireshark has become very long since then, and almost all of them started with a protocol that they - needed that Ethereal did not already handle. So they copied an existing + needed that Wireshark did not already handle. So they copied an existing dissector and contributed the code back to the team. </para> </section> <section id="ChIntroMaintenance"> <title> - Development and maintenance of <application>Ethereal</application> + Development and maintenance of <application>Wireshark</application> </title> <para> - Ethereal was initially developed by Gerald Combs. Ongoing development + Wireshark was initially developed by Gerald Combs. Ongoing development and maintenance of Wireshark is handled by the Wireshark team, a loose group of individuals who fix bugs and provide new functionality. </para> <para> There have also been a large number of people who have contributed - protocol dissectors to Ethereal, and it is expected that this will + protocol dissectors to Wireshark, and it is expected that this will continue. You can find a list of the people who have contributed - code to Ethereal by checking the about dialog box of Ethereal, or at - the <ulink url="&EtherealAuthorsPage;">authors</ulink> page on the - Ethereal web site. + code to Wireshark by checking the about dialog box of Wireshark, or at + the <ulink url="&WiresharkAuthorsPage;">authors</ulink> page on the + Wireshark web site. </para> <para> Wireshark is an open source software project, and is released under the <ulink url="&GPLWebsite;">GNU General Public Licence</ulink> (GPL). All source code is freely available under the GPL. You are welcome to - modify Ethereal to suit your own needs, and it would be appreciated + modify Wireshark to suit your own needs, and it would be appreciated if you contribute your improvements back to the Wireshark team. </para> <para> @@ -367,12 +367,12 @@ <para> Other people who find your contributions useful will appreciate them, and you will know that you have helped people in the - same way that the developers of Ethereal have helped people. + same way that the developers of Wireshark have helped people. </para> </listitem> <listitem> <para> - The developers of Ethereal might improve your changes even more, + The developers of Wireshark might improve your changes even more, as there's always room for improvements. Or they may implement some advanced things on top of your code, which can be useful for yourself too. @@ -380,11 +380,11 @@ </listitem> <listitem> <para> - The maintainers and developers of Ethereal will maintain your + The maintainers and developers of Wireshark will maintain your code as well, fixing it when API changes or other changes are made, and generally keeping it in tune with what is happening - with Ethereal. So if Wireshark is updated (which is done often), - you can get a new Ethereal version from the website and your changes + with Wireshark. So if Wireshark is updated (which is done often), + you can get a new Wireshark version from the website and your changes will already be included without any effort for you. </para> </listitem> @@ -393,14 +393,14 @@ <para> The Wireshark source code and binary kits for some platforms are all available on the download page of the Wireshark website: - <ulink url="&EtherealDownloadPage;">&EtherealDownloadPage;</ulink>. + <ulink url="&WiresharkDownloadPage;">&WiresharkDownloadPage;</ulink>. </para> </section> <section id="ChIntroHelp"> <title>Reporting problems and getting help</title> <para> - If you have problems, or need help with Ethereal, there are several + 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). </para> @@ -408,15 +408,15 @@ <section id="ChIntroHomepage"><title>Website</title> <para> You will find lot's of useful information on the Wireshark homepage at - <ulink url="&EtherealWebSite;">&EtherealWebSite;</ulink>. + <ulink url="&WiresharkWebSite;">&WiresharkWebSite;</ulink>. </para> </section> <section id="ChIntroWiki"><title>Wiki</title> <para> The Wireshark Wiki at <ulink - url="&EtherealWikiPage;">&EtherealWikiPage;</ulink> provides a wide range - of information related to Ethereal and packet capturing in general. + url="&WiresharkWikiPage;">&WiresharkWikiPage;</ulink> 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 user'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. @@ -440,12 +440,12 @@ subscribed to the mailing lists). </para> </note> - You will find the FAQ inside Ethereal by clicking the menu item + You will find the FAQ inside Wireshark by clicking the menu item Help/Contents and selecting the FAQ page in the upcoming dialog. </para> <para> An online version is available at the ethereal website: - <ulink url="&EtherealFAQPage;">&EtherealFAQPage;</ulink>. You might + <ulink url="&WiresharkFAQPage;">&WiresharkFAQPage;</ulink>. You might prefer this online version, as it's typically more up to date and the HTML format is easier to use. </para> @@ -453,7 +453,7 @@ <section id="ChIntroMailingLists"><title>Mailing Lists</title> <para> - There are several mailing lists of specific Ethereal topics available: + There are several mailing lists of specific Wireshark topics available: <variablelist> <varlistentry><term><command>ethereal-announce</command></term> <listitem> @@ -466,8 +466,8 @@ <varlistentry><term><command>ethereal-users</command></term> <listitem> <para> - This list is for users of Ethereal. People post - questions about building and using Ethereal, others (hopefully) + This list is for users of Wireshark. People post + questions about building and using Wireshark, others (hopefully) provide answers. </para> </listitem> @@ -482,7 +482,7 @@ </varlistentry> </variablelist> You can subscribe to each of these lists from the Wireshark web site: - <ulink url="&EtherealWebSite;">&EtherealWebSite;</ulink>. Simply + <ulink url="&WiresharkWebSite;">&WiresharkWebSite;</ulink>. Simply select the <command>mailing lists</command> link on the left hand side of the site. The lists are archived at the Wireshark web site as well. @@ -500,23 +500,23 @@ <note><title>Note!</title> <para> Before reporting any problems, please make sure you have installed the - latest version of Ethereal. + latest version of Wireshark. </para> </note> <para> - When reporting problems with Ethereal, it is helpful if you supply the + When reporting problems with Wireshark, it is helpful if you supply the following information: <orderedlist> <listitem> <para> - The version number of Ethereal and the dependent libraries linked with + The version number of Wireshark and the dependent libraries linked with it, eg GTK+, etc. You can obtain this with the command <command>ethereal -v</command>. </para> </listitem> <listitem> <para> - Information about the platform you run Ethereal on. + Information about the platform you run Wireshark on. </para> </listitem> <listitem> @@ -554,7 +554,7 @@ <section><title>Reporting Crashes on UNIX/Linux platforms</title> <para> - When reporting crashes with Ethereal, it is helpful if you supply the + When reporting crashes with Wireshark, it is helpful if you supply the traceback information (besides the information mentioned in "Reporting Problems"). </para> @@ -595,7 +595,7 @@ $ </para> <para> You should mail the traceback to the - <ulink url="mailto:&EtherealDevMailList;">&EtherealDevMailList;</ulink> + <ulink url="mailto:&WiresharkDevMailList;">&WiresharkDevMailList;</ulink> mailing list. </para> </section> diff --git a/docbook/wsug_src/WSUG_chapter_io.xml b/docbook/wsug_src/WSUG_chapter_io.xml index 05e7fdffdc..e7475cd004 100644 --- a/docbook/wsug_src/WSUG_chapter_io.xml +++ b/docbook/wsug_src/WSUG_chapter_io.xml @@ -34,18 +34,18 @@ <section id="ChIOOpenSection"><title>Open capture files</title> <para> - Ethereal can read in previously saved capture files. + Wireshark can read in previously saved capture files. To read them, simply select the menu or toolbar item: "File/ - <inlinegraphic entityref="EtherealToolbarOpen" format="PNG"/> + <inlinegraphic entityref="WiresharkToolbarOpen" format="PNG"/> <command>Open</command>". - Ethereal will then pop up the File + Wireshark will then pop up the File Open dialog box, which is discussed in more detail in <xref linkend="ChIOOpen"/>. </para> <note><title>Note!</title> <para> You can also use <command>drag-and-drop </command> to open a file, by - simply dropping the desired file from your file manager onto Ethereal's + simply dropping the desired file from your file manager onto Wireshark's main window. However, drag-and-drop is not available/won't work in all desktop environments. </para> @@ -57,33 +57,33 @@ </para> <para> In addition to its native file format (libpcap format, also used by - tcpdump/WinDump and other libpcap/WinPcap-based programs), Ethereal can + tcpdump/WinDump and other libpcap/WinPcap-based programs), Wireshark can read capture files from a large number of other packet capture programs as well. See <xref linkend="ChIOInputFormatsSection"/> for the list of - capture formats Ethereal understands. + capture formats Wireshark understands. </para> <section id="ChIOOpen"><title>The "Open Capture File" dialog box</title> <para> The "Open Capture File" dialog box allows you to search for a capture file containing previously captured packets for display in - Ethereal. <xref linkend="ChIOOpenFileDialog"/> shows an example + Wireshark. <xref linkend="ChIOOpenFileDialog"/> shows an example of the Wireshark Open File Dialog box. </para> <note> <title>Note</title> <para> - Ethereal uses the open dialog box from the version of the GTK+ + Wireshark uses the open dialog box from the version of the GTK+ toolkit that it's using. This dialog was completely redesigned in GTK version 2.4. Depending on the installed GTK version, your dialog box might look different. However, as the functionality remains almost the same, much of this description - will work with your version of Ethereal. + will work with your version of Wireshark. </para> </note> <figure id="ChIOOpenFileDialog"> <title>The "Open Capture File" Dialog box</title> - <graphic entityref="EtherealOpen" format="PNG"/> + <graphic entityref="WiresharkOpen" format="PNG"/> </figure> <para> With this dialog box, you can perform the following actions: @@ -117,7 +117,7 @@ <para> Specify a display filter with the Filter button and filter field. This filter will be used when opening the new file. - Clicking on the Filter button causes Ethereal to pop up + Clicking on the Filter button causes Wireshark to pop up the Filters dialog box (which is discussed further in <xref linkend="ChWorkDisplayFilterSection"/>). </para> @@ -133,13 +133,13 @@ <listitem> <para> Click the Open button to accept your selected file and open it. - If Ethereal doesn't recognize the capture format, it will grey out + If Wireshark doesn't recognize the capture format, it will grey out this button. </para> </listitem> <listitem> <para> - Click the Cancel button to go back to Ethereal and not load a capture + Click the Cancel button to go back to Wireshark and not load a capture file. </para> </listitem> @@ -155,7 +155,7 @@ <title>Input File Formats</title> <para> The following file formats from other capture tools can be opened by - <application>Ethereal</application>: + <application>Wireshark</application>: <itemizedlist> <listitem><para>libpcap, tcpdump and various other tools using tcpdump's capture format</para></listitem> <listitem><para>Sun snoop and atmsnoop</para></listitem> @@ -202,7 +202,7 @@ <section id="ChIOSaveSection"><title>Saving captured packets</title> <para> You can save captured packets simply by using the Save As... menu - item from the File menu under Ethereal. You can choose which + item from the File menu under Wireshark. You can choose which packets to save and which file format to be used. </para> <section id="ChIOSaveAs"> @@ -216,17 +216,17 @@ <note> <title>Note</title> <para> - Ethereal uses the open dialog box from the version of the GTK+ + Wireshark uses the open dialog box from the version of the GTK+ toolkit that it's using. This dialog was completely redesigned in the GTK version 2.4. Depending on the installed GTK version, your dialog box might look different. However, as the functionality remains almost the same, much of this description - will work with your version of Ethereal. + will work with your version of Wireshark. </para> </note> <figure id="ChIOSaveCaptureFileAs"> <title>The "Save Capture File As" dialog box</title> - <graphic entityref="EtherealSaveAs" format="PNG"/> + <graphic entityref="WiresharkSaveAs" format="PNG"/> </figure> <para> With this dialog box, you can perform the following actions: @@ -279,14 +279,14 @@ <listitem> <para> Click on the Save button to accept your selected file and save to - it. If Ethereal has a problem saving the captured packets to + it. If Wireshark has a problem saving the captured packets to the file you specified, it will display an error dialog box. After clicking OK on this error dialog box, you can try again. </para> </listitem> <listitem> <para> - Click on the Cancel button to go back to Ethereal and not save the + Click on the Cancel button to go back to Wireshark and not save the captured packets. </para> </listitem> @@ -296,7 +296,7 @@ <section id="ChIOOutputFormatsSection"> <title>Output File Formats</title> <para> - The following file formats can be saved by <application>Ethereal</application>, + The following file formats can be saved by <application>Wireshark</application>, so other capture tools can read the capture data from: <itemizedlist> <listitem><para>libpcap (tcpdump)</para></listitem> @@ -313,7 +313,7 @@ <note><title></title> <para> Other protocol analyzers may require that the file has a certain suffix - in order to read the files you generate with Ethereal, e.g.: + in order to read the files you generate with Wireshark, e.g.: </para> <para> ".DMP" for Tcpdump/libpcap @@ -329,7 +329,7 @@ <para> Sometimes you need to merge several capture files into one. For example this can be useful, if you have captured simultaneously from multiple - interfaces at once (e.g. using multiple instances of Ethereal). + interfaces at once (e.g. using multiple instances of Wireshark). </para> <para> Merging capture files can be done in three ways: @@ -341,7 +341,7 @@ </para></listitem> <listitem><para> Use <command>drag-and-drop</command> to drop multiple files on the - main window. Ethereal will try to merge the packets in chronological + main window. Wireshark will try to merge the packets in chronological order from the dropped files into a newly created temporary file. If you drop only a single file, it will simply replace a (maybe) existing one. @@ -364,7 +364,7 @@ </note> <figure id="ChIOMergeDialog"> <title>The "Merge with Capture File" dialog box</title> - <graphic entityref="EtherealMergeDialog" format="PNG"/> + <graphic entityref="WiresharkMergeDialog" format="PNG"/> </figure> <variablelist> <varlistentry> @@ -410,10 +410,10 @@ set. </para> <para> - As it can become tedious to work with a file set by hand, Ethereal + As it can become tedious to work with a file set by hand, Wireshark provides some features to handle these file sets in a convenient way. </para> - <sidebar><title>How does Ethereal detect the files of a file set?</title> + <sidebar><title>How does Wireshark detect the files of a file set?</title> <para> A filename in a file set uses the format Prefix_Number_DateTimeSuffix which might look like this: "test_00001_20060420183910.pcap". @@ -421,13 +421,13 @@ (e.g. ".pcap") and a varying middle part. </para> <para> - To find the files of a file set, Ethereal scans the directory where the + To find the files of a file set, Wireshark scans the directory where the currently loaded file resides and scans for files matching the same filename pattern (prefix and suffix) than the currently loaded file. </para> <para> This simple mechanism usually works well, but has it's drawbacks. If several - file sets were captured with the same prefix and suffix, Ethereal will detect + file sets were captured with the same prefix and suffix, Wireshark will detect them as a single file set. If files were renamed or spreaded over several directories the mechanism will fail to find all files of a set. </para> @@ -439,7 +439,7 @@ <itemizedlist> <listitem><para> The <command>List Files</command> dialog box will list the files - Ethereal has recognized as being part of the current file set. + Wireshark has recognized as being part of the current file set. </para></listitem> <listitem><para> <command>Next File</command> closes the current and opens the next @@ -454,7 +454,7 @@ <title>The "List Files" dialog box</title> <figure> <title>The "List Files" dialog box</title> - <graphic entityref="EtherealFileSetDialog" format="PNG"/> + <graphic entityref="WiresharkFileSetDialog" format="PNG"/> </figure> <para> Each line contains information about a file of the file set: @@ -488,8 +488,8 @@ </section> <section id="ChIOExportSection"><title>Exporting data</title> <para> - Ethereal provides several ways and formats to export packet data. This - section describes general ways to export data from Ethereal. + Wireshark provides several ways and formats to export packet data. This + section describes general ways to export data from Wireshark. </para> <note><title>Note!</title> <para> @@ -508,7 +508,7 @@ used to print packets. <figure> <title>The "Export as Plain Text File" dialog box</title> - <graphic entityref="EtherealExportPlainDialog" format="PNG"/> + <graphic entityref="WiresharkExportPlainDialog" format="PNG"/> </figure> <itemizedlist> <listitem><para> @@ -540,7 +540,7 @@ </tip> <figure> <title>The "Export as PostScript File" dialog box</title> - <graphic entityref="EtherealExportPSDialog" format="PNG"/> + <graphic entityref="WiresharkExportPSDialog" format="PNG"/> </figure> <itemizedlist> <listitem><para> @@ -566,7 +566,7 @@ im-/export data. <!--<figure> <title>The "Export as Comma Seperated Values File" dialog box</title> - <graphic entityref="EtherealExportCSVDialog" format="PNG"/> + <graphic entityref="WiresharkExportCSVDialog" format="PNG"/> </figure>--> <itemizedlist> <listitem><para> @@ -587,7 +587,7 @@ only the packet summary. <figure> <title>The "Export as PSML File" dialog box</title> - <graphic entityref="EtherealExportPSMLDialog" format="PNG"/> + <graphic entityref="WiresharkExportPSMLDialog" format="PNG"/> </figure> <itemizedlist> <listitem><para> @@ -612,14 +612,14 @@ PDML specification</ulink>. <note><title></title> <para> - The PDML specification is not officially released and Ethereal's + The PDML specification is not officially released and Wireshark's implementation of it is still in an early beta state, so please expect - changes in future Ethereal versions. + changes in future Wireshark versions. </para> </note> <figure> <title>The "Export as PDML File" dialog box</title> - <graphic entityref="EtherealExportPDMLDialog" format="PNG"/> + <graphic entityref="WiresharkExportPDMLDialog" format="PNG"/> </figure> <itemizedlist> <listitem><para> @@ -642,7 +642,7 @@ binary file. <figure> <title>The "Export Selected Packet Bytes" dialog box</title> - <graphic entityref="EtherealExportSelectedDialog" format="PNG"/> + <graphic entityref="WiresharkExportSelectedDialog" format="PNG"/> </figure> <itemizedlist> <listitem><para> @@ -664,13 +664,13 @@ <section id="ChIOPrintSection"><title>Printing packets</title> <para> To print packets, select the "Print..." menu item from the File menu. - When you do this, Ethereal pops up the Print dialog box as shown in + When you do this, Wireshark pops up the Print dialog box as shown in <xref linkend="ChIOPrintDialogBox"/>. </para> <section><title>The "Print" dialog box</title> <figure id="ChIOPrintDialogBox"> <title>The "Print" dialog box</title> - <graphic entityref="EtherealPrint" format="PNG"/> + <graphic entityref="WiresharkPrint" format="PNG"/> </figure> <para> The following fields are available in the Print dialog box: @@ -764,7 +764,7 @@ lpr -Pmypostscript output function. <figure id="ChIOPacketRangeFrame"> <title>The "Packet Range" frame</title> - <graphic entityref="EtherealPacketRangeFrame" format="PNG"/> + <graphic entityref="WiresharkPacketRangeFrame" format="PNG"/> </figure> </para> <para> @@ -818,7 +818,7 @@ lpr -Pmypostscript the output function. <figure id="ChIOPacketFormatFrame"> <title>The "Packet Format" frame</title> - <graphic entityref="EtherealPacketFormatFrame" format="PNG"/> + <graphic entityref="WiresharkPacketFormatFrame" format="PNG"/> </figure> <itemizedlist> <listitem> diff --git a/docbook/wsug_src/WSUG_chapter_statistics.xml b/docbook/wsug_src/WSUG_chapter_statistics.xml index e6f72e7386..11f9d8532f 100644 --- a/docbook/wsug_src/WSUG_chapter_statistics.xml +++ b/docbook/wsug_src/WSUG_chapter_statistics.xml @@ -6,7 +6,7 @@ <section id="ChStatIntroduction"> <title>Introduction</title> <para> - Ethereal provides a wide range of network statistics. + Wireshark provides a wide range of network statistics. </para> <para> These statistics range @@ -70,7 +70,7 @@ General statistics about the current capture file. </para> <figure><title>The "Summary" window</title> - <graphic entityref="EtherealStatsSummary" format="PNG"/> + <graphic entityref="WiresharkStatsSummary" format="PNG"/> </figure> <itemizedlist> <listitem> @@ -106,7 +106,7 @@ <para> The protocol hierarchy of the captured packets. <figure><title>The "Protocol Hierarchy" window</title> - <graphic entityref="EtherealStatsHierarchy" format="PNG"/> + <graphic entityref="WiresharkStatsHierarchy" format="PNG"/> </figure> This is a tree of all the protocols in the capture. You can collapse or expand subtrees, by clicking on the plus / minus icons. By default, all @@ -189,7 +189,7 @@ <section id="ChStatEndpointDefinition"><title>What is an Endpoint?</title> <para> A network endpoint is the logical endpoint of separate protocol traffic of - a specific protocol layer. The endpoint statistics of Ethereal will take + a specific protocol layer. The endpoint statistics of Wireshark will take the following endpoints into account: </para> <itemizedlist> @@ -256,7 +256,7 @@ This window shows statistics about the endpoints captured. </para> <figure><title>The "Endpoints" window</title> - <graphic entityref="EtherealStatsEndpoints" format="PNG"/> + <graphic entityref="WiresharkStatsEndpoints" format="PNG"/> </figure> <para> For each supported protocol, a tab is shown in this window. @@ -318,7 +318,7 @@ endpoint ones, see <xref linkend="ChStatEndpointsWindow"/> for a description how it works. <figure><title>The "Conversations" window</title> - <graphic entityref="EtherealStatsConversations" format="PNG"/> + <graphic entityref="WiresharkStatsConversations" format="PNG"/> </figure> </para> </section> @@ -345,7 +345,7 @@ </para> <figure><title>The "IO Graphs" window</title> - <graphic entityref="EtherealStatsIOGraphs" format="PNG"/> + <graphic entityref="WiresharkStatsIOGraphs" format="PNG"/> </figure> <para> @@ -473,13 +473,13 @@ First of all, you have to select the DCE-RPC interface: </para> <figure><title>The "Compute DCE-RPC statistics" window</title> - <graphic entityref="EtherealStatsSrtDcerpcFilter" format="PNG"/> + <graphic entityref="WiresharkStatsSrtDcerpcFilter" format="PNG"/> </figure> <para> You can optionally set a display filter, to reduce the amount of packets. </para> <figure><title>The "DCE-RPC Statistic for ..." window</title> - <graphic entityref="EtherealStatsSrtDcerpc" format="PNG"/> + <graphic entityref="WiresharkStatsSrtDcerpc" format="PNG"/> </figure> <para> Each row corresponds to a method of the interface selected (so the EPM diff --git a/docbook/wsug_src/WSUG_chapter_troubleshoot.xml b/docbook/wsug_src/WSUG_chapter_troubleshoot.xml index 999c960fca..ed4a876951 100644 --- a/docbook/wsug_src/WSUG_chapter_troubleshoot.xml +++ b/docbook/wsug_src/WSUG_chapter_troubleshoot.xml @@ -2,9 +2,9 @@ <!-- $Id$ --> <chapter id="Chap04"> - <title>Troubleshooting with <application>Ethereal</application></title> + <title>Troubleshooting with <application>Wireshark</application></title> <section> - <title>An approach to troubleshooting with Ethereal</title> + <title>An approach to troubleshooting with Wireshark</title> <para> Wireshark is a very useful tool for network troubleshooting, since it contains a number of features that allow you to quickly focus on @@ -53,7 +53,7 @@ See <xref linkend="Ch04ROUSWI"/> for more details. </para> <para> - Because Ethereal can read many capture file formats, you can + Because Wireshark can read many capture file formats, you can capture using any conventient tool. One useful approach is to use <command>tcpdump</command> to capture on remote systems and then copy the capture file to your system for @@ -64,8 +64,8 @@ <listitem> <para> Once you have captured packets that you think relate to - the problem, load them into Ethereal and look for your - problem. Using Ethereal's filtering and colorization + the problem, load them into Wireshark and look for your + problem. Using Wireshark's filtering and colorization capabilities, you can quickly narrow down the capture to the area of interest. </para> @@ -119,7 +119,7 @@ <title>Examples of troubleshooting</title> <para> Troubleshooting often requires a reasonable knowledge of the - protocols in question. However, as Ethereal will often give you some + protocols in question. However, as Wireshark will often give you some good hints, you might get an idea of what is going wrong simply by looking in the packets being exchanged. </para> diff --git a/docbook/wsug_src/WSUG_chapter_use.xml b/docbook/wsug_src/WSUG_chapter_use.xml index b8517ea3ff..4f10c28987 100644 --- a/docbook/wsug_src/WSUG_chapter_use.xml +++ b/docbook/wsug_src/WSUG_chapter_use.xml @@ -5,7 +5,7 @@ <title>User Interface</title> <section id="ChUseIntroductionSection"><title>Introduction</title> <para> - By now you have installed <application>Ethereal</application> and + By now you have installed <application>Wireshark</application> and are most likely keen to get started capturing your first packets. In the next chapters we will explore: <itemizedlist> @@ -16,17 +16,17 @@ </listitem> <listitem> <para> - How to capture packets in <application>Ethereal</application> + How to capture packets in <application>Wireshark</application> </para> </listitem> <listitem> <para> - How to view packets in <application>Ethereal</application> + How to view packets in <application>Wireshark</application> </para> </listitem> <listitem> <para> - How to filter packets in <application>Ethereal</application> + How to filter packets in <application>Wireshark</application> </para> </listitem> <listitem> @@ -38,19 +38,19 @@ </para> </section> - <section id="ChUseStartSection"><title>Start Ethereal</title> + <section id="ChUseStartSection"><title>Start Wireshark</title> <para> - You can start Ethereal from your shell or window manager. + You can start Wireshark from your shell or window manager. <tip><title>Tip!</title> <para> - When starting Ethereal it's possible to specify optional settings using + When starting Wireshark it's possible to specify optional settings using the command line. See <xref linkend="ChCustCommandLine"/> for details. </para> </tip> <note><title>Note!</title> <para> - In the following chapters, a lot of screenshots from Ethereal will be shown. - As Ethereal runs on many different platforms and there are different + In the following chapters, a lot of screenshots from Wireshark will be shown. + As Wireshark runs on many different platforms and there are different versions of the underlying GUI toolkit (GTK 1.x / 2.x) used, your screen might look different from the provided screenshots. But as there are no real differences in functionality, these screenshots should still @@ -62,16 +62,16 @@ <section id="ChUseMainWindowSection"><title>The Main window</title> <para> - Lets look at Ethereal's user interface. <xref linkend="ChUseFig01"/> shows - Ethereal as you would usually see it after some packets captured or loaded + Lets look at Wireshark's user interface. <xref linkend="ChUseFig01"/> shows + Wireshark as you would usually see it after some packets captured or loaded (how to do this will be described later). <figure id="ChUseFig01"> <title>The Main window</title> - <graphic scale="100" entityref="EtherealThreePane1" format="PNG"/> + <graphic scale="100" entityref="WiresharkThreePane1" format="PNG"/> </figure> </para> <para> - Ethereal's main window consist of parts that are commonly known from many + Wireshark's main window consist of parts that are commonly known from many other GUI programs. <orderedlist> <listitem> @@ -133,7 +133,7 @@ <section id="ChUseMenuSection"><title>The Menu</title> <para> The Wireshark menu sits on top of the Wireshark window. - An example is shown in <xref linkend="ChUseEtherealMenu"/>. + An example is shown in <xref linkend="ChUseWiresharkMenu"/>. </para> <note><title>Note!</title> <para> @@ -143,8 +143,8 @@ </para> </note> <para> - <figure id="ChUseEtherealMenu"><title>The Menu</title> - <graphic entityref="EtherealMenuOnly" format="PNG"/> + <figure id="ChUseWiresharkMenu"><title>The Menu</title> + <graphic entityref="WiresharkMenuOnly" format="PNG"/> </figure> </para> <para> @@ -155,7 +155,7 @@ <para> This menu contains items to open and merge capture files, save / print / export capture files in whole or in part, - and to quit from Ethereal. See <xref linkend="ChUseFileMenuSection"/>. + and to quit from Wireshark. See <xref linkend="ChUseFileMenuSection"/>. </para> </listitem> </varlistentry> @@ -241,9 +241,9 @@ The Wireshark file menu contains the fields shown in <xref linkend="ChUseTabFile"/>. </para> - <figure id="ChUseEtherealFileMenu"> + <figure id="ChUseWiresharkFileMenu"> <title>The "File" Menu</title> - <graphic entityref="EtherealFileMenu" format="PNG"/> + <graphic entityref="WiresharkFileMenu" format="PNG"/> </figure> <table id="ChUseTabFile" frame="none"><title>File menu items</title> <tgroup cols="3"> @@ -304,7 +304,7 @@ <entry><para> This menu item saves the current capture. If you have not set a default capture file name (perhaps with - the -w <capfile> option), Ethereal pops up the + the -w <capfile> option), Wireshark pops up the Save Capture File As dialog box (which is discussed further in <xref linkend="ChIOSaveAs"/>). </para><note> @@ -425,7 +425,7 @@ <entry><para> This menu item allows you to export the currently selected bytes in the packet bytes pane to a binary file. It pops up the - Ethereal Export dialog box (which is discussed further in + Wireshark Export dialog box (which is discussed further in <xref linkend="ChIOExportSelectedDialog"/>) </para></entry> </row> @@ -453,8 +453,8 @@ <entry><command>Quit</command></entry> <entry>Ctrl+Q</entry> <entry><para> - This menu item allows you to quit from Ethereal. - Ethereal will ask to save your capture file if you haven't saved + This menu item allows you to quit from Wireshark. + Wireshark will ask to save your capture file if you haven't saved it before (this can be disabled by a preference setting). </para></entry> </row> @@ -468,9 +468,9 @@ The Wireshark Edit menu contains the fields shown in <xref linkend="ChUseTabEdit"/>. </para> - <figure id="ChUseEtherealEditMenu"> + <figure id="ChUseWiresharkEditMenu"> <title>The "Edit" Menu</title> - <graphic entityref="EtherealEditMenu" format="PNG"/> + <graphic entityref="WiresharkEditMenu" format="PNG"/> </figure> <table id="ChUseTabEdit" frame="none"> <title>Edit menu items</title> @@ -571,7 +571,7 @@ <entry><para> This menu item brings up a dialog box that allows you to set preferences for many parameters that control - Ethereal. You can also save your preferences so Ethereal + Wireshark. You can also save your preferences so Wireshark will use them the next time you start it. More detail is provided in <xref linkend="ChCustPreferencesSection"/>. </para></entry> @@ -586,9 +586,9 @@ The Wireshark View menu contains the fields shown in <xref linkend="ChUseTabView"/>. </para> - <figure id="ChUseEtherealViewMenu"> + <figure id="ChUseWiresharkViewMenu"> <title>The "View" Menu</title> - <graphic entityref="EtherealViewMenu" format="PNG"/> + <graphic entityref="WiresharkViewMenu" format="PNG"/> </figure> <table id="ChUseTabView" frame="none"> <title>View menu items</title> @@ -665,7 +665,7 @@ <entry><command>Time Display Format > Date and Time of Day: 1970-01-01 01:02:03.123456</command></entry> <entry></entry> <entry><para> - Selecting this tells Ethereal to display the + Selecting this tells Wireshark to display the time stamps in date and time of day format, see <xref linkend="ChWorkTimeFormatsSection"/>. <note><title>Note!</title> @@ -681,7 +681,7 @@ <entry><command>Time Display Format > Time of Day: 01:02:03.123456</command></entry> <entry></entry> <entry><para> - Selecting this tells Ethereal to display time + Selecting this tells Wireshark to display time stamps in time of day format, see <xref linkend="ChWorkTimeFormatsSection"/>. </para></entry> @@ -690,7 +690,7 @@ <entry><command>Time Display Format > Seconds Since Beginning of Capture: 123.123456</command></entry> <entry></entry> <entry><para> - Selecting this tells Ethereal to display time + Selecting this tells Wireshark to display time stamps in seconds since beginning of capture format, see <xref linkend="ChWorkTimeFormatsSection"/>. </para></entry> @@ -699,7 +699,7 @@ <entry><command>Time Display Format > Seconds Since Previous Packet: 1.123456</command></entry> <entry></entry> <entry><para> - Selecting this tells Ethereal to display time stamps in + Selecting this tells Wireshark to display time stamps in seconds since previous packet format, see <xref linkend="ChWorkTimeFormatsSection"/>. </para></entry> @@ -713,7 +713,7 @@ <entry><command>Time Display Format > Automatic (File Format Precision)</command></entry> <entry></entry> <entry><para> - Selecting this tells Ethereal to display time stamps with the + Selecting this tells Wireshark to display time stamps with the precision given by the capture file format used, see <xref linkend="ChWorkTimeFormatsSection"/>. <note><title>Note!</title> @@ -727,7 +727,7 @@ <entry><command>Time Display Format > Seconds: 0</command></entry> <entry></entry> <entry><para> - Selecting this tells Ethereal to display time stamps with a precision of one second, see + Selecting this tells Wireshark to display time stamps with a precision of one second, see <xref linkend="ChWorkTimeFormatsSection"/>. </para></entry> </row> @@ -735,7 +735,7 @@ <entry><command>Time Display Format > ...seconds: 0....</command></entry> <entry></entry> <entry><para> - Selecting this tells Ethereal to display time stamps with a precision of one second, decisecond, centisecond, millisecond, microsecond or nanosecond, see + Selecting this tells Wireshark to display time stamps with a precision of one second, decisecond, centisecond, millisecond, microsecond or nanosecond, see <xref linkend="ChWorkTimeFormatsSection"/>. </para></entry> </row> @@ -752,7 +752,7 @@ <entry></entry> <entry><para> This item allows you to control whether or not - Ethereal translates MAC addresses into names, see + Wireshark translates MAC addresses into names, see <xref linkend="ChAdvNameResolutionSection"/>. </para></entry> </row> @@ -761,7 +761,7 @@ <entry></entry> <entry><para> This item allows you to control whether or not - Ethereal translates network addresses into names, see + Wireshark translates network addresses into names, see <xref linkend="ChAdvNameResolutionSection"/>. </para></entry> </row> @@ -770,7 +770,7 @@ <entry></entry> <entry><para> This item allows you to control whether or not - Ethereal translates transport addresses into names, see + Wireshark translates transport addresses into names, see <xref linkend="ChAdvNameResolutionSection"/>. </para></entry> </row> @@ -778,7 +778,7 @@ <entry><command>Colorize Packet List</command></entry> <entry></entry> <entry><para> - This item allows you to control wether or not Ethereal should colorize + This item allows you to control wether or not Wireshark should colorize the packet list.</para> <note><title>Note!</title><para> Enabling colorization will slow down the display @@ -789,10 +789,10 @@ <entry><command>Auto Scroll in Live Capture</command></entry> <entry></entry> <entry><para> - This item allows you to specify that Ethereal + This item allows you to specify that Wireshark should scroll the packet list pane as new packets come in, so you are always looking at the last packet. If you - do not specify this, Ethereal simply adds new packets onto + do not specify this, Wireshark simply adds new packets onto the end of the list, but does not scroll the packet list pane. </para></entry> @@ -852,7 +852,7 @@ <entry><command>Expand All</command></entry> <entry></entry> <entry><para> - Ethereal keeps a list of all the protocol subtrees + Wireshark keeps a list of all the protocol subtrees that are expanded, and uses it to ensure that the correct subtrees are expanded when you display a packet. This menu item expands all subtrees in all packets in @@ -915,9 +915,9 @@ The Wireshark Go menu contains the fields shown in <xref linkend="ChUseTabGo"/>. </para> - <figure id="ChUseEtherealGoMenu"> + <figure id="ChUseWiresharkGoMenu"> <title>The "Go" Menu</title> - <graphic entityref="EtherealGoMenu" format="PNG"/> + <graphic entityref="WiresharkGoMenu" format="PNG"/> </figure> <table id="ChUseTabGo" frame="none"> <title>Go menu items</title> @@ -995,9 +995,9 @@ The Wireshark Capture menu contains the fields shown in <xref linkend="ChUseTabCap"/>. </para> - <figure id="ChUseEtherealCaptureMenu"> + <figure id="ChUseWiresharkCaptureMenu"> <title>The "Capture" Menu</title> - <graphic entityref="EtherealCaptureMenu" format="PNG"/> + <graphic entityref="WiresharkCaptureMenu" format="PNG"/> </figure> <table id="ChUseTabCap" frame="none"> <title>Capture menu items</title> @@ -1017,7 +1017,7 @@ <entry></entry> <entry><para> This menu item brings up a dialog box that shows what's going on - at the network interfaces Ethereal knows of, see + at the network interfaces Wireshark knows of, see <xref linkend="ChCapInterfaceSection"/>) . </para></entry> </row> @@ -1076,9 +1076,9 @@ The Wireshark Analyze menu contains the fields shown in <xref linkend="ChUseAnalyze"/>. </para> - <figure id="ChUseEtherealAnalyzeMenu"> + <figure id="ChUseWiresharkAnalyzeMenu"> <title>The "Analyze" Menu</title> - <graphic entityref="EtherealAnalyzeMenu" format="PNG"/> + <graphic entityref="WiresharkAnalyzeMenu" format="PNG"/> </figure> <table id="ChUseAnalyze" frame="none"><title>Analyze menu items</title> <tgroup cols="3"> @@ -1140,7 +1140,7 @@ <entry><command>Decode As...</command></entry> <entry></entry> <entry><para> - This menu item allows the user to force Ethereal to + This menu item allows the user to force Wireshark to decode certain packets as a particular protocol, see <xref linkend="ChAdvDecodeAs"/> </para></entry> @@ -1149,7 +1149,7 @@ <entry><command>User Specified Decodes...</command></entry> <entry></entry> <entry><para> - This menu item allows the user to force Ethereal to + This menu item allows the user to force Wireshark to decode certain packets as a particular protocol, see <xref linkend="ChAdvDecodeAsShow"/> </para></entry> @@ -1179,9 +1179,9 @@ The Wireshark Statistics menu contains the fields shown in <xref linkend="ChUseStatistics"/>. </para> - <figure id="ChUseEtherealStatisticsMenu"> + <figure id="ChUseWiresharkStatisticsMenu"> <title>The "Statistics" Menu</title> - <graphic entityref="EtherealStatisticsMenu" format="PNG"/> + <graphic entityref="WiresharkStatisticsMenu" format="PNG"/> </figure> <para> All menu items will bring up a new window showing specific statistical @@ -1366,9 +1366,9 @@ The Wireshark Help menu contains the fields shown in <xref linkend="ChUseHelp"/>. </para> - <figure id="ChUseEtherealHelpMenu"> + <figure id="ChUseWiresharkHelpMenu"> <title>The "Help" Menu</title> - <graphic entityref="EtherealHelpMenu" format="PNG"/> + <graphic entityref="WiresharkHelpMenu" format="PNG"/> </figure> <table id="ChUseHelp" frame="none"> <title>Help menu items</title> @@ -1407,12 +1407,12 @@ </para></entry> </row> <row> - <entry><command>Ethereal Online > ...</command></entry> + <entry><command>Wireshark Online > ...</command></entry> <entry></entry> <entry><para> This menu item starts a Web browser showing the chosen webpage from: - <ulink url="&EtherealWebSite;">&EtherealWebSite;</ulink>. + <ulink url="&WiresharkWebSite;">&WiresharkWebSite;</ulink>. </para></entry> </row> <row> @@ -1421,11 +1421,11 @@ <entry></entry> </row> <row> - <entry><command>About Ethereal</command></entry> + <entry><command>About Wireshark</command></entry> <entry></entry> <entry><para> This menu item brings up an information window that - provides some information on Ethereal, such as the plugins, the + provides some information on Wireshark, such as the plugins, the used folders, ... </para></entry> </row> @@ -1434,7 +1434,7 @@ </table> <note><title>Note!</title> <para> - Calling a Web browser might be unsupported in your version of Ethereal. + Calling a Web browser might be unsupported in your version of Wireshark. If this is the case, the corresponding menu items will be hidden. </para> </note> @@ -1458,9 +1458,9 @@ As in the menu, only the items useful in the current program state will be available. The others will be greyed out (e.g. you cannot save a capture file if you haven't loaded one). - <figure id="ChUseEtherealMainToolbar"> + <figure id="ChUseWiresharkMainToolbar"> <title>The "Main" toolbar</title> - <graphic entityref="EtherealMainToolbar" format="PNG"/> + <graphic entityref="WiresharkMainToolbar" format="PNG"/> </figure> </para> <table id="ChUseMainToolbar" frame="none"> @@ -1479,7 +1479,7 @@ </thead> <tbody> <row> - <entry><graphic entityref="EtherealToolbarCaptureInterfaces" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarCaptureInterfaces" format="PNG"/></entry> <entry><command>Interfaces...</command></entry> <entry>Capture/Interfaces...</entry> <entry><para> @@ -1490,7 +1490,7 @@ </entry> </row> <row> - <entry><graphic entityref="EtherealToolbarCaptureOptions" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarCaptureOptions" format="PNG"/></entry> <entry><command>Options...</command></entry> <entry>Capture/Options...</entry> <entry><para> @@ -1502,7 +1502,7 @@ </entry> </row> <row> - <entry><graphic entityref="EtherealToolbarCaptureStart" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarCaptureStart" format="PNG"/></entry> <entry><command>Start</command></entry> <entry>Capture/Start</entry> <entry><para> @@ -1512,7 +1512,7 @@ </entry> </row> <row> - <entry><graphic entityref="EtherealToolbarCaptureStop" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarCaptureStop" format="PNG"/></entry> <entry><command>Stop</command></entry> <entry>Capture/Stop</entry> <entry><para> @@ -1522,7 +1522,7 @@ </entry> </row> <row> - <entry><graphic entityref="EtherealToolbarCaptureRestart" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarCaptureRestart" format="PNG"/></entry> <entry><command>Restart</command></entry> <entry>Capture/Restart</entry> <entry><para> @@ -1537,7 +1537,7 @@ <entry></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarOpen" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarOpen" format="PNG"/></entry> <entry><command>Open...</command></entry> <entry>File/Open...</entry> <entry><para> @@ -1547,7 +1547,7 @@ </para></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarSaveAs" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarSaveAs" format="PNG"/></entry> <entry><command>Save As...</command></entry> <entry>File/Save As...</entry> <entry><para> @@ -1558,13 +1558,13 @@ <note><title>Note!</title> <para> If you currently have a temporary capture file, the Save icon - <inlinegraphic entityref="EtherealToolbarSave" format="PNG"/> will be + <inlinegraphic entityref="WiresharkToolbarSave" format="PNG"/> will be shown instead. </para></note> </entry> </row> <row> - <entry><graphic entityref="EtherealToolbarClose" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarClose" format="PNG"/></entry> <entry><command>Close</command></entry> <entry>File/Close</entry> <entry><para> @@ -1573,7 +1573,7 @@ </para></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarReload" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarReload" format="PNG"/></entry> <entry><command>Reload</command></entry> <entry>View/Reload</entry> <entry><para> @@ -1581,7 +1581,7 @@ </para></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarPrint" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarPrint" format="PNG"/></entry> <entry><command>Print...</command></entry> <entry>File/Print...</entry> <entry><para> @@ -1597,7 +1597,7 @@ <entry></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarFind" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarFind" format="PNG"/></entry> <entry><command>Find Packet...</command></entry> <entry>Edit/Find Packet...</entry> <entry><para> @@ -1607,7 +1607,7 @@ </para></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarGoBack" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarGoBack" format="PNG"/></entry> <entry><command>Go Back</command></entry> <entry>Go/Go Back</entry> <entry><para> @@ -1615,7 +1615,7 @@ </para></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarGoForward" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarGoForward" format="PNG"/></entry> <entry><command>Go Forward</command></entry> <entry>Go/Go Forward</entry> <entry><para> @@ -1623,7 +1623,7 @@ </para></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarGoTo" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarGoTo" format="PNG"/></entry> <entry><command>Go to Packet...</command></entry> <entry>Go/Go to Packet...</entry> <entry><para> @@ -1632,7 +1632,7 @@ </para></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarGoFirst" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarGoFirst" format="PNG"/></entry> <entry><command>Go To First Packet</command></entry> <entry>Go/First Packet</entry> <entry><para> @@ -1640,7 +1640,7 @@ </para></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarGoLast" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarGoLast" format="PNG"/></entry> <entry><command>Go To Last Packet</command></entry> <entry>Go/Last Packet</entry> <entry><para> @@ -1653,7 +1653,7 @@ <entry></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarColorize" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarColorize" format="PNG"/></entry> <entry><command>Colorize</command></entry> <entry>View/Colorize</entry> <entry><para> @@ -1661,7 +1661,7 @@ </para></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarAutoScroll" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarAutoScroll" format="PNG"/></entry> <entry><command>Auto Scroll in Live Capture</command></entry> <entry>View/Auto Scroll in Live Capture</entry> <entry><para> @@ -1674,7 +1674,7 @@ <entry></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarZoomIn" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarZoomIn" format="PNG"/></entry> <entry><command>Zoom In</command></entry> <entry>View/Zoom In</entry> <entry><para> @@ -1682,7 +1682,7 @@ </para></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarZoomOut" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarZoomOut" format="PNG"/></entry> <entry><command>Zoom Out</command></entry> <entry>View/Zoom Out</entry> <entry><para> @@ -1690,7 +1690,7 @@ </para></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarZoom100" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarZoom100" format="PNG"/></entry> <entry><command>Normal Size</command></entry> <entry>View/Normal Size</entry> <entry><para> @@ -1698,7 +1698,7 @@ </para></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarResizeColumns" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarResizeColumns" format="PNG"/></entry> <entry><command>Resize Columns</command></entry> <entry>View/Resize Columns</entry> <entry><para> @@ -1711,7 +1711,7 @@ <entry></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarCaptureFilters" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarCaptureFilters" format="PNG"/></entry> <entry><command>Capture Filters...</command></entry> <entry>Capture/Capture Filters...</entry> <entry><para> @@ -1723,7 +1723,7 @@ </para></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarDisplayFilters" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarDisplayFilters" format="PNG"/></entry> <entry><command>Display Filters...</command></entry> <entry>Analyze/Display Filters...</entry> <entry><para> @@ -1735,7 +1735,7 @@ </para></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarColoringRules" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarColoringRules" format="PNG"/></entry> <entry><command>Coloring Rules...</command></entry> <entry>View/Coloring Rules...</entry> <entry><para> @@ -1748,13 +1748,13 @@ </para></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarPreferences" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarPreferences" format="PNG"/></entry> <entry><command>Preferences...</command></entry> <entry>Edit/Preferences</entry> <entry><para> This item brings up a dialog box that allows you to set preferences for many parameters that control - Ethereal. You can also save your preferences so Ethereal + Wireshark. You can also save your preferences so Wireshark will use them the next time you start it. More detail is provided in <xref linkend="ChCustPreferencesSection"/> </para></entry> @@ -1765,7 +1765,7 @@ <entry></entry> </row> <row> - <entry><graphic entityref="EtherealToolbarHelp" format="PNG"/></entry> + <entry><graphic entityref="WiresharkToolbarHelp" format="PNG"/></entry> <entry><command>Help</command></entry> <entry>Help/Contents</entry> <entry><para> @@ -1781,9 +1781,9 @@ <para> The filter toolbar lets you quickly edit and apply display filters. More information on display filters is available in <xref linkend="ChWorkDisplayFilterSection"/>. - <figure id="ChUseEtherealFilterToolbar"> + <figure id="ChUseWiresharkFilterToolbar"> <title>The "Filter" toolbar</title> - <graphic entityref="EtherealFilterToolbar" format="PNG"/> + <graphic entityref="WiresharkFilterToolbar" format="PNG"/> </figure> <itemizedlist> <listitem> @@ -1848,16 +1848,16 @@ <para> The packet list pane displays all the packets in the current capture file. - <figure id="ChUseEtherealListPane"> + <figure id="ChUseWiresharkListPane"> <title>The "Packet List" pane</title> - <graphic entityref="EtherealListPane" format="PNG"/> + <graphic entityref="WiresharkListPane" format="PNG"/> </figure> Each line in the packet list corresponds to one packet in the capture file. If you select a line in this pane, more details will be displayed in the "Packet Details" and "Packet Bytes" panes. </para> <para> - While dissecting a packet, Ethereal will place information from the + While dissecting a packet, Wireshark will place information from the protocol dissectors into the columns. As higher level protocols might overwrite information from lower levels, you will typically see the information from the highest possible level only. @@ -1921,9 +1921,9 @@ <para> The packet details pane shows the current packet (selected in the "Packet List" pane) in a more detailed form. - <figure id="ChUseEtherealDetailsPane"> + <figure id="ChUseWiresharkDetailsPane"> <title>The "Packet Details" pane</title> - <graphic entityref="EtherealDetailsPane" format="PNG"/> + <graphic entityref="WiresharkDetailsPane" format="PNG"/> </figure> </para> <para> @@ -1942,9 +1942,9 @@ <listitem> <para> <command>Generated fields</command> - Ethereal itself will generate additional protocol fields which are + Wireshark itself will generate additional protocol fields which are surrounded by brackets. The information in these fields is derived from the - known context to other packets in the capture file. For example, Ethereal + known context to other packets in the capture file. For example, Wireshark is doing a sequence/acknowledge analysis of each TCP stream, which is displayed in the [SEQ/ACK analysis] fields of the TCP protocol. </para> @@ -1952,9 +1952,9 @@ <listitem> <para> <command>Links</command> - If Ethereal detected a relationship to another packet in the capture file, + If Wireshark detected a relationship to another packet in the capture file, it will generate a link to that packet. Links are underlined and displayed - in blue. If double-clicked, Ethereal jumps to the corresponding packet. + in blue. If double-clicked, Wireshark jumps to the corresponding packet. </para> </listitem> </itemizedlist> @@ -1964,9 +1964,9 @@ <para> The packet bytes pane shows the data of the current packet (selected in the "Packet List" pane) in a hexdump style. - <figure id="ChUseEtherealBytesPane"> + <figure id="ChUseWiresharkBytesPane"> <title>The "Packet Bytes" pane</title> - <graphic entityref="EtherealBytesPane" format="PNG"/> + <graphic entityref="WiresharkBytesPane" format="PNG"/> </figure> </para> <para> @@ -1981,13 +1981,13 @@ </para> <para> Depending on the packet data, sometimes more than one page is available, - e.g. when Ethereal has reassembled some packets into a single chunk of + e.g. when Wireshark has reassembled some packets into a single chunk of data, see <xref linkend="ChAdvReassemblySection"/>. In this case there are some additional tabs shown at the bottom of the pane to let you select the page you want to see. - <figure id="ChUseEtherealBytesPaneTabs"> + <figure id="ChUseWiresharkBytesPaneTabs"> <title>The "Packet Bytes" pane with tabs</title> - <graphic entityref="EtherealBytesPaneTabs" format="PNG"/> + <graphic entityref="WiresharkBytesPaneTabs" format="PNG"/> </figure> </para> <note><title>Note!</title> @@ -2011,17 +2011,17 @@ right side will show the current number of packets. </para> <para> - <figure id="ChUseEtherealStatusbarEmpty"> + <figure id="ChUseWiresharkStatusbarEmpty"> <title>The initial Statusbar</title> - <graphic entityref="EtherealStatusbarEmpty" format="PNG"/> + <graphic entityref="WiresharkStatusbarEmpty" format="PNG"/> </figure> This statusbar is shown while no capture file is loaded, e.g. when Wireshark is started. </para> <para> - <figure id="ChUseEtherealStatusbarLoaded"> + <figure id="ChUseWiresharkStatusbarLoaded"> <title>The Statusbar with a loaded capture file</title> - <graphic entityref="EtherealStatusbarLoaded" format="PNG"/> + <graphic entityref="WiresharkStatusbarLoaded" format="PNG"/> </figure> The left side shows information about the capture file, its name, its size and the elapsed time while it was being captured. @@ -2043,9 +2043,9 @@ </itemizedlist> </para> <para> - <figure id="ChUseEtherealStatusbarSelected"> + <figure id="ChUseWiresharkStatusbarSelected"> <title>The Statusbar with a selected protocol field</title> - <graphic entityref="EtherealStatusbarSelected" format="PNG"/> + <graphic entityref="WiresharkStatusbarSelected" format="PNG"/> </figure> This is displayed if you have selected a protocol field from the "Packet Details" pane. diff --git a/docbook/wsug_src/WSUG_chapter_work.xml b/docbook/wsug_src/WSUG_chapter_work.xml index 656861a65d..0ed9e1365a 100644 --- a/docbook/wsug_src/WSUG_chapter_work.xml +++ b/docbook/wsug_src/WSUG_chapter_work.xml @@ -22,14 +22,14 @@ in the TCP header selected, which shows up in the byte view as the selected bytes. <figure id="ChWorkSelPack1"> - <title>Ethereal with a TCP packet selected for viewing</title> - <graphic entityref="EtherealPacketSelected1" format="PNG"/> + <title>Wireshark with a TCP packet selected for viewing</title> + <graphic entityref="WiresharkPacketSelected1" format="PNG"/> </figure> </para> <para> You can also select and view packets the same way, while Wireshark is capturing, if you selected "Update list of packets in real time" in the - Ethereal Capture Preferences dialog box. + Wireshark Capture Preferences dialog box. </para> <para> In addition, you can view individual packets in a separate window as @@ -39,7 +39,7 @@ allows you to easily compare two or even more packets. <figure id="ChWorkPacketSepView"> <title>Viewing a packet in a separate window</title> - <graphic entityref="EtherealPacketSepView" format="PNG"/> + <graphic entityref="WiresharkPacketSepView" format="PNG"/> </figure> </para> <para> @@ -120,7 +120,7 @@ <entry>View</entry> <entry> <para> - Ethereal keeps a list of all the protocol subtrees that are + Wireshark keeps a list of all the protocol subtrees that are expanded, and uses it to ensure that the correct subtrees are expanded when you display a packet. This menu item collapses the tree view of all packets in the capture list. @@ -277,7 +277,7 @@ <para> <figure id="ChWorkPacketListPanePopUpMenu"> <title>Pop-up menu of "Packet List" pane</title> - <graphic entityref="EtherealPacketPanePopupMenu" format="PNG"/> + <graphic entityref="WiresharkPacketPanePopupMenu" format="PNG"/> </figure> <variablelist> <varlistentry><term><command>Mark Packet (toggle)</command></term> @@ -352,7 +352,7 @@ <para> <figure id="ChWorkPacketDetailsPanePopUpMenu"> <title>Pop-up menu of "Packet Details" pane</title> - <graphic entityref="EtherealDetailsPanePopupMenu" format="PNG"/> + <graphic entityref="WiresharkDetailsPanePopupMenu" format="PNG"/> </figure> <variablelist> <varlistentry><term><command>Expand Subtrees</command></term> @@ -373,7 +373,7 @@ <varlistentry><term><command>Collapse All</command></term> <listitem> <para> - Ethereal keeps a list of all the protocol subtrees that are + Wireshark keeps a list of all the protocol subtrees that are expanded, and uses it to ensure that the correct subtrees are expanded when you display a packet. This menu item collapses the tree view of all packets in the capture list. @@ -462,7 +462,7 @@ <para> <figure id="ChWorkPacketBytesPanePopUpMenu"> <title>Pop-up menu of "Packet Bytes" pane</title> - <graphic entityref="EtherealBytesPanePopupMenu" format="PNG"/> + <graphic entityref="WiresharkBytesPanePopupMenu" format="PNG"/> </figure> <variablelist> <varlistentry><term><command>Copy</command></term> @@ -486,7 +486,7 @@ <section id="ChWorkDisplayFilterSection"><title>Filtering packets while viewing</title> <para> - Ethereal has two filtering languages: One used when capturing + Wireshark has two filtering languages: One used when capturing packets, and one used when displaying packets. In this section we explore that second type of filter: Display filters. The first one has already been dealt with in <xref linkend="ChCapCaptureFilterSection"/>. @@ -518,7 +518,7 @@ </para> </note> <figure id="ChWorkTCPFilter"><title>Filtering on the TCP protocol</title> - <graphic entityref="EtherealFilterTCP" format="JPG"/> + <graphic entityref="WiresharkFilterTCP" format="JPG"/> </figure> <para> As you might have noticed, only packets of the TCP protocol are displayed @@ -534,7 +534,7 @@ </para> </note> <para> - You can filter on any protocol that Ethereal understands. + You can filter on any protocol that Wireshark understands. You can also filter on any field that a dissector adds to the tree view, but only if the dissector has added an abbreviation for the field. A list of such fields is available in the Wireshark in the @@ -559,7 +559,7 @@ <section id="ChWorkBuildDisplayFilterSection"> <title>Building display filter expressions</title> <para> - Ethereal provides a simple but powerful display filter language that you + Wireshark provides a simple but powerful display filter language that you can build quite complex filter expressions with. You can compare values in packets as well as combine expressions into more specific expressions. The following sections provide more @@ -568,9 +568,9 @@ <tip> <title>Tip!</title> <para> - You will find a lot of Display Filter examples at the <command>Ethereal + You will find a lot of Display Filter examples at the <command>Wireshark Wiki Display Filter page</command> at <ulink - url="&EtherealWikiDisplayFiltersPage;">&EtherealWikiDisplayFiltersPage;</ulink>. + url="&WiresharkWikiDisplayFiltersPage;">&WiresharkWikiDisplayFiltersPage;</ulink>. </para> </tip> <section> @@ -806,7 +806,7 @@ ip.len le 0x436 <entry></entry> <entry><para> <command>Substring Operator</command></para><para> - Ethereal allows you to select subsequences of a + Wireshark allows you to select subsequences of a sequence in rather elaborate ways. After a label you can place a pair of brackets [] containing a comma separated list of range specifiers. </para><para> @@ -836,7 +836,7 @@ eth.src[1-2] == 00:83 to n:1.</para><para> <programlisting>eth.src[0:3,1-2,:4,4:,2] == 00:00:83:00:83:00:00:83:00:20:20:83</programlisting></para><para> - Ethereal allows you to string together single ranges + Wireshark allows you to string together single ranges in a comma separated list to form compound ranges as shown above. </para></entry> @@ -886,9 +886,9 @@ eth.src[1-2] == 00:83 <section id="ChWorkFilterAddExpressionSection"> <title>The "Filter Expression" dialog box</title> <para> - When you are accustomed to Ethereal's filtering system and know what + When you are accustomed to Wireshark's filtering system and know what labels you wish to use in your filters it can be very quick to - simply type a filter string. However if you are new to Ethereal or + simply type a filter string. However if you are new to Wireshark or are working with a slightly unfamiliar protocol it can be very confusing to try to figure out what to type. The Filter Expression dialog box helps with this. @@ -896,12 +896,12 @@ eth.src[1-2] == 00:83 <tip><title>Tip!</title> <para> The "Filter Expression" dialog box is an excellent way to learn how to - write Ethereal display filter strings. + write Wireshark display filter strings. </para> </tip> <figure id="ChWorkFilterAddExpression1"> <title>The "Filter Expression" dialog box</title> - <graphic entityref="EtherealFilterAddExpression" format="PNG"/> + <graphic entityref="WiresharkFilterAddExpression" format="PNG"/> </figure> <para> When you first bring up the Filter Expression dialog box you are shown a @@ -988,7 +988,7 @@ eth.src[1-2] == 00:83 <section id="ChWorkDefineFilterSection"><title>Defining and saving filters</title> <para> - You can define filters with Ethereal and give them labels for + You can define filters with Wireshark and give them labels for later use. This can save time in remembering and retyping some of the more complex filters you use. </para> @@ -996,7 +996,7 @@ eth.src[1-2] == 00:83 To define a new filter or edit an existing one, select the <command>Capture Filters...</command> menu item from the Capture menu or the <command>Display Filters...</command> menu item from the Analyze - menu. Ethereal will then pop up the Filters dialog as shown in + menu. Wireshark will then pop up the Filters dialog as shown in <xref linkend="FiltersDialog"/>. </para> <note> @@ -1011,12 +1011,12 @@ eth.src[1-2] == 00:83 <para> You must use <command>Save</command> to save your filters permanently. <command>Ok</command> or <command>Apply</command> will not save the filters, - so they will be lost when you close Ethereal. + so they will be lost when you close Wireshark. </para> </warning> <figure id="FiltersDialog"> <title>The "Capture Filters" and "Display Filters" dialog boxes</title> - <graphic entityref="EtherealFilters" format="PNG"/> + <graphic entityref="WiresharkFilters" format="PNG"/> </figure> <para> <variablelist> @@ -1119,13 +1119,13 @@ eth.src[1-2] == 00:83 You can easily find packets once you have captured some packets or have read in a previously saved capture file. Simply select the <command>Find Packet...</command> menu item from the - <command>Edit</command> menu. Ethereal will pop up the dialog box + <command>Edit</command> menu. Wireshark will pop up the dialog box shown in <xref linkend="ChWorkFindPacketDialog"/>. </para> <section><title>The "Find Packet" dialog box</title> <figure id="ChWorkFindPacketDialog"> <title>The "Find Packet" dialog box</title> - <graphic entityref="EtherealFindPacket" format="PNG"/> + <graphic entityref="WiresharkFindPacket" format="PNG"/> </figure> <para> You might first select the kind of thing to search for: @@ -1222,11 +1222,11 @@ eth.src[1-2] == 00:83 <section><title>The "Go to Packet" dialog box</title> <figure id="ChWorkGoToPacketDialog"> <title>The "Go To Packet" dialog box</title> - <graphic entityref="EtherealGoToPacket" format="PNG"/> + <graphic entityref="WiresharkGoToPacket" format="PNG"/> </figure> <para> This dialog box will let you enter a packet number. When you press - <command>OK</command>, Ethereal will jump to that packet. + <command>OK</command>, Wireshark will jump to that packet. </para> </section> <section><title>The "Go to Corresponding Packet" command</title> @@ -1313,7 +1313,7 @@ eth.src[1-2] == 00:83 </para> <para> The timestamp presentation format and the precision in the packet list can - be chosen using the View menu, see <xref linkend="ChUseEtherealViewMenu"/>. + be chosen using the View menu, see <xref linkend="ChUseWiresharkViewMenu"/>. </para> <para> The available presentation formats are: @@ -1402,8 +1402,8 @@ eth.src[1-2] == 00:83 </itemizedlist> <para> <figure id="ChWorkTimeReference"> - <title>Ethereal showing a time referenced packet</title> - <graphic entityref="EtherealTimeReference" format="PNG"/> + <title>Wireshark showing a time referenced packet</title> + <graphic entityref="WiresharkTimeReference" format="PNG"/> </figure> </para> <para> diff --git a/docbook/wsug_src/WSUG_meta_info.xml b/docbook/wsug_src/WSUG_meta_info.xml index 62005e27d6..8efacfe69f 100644 --- a/docbook/wsug_src/WSUG_meta_info.xml +++ b/docbook/wsug_src/WSUG_meta_info.xml @@ -1,7 +1,7 @@ <!-- $Id$ --> <bookinfo> - <title><inlinegraphic entityref="EtherealLogo" valign="middle" format="PNG"/> &DocumentTitle;</title> + <title><inlinegraphic entityref="WiresharkLogo" valign="middle" format="PNG"/> &DocumentTitle;</title> <subtitle>&DocumentSubTitle;</subtitle> <authorgroup> <author> @@ -29,7 +29,7 @@ <holder>&DocumentCopyrightHolder3;</holder> </copyright> - <graphic scale="100" entityref="EtherealLogo" format="PNG"/> + <graphic scale="100" entityref="WiresharkLogo" format="PNG"/> <legalnotice> &DocumentLegalNotice; diff --git a/docbook/wsug_src/WSUG_preface.xml b/docbook/wsug_src/WSUG_preface.xml index 665fc98423..bd673759ac 100644 --- a/docbook/wsug_src/WSUG_preface.xml +++ b/docbook/wsug_src/WSUG_preface.xml @@ -7,11 +7,11 @@ <para> Wireshark is one of those programs that many network managers would love to be able to use, but they are often prevented from getting what they - would like from Ethereal because of the lack of documentation. + would like from Wireshark because of the lack of documentation. </para> <para> This document is part of an effort by the Wireshark team to improve the - usability of Ethereal. + usability of Wireshark. </para> <para> We hope that you find it useful, and look forward to your comments. @@ -21,34 +21,34 @@ <section id="PreAudience"> <title>Who should read this document?</title> <para> - The intended audience of this book is anyone using Ethereal. + The intended audience of this book is anyone using Wireshark. </para> <para> This book will explain all the basics and also some of the advanced features - that Ethereal provides. As Ethereal has become a very complex program since - the early days, not every feature of Ethereal might be explained in this + that Wireshark provides. As Wireshark has become a very complex program since + the early days, not every feature of Wireshark might be explained in this book. </para> <para> This book is not intended to explain network sniffing in general and it will not provide details about specific network protocols. A lot of useful information regarding these topics can be found at the Wireshark Wiki at - <ulink url="&EtherealWikiPage;">&EtherealWikiPage;</ulink> + <ulink url="&WiresharkWikiPage;">&WiresharkWikiPage;</ulink> </para> <para> - By reading this book, you will learn how to install Ethereal, how to use the + By reading this book, you will learn how to install Wireshark, how to use the basic elements of the graphical user interface (like the menu) and what's behind some of the advanced features that are maybe not that obvious at first sight. It will hopefully guide you around some common problems that frequently appears for - new (and sometimes even advanced) users of Ethereal. + new (and sometimes even advanced) users of Wireshark. </para> </section> <section id="PreAck"> <title>Acknowledgements</title> <para> - The authors would like to thank the whole Ethereal team for their + The authors would like to thank the whole Wireshark team for their assistance. In particular, the authors would like to thank: <itemizedlist> <listitem> @@ -148,7 +148,7 @@ </note> <tip><title>This is a tip!</title> <para> - Tips will be helpful for your everyday work using Ethereal. + Tips will be helpful for your everyday work using Wireshark. </para> </tip> </section> @@ -157,7 +157,7 @@ <title>Where to get the latest copy of this document?</title> <para> The latest copy of this documentation can always be found at: - <ulink url="&EtherealUsersGuidePage;"/>. + <ulink url="&WiresharkUsersGuidePage;"/>. </para> </section> @@ -165,7 +165,7 @@ <title>Providing feedback about this document</title> <para> Should you have any feedback about this document, please send them - to the authors through <ulink url="mailto:&EtherealDevMailList;">&EtherealDevMailList;</ulink>. + to the authors through <ulink url="mailto:&WiresharkDevMailList;">&WiresharkDevMailList;</ulink>. </para> </section> </preface> |
