
Chapter 14 Firewalls
P-2602HWLNI User’s Guide
241
If an initiation packet originates on the LAN, this means that someone is trying to make a
connection from the LAN to the Internet. Assuming that this is an acceptable part of the
security policy (as is the case with the default policy), the connection will be allowed. A cache
entry is added which includes connection information such as IP addresses, TCP ports,
sequence numbers, etc.
When the ZyXEL Device receives any subsequent packet (from the Internet or from the LAN),
its connection information is extracted and checked against the cache. A packet is only
allowed to pass through if it corresponds to a valid connection (that is, if it is a response to a
connection which originated on the LAN).
14.5.4 UDP/ICMP Security
UDP and ICMP do not themselves contain any connection information (such as sequence
numbers). However, at the very minimum, they contain an IP address pair (source and
destination). UDP also contains port pairs, and ICMP has type and code information. All of
this data can be analyzed in order to build "virtual connections" in the cache.
For instance, any UDP packet that originates on the LAN will create a cache entry. Its IP
address and port pairs will be stored. For a short period of time, UDP packets from the WAN
that have matching IP and UDP information will be allowed back in through the firewall.
A similar situation exists for ICMP, except that the ZyXEL Device is even more restrictive.
Specifically, only outgoing echoes will allow incoming echo replies, outgoing address mask
requests will allow incoming address mask replies, and outgoing timestamp requests will
allow incoming timestamp replies. No other ICMP packets are allowed in through the firewall,
simply because they are too dangerous and contain too little tracking information. For
instance, ICMP redirect packets are never allowed in, since they could be used to reroute
traffic through attacking machines.
14.5.5 Upper Layer Protocols
Some higher layer protocols (such as FTP and RealAudio) utilize multiple network
connections simultaneously. In general terms, they usually have a "control connection" which
is used for sending commands between endpoints, and then "data connections" which are used
for transmitting bulk information.
Consider the FTP protocol. A user on the LAN opens a control connection to a server on the
Internet and requests a file. At this point, the remote server will open a data connection from
the Internet. For FTP to work properly, this connection must be allowed to pass through even
though a connection from the Internet would normally be rejected.
In order to achieve this, the ZyXEL Device inspects the application-level FTP data.
Specifically, it searches for outgoing "PORT" commands, and when it sees these, it adds a
cache entry for the anticipated data connection. This can be done safely, since the PORT
command contains address and port information, which can be used to uniquely identify the
connection.
Any protocol that operates in this way must be supported on a case-by-case basis. You can use
the web configurator’s Custom Ports feature to do this.
Summary of Contents for P-2602HWLNI
Page 2: ......
Page 7: ...Safety Warnings P 2602HWLNI User s Guide 7...
Page 8: ...Safety Warnings P 2602HWLNI User s Guide 8...
Page 24: ...Table of Contents P 2602HWLNI User s Guide 24...
Page 32: ...List of Figures P 2602HWLNI User s Guide 32...
Page 38: ...List of Tables P 2602HWLNI User s Guide 38...
Page 39: ...39 PART I Introduction Introducing the ZyXEL Device 41 Introducing the Web Configurator 49...
Page 40: ...40...
Page 60: ...Chapter 2 Introducing the Web Configurator P 2602HWLNI User s Guide 60...
Page 62: ...62...
Page 86: ...Chapter 5 Bandwidth Management Wizard P 2602HWLNI User s Guide 86...
Page 98: ...Chapter 6 Status Screens P 2602HWLNI User s Guide 98...
Page 100: ...100...
Page 154: ...Chapter 9 Wireless LAN P 2602HWLNI User s Guide 154...
Page 166: ...Chapter 10 Network Address Translation NAT Screens P 2602HWLNI User s Guide 166...
Page 167: ...167 PART IV VoIP Voice 169 VoIP Trunking 211 Phone Usage 227...
Page 168: ...168...
Page 226: ...Chapter 12 VoIP Trunking P 2602HWLNI User s Guide 226...
Page 230: ...Chapter 13 Phone Usage P 2602HWLNI User s Guide 230...
Page 232: ...232...
Page 264: ...Chapter 15 Firewall Configuration P 2602HWLNI User s Guide 264...
Page 268: ...Chapter 16 Content Filtering P 2602HWLNI User s Guide 268...
Page 274: ...Chapter 17 Introduction to IPSec P 2602HWLNI User s Guide 274...
Page 309: ...Chapter 19 Certificates P 2602HWLNI User s Guide 309 Figure 173 My Certificate Details...
Page 320: ...Chapter 19 Certificates P 2602HWLNI User s Guide 320 Figure 181 Trusted Remote Host Details...
Page 326: ...326...
Page 330: ...Chapter 20 Static Route P 2602HWLNI User s Guide 330...
Page 338: ...Chapter 21 Bandwidth Management P 2602HWLNI User s Guide 338...
Page 342: ...Chapter 22 Dynamic DNS Setup P 2602HWLNI User s Guide 342...
Page 360: ...Chapter 23 Remote Management Configuration P 2602HWLNI User s Guide 360...
Page 372: ...Chapter 24 Universal Plug and Play UPnP P 2602HWLNI User s Guide 372...
Page 374: ...374...
Page 380: ...Chapter 25 System P 2602HWLNI User s Guide 380...
Page 406: ...Chapter 28 Troubleshooting P 2602HWLNI User s Guide 406...
Page 422: ...Chapter 30 Diagnostic P 2602HWLNI User s Guide 422...
Page 432: ...Chapter 31 Product Specifications P 2602HWLNI User s Guide 432...
Page 434: ...434...
Page 446: ...Appendix A Setting up Your Computer s IP Address P 2602HWLNI User s Guide 446...
Page 482: ...Appendix F Legal Information P 2602HWLNI User s Guide 482...
Page 488: ...Appendix G Customer Support P 2602HWLNI User s Guide 488...