From cdab66760ab49a0bfbbb9eb9531dfa3780f28869 Mon Sep 17 00:00:00 2001 From: Gerald Combs Date: Thu, 18 Apr 2013 17:10:47 +0000 Subject: =?UTF-8?q?=20=E2=86=92=20?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit svn path=/trunk/; revision=48912 --- help/faq.py | 80 ++++++++++++++++++++++++++++++------------------------------- 1 file changed, 40 insertions(+), 40 deletions(-) (limited to 'help') diff --git a/help/faq.py b/help/faq.py index 771d3d95b3..5062edd684 100755 --- a/help/faq.py +++ b/help/faq.py @@ -580,12 +580,12 @@ interface that uses wget;
  • WS_FTP from Ipswitch, -
  • the ftp command that comes with Windows. +
  • the ftp command that comes with Windows. -If you use the ftp command, make sure you do the transfer in -binary mode rather than ASCII mode, by using the binary command +If you use the ftp command, make sure you do the transfer in +binary mode rather than ASCII mode, by using the binary command before transferring the file. """) @@ -603,7 +603,7 @@ answer(""" Many distributions have separate Wireshark packages, one for non-GUI components such as TShark, editcap, dumpcap, etc. and one for the GUI. If this is the case on your system, there's probably a separate package -named wireshark-gnome or wireshark-gtk+. Find it and +named wireshark-gnome or wireshark-gtk+. Find it and install it. """) @@ -652,25 +652,25 @@ followed by linker errors when I try to build Wireshark? """) answer(""" -The version of the sed command on your system is incapable of +The version of the sed command on your system is incapable of handling very long lines. On Solaris, for example, -/usr/bin/sed has a line length limit too low to allow -libtool to work; /usr/xpg4/bin/sed can handle it, as -can GNU sed if you have it installed. +/usr/bin/sed has a line length limit too low to allow +libtool to work; /usr/xpg4/bin/sed can handle it, as +can GNU sed if you have it installed.
    On Solaris, changing your command search path to search -/usr/xpg4/bin before /usr/bin should make the problem +/usr/xpg4/bin before /usr/bin should make the problem go away; on any platform on which you have this problem, installing GNU -sed and changing your command path to search the directory in +sed and changing your command path to search the directory in which it is installed before searching the directory with the version of -sed that came with the OS should make the problem go away. +sed that came with the OS should make the problem go away. """) question(""" When I try to build Wireshark on Solaris, why does the link fail -complaining that plugin_list is undefined? +complaining that plugin_list is undefined? """) answer(""" @@ -689,7 +689,7 @@ other versions mentioned.) question(""" When I try to build Wireshark on Windows, why does the build fail because -of conflicts between winsock.h and winsock2.h? +of conflicts between winsock.h and winsock2.h? """) answer(""" @@ -697,10 +697,10 @@ As of Wireshark 0.9.5, you must install WinPcap 2.3 or later, and the corresponding version of the developer's pack, in order to be able to compile Wireshark; it will not compile with older versions of the developer's pack. The symptoms of this failure are conflicts between -definitions in winsock.h and in winsock2.h; Wireshark -uses winsock2.h, but pre-2.3 versions of the WinPcap -developer's packet use winsock.h. (2.3 uses -winsock2.h, so if Wireshark were to use winsock.h, it +definitions in winsock.h and in winsock2.h; Wireshark +uses winsock2.h, but pre-2.3 versions of the WinPcap +developer's packet use winsock.h. (2.3 uses +winsock2.h, so if Wireshark were to use winsock.h, it would not be able to build with current versions of the WinPcap developer's pack.) @@ -738,7 +738,7 @@ versions of Solaris. """) question("""When I try to run Wireshark, why does it complain about -sprint_realloc_objid being undefined?""") +sprint_realloc_objid being undefined?""") answer(""" Wireshark can only be linked with version 4.2.2 or later of UCD SNMP. @@ -900,7 +900,7 @@ to put the interface on which it's capturing into promiscuous mode unless the "Capture packets in promiscuous mode" option is turned off in the "Capture Options" dialog box, and TShark will try to put the interface on which it's capturing into promiscuous mode unless the --p option was specified. However, some network interfaces +-p option was specified. However, some network interfaces don't support promiscuous mode, and some OSes might not allow interfaces to be put into promiscuous mode. @@ -1050,7 +1050,7 @@ Note, however, that:
  • the form of promiscuous mode that libpcap (the library that programs such as tcpdump, Wireshark, etc. use to do packet capture) turns on will not necessarily be shown if you run -ifconfig on the interface on a UNIX system; +ifconfig on the interface on a UNIX system;
  • some network interfaces might not support promiscuous mode, and some drivers might not allow promiscuous mode to be turned on - see this earlier question for more information on @@ -1312,17 +1312,17 @@ upgrade to that release, as, if there's a bug of that sort, it might've been fixed in a release after the one you're running. If the hang occurs in the most recent release of Wireshark, the bug should be reported to the Wireshark -developers' mailing list at wireshark-dev@wireshark.org. +developers' mailing list at wireshark-dev@wireshark.org.
    On UNIX-flavored OSes, please try to force Wireshark to dump core, by -sending it a SIGABRT signal (usually signal 6) with the -kill command, and then get a stack trace if you have a debugger +sending it a SIGABRT signal (usually signal 6) with the +kill command, and then get a stack trace if you have a debugger installed. A stack trace can be obtained by using your debugger -(gdb in this example), the Wireshark binary, and the resulting +(gdb in this example), the Wireshark binary, and the resulting core file. Here's an example of how to use the gdb command -backtrace to do so. +backtrace to do so. 
             $ gdb wireshark core
@@ -1339,19 +1339,19 @@ some platforms (e.g., BSD systems).
 
 Also, if at all possible, please send a copy of the capture file that caused
 the problem.  When capturing packets, Wireshark normally writes captured
-packets to a temporary file, which will probably be in /tmp or
-/var/tmp on UNIX-flavored OSes, \\TEMP on the main system disk
-(normally \\Documents and Settings\\your login name
-\\Local Settings\\Temp on the main system disk on Windows
+packets to a temporary file, which will probably be in /tmp or
+/var/tmp on UNIX-flavored OSes, \\TEMP on the main system disk
+(normally \\Documents and Settings\\your login name
+\\Local Settings\\Temp on the main system disk on Windows
 Windows XP and Server 2003, and
-\\Users\\your login name\\AppData\\Local\\Temp on the main
+\\Users\\your login name\\AppData\\Local\\Temp on the main
 system disk on Windows Vista and later, so the capture file will probably be there.  If you
 are capturing on a single interface, it will have a name of the form,
-wireshark_<fmt>_<iface>_YYYYmmddHHMMSS_XXXXXX, where
+wireshark_<fmt>_<iface>_YYYYmmddHHMMSS_XXXXXX, where
 <fmt> is the capture file format (pcap or pcapng), and <iface> is
 the actual name of the interface you are capturing on; otherwise, if you are
 capturing on multiple interfaces, it will have a name of the form,
-wireshark_<N>_interfaces_YYYYmmddHHMMSS_XXXXXX, where <N>
+wireshark_<N>_interfaces_YYYYmmddHHMMSS_XXXXXX, where <N>
 is the number of simultaneous interfaces you are capturing on.  Please don't
 send a trace file greater than 1 MB when compressed; instead, make it available
 via FTP or HTTP, or say it's available but leave it up to a developer to ask
@@ -1450,7 +1450,7 @@ for information on using WinDump.
 
 
    
 
-You would run WinDump with the -D flag; if it lists the
+You would run WinDump with the -D flag; if it lists the
 interface, please report this to wireshark-dev@wireshark.org
 giving full details of the problem, including
@@ -1579,7 +1579,7 @@ Windows NT 4.0, Windows 2000, Windows XP, and Windows Server 2003; one
 symptom that may be seen is that attempts to capture in promiscuous mode
 on the interface cause the interface to be incapable of sending or
 receiving packets.  You can disable promiscuous mode using the
--p command-line flag or the item in the "Capture Preferences"
+-p command-line flag or the item in the "Capture Preferences"
 dialog box, but this may mean that outgoing packets, or incoming
 packets, won't be seen in the capture.
 
@@ -1748,11 +1748,11 @@ name and version number of the distribution you're using);
 If you are having trouble capturing on a particular network interface,
 and you've made sure that (on platforms that require it) you've arranged
 that packet capture support is present, as per the above, first try
-capturing on that device with tcpdump.
+capturing on that device with tcpdump.
 
 
    
 
-If you can capture on the interface with tcpdump, send mail to
+If you can capture on the interface with tcpdump, send mail to
 wireshark-users@wireshark.org
 giving full details of the problem, including
@@ -1765,7 +1765,7 @@ name and version number of the distribution you're using);
 
  • the error message you get from Wireshark.
 
 
-If you cannot capture on the interface with tcpdump,
+If you cannot capture on the interface with tcpdump,
 this is almost certainly a problem with one or more of:
 
 
      
@@ -1787,7 +1787,7 @@ href="mailto:tcpdump-workers@lists.tcpdump.org">tcpdump-workers@lists.tcpdump.or
 mailing lists to see if anybody happens to know about the problem and
 know a workaround or fix for the problem.  In your mail, please give
 full details of the problem, as described above, and also indicate that
-the problem occurs with tcpdump not just with Wireshark.
+the problem occurs with tcpdump not just with Wireshark.
 """)
 
 question("""
@@ -1941,8 +1941,8 @@ you want to save that setting in your preference file, and clicking
 
      
 
 It can also be set on the Wireshark or TShark command line with a
--o tcp.check_checksum:false command-line flag, or manually set
-in your preferences file by adding a tcp.check_checksum:false
+-o tcp.check_checksum:false command-line flag, or manually set
+in your preferences file by adding a tcp.check_checksum:false
 line.
 """)
 
-- 
cgit v1.2.1