Address objects can represent a single IP address or a range of IP addresses. Address groups are composed of address objects and other address groups.

Address objects and address groups are used in policy routes, security policies, application patrol, content filtering, and VPN connection policies. For example, addresses are used to specify where content restrictions apply in content filtering. Please see the respective sections for more information about how address objects and address groups are used in each one.

Address groups are composed of address objects and address groups. The sequence of members in the address group is not important.

The address screens are used to create, maintain, and remove addresses.

The Address screen provides a summary of all addresses in the Zyxel Device. Click a column’s heading cell to sort the table entries by that column’s criteria. Click the heading cell again to reverse the sort order.

The Object > Address > Address > Add/Edit screen allows you to create a new address or edit an existing one.

The following table describes the labels in this screen.

The Address Group screen provides a summary of all address groups. Click a column’s heading cell to sort the table entries by that column’s criteria. Click the heading cell again to reverse the sort order.

The Address Group Add/Edit screen allows you to create a new address group or edit an existing one.

Use this screen to update the database of country-to-IP and continent-to-IP address mappings and manually configure custom country-to-IP and continent-to-IP address mappings in geographic address objects. You can then use geographic address objects in security policies to forward or deny traffic to whole countries or regions.

Click a column’s heading cell to sort the table entries by that column’s criteria. Click the heading cell again to reverse the sort order.The following table describes the labels in this screen.

This screen allows you to create a new geography-to-IP address mapping. The following table describes the labels in this screen.

Use service objects to define TCP applications, UDP applications, and ICMP messages. You can also create service groups to refer to multiple service objects in other features.

IP protocols are based on the eight-bit protocol field in the IP header. This field represents the next-level protocol that is sent in this packet. This section discusses three of the most common IP protocols.

Computers use Transmission Control Protocol (TCP, IP protocol 6) and User Datagram Protocol (UDP, IP protocol 17) to exchange data with each other. TCP guarantees reliable delivery but is slower and more complex. Some uses are FTP, HTTP, SMTP, and TELNET. UDP is simpler and faster but is less reliable. Some uses are DHCP, DNS, RIP, and SNMP.

TCP creates connections between computers to exchange data. Once the connection is established, the computers exchange data. If data arrives out of sequence or is missing, TCP puts it in sequence or waits for the data to be re-transmitted. Then, the connection is terminated.

In contrast, computers use UDP to send short messages to each other. There is no guarantee that the messages arrive in sequence or that the messages arrive at all.

Both TCP and UDP use ports to identify the source and destination. Each port is a 16-bit number. Some port numbers have been standardized and are used by low-level system processes; many others have no particular meaning.

Unlike TCP and UDP, Internet Control Message Protocol (ICMP, IP protocol 1) is mainly used to send error messages or to investigate problems. For example, ICMP is used to send the response if a computer cannot be reached. Another use is ping. ICMP does not guarantee delivery, but networks often treat ICMP messages differently, sometimes looking at the message itself to decide where to send it.

Use service objects to define IP protocols.

These objects are used in policy routes and security policies.

Use service groups when you want to create the same rule for several services, instead of creating separate rules for each service. Service groups may consist of services and other service groups. The sequence of members in the service group is not important.

Use Reference in a screen to view which configuration settings reference to the object.

For example, go to Object > Service. select an entry, then click Reference to open the References screen. The References screen displays which settings are using the selected entry.

This table describes the fields in this screen.

The Service summary screen provides a summary of all services and their definitions. In addition, this screen allows you to add, edit, and remove services.

Click a column’s heading cell to sort the table entries by that column’s criteria. Click the heading cell again to reverse the sort order.

The Service Add/Edit screen allows you to create a new service or edit an existing one.

The Service Group summary screen provides a summary of all service groups. In addition, this screen allows you to add, edit, and remove service groups.

The following table describes the labels in this screen. See The Service Group Add/Edit Screen for more information as well.

The Service Group Add/Edit screen allows you to create a new service group or edit an existing one. The following table describes the labels in this screen.

Set up zones to configure network security and network policies in the Zyxel Device. A zone is a group of interfaces and/or VPN tunnels. The Zyxel Device uses zones instead of interfaces in many security and policy settings, such as Security Policy rules, Security Service, and remote management.

Zones cannot overlap. Each Ethernet interface, VLAN interface, bridge interface, PPPoE/PPTP interface and VPN tunnel can be assigned to at most one zone. Virtual interfaces are automatically assigned to the same zone as the interface on which they run.

Zones effectively divide traffic into three types--intra-zone traffic, inter-zone traffic, and extra-zone traffic.

Inter-zone traffic is traffic between interfaces or VPN tunnels in different zones.

The Zone screen provides a summary of all zones. In addition, this screen allows you to add, edit, and remove zones.

The Zone Edit screen allows you to add or edit a zone.

Use schedules to set up one-time and recurring schedules for policy routes, security policies, application patrol, and content filtering. The Zyxel Device supports one-time and recurring schedules. One-time schedules are effective only once, while recurring schedules usually repeat. Both types of schedules are based on the current date and time in the Zyxel Device.

One-time schedules begin on a specific start date and time and end on a specific stop date and time. One-time schedules are useful for long holidays and vacation periods.

Recurring schedules begin at a specific start time and end at a specific stop time on selected days of the week (Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, and Saturday). Recurring schedules always begin and end in the same day. Recurring schedules are useful for defining the workday and off-work hours.

The Schedule screen provides a summary of all schedules in the Zyxel Device.

The One-Time Schedule Add/Edit screen allows you to define a one-time schedule or edit an existing one.

The Recurring Schedule Add/Edit screen allows you to define a recurring schedule or edit an existing one.

The Schedule Group screen provides a summary of all groups of schedules in the Zyxel Device. The following table describes the fields in the above screen.

The Schedule Group Add/Edit screen allows you to define a schedule group or edit an existing one.Object > The following table describes the fields in the above screen.