Update FAQ to April 10th

svn path=/trunk/; revision=7448

1 files changed, 212 insertions, 125 deletions

diff --git a/FAQ.include b/FAQ.include
index 3cc3df6615..726aa1ef3c 100644
--- a/FAQ.include
+++ b/FAQ.include
@@ -97,39 +97,48 @@ const char *faq_part[] = {
 "   5.13 When I try to run Ethereal on Windows, it fails to run because it\n"
 "   can't find packet.dll.\n"
 "\n"
-"   5.14 Why does some network interface on my machine not show up in the\n"
-"   list of interfaces in the \"Interface:\" field in the dialog box popped\n"
-"   up by \"Capture->Start\", and/or why does Ethereal give me an error if I\n"
-"   try to capture on that interface? \n"
-"\n"
-"   5.15 I'm running Ethereal on Windows NT/2000/XP/Server; my machine has\n"
+"   5.14 I'm running on Windows; why does some network interface on my\n"
+"   machine not show up in the list of interfaces in the \"Interface:\"\n"
+"   field in the dialog box popped up by \"Capture->Start\", and/or why does\n"
+"   Ethereal give me an error if I try to capture on that interface? \n"
+"\n"
+"   5.15 I'm running on a UNIX-flavored OS; why does some network\n"
+"   interface on my machine not show up in the list of interfaces in the\n"
+"   \"Interface:\" field in the dialog box popped up by \"Capture->Start\",\n"
+"   and/or why does Ethereal give me an error if I try to capture on that\n"
+"   interface? \n"
+"\n"
+"   5.16 I'm running Ethereal on Windows NT/2000/XP/Server; my machine has\n"
 "   a PPP (dial-up POTS, ISDN, etc.) interface, and it shows up in the\n"
 "   \"Interface\" item in the \"Capture Options\" dialog box. Why can no\n"
 "   packets be sent on or received from that network while I'm trying to\n"
 "   capture traffic on that interface?\n"
 "\n"
-"   5.16 I'm running Ethereal on Windows 95/98/Me, on a machine with more\n"
+"   5.17 I'm running Ethereal on Windows 95/98/Me, on a machine with more\n"
 "   than one network adapter of the same type; Ethereal shows all of those\n"
 "   adapters with the same name, but I can't use any of those adapters\n"
 "   other than the first one.\n"
 "\n"
-"   5.17 I have an XXX network card on my machine; if I try to capture on\n"
+"   5.18 I'm running Ethereal on Windows, and I'm not seeing any traffic\n"
+"   being sent by the machine running Ethereal.\n"
+"\n"
+"   5.19 I have an XXX network card on my machine; if I try to capture on\n"
 "   it, my machine crashes or resets itself. \n"
 "\n"
-"   5.18 My machine crashes or resets itself when I select \"Start\" from\n"
+"   5.20 My machine crashes or resets itself when I select \"Start\" from\n"
 "   the \"Capture\" menu or select \"Preferences\" from the \"Edit\" menu. \n"
 "\n"
-"   5.19 Does Ethereal work on Windows ME? \n"
+"   5.21 Does Ethereal work on Windows ME? \n"
 "\n"
-"   5.20 Does Ethereal work on Windows XP? \n"
+"   5.22 Does Ethereal work on Windows XP? \n"
 "\n"
-"   5.21 Why doesn't Ethereal correctly identify RTP packets? It shows\n"
+"   5.23 Why doesn't Ethereal correctly identify RTP packets? It shows\n"
 "   them only as UDP.\n"
 "\n"
-"   5.22 Why doesn't Ethereal show Yahoo Messenger packets in captures\n"
+"   5.24 Why doesn't Ethereal show Yahoo Messenger packets in captures\n"
 "   that contain Yahoo Messenger traffic?\n"
 "\n"
-"   5.23 Why do I get the error \n"
+"   5.25 Why do I get the error \n"
 "\n"
 "     Gdk-ERROR **: Palettized display (256-colour) mode not supported on\n"
 "     Windows.\n"
@@ -137,22 +146,22 @@ const char *faq_part[] = {
 "\n"
 "   when I try to run Ethereal on Windows?\n"
 "\n"
-"   5.24 When I capture on Windows in promiscuous mode, I can see packets\n"
+"   5.26 When I capture on Windows in promiscuous mode, I can see packets\n"
 "   other than those sent to or from my machine; however, those packets\n"
 "   show up with a \"Short Frame\" indication, unlike packets to or from my\n"
 "   machine. What should I do to arrange that I see those packets in their\n"
 "   entirety? \n"
 "\n"
-"   5.25 How can I capture raw 802.11 packets, including non-data\n"
+"   5.27 How can I capture raw 802.11 packets, including non-data\n"
 "   (management, beacon) packets? \n"
 "\n"
-"   5.26 How can I capture packets with CRC errors? \n"
+"   5.28 How can I capture packets with CRC errors? \n"
 "\n"
-"   5.27 How can I capture entire frames, including the FCS? \n"
+"   5.29 How can I capture entire frames, including the FCS? \n"
 "\n"
-"   5.28 Ethereal hangs after I stop a capture. \n"
+"   5.30 Ethereal hangs after I stop a capture. \n"
 "\n"
-"   5.29 How can I search for, or filter, packets that have a particular\n"
+"   5.31 How can I search for, or filter, packets that have a particular\n"
 "   string anywhere in them? \n"
 "\n"
 "   GENERAL QUESTIONS \n"
@@ -390,6 +399,8 @@ const char *faq_part[] = {
 "            Network News Transfer Protocol\n"
 "            Network Status Monitor CallBack Protocol\n"
 "            Network Status Monitor Protocol\n"
+,
+
 "            Network Time Protocol\n"
 "            Novell Distributed Print System\n"
 "            Null/Loopback\n"
@@ -399,8 +410,6 @@ const char *faq_part[] = {
 "            PC NFS\n"
 "            PPP Bandwidth Allocation Control Protocol\n"
 "            PPP Bandwidth Allocation Protocol\n"
-,
-
 "            PPP CDP Control Protocol\n"
 "            PPP Callback Control Protocol\n"
 "            PPP Challenge Handshake Authentication Protocol\n"
@@ -792,6 +801,8 @@ const char *faq_part[] = {
 "   off in the \"Capture Options\" dialog box, and Tethereal will try to put\n"
 "   the interface on which it's capturing into promiscuous mode unless the\n"
 "   -p option was specified. However, some network interfaces don't\n"
+,
+
 "   support promiscuous mode, and some OSes might not allow interfaces to\n"
 "   be put into promiscuous mode.\n"
 "\n"
@@ -801,8 +812,6 @@ const char *faq_part[] = {
 "   address the interface is set up to receive.\n"
 "\n"
 "   You should ask the vendor of your network interface whether it\n"
-,
-
 "   supports promiscuous mode. If it does, you should ask whoever supplied\n"
 "   the driver for the interface (the vendor, or the supplier of the OS\n"
 "   you're running on your machine) whether it supports promiscuous mode\n"
@@ -1028,11 +1037,8 @@ const char *faq_part[] = {
 "   Q 5.12: I'm capturing packets on {Windows 95, Windows 98, Windows Me};\n"
 "   why are the time stamps on packets wrong? \n"
 "\n"
-"   A: This is due to a bug in WinPcap. The bug should be fixed in the\n"
-"   WinPcap 3.0 beta release - note that it's an beta release, so it may\n"
-"   be buggier than the current production release of WinPcap; please\n"
-"   report those bugs to the WinPcap developers, and help them try to\n"
-"   track down the problem, so that they can fix it for the final release.\n"
+"   A: This is due to a bug in WinPcap. The bug should be fixed in WinPcap\n"
+"   3.0.\n"
 "\n"
 "   Q 5.13: When I try to run Ethereal on Windows, it fails to run because\n"
 "   it can't find packet.dll.\n"
@@ -1051,53 +1057,31 @@ const char *faq_part[] = {
 "   Web site, the local mirror of the WinPcap Web site, or the\n"
 "   Wiretapped.net mirror of the WinPcap site.\n"
 "\n"
-"   Q 5.14: Why does some network interface on my machine not show up in\n"
-"   the list of interfaces in the \"Interface:\" field in the dialog box\n"
-"   popped up by \"Capture->Start\", and/or why does Ethereal give me an\n"
-"   error if I try to capture on that interface? \n"
-"\n"
-"   A: If you are running Ethereal on a UNIX-flavored platform, you may\n"
-"   need to run Ethereal from an account with sufficient privileges to\n"
-"   capture packets, such as the super-user account. Only those interfaces\n"
-"   that Ethereal can open for capturing show up in that list; if you\n"
-"   don't have sufficient privileges to capture on any interfaces, no\n"
-"   interfaces will show up in the list.\n"
-"\n"
-"   If you are running Ethereal on Windows NT 4.0, Windows 2000, Windows\n"
-"   XP, or Windows Server, and this is the first time you have run a\n"
-"   WinPcap-based program (such as Ethereal, or Tethereal, or WinDump, or\n"
-"   Analyzer, or...) since the machine was rebooted, you need to run that\n"
-"   program from an account with administrator privileges; once you have\n"
-"   run such a program, you will not need administrator privileges to run\n"
-"   any such programs until you reboot.\n"
-"\n"
-"   If you are running on a UNIX-flavored platform and have sufficient\n"
-"   privileges, or if you are running on Windows 95/98/Me, or if you are\n"
-"   running on Windows NT 4.0/2000/XP/Server and have administrator\n"
-"   privileges or a WinPcap program has been run with those privileges\n"
-"   since the machine rebooted, then note that Ethereal relies on the\n"
-"   libpcap library, and on the facilities that come with the OS on which\n"
-"   it's running in order to do captures; on Windows, it also relies on\n"
-"   the device driver that comes with WinPcap (which is a version of\n"
-"   libpcap for Windows).\n"
-"\n"
-"   Therefore, if the OS, the libpcap library, or the WinPcap driver don't\n"
+"   Q 5.14: I'm running on Windows; why does some network interface on my\n"
+"   machine not show up in the list of interfaces in the \"Interface:\"\n"
+"   field in the dialog box popped up by \"Capture->Start\", and/or why does\n"
+"   Ethereal give me an error if I try to capture on that interface? \n"
+"\n"
+"   A: If you are running Ethereal on Windows NT 4.0, Windows 2000,\n"
+"   Windows XP, or Windows Server, and this is the first time you have run\n"
+"   a WinPcap-based program (such as Ethereal, or Tethereal, or WinDump,\n"
+"   or Analyzer, or...) since the machine was rebooted, you need to run\n"
+"   that program from an account with administrator privileges; once you\n"
+"   have run such a program, you will not need administrator privileges to\n"
+"   run any such programs until you reboot.\n"
+"\n"
+"   If you are running on Windows 95/98/Me, or if you are running on\n"
+"   Windows NT 4.0/2000/XP/Server and have administrator privileges or a\n"
+"   WinPcap program has been run with those privileges since the machine\n"
+"   rebooted, then note that Ethereal relies on the WinPcap library, on\n"
+"   the WinPcap device driver, and on the facilities that come with the OS\n"
+"   on which it's running in order to do captures.\n"
+"\n"
+"   Therefore, if the OS, the WinPcap library, or the WinPcap driver don't\n"
 "   support capturing on a particular network interface device, Ethereal\n"
 "   won't be able to capture on that device.\n"
 "\n"
-"   On Linux, note that you need to have \"packet socket\" support enabled\n"
-"   in your kernel; see the \"Packet socket\" item in the Linux\n"
-"   \"Configure.help\" file.\n"
-"\n"
-"   On BSD, note that you need to have BPF support enabled in your kernel;\n"
-"   see the documentation for your system for information on how to enable\n"
-"   BPF support (if it's not enabled by default on your system).\n"
-"\n"
-"   On DEC OSF/1, Digital UNIX, or Tru64 UNIX, note that you need to have\n"
-"   packet filtering support in your kernel; the doconfig command will\n"
-"   allow you to configure and build a new kernel with that option.\n"
-"\n"
-"   On Windows, note that:\n"
+"   Note that:\n"
 "     * 2.02 and earlier versions of the WinPcap driver and library that\n"
 "       Ethereal uses for packet capture didn't support Token Ring\n"
 "       interfaces; the current version, 2.3, does support Token Ring, and\n"
@@ -1124,23 +1108,124 @@ const char *faq_part[] = {
 "       lines, ISDN lines, and various other lines such as T1/E1 lines are\n"
 "       all PPP interfaces. This may cause the interface not to show up on\n"
 "       the list of interfaces in the \"Capture Options\" dialog.\n"
-"     * WinPcap currently does not support multiprocessor machines (note\n"
-"       that machines with a single multi-threaded processor, such as\n"
-"       Intel's new multi-threaded x86 processors, are multiprocessor\n"
+"     * WinPcap prior to 3.0 does not support multiprocessor machines\n"
+"       (note that machines with a single multi-threaded processor, such\n"
+"       as Intel's new multi-threaded x86 processors, are multiprocessor\n"
 "       machines as far as the OS and WinPcap are concerned), and recent\n"
-"       versions refuse to operate if they detect that they're running on\n"
-"       a multiprocessor machine, which means that they may not show any\n"
-"       network interfaces.\n"
+"       2.x versions of WinPcap refuse to operate if they detect that\n"
+"       they're running on a multiprocessor machine, which means that they\n"
+"       may not show any network interfaces. You will need to use WinPcap\n"
+"       3.0 to capture on a multiprocessor machine.\n"
+"\n"
+"   If an interface doesn't show up in the list of interfaces in the\n"
+"   \"Interface:\" field, and you know the name of the interface, try\n"
+"   entering that name in the \"Interface:\" field and capturing on that\n"
+"   device.\n"
+"\n"
+"   If the attempt to capture on it succeeds, the interface is somehow not\n"
+"   being reported by the mechanism Ethereal uses to get a list of\n"
+"   interfaces; please report this to ethereal-dev@ethereal.com giving\n"
+"   full details of the problem, including\n"
+"     * the operating system you're using, and the version of that\n"
+"       operating system;\n"
+"     * the type of network device you're using.\n"
+"\n"
+"   If you are having trouble capturing on a particular network interface,\n"
+"   and you've made sure that (on platforms that require it) you've\n"
+"   arranged that packet capture support is present, as per the above,\n"
+"   first try capturing on that device with WinDump; see the WinDump Web\n"
+"   site or the local mirror of the WinDump Web site for information on\n"
+"   using WinDump.\n"
+"\n"
+"   If you can capture on the interface with WinDump, send mail to\n"
+"   ethereal-users@ethereal.com giving full details of the problem,\n"
+"   including\n"
+"     * the operating system you're using, and the version of that\n"
+"       operating system;\n"
+"     * the type of network device you're using;\n"
+"     * the error message you get from Ethereal.\n"
+"\n"
+"   If you cannot capture on the interface with WinDump, this is almost\n"
+"   certainly a problem with one or more of:\n"
+"     * the operating system you're using;\n"
+"     * the device driver for the interface you're using;\n"
+"     * the WinPcap library and/or the WinPcap device driver;\n"
+"\n"
+"   so first check the WinPcap FAQ, the local mirror of that FAQ, or the\n"
+"   Wiretapped.net mirror of that FAQ, to see if your problem is mentioned\n"
+"   there. If not, then see the WinPcap support page (or the local mirror\n"
+"   of that page) - check the \"Submitting bugs\" section.\n"
+"\n"
+"   You may also want to ask the ethereal-users@ethereal.com and the\n"
+"   winpcap-users@winpcap.polito.it mailing lists to see if anybody\n"
+"   happens to know about the problem and know a workaround or fix for the\n"
+"   problem. (Note that you will have to subscribe to that list in order\n"
+"   to be allowed to mail to it; see the WinPcap support page, or the\n"
+"   local mirror of that page, for information on the mailing list.) In\n"
+"   your mail, please give full details of the problem, as described\n"
+"   above, and also indicate that the problem occurs with WinDump, not\n"
+"   just with Ethereal.\n"
+"\n"
+"   Q 5.15: I'm running on a UNIX-flavored OS; why does some network\n"
+"   interface on my machine not show up in the list of interfaces in the\n"
+"   \"Interface:\" field in the dialog box popped up by \"Capture->Start\",\n"
+"   and/or why does Ethereal give me an error if I try to capture on that\n"
+"   interface? \n"
+"\n"
+"   A: You may need to run Ethereal from an account with sufficient\n"
+"   privileges to capture packets, such as the super-user account. Only\n"
+"   those interfaces that Ethereal can open for capturing show up in that\n"
+"   list; if you don't have sufficient privileges to capture on any\n"
+"   interfaces, no interfaces will show up in the list.\n"
+"\n"
+"   If you are running Ethereal from an account with sufficient\n"
+"   privileges, then note that Ethereal relies on the libpcap library, and\n"
+"   on the facilities that come with the OS on which it's running in order\n"
+"   to do captures.\n"
+"\n"
+"   Therefore, if the OS or the libpcap library don't support capturing on\n"
+"   a particular network interface device, Ethereal won't be able to\n"
+"   capture on that device.\n"
+"\n"
+"   On Linux, note that you need to have \"packet socket\" support enabled\n"
+"   in your kernel; see the \"Packet socket\" item in the Linux\n"
+"   \"Configure.help\" file.\n"
+"\n"
+"   On BSD, note that you need to have BPF support enabled in your kernel;\n"
+"   see the documentation for your system for information on how to enable\n"
+"   BPF support (if it's not enabled by default on your system).\n"
+"\n"
+"   On DEC OSF/1, Digital UNIX, or Tru64 UNIX, note that you need to have\n"
+"   packet filtering support in your kernel; the doconfig command will\n"
+"   allow you to configure and build a new kernel with that option.\n"
+"\n"
+"   On Solaris, note that libpcap 0.6.2 and earlier didn't support Token\n"
+"   Ring interfaces; the current version, 0.7.2, does support Token Ring,\n"
+"   and the current version of Ethereal works with libcap 0.7.2 and later.\n"
+"\n"
+,
+
+"   If an interface doesn't show up in the list of interfaces in the\n"
+"   \"Interface:\" field, and you know the name of the interface, try\n"
+"   entering that name in the \"Interface:\" field and capturing on that\n"
+"   device.\n"
+"\n"
+"   If the attempt to capture on it succeeds, the interface is somehow not\n"
+"   being reported by the mechanism Ethereal uses to get a list of\n"
+"   interfaces; please report this to ethereal-dev@ethereal.com giving\n"
+"   full details of the problem, including\n"
+"     * the operating system you're using, and the version of that\n"
+"       operating system (for Linux, give both the version number of the\n"
+"       kernel and the name and version number of the distribution you're\n"
+"       using);\n"
+"     * the type of network device you're using.\n"
 "\n"
 "   If you are having trouble capturing on a particular network interface,\n"
 "   and you've made sure that (on platforms that require it) you've\n"
 "   arranged that packet capture support is present, as per the above,\n"
-"   first try capturing on that device with tcpdump - or, on Windows, the\n"
-"   tcpdump port to Windows, named WinDump; see the WinDump Web site, the\n"
-"   local mirror of the WinDump Web site, or the Wiretapped.net mirror of\n"
-"   the WinDump site, for information on using WinDump.\n"
+"   first try capturing on that device with tcpdump.\n"
 "\n"
-"   If you can capture on the interface with tcpdump/WinDump, send mail to\n"
+"   If you can capture on the interface with tcpdump, send mail to\n"
 "   ethereal-users@ethereal.com giving full details of the problem,\n"
 "   including\n"
 "     * the operating system you're using, and the version of that\n"
@@ -1150,33 +1235,24 @@ const char *faq_part[] = {
 "     * the type of network device you're using;\n"
 "     * the error message you get from Ethereal.\n"
 "\n"
-"   If you cannot capture on the interface with tcpdump/WinDump, this is\n"
-"   almost certainly a problem with one or more of:\n"
+"   If you cannot capture on the interface with tcpdump, this is almost\n"
+"   certainly a problem with one or more of:\n"
 "     * the operating system you're using;\n"
 "     * the device driver for the interface you're using;\n"
-"     * the libpcap/WinPcap library and, if this is Windows, the WinPcap\n"
-"       device driver;\n"
+"     * the libpcap library;\n"
 "\n"
-"   so:\n"
-"     * if you are using Windows, first check the WinPcap FAQ, the local\n"
-"       mirror of that FAQ, or the Wiretapped.net mirror of that FAQ, to\n"
-"       see if your problem is mentioned there. If not, then see the\n"
-"       WinPcap support page (or the local mirror of that page) - check\n"
-"       the \"Submitting bugs\" section;\n"
-"     * if you are using some Linux distribution, some version of BSD, or\n"
-"       some other UNIX-flavored OS, you should report the problem to the\n"
-"       company or organization that produces the OS (in the case of a\n"
-"       Linux distribution, report the problem to whoever produces the\n"
-"       distribution).\n"
+"   so you should report the problem to the company or organization that\n"
+"   produces the OS (in the case of a Linux distribution, report the\n"
+"   problem to whoever produces the distribution).\n"
 "\n"
-"   You may also want to ask the ethereal-users@ethereal.com and, if this\n"
-"   is a UNIX-flavored platform, tcpdump-workers@tcpdump.org mailing lists\n"
-"   to see if anybody happens to know about the problem and know a\n"
-"   workaround or fix for the problem. In your mail, please give full\n"
-"   details of the problem, as described above, and also indicate that the\n"
-"   problem occurs with tcpdump/WinDump, not just with Ethereal.\n"
+"   You may also want to ask the ethereal-users@ethereal.com and the\n"
+"   tcpdump-workers@tcpdump.org mailing lists to see if anybody happens to\n"
+"   know about the problem and know a workaround or fix for the problem.\n"
+"   In your mail, please give full details of the problem, as described\n"
+"   above, and also indicate that the problem occurs with tcpdump not just\n"
+"   with Ethereal.\n"
 "\n"
-"   Q 5.15: I'm running Ethereal on Windows NT/2000/XP/Server; my machine\n"
+"   Q 5.16: I'm running Ethereal on Windows NT/2000/XP/Server; my machine\n"
 "   has a PPP (dial-up POTS, ISDN, etc.) interface, and it shows up in the\n"
 "   \"Interface\" item in the \"Capture Options\" dialog box. Why can no\n"
 "   packets be sent on or received from that network while I'm trying to\n"
@@ -1190,7 +1266,7 @@ const char *faq_part[] = {
 "   Preferences\" dialog box, but this may mean that outgoing packets, or\n"
 "   incoming packets, won't be seen in the capture.\n"
 "\n"
-"   Q 5.16: I'm running Ethereal on Windows 95/98/Me, on a machine with\n"
+"   Q 5.17: I'm running Ethereal on Windows 95/98/Me, on a machine with\n"
 "   more than one network adapter of the same type; Ethereal shows all of\n"
 "   those adapters with the same name, but I can't use any of those\n"
 "   adapters other than the first one.\n"
@@ -1201,10 +1277,19 @@ const char *faq_part[] = {
 "   capture only on the first such interface; Ethereal is a\n"
 "   libpcap/WinPcap-based application.\n"
 "\n"
-"   Q 5.17: I have an XXX network card on my machine; if I try to capture\n"
+"   Q 5.18: I'm running Ethereal on Windows, and I'm not seeing any\n"
+"   traffic being sent by the machine running Ethereal.\n"
+"\n"
+"   A: If you are running some form of VPN client software, it might be\n"
+"   causing this problem; people have seen this problem when they have\n"
+"   Check Point's VPN software installed on their machine. If that's the\n"
+"   cause of the problem, you will have to remove the VPN software in\n"
+"   order to have Ethereal (or any other application using WinPcap) see\n"
+"   outgoing packets; unfortunately, neither we nor the WinPcap developers\n"
+"   know any way to make WinPcap and the VPN software work well together.\n"
+"\n"
+"   Q 5.19: I have an XXX network card on my machine; if I try to capture\n"
 "   on it, my machine crashes or resets itself. \n"
-,
-
 "\n"
 "   A: This is almost certainly a problem with one or more of:\n"
 "     * the operating system you're using;\n"
@@ -1221,7 +1306,7 @@ const char *faq_part[] = {
 "       Linux distribution, report the problem to whoever produces the\n"
 "       distribution).\n"
 "\n"
-"   Q 5.18: My machine crashes or resets itself when I select \"Start\" from\n"
+"   Q 5.20: My machine crashes or resets itself when I select \"Start\" from\n"
 "   the \"Capture\" menu or select \"Preferences\" from the \"Edit\" menu. \n"
 "\n"
 "   A: Both of those operations cause Ethereal to try to build a list of\n"
@@ -1230,20 +1315,20 @@ const char *faq_part[] = {
 "   or, for Windows, WinPcap bug that causes the system to crash when this\n"
 "   happens; see the previous question.\n"
 "\n"
-"   Q 5.19: Does Ethereal work on Windows ME? \n"
+"   Q 5.21: Does Ethereal work on Windows ME? \n"
 "\n"
 "   A: Yes, but if you want to capture packets, you will need to install\n"
 "   the latest version of WinPcap, as 2.02 and earlier versions of WinPcap\n"
 "   didn't support Windows ME. You should also install the latest version\n"
 "   of Ethereal as well.\n"
 "\n"
-"   Q 5.20: Does Ethereal work on Windows XP? \n"
+"   Q 5.22: Does Ethereal work on Windows XP? \n"
 "\n"
 "   A: Yes, but if you want to capture packets, you will need to install\n"
 "   the latest version of WinPcap, as 2.2 and earlier versions of WinPcap\n"
 "   didn't support Windows XP.\n"
 "\n"
-"   Q 5.21: Why doesn't Ethereal correctly identify RTP packets? It shows\n"
+"   Q 5.23: Why doesn't Ethereal correctly identify RTP packets? It shows\n"
 "   them only as UDP.\n"
 "\n"
 "   A: Ethereal can identify a UDP datagram as containing a packet of a\n"
@@ -1276,7 +1361,7 @@ const char *faq_part[] = {
 "   both the source and destination ports of the packet should be\n"
 "   dissected as some particular protocol.\n"
 "\n"
-"   Q 5.22: Why doesn't Ethereal show Yahoo Messenger packets in captures\n"
+"   Q 5.24: Why doesn't Ethereal show Yahoo Messenger packets in captures\n"
 "   that contain Yahoo Messenger traffic?\n"
 "\n"
 "   A: Ethereal only recognizes as Yahoo Messenger traffic packets to or\n"
@@ -1286,7 +1371,7 @@ const char *faq_part[] = {
 "   Messenger packets (even if the TCP segment also contains the beginning\n"
 "   of another Yahoo Messenger packet).\n"
 "\n"
-"   Q 5.23: Why do I get the error \n"
+"   Q 5.25: Why do I get the error \n"
 "\n"
 "     Gdk-ERROR **: Palettized display (256-colour) mode not supported on\n"
 "     Windows.\n"
@@ -1301,7 +1386,7 @@ const char *faq_part[] = {
 "   to a display mode with more colors; if it doesn't support more than\n"
 "   256 colors, you will be unable to run Ethereal.\n"
 "\n"
-"   Q 5.24: When I capture on Windows in promiscuous mode, I can see\n"
+"   Q 5.26: When I capture on Windows in promiscuous mode, I can see\n"
 "   packets other than those sent to or from my machine; however, those\n"
 "   packets show up with a \"Short Frame\" indication, unlike packets to or\n"
 "   from my machine. What should I do to arrange that I see those packets\n"
@@ -1311,7 +1396,7 @@ const char *faq_part[] = {
 "   running on the network interface on which you're capturing; turn it\n"
 "   off on that interface.\n"
 "\n"
-"   Q 5.25: How can I capture raw 802.11 packets, including non-data\n"
+"   Q 5.27: How can I capture raw 802.11 packets, including non-data\n"
 "   (management, beacon) packets? \n"
 "\n"
 "   A: That would require that your 802.11 interface run in the mode\n"
@@ -1442,7 +1527,7 @@ const char *faq_part[] = {
 "   On platforms that don't allow Ethereal to capture raw 802.11 packets,\n"
 "   the 802.11 network will appear like an Ethernet to Ethereal.\n"
 "\n"
-"   Q 5.26: How can I capture packets with CRC errors? \n"
+"   Q 5.28: How can I capture packets with CRC errors? \n"
 "\n"
 "   A: Ethereal can capture only the packets that the packet capture\n"
 "   library - libpcap on UNIX-flavored OSes, and the WinPcap port to\n"
@@ -1459,7 +1544,7 @@ const char *faq_part[] = {
 "   libpcap and the packet capture program you're using are necessary to\n"
 "   support capturing those packets.\n"
 "\n"
-"   Q 5.27: How can I capture entire frames, including the FCS? \n"
+"   Q 5.29: How can I capture entire frames, including the FCS? \n"
 "\n"
 "   A: Ethereal can't capture any data that the packet capture library -\n"
 "   libpcap on UNIX-flavored OSes, and the WinPcap port to Windows of\n"
@@ -1479,7 +1564,7 @@ const char *faq_part[] = {
 "   not support capturing the FCS of a frame on Ethernet, and probably do\n"
 "   not support it on most other link-layer types.\n"
 "\n"
-"   Q 5.28: Ethereal hangs after I stop a capture. \n"
+"   Q 5.30: Ethereal hangs after I stop a capture. \n"
 "\n"
 "   A: The most likely reason for this is that Ethereal is trying to look\n"
 "   up an IP address in the capture to convert it to a name (so that, for\n"
@@ -1520,6 +1605,8 @@ const char *faq_part[] = {
 "\n"
 "   If Ethereal hangs when reading a capture even with network name\n"
 "   resolution turned off, there might, for example, be a bug in one of\n"
+,
+
 "   Ethereal's dissectors for a protocol causing it to loop infinitely.\n"
 "   The bug should be reported to the Ethereal developers' mailing list at\n"
 "   ethereal-dev@ethereal.com.\n"
@@ -1549,7 +1636,7 @@ const char *faq_part[] = {
 "   contains sensitive information (e.g., passwords), then please do not\n"
 "   send it.\n"
 "\n"
-"   Q 5.29: How can I search for, or filter, packets that have a\n"
+"   Q 5.31: How can I search for, or filter, packets that have a\n"
 "   particular string anywhere in them? \n"
 "\n"
 "   A: Currently, you can't.\n"
@@ -1571,7 +1658,7 @@ const char *faq_part[] = {
 "   list. \n"
 "   For corrections/additions/suggestions for this page, please send email\n"
 "   to: ethereal-web[AT]ethereal.com\n"
-"   Last modified: Thu, March 20 2003.\n"
+"   Last modified: Thu, April 10 2003.\n"
 };
-#define FAQ_PARTS 4
-#define FAQ_SIZE 71384
+#define FAQ_PARTS 5
+#define FAQ_SIZE 75375