Information in this guide is subject to change without notice. Companies, names, and data used in
examples herein are fictitious unless otherwise noted. No part of this guide may be reproduced or
transmitted in any form or by any means, electronic or mechanical, for any purpose, without the
express written permission of WatchGuard Technologies, Inc.
trademarks of WatchGuard Technologies, Inc. in the United States and other countries. This product
is covered by one or more pending patent applications.
All other trademarks and tradenames are the property of their respective owners.
Printed in the United States of America.
DocVer:WatchGuard Firebox System 4.6 Reference Guide - 4.6.1
ii
Table of Contents
CHAPTER 1 Internet Protocol Reference............................................. 1
Internet Protocol header................................................................1
Internet Protocol options............................................................... 5
Transfer protocols...........................................................................5
Standard ports and random ports.................................................. 7
Index ............................................................................................... 73
iv
CHAPTER 1Internet Protocol Reference
Internet Protocol (IP) specifies the format of packets and the addressing scheme for
sending data over the Internet. By itself, it functions like a postal system allowing you
to address a package and drop it into the system. There is, however, no direct link
between you and the recipient. In other words, there is no package.
Most networks combine IP with higher-level protocols like Transmission Control
Protocol (TCP). Unlike simple IP, TCP/IP establishes a connection between two host
servers so that they can send messages back and forth. TCP/IP provides the
“packaging.”
Internet Protocol header
Internet Protocol (IP) is an Internet standard and enables the shipment of datagrams
– self-contained packets of information that include their own address and delivery
instructions. IP prepends a header to each datagram. The IP header contains a
minimum of twelve attributes as well as additional optional attributes.
AttributeSizeDescription
Version4 bitsIP format number (Current version = 4)
IHL4 bitsHeader length in 32-bit words (Minimum = 5)
TOS8 bitsType of service sets routing priorities. It is generally
Tot _L en16 bitsTotal length of packet measured in octets. It is used in
ID16 bitsPacket ID, used for reassembling fragments.
Flags3 bitsMiscellaneous flags
Frag_Off13 bitsIdentifies fragment part for this packet.
TTL8 bitsTime to live. It sets the maximum time the datagram
under-utilized because few application layers can set it.
reassembling fragments.
remains alive in the system.
Reference Guide1
Internet Protocol header
AttributeSizeDescription
Protocol8 bitsIP protocol number. Indicates which of TCP, UDP, ICMP,
Check16 bitsChecksum for the IP header
Sour_Addr32 bitsSource IP address
Dest_Addr32 bitsDestination IP address
Options24 bitsIP Options (Present if IHL is 6)
IP header number list
The IP Protocol header contains an 8-bit field that identifies the protocol for the
Transport layer for the datagram.
KeywordNumberProtocol
ICMP1 Internet Control Message
IGMP2 Internet Group Management
GGP 3 Gateway-to-Gateway
IP4 IP-within-IP (encapsulation)
ST5 Stream
TCP 6 Transmission Control Protocol
UCL 7 UCL
EGP 8 Exterior Gateway Protocol
IGP 9 Any private interior gateway
BBN-RCC-MON 10BBN RCC Monitoring
NVP-II11Network Voice Protocol
PUP 12PUP
ARGUS 13ARGUS
EMCON 14EMCON
XNET15Cross Net Debugger
CHAOS 16Chaos
UDP 17User Datagram Protocol
MUX 18Multiplexing
DCN-MEAS19DCN Measurement Subsystems
HMP 20Host Monitoring
PRM 21Packet Radio Measurement
XNS-IDP 22XEROX NS IDP
TRUNK-1 23Trunk-1
TRUNK-2 24Trunk-2
LEAF-125Leaf-1
LEAF-226Leaf-2
IGMP, or other Transport protocol is inside.
0 Reserved
2
Internet Protocol header
KeywordNumberProtocol
RDP 27Reliable Data Protocol
IRTP28Internet Reliable Transaction
ISO-TP4 29ISO Transport Protocol Class 4
NETBLT30Bulk Data Transfer Protocol
MFE-NSP 31MFE Network Services Protocol
MERIT-INP 32MERIT Internodal Protocol
SEP 33Sequential Exchange Protocol
3PC 34Third Party Connect Protocol
IDPR35Inter-Domain Policy Routing Protocol
XTP 36XTP
DDP 37Datagram Delivery Protocol
IDPR-CMTP 38IDPR Control Message Transport Protocol
Internet Protocol options are variable-length additions to the standard IP header. IP
options can either be of limited usefulness or very dangerous. There are several kinds
of IP options:
Security
Control routing of IP packets that carry sensitive data. Security options are
rarely supported.
Stream ID (SID)
The stream ID option is rarely supported.
Source Routing
Both the loose source route option and the strict source route option enable
the source of an Internet packet to provide routing information. Source
routing options can be very dangerous, because a clever attacker might use
them to masquerade as another site. However, loose source routing and the
traceroute facility can also help debug some obscure routing problems.
Record Route
The record route option was originally intended for use in testing the Internet.
Unfortunately, record route can record only ten IP addresses. On the present
Internet, typical long-haul transmissions can involve twenty or thirty hops,
rendering the record route option obsolete.
Internet Protocol options
Time Stamp
The time stamp option helps measure network propagation delays. This task
is done more effectively, however, with higher-level time protocols or timestamp messages.
Because most applications make it very obscure or difficult to use IP options, they are
rarely used.
Transfer protocols
The IP protocol encapsulates information contained in the transport layer. The
transport layer has several protocols that specify how to transmit data between
applications: for example, UDP, TCP, ICMP, and others.
UDP
User Datagram Protocol (UDP) is a connectionless, potentially unreliable datagram
protocol. It trades reliability for speed and low overhead. To ensure accurate
transmission, it requires that the application layer verify that packets arrive at their
destination.
Characteristics of UDP include:
Reference Guide5
Transfer protocols
• Often used for services involving the transfer of small amounts of data where
retransmitting a request is not a problem.
• Used for services such as time synchronization in which an occasionally lost
packet will not affect continued operation. Many systems using UDP resend
packets at a constant rate to inform their peers about interesting events.
• Primarily used on LANs, in particular for NFS services where its low overhead
gives it a substantial performance advantage. A lack of congestion control
means that using UDP for bulk data transfer over long-haul connections is not
recommended.
• Supports broadcasts.
• Provides abstraction of ports.
• A connection is described by its source and destination ports and its source and
destination IP addresses. In typical usage, port numbers below 1024 are
reserved for well-known services (destinations), and the client side is supposed
to use ports above 1023 for the source of the connection. However, this rule has
many notable exceptions. In particular, NFS (port 2049) and Archie (port 1525)
use server ports at numbers above 1024. Some services use the same source and
destination port for server-to-server connections. Common examples are DNS
(53), NTP (123), syslog (514), and RIP (520).
TCP
Transmission Control Protocol (TCP) provides reliable stream-oriented services. It
trades speed and overhead for increased reliability. Like UDP, TCP provides source
and destination ports that are used in a similar fashion.
TCP uses a rather complicated state machine to manage connections. There are
several attribute bits that control the state of a connection. Three very important
attribute bits of TCP packets are the SYN, ACK, and FIN bits. The SYN bit is set only
on the first packet sent in each direction for a given connection. The ACK bit is set
when the other side is acknowledging the receipt of data to the peer. The FIN bit is set
when either side chooses to close the connection.
ICMP
The Internet Control Message Protocol (ICMP) is used primarily to deliver error
information about other services. It is otherwise quite similar in practical operation to
UDP. That is, it is connectionless and does not guarantee that packets are delivered to
their destination. One dangerous ICMP packet is the ICMP redirect packet, which can
change routing information on the machines that receive it.
Other protocols
The vast majority of the traffic on the Internet uses one of the three protocols
mentioned above. There are some others that are of interest:
IGMP (Internet Group Multicast Protocol)
A protocol supporting multicasts used by SGI’s Dogfight game.
6
IPIP (IP-within-IP)
An encapsulation protocol used to build virtual networks over the Internet.
GGP (Gateway-Gateway Protocol)
A routing protocol used between autonomous systems.
GRE
A protocol used for PPTP.
ESP
An encryption protocol used for IPSec.
Standard ports and random ports
UDP and TCP encapsulate information contained within the application layer. The
appropriate application processes are designated by source and destination port
numbers. These port numbers, along with the source and destination IP addresses,
specify a unique connection on the Internet.
Standard ports and random ports
For example, it is reasonable to have two telnet sessions from one host to another.
However, since telnet uses a well-known service number of 23, something must
distinguish these two connections. The other port in these cases will be a port that is
typically greater than 1023. This alternative port designation is dynamically allocated
by the operating system on the client side.
Random ports can cause a great amount of trouble if they happen to match a wellknown service on a port above 1023. If some client machine assigns a random port of
2049, the connection may mysteriously fail. Similar problems can occur with the X
Window and Archie services.
In practice, most operating systems cycle port numbers between 1024 and a number
somewhere in the range of 2100, depending on how many TCP connections are
currently open and whether a recently closed connection used a similar port number.
This makes the above problem rare.
Reference Guide7
Standard ports and random ports
8
CHAPTER 2Content Types
A content-type header is used by applications to determine what kind of data they
are receiving, thus allowing them to make decisions about how it should be handled.
It allows clients to correctly identify and display video clips, images, sound, or nonHTML data. People are probably most familiar with the MIME content-types sent in
e-mail.
The WatchGuard Proxied HTTP service uses content-type headers to determine
whether to allow or deny an HTTP transaction. Use the Policy Manager to configure
the Proxied HTTP service to allow or deny content-types. Content types are also used
in SMTP and are configurable in the SMTP proxy. This chapter contains a list of the
more commonly used MIME content-types. The MIME content-types are written as
follows:
type/sub-type
Wildcards may be used to select all sub-types within a type, thereby denying all or
allowing all of that MIME type. For example, to allow all content-types that are text
(including text/enriched, text/plain, and others), use the content-type
New, registered MIME content-types appear regularly. WatchGuard
recommends frequent checking of an online reference for the most current list.
One source of current MIME types is
Well-known services are a combination of port number and transport protocol for
specific, standard applications. This chapter contains several tables that list service
names, port number, protocol and description.
Ports used by WatchGuard products
The WatchGuard Firebox, Management Station, and LiveSecurity Event Processor
(LSEP) use several ports during normal functioning.
Port #ProtocolPurpose
4100TCPAuthentication applet
4101TCPLSEP and Management Station
4107TCPLSEP and Firebox
Port #ProtocolUsed
By
4103TCPdbfetchConnect to webblocker.sealabs.com to retrieve
4102TCPFireboxUsed only in LSS 3.0x or earlier for logs
Purpose
WebBlocker database
Reference Guide19
Ports used by Microsoft products
Ports used by Microsoft products
Port #ProtocolPurpose
137, 138UDPBrowsing
67, 68UDPDHCP Lease
135TCPDHCP Manager
138
139
135TCPDNS Administration
53UDPDNS Resolution
139TCPEvent Viewer
139TCPFile Sharing
137, 138
139
138UDPNetLogon
137, 138
139
139TCPPerformance Monitor
1723
47
137, 138
139
139TCPRegistry Editor
139TCPServer Manager
137, 138
139
139TCPUser Manager
139TCPWinNT Diagnostics
137, 138
139
42TCPWINS Replication
135TCPWINS Manager
137TCPWINS Registration
UDP
TCP
UDP
TCP
UDP
TCP
TCP
IP
UDP
TCP
UDP
TCP
UDP
TCP
Directory Replication
Logon Sequence
Pass Through Validation
PPTP
Printing
Trust s
WinNT Secure Channel
Port #ProtocolPurpose
135TCPClient/Server
135TCPExchange Administrator
143TCPIMAP
993TCPIMAP (SSL)
389TCPLDAP
636TCPLDAP (SSL)
20
Communications
Loading...
+ 54 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.