osmocom
/
wireshark
14
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

Added this intermediate files, until a Makfile.am is available for unix systems 

svn path=/trunk/; revision=9097
This commit is contained in:
Ulf Lamping 2003-11-27 00:17:12 +00:00
parent ff5569c895
commit 4c5b5d8d51
5 changed files with 2027 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

83
help/capture_filters.h Normal file
View File

@ -0,0 +1,83 @@
/* THIS FILE IS AUTOMATICALLY GENERATED, DO NOT MODIFY!!! */
const char *capture_filters_part[] = {
"Filtering packets while capturing \n"
"--------------------------------- \n"
"Capture Filters are used to filter out uninteresting packets already at capture time. This is done to reduce the size of the resulting capture (file) and is especially useful on high traffic networks or for long term capturing. \n"
" \n"
"Ethereal uses the pcap (libpcap/WinPcap) filter language for capture filters. This language is explained in the tcpdump man page (http://www.tcpdump.org). \n"
" \n"
"Note: This capture filter language is different from the one used for the Ethereal display filters! \n"
" \n"
"------------------------------------------------- \n"
" \n"
"Some common examples: \n"
"--------------------- \n"
"Example Ethernet: capture all traffic to and from the Ethernet address 08.00.08.15.ca.fe \n"
" \n"
"ether 08.00.08.15.ca.fe \n"
" \n"
"Example IP: capture all traffic to and from the IP address 192.168.0.10 \n"
" \n"
"host 192.168.0.10 \n"
" \n"
"Example TCP: capture all traffic to and from the TCP port 80 (http) of all machines \n"
" \n"
"tcp port 80 \n"
" \n"
"Examples combined: capture all traffic to and from 192.168.0.10 except http \n"
" \n"
"host 192.168.0.10 and not tcp port 80 \n"
" \n"
"Beware: if you capture TCP/IP traffic with the primitives \"host\" or \"port\", you will not see the ARP traffic belonging to it! \n"
" \n"
"------------------------------------------------- \n"
" \n"
"Capture Filter Syntax: \n"
"---------------------- \n"
"The following is a short description of the capture filter language syntax. For a further reference, have a look at: http://www.tcpdump.org/tcpdump_man.html \n"
" \n"
"A capture filter takes the form of a series of primitive expressions, connected by conjunctions (and/or) and optionally preceeded by not: \n"
" \n"
"[not] primitive [and|or [not] primitive ...] \n"
" \n"
"A primitive is simply one of the following: \n"
" \n"
"[src|dst] host <host> \n"
" \n"
"This primitive allows you to filter on a host IP address or name. You can optionally preceed the primitive with the keyword src|dst to specify that you are only interested in source or destination addresses. If these are not present, packets where the specified address appears as either the source or the destination address will be selected. \n"
" \n"
"ether [src|dst] host <ehost> \n"
" \n"
"This primitive allows you to filter on Ethernet host addresses. You can optionally includethe keyword src|dst between the keywords ether and host to specify that you are only interested in source or destination addresses. If these are not present, packets where the specified address appears in either the source or destination address will be selected. \n"
" \n"
"gateway host <host> \n"
" \n"
"This primitive allows you to filter on packets that used host as a gateway. That is, where the Ethernet source or destination was host but neither the source nor destination IP address was host. \n"
" \n"
"[src|dst] net <net> [{mask <mask>}|{len <len>}] \n"
" \n"
"This primitive allows you to filter on network numbers. You can optionally preceed this primitive with the keyword src|dst to specify that you are only interested in a source or destination network. If neither of these are present, packets will be selected that have the specified network in either the source or destination address. In addition, you can specify either the netmask or the CIDR prefix for the network if they are different from your own. \n"
" \n"
"[tcp|udp] [src|dst] port <port> \n"
" \n"
"This primitive allows you to filter on TCP and UDP port numbers. You can optionally preceed this primitive with the keywords src|dst and tcp|udp which allow you to specify that you are only interested in source or destination ports and TCP or UDP packets respectively. The keywords tcp|udp must appear before src|dst. \n"
"If these are not specified, packets will be selected for both the TCP and UDP protocols and when the specified address appears in either the source or destination port field. \n"
" \n"
"less|greater <length> \n"
" \n"
"This primitive allows you to filter on packets whose length was less than or equal to the specified length, or greater than or equal to the specified length, respectively. \n"
" \n"
"ip|ether proto <protocol> \n"
" \n"
"This primitive allows you to filter on the specified protocol at either the Ethernet layer or the IP layer. \n"
" \n"
"ether|ip broadcast|multicast \n"
" \n"
"This primitive allows you to filter on either Ethernet or IP broadcasts or multicasts. \n"
" \n"
"<expr> relop <expr> \n"
" \n"
"This primitive allows you to create complex filter expressions that select bytes or ranges of bytes in packets. Please see the tcpdump man pages for more details. \n"
};
#define CAPTURE_FILTERS_PARTS 1
#define CAPTURE_FILTERS_SIZE 4397

45
help/display_filters.h Normal file
View File

@ -0,0 +1,45 @@
/* THIS FILE IS AUTOMATICALLY GENERATED, DO NOT MODIFY!!! */
const char *display_filters_part[] = {
"Filtering packets while viewing \n"
"------------------------------- \n"
"After capturing packets or loading some network traffic from a file, Ethereal will display the packet data immediately on the screen. \n"
" \n"
"Using display filters, you can choose which packets should (not) be shown on the screen. This is useful to reduce the \"noice\" usually on the network, showing only the packets you want to. So you can concentrate on the things you are really interested in. \n"
" \n"
"The display filter will not affect the data captured, it will only select for you which packets of the captured data are displayed on the screen. \n"
" \n"
"Everytime you change the filter string, all packets will be reread from the capture file (or from memory), and processed by the display filter \"machine\". Packet by packet, this \"machine\" is asked, if this particular packet should be shown or not. \n"
" \n"
"Ethereal offers a very powerful display filter language for this. It can be used for a wide range of purposes, from simply: \"show only packets from a specific IP address\", or on the other hand, to very complex filters like: \"find all packets where a special application specific flag is set\". \n"
" \n"
"Note: This display filter language is different from the one used for the Ethereal capture filters! \n"
" \n"
"------------------------------------------------- \n"
" \n"
"Some common examples: \n"
"--------------------- \n"
"Example Ethernet: display all traffic to and from the Ethernet address 08.00.08.15.ca.fe \n"
" \n"
"eth.addr==08.00.08.15.ca.fe \n"
" \n"
"Example IP: display all traffic to and from the IP address 192.168.0.10 \n"
" \n"
"ip.addr==192.168.0.10 \n"
" \n"
"Example TCP: display all traffic to and from the TCP port 80 (http) of all machines \n"
" \n"
"tcp.port==80 \n"
" \n"
"Examples combined: display all traffic to and from 192.168.0.10 except http \n"
" \n"
"ip.addr==192.168.0.10 && tcp.port!=80 \n"
" \n"
"Beware: The filter string builds a logical expression, which must be true to show the packet. The && is a \"logical and\", \"A && B\" means: A must be true AND B must be true to show the packet (it doesn't mean: A will be shown AND B will be shown). \n"
" \n"
"------------------------------------------------- \n"
" \n"
"Hints: \n"
"Filtering can lead to side effects, which are sometimes not obvious at first sight. Example: If you capture TCP/IP traffic with the primitive \"ip\", you will not see the ARP traffic belonging to it, as this is a lower protocol layer than IP! \n"
};
#define DISPLAY_FILTERS_PARTS 1
#define DISPLAY_FILTERS_SIZE 2358

1746
help/faq.h Normal file
View File

File diff suppressed because it is too large Load Diff

36
help/overview.h Normal file
View File

@ -0,0 +1,36 @@
/* THIS FILE IS AUTOMATICALLY GENERATED, DO NOT MODIFY!!! */
const char *overview_part[] = {
"Ethereal is a GUI network protocol analyzer. \n"
" \n"
"It lets you interactively browse packet data from a live network or from a previously saved capture file. \n"
" \n"
"See: http://www.ethereal.com for new versions, documentation, ... \n"
" \n"
"Ethereal's native capture file format is libpcap format, which is also the format used by tcpdump and various other tools. So Ethereal can read capture files from: \n"
" \n"
"-libpcap/WinPcap \n"
"-snoop and atmsnoop \n"
"-Shomiti/Finisar Surveyor \n"
"-Novell LANalyzer \n"
"-Network General/Network Associates DOS-based Sniffer (compressed or uncompressed), \n"
"-Microsoft Network Monitor \n"
"-AIX's iptrace \n"
"-Cinco Networks NetXRay \n"
"-Network Associates Windows-based Sniffer \n"
"-AG Group/WildPackets EtherPeek/TokenPeek/AiroPeek \n"
"-RADCOM's WAN/LAN analyzer \n"
"-Lucent/Ascend router debug output \n"
"-HP-UX's nettl \n"
"-the dump output from Toshiba's ISDN routers \n"
"-the output from i4btrace from the ISDN4BSD project \n"
"-the output in IPLog format from the Cisco Secure Intrusion Detection System, \n"
"-pppd logs (pppdump format) \n"
"-the output from VMS's TCPIPtrace utility \n"
"-the text output from the DBS Etherwatch VMS utility \n"
"-traffic capture files from Visual Networks' Visual UpTime \n"
"-the output from CoSine L2 debug \n"
" \n"
"There is no need to tell Ethereal what type of file you are reading; it will determine the file type by itself. Ethereal is also capable of reading any of these file formats if they are compressed using gzip. Ethereal recognizes this directly from the file; the '.gz' extension is not required for this purpose. \n"
};
#define OVERVIEW_PARTS 1
#define OVERVIEW_SIZE 1521

117
help/well_known.h Normal file
View File

@ -0,0 +1,117 @@
/* THIS FILE IS AUTOMATICALLY GENERATED, DO NOT MODIFY!!! */
const char *well_known_part[] = {
"Well known things \n"
"----------------- \n"
"Following is a simple selection of well known numbers, useful when working with Ethereal. This is not intended to replace comprehensive network documentation. \n"
" \n"
" \n"
"Ethernet addresses [RFC 1700]: \n"
"------------------------------ \n"
"ff:ff:ff:ff:ff:ff Broadcast, send to all nodes \n"
" \n"
"Ethernet type field: \n"
"-------------------- \n"
" 0 - 45 invalid \n"
"46 - 1500 length field (Ethernet-II) \n"
" 0x0800 IP(V4), internet protocol version 4 \n"
" 0x0806 ARP, address resolution protocol \n"
" 0x8137 IPX, internet packet exchange (Novell) \n"
" \n"
"IP addresses: \n"
"------------- \n"
"127.0.0.0 - 127.255.255.255 local loopback, should never appear on the network \n"
"224.0.0.0 - 239.255.255.255 multicasting [RFC1112], transmission to a host group \n"
" 255.255.255.255 limited Broadcast, send to all nodes \n"
" \n"
"IP private addresses [RFC 1597]: \n"
"-------------------------------- \n"
"The following IP addresses will not be routed, and should be used for private networks: \n"
" 10.0.0.0 - 10.255.255.255 private in Class A \n"
" 172.16.0.0 - 172.31.255.255 private in Class B \n"
"192.168.0.0 - 192.168.255.255 private in Class C \n"
" \n"
"IP address classes: \n"
"------------------- \n"
" 0.1.0.0 - 126.0.0.0 Class A \n"
"128.0.0.0 - 191.255.0.0 Class B \n"
"192.0.1.0 - 223.255.255.0 Class C \n"
"224.0.0.0 - 239.255.255.255 Class D \n"
"240.0.0.0 - 247.255.255.255 Class E \n"
" \n"
"IP protocols: \n"
"------------- \n"
" 1 ICMP internet control message protocol v 4 \n"
" 6 TCP transmission control protocol \n"
"17 UDP user datagram protocol \n"
"58 ICMPv6 internet control message protocol v 6 \n"
" \n"
"TCP/UDP ports [RFC 1700]: \n"
"------------------------- \n"
" 20 FTP-data file transfer protocol \n"
" 21 FTP-ctrl file transfer protocol \n"
" 22 SSH secure shell \n"
" 23 Telnet telecommunications networking \n"
" 25 SMTP simple mail transfer protocol \n"
" 53 DNS domain name server \n"
" 67 BOOTPS bootstrap protocol server / DHCP \n"
" 68 BOOTPC bootstrap protocol client / DHCP \n"
" 69 TFTP trivial file transfer protocol \n"
" 80 HTTP hypertext transfer protocol \n"
" 102 ISO-TSAP iso on tcp \n"
" 110 POP3 post office protocol version 3 \n"
" 119 NNTP network news transfer protocol \n"
" 123 NTP network time protocol \n"
" 137 NETBIOS name service \n"
" 138 NETBIOS datagram \n"
" 139 NETBIOS session \n"
" 143 IMAP interim mail access protocol v2 \n"
" 161 SNMP simple network management protocol \n"
" 194 IRC internet relay chat protocol \n"
" 389 LDAP lightweight directory access protocol \n"
" 443 HTTPS http through SSL \n"
"2401 CVSPSERVER concurrent versioning system \n"
" \n"
" \n"
" \n"
"RFC References: \n"
"--------------- \n"
"ARP RFC 826 \"An Ethernet Address Resolution Protocol\" \n"
"BOOTP RFC 951 \"BOOTSTRAP PROTOCOL (BOOTP)\" \n"
"CSLIP RFC 1144 \"Compressing TCP/IP Headers for Low-Speed Serial Links\" \n"
"DHCP RFC 2131 \"Dynamic Host Configuration Protocol\" \n"
"DNS RFC 1034,1035 \"DOMAIN NAMES\" \n"
"FTP RFC 959 \"FILE TRANSFER PROTOCOL (FTP)\" \n"
"HTTP RFC 2068 \"Hypertext Transfer Protocol -- HTTP/1.1\" \n"
"ICMP RFC 792 \"INTERNET CONTROL MESSAGE PROTOCOL\" \n"
"IMAPv4 RFC 2060 \"INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1\" \n"
"IPv4 RFC 791 \"INTERNET PROTOCOL\" \n"
"IP RFC 894 \"Transmission of IP Datagrams over Ethernet Networks\" \n"
"IP RFC 950 \"Internet Standard Subnetting Procedure\" \n"
"IP RFC 1112 \"Host Extensions for IP Multicasting\" \n"
"IP RFC 1812 \"Requirements for IP Version 4 Routers\" \n"
"MIME RFC 2045-2049 \"Multipurpose Internet Mail Extensions (MIME)\" \n"
"NetBIOS RFC 1001,1002 \"NetBIOS SERVICE ON A TCP/UDP TRANSPORT\" \n"
"NFS RFC 1014,1057,1094,1813 \"XDR/SUN-RPC/NFS/NFSv3\" \n"
"NNTP RFC 977 \"Network News Transfer Protocol\" \n"
"NTP RFC 958 \"Network Time Protocol (NTP)\" \n"
"POP2 RFC 918 \"POST OFFICE PROTOCOL\" \n"
"POP3 RFC 1725 \"Post Office Protocol - Version 3\" \n"
"PPP RFC 1661 \"The Point-to-Point Protocol (PPP)\" \n"
"PPP-MP RFC 1990 \"The PPP Multilink Protocol (MP)\" \n"
"RARP RFC 903 \"A Reverse Address Resolution Protocol\" \n"
"SLIP RFC 1055 \"TRANSMISSION OF IP DATAGRAMS OVER SERIAL LINES: SLIP\" \n"
"SMTP RFC 821,822 \"SIMPLE MAIL TRANSFER PROTOCOL\" \n"
"SNMP RFC 1157,1901-10,2271-75 \"A Simple Network Management Protocol (SNMP)\" \n"
"UDP RFC 768 \"User Datagram Protocol\" \n"
"URN RFC 1737 \"Functional Requirements for Uniform Resource Names\" \n"
"URL RFC 1738 \"Uniform Resource Locators (URL)\" \n"
"TCP RFC 793 \"TRANSMISSION CONTROL PROTOCOL\" \n"
"TELNET RFC 854,855 \"TELNET PROTOCOL SPECIFICATION\" \n"
"TELNET RFC 1700 see: TELNET OPTIONS \n"
"TFTP RFC 783 \"THE TFTP PROTOCOL (REVISION 2)\" \n"
" \n"
"RFC 1166 \"INTERNET NUMBERS\" list of assigned IP addresses \n"
"RFC 1700 \"ASSIGNED NUMBERS\" Various assigned numbers, e.g. TCP/UDP ports \n"
};
#define WELL_KNOWN_PARTS 1
#define WELL_KNOWN_SIZE 4649