aboutsummaryrefslogtreecommitdiffstats
path: root/FAQ.include
diff options
context:
space:
mode:
authorJörg Mayer <jmayer@loplof.de>2003-09-08 16:28:11 +0000
committerJörg Mayer <jmayer@loplof.de>2003-09-08 16:28:11 +0000
commitbc91283f0a312d1909f739d4234a684e909a40ac (patch)
treef12565f5c7ce7b2c2aa81eb878735d48ad575cdf /FAQ.include
parentaacc36ae2da869898287b6970a77803482f5e6d2 (diff)
downloadwireshark-bc91283f0a312d1909f739d4234a684e909a40ac.tar.gz
wireshark-bc91283f0a312d1909f739d4234a684e909a40ac.tar.bz2
wireshark-bc91283f0a312d1909f739d4234a684e909a40ac.zip
Update FAQ
svn path=/trunk/; revision=8413
Diffstat (limited to 'FAQ.include')
-rw-r--r--FAQ.include71
1 files changed, 44 insertions, 27 deletions
diff --git a/FAQ.include b/FAQ.include
index 2411e74fa8..21fa7d2056 100644
--- a/FAQ.include
+++ b/FAQ.include
@@ -183,7 +183,7 @@ const char *faq_part[] = {
"\n"
" Q 1.2: What protocols are currently supported?\n"
"\n"
-" A: There are currently 385 supported protocols and media, listed\n"
+" A: There are currently 393 supported protocols and media, listed\n"
" below. Descriptions can be found in the ethereal(1) man page.\n"
"\n"
" 802.1q Virtual LAN\n"
@@ -279,6 +279,7 @@ const char *faq_part[] = {
" Distributed Checksum Clearinghouse Prototocl\n"
" Domain Name Service\n"
" Dynamic DNS Tools Protocol\n"
+" Echo\n"
" Encapsulating Security Payload\n"
" Enhanced Interior Gateway Routing Protocol\n"
" EtherNet/IP (Industrial Protocol)\n"
@@ -310,6 +311,7 @@ const char *faq_part[] = {
" Generic Routing Encapsulation\n"
" Generic Security Service Application Program Interface\n"
" Gnutella Protocol\n"
+" H245\n"
" HP Extended Local-Link Control\n"
" HP Remote Maintenance Protocol\n"
" Hummingbird NFS Daemon\n"
@@ -333,6 +335,7 @@ const char *faq_part[] = {
" ISO 8602 CLTP ConnectionLess Transport Protocol\n"
" ISO 9542 ESIS Routeing Information Exchange Protocol\n"
" ITU-T Recommendation H.261\n"
+" InMon sFlow\n"
" Intel ANS probe\n"
" Intelligent Platform Management Interface\n"
" Inter-Access-Point Protocol\n"
@@ -349,6 +352,7 @@ const char *faq_part[] = {
" Internet Relay Chat\n"
" Internet Security Association and Key Management Protocol\n"
" Internetwork Packet eXchange\n"
+" Jabber XML Messaging\n"
" Java RMI\n"
" Java Serialization\n"
" Kerberos\n"
@@ -384,6 +388,7 @@ const char *faq_part[] = {
" Microsoft Exchange MAPI\n"
" Microsoft Local Security Architecture\n"
" Microsoft Local Security Architecture (Directory Services)\n"
+" Microsoft Messenger Service\n"
" Microsoft Network Logon\n"
" Microsoft Registry\n"
" Microsoft Security Account Manager\n"
@@ -394,13 +399,13 @@ const char *faq_part[] = {
" Microsoft Telephony API Service\n"
" Microsoft Windows Browser Protocol\n"
" Microsoft Windows Lanman Remote API Protocol\n"
+,
+
" Microsoft Windows Logon Protocol\n"
" Microsoft Workstation Service\n"
" Mobile IP\n"
" Mobile IPv6\n"
" Modbus/TCP\n"
-,
-
" Mount Service\n"
" MultiProtocol Label Switching Header\n"
" Multicast Router DISCovery protocol\n"
@@ -453,6 +458,7 @@ const char *faq_part[] = {
" PPP-over-Ethernet Discovery\n"
" PPP-over-Ethernet Session\n"
" PPPMux Control Protocol\n"
+" Packet Encoding Rules (ASN.1 X.691)\n"
" Point-to-Point Protocol\n"
" Point-to-Point Tunnelling Protocol\n"
" Portmap\n"
@@ -543,6 +549,7 @@ const char *faq_part[] = {
" Transmission Control Protocol\n"
" Transparent Network Substrate Protocol\n"
" Trivial File Transfer Protocol\n"
+" UDP Encapsulation of IPsec Packets\n"
" Universal Computer Protocol\n"
" User Datagram Protocol\n"
" Virtual Router Redundancy Protocol\n"
@@ -571,6 +578,7 @@ const char *faq_part[] = {
" Yellow Pages Transfer\n"
" Zebra Protocol\n"
" Zone Information Protocol\n"
+" eDonkey Protocol\n"
" iSCSI\n"
" iSNS\n"
"\n"
@@ -793,6 +801,8 @@ const char *faq_part[] = {
" this. See, for example:\n"
" * this documentation from Cisco on the Switched Port Analyzer (SPAN)\n"
" feature on Catalyst switches;\n"
+,
+
" * documentation from HP on how to set \"monitoring\"/\"mirroring\" on\n"
" ports on the console for HP Advancestack Switch 208 and 224;\n"
" * the \"Network Monitoring Port Features\" section of chapter 6 of\n"
@@ -801,8 +811,6 @@ const char *faq_part[] = {
"\n"
" Note also that many firewall/NAT boxes have a switch built into them;\n"
" this includes many of the \"cable/DSL router\" boxes. If you have a box\n"
-,
-
" of that sort, that has a switch with some number of Ethernet ports\n"
" into which you plug machines on your network, and another Ethernet\n"
" port used to connect to a cable or DSL modem, you can, at least, sniff\n"
@@ -1195,6 +1203,8 @@ const char *faq_part[] = {
"\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"
@@ -1203,8 +1213,6 @@ const char *faq_part[] = {
" 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"
@@ -1336,6 +1344,12 @@ const char *faq_part[] = {
" 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"
+" Also, some drivers for Windows (especially some wireless network\n"
+" interface drivers) apparently do not, when running in promiscuous\n"
+" mode, arrange that outgoing packets are delivered to the software that\n"
+" requested that the interface run promiscuously; try turning\n"
+" promiscuous mode off.\n"
+"\n"
" Q 5.21: I'm trying to capture traffic but I'm not seeing any.\n"
"\n"
" A: Is the machine running Ethereal sending out any traffic on the\n"
@@ -1444,11 +1458,15 @@ const char *faq_part[] = {
" when I try to run Ethereal on Windows?\n"
"\n"
" A: Ethereal is built using the GTK+ toolkit, which supports most\n"
-" UNIX-flavored OSes, and also supports Windows; that toolkit doesn't\n"
-" support 256-color mode on Windows - it requires HiColor (16-bit\n"
-" colors) or more. If your display supports more than 256 colors, switch\n"
-" 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"
+" UNIX-flavored OSes, and also supports Windows.\n"
+"\n"
+" Windows versions of Ethereal before 0.9.14 were built with an older\n"
+" version of that toolkit, which didn't support 256-color mode on\n"
+" Windows - it required HiColor (16-bit colors) or more.\n"
+"\n"
+" Windows versions of Ethereal 0.9.14 and later are built with a version\n"
+" of that toolkit that supports 256-color mode; upgrade to the current\n"
+" version of Ethereal if you want to run on a display in 256-color mode.\n"
"\n"
" Q 5.29: 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"
@@ -1587,6 +1605,8 @@ const char *faq_part[] = {
" cards\", so your card might be a Prism II card), please let us know,\n"
" and include URLs for sites containing any necessary patches to add\n"
" this support.\n"
+,
+
"\n"
" 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"
@@ -1605,8 +1625,6 @@ const char *faq_part[] = {
" programs that capture raw packets, such as tcpdump - cannot capture\n"
" those packets. You will have to determine whether your OS can be so\n"
" configured, configure it if possible, and make whatever changes to\n"
-,
-
" libpcap and the packet capture program you're using are necessary to\n"
" support capturing those packets.\n"
"\n"
@@ -1703,26 +1721,25 @@ const char *faq_part[] = {
" Q 5.34: 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"
+" A: If you want to do this when capturing, you can't. That's a feature\n"
+" that would be hard to implement in capture filters without changes to\n"
+" the capture filter code, which, on many platforms, is in the OS kernel\n"
+" and, on other platforms, is in the libpcap library.\n"
"\n"
-" That's a feature that would be hard to implement in capture filters\n"
-" without changes to the capture filter code, which, on many platforms,\n"
-" is in the OS kernel and, on other platforms, is in the libpcap\n"
-" library.\n"
+" In releases prior to 0.9.14, you also can't search for, or filter,\n"
+" packets containing a particular string even after you've captured\n"
+" them.\n"
"\n"
-" It would be easier to implement in display filters, but it hasn't been\n"
-" implemented yet. It would be best implemented as a display filter\n"
-" \"string match\" operator, which would let you check not only the entire\n"
-" packet for a string, but check portions of the packet for a string. It\n"
-" should probably not use a naive string matching mechanism, as there\n"
-" are mechanisms much faster than the naive one.\n"
+" In 0.9.14, you can search for, but not filter, packets that have a\n"
+" particular string; this has been added to the \"Find Frame\" dialog\n"
+" (\"Find Frame\" under the \"Edit\" menu, or control-F).\n"
"\n"
"\n"
" Support can be found on the ethereal-users[AT]ethereal.com mailing\n"
" list. \n"
" For corrections/additions/suggestions for this page, please send email\n"
" to: ethereal-web[AT]ethereal.com\n"
-" Last modified: Sat, July 19 2003.\n"
+" Last modified: Tue, August 19 2003.\n"
};
#define FAQ_PARTS 5
-#define FAQ_SIZE 78005
+#define FAQ_SIZE 78651