This publication, including all photographs, illustrations and software, is protected under
international copyright laws, with all rights reserved. Neither this manual, nor any of the material
contained herein, may be reproduced without written consent of the author.
Disclaimer
The information in this document is subject to change without notice. The manufacturer makes no
representations or warranties with respect to the contents hereof and specifically disclaim any
implied warranties of merchantability or fitness for any particular purpose. The manufacturer
reserves the right to revise this publication and to make changes from time to time in the content
hereof without obligation of the manufacturer to notify any person of such revision or changes.
Limitations of Liability
UNDER NO CIRCUMSTANCES SHALL D-LINK OR ITS SUPPLIERS BE LIABLE FOR
DAMAGES OF ANY CHARACTER (E.G. DAMAGES FOR LOSS OF PROFIT, SOFTWARE
RESTORATION, WORK STOPPAGE, LOSS OF SAVED DATA OR ANY OTHER
COMMERCIAL DAMAGES OR LOSSES) RESULTING FROM THE APPLICATION OR
IMPROPER USE OF THE D-LINK PRODUCT OR FAILURE OF THE PRODUCT, EVEN IF
D-LINK IS INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. FURTHERMORE,
D-LINK WILL NOT BE LIABLE FOR THIRD-PARTY CLAIMS AGAINST CUSTOMER FOR
LOSSES OR DAMAGES. D-LINK WILL IN NO EVENT BE LIABLE FOR ANY DAMAGES IN
EXCESS OF THE AMOUNT D-LINK RECEIVED FROM THE END-USER FOR THE
PRODUCT.
6.19. Configuring an SMTP Log Receiver .............................................................. 194
6.20. Setting up IDP for a Mail Server .................................................................... 195
7.1. Adding a NAT rule ....................................................................................... 205
7.2. Using NAT Pools ......................................................................................... 208
7.3. Enabling Traffic to a Protected Web Server in a DMZ ......................................... 210
7.4. Enabling Traffic to a Web Server on an Internal Network ....................................212
7.5. Translating Traffic to Multiple Protected Web Servers ........................................ 214
8.1. Creating an authentication user group ............................................................... 226
8.2. User Authentication Setup for Web Access. ....................................................... 226
8.3. Configuring a RADIUS server. ....................................................................... 227
9.1. Using a Proposal List .................................................................................... 249
9.2. Using a Pre-Shared key ................................................................................. 250
9.3. Using an Identity List .................................................................................... 251
9.4. Setting up a PSK based VPN tunnel for roaming clients ....................................... 254
9.5. Setting up a Self-signed Certificate based VPN tunnel for roaming clients ............... 255
9.6. Setting up a CA Server issued Certificate based VPN tunnel for roaming clients ....... 256
9.7. Setting Up Config Mode ................................................................................ 258
9.8. Using Config Mode with IPsec Tunnels ............................................................ 258
9.9. Setting up an LDAP server ............................................................................. 259
9.10. Setting up a PPTP server .............................................................................. 260
9.11. Setting up an L2TP server ............................................................................ 261
9.12. Setting up an L2TP Tunnel ...........................................................................262
10.1. Applying a Simple Bandwidth Limit .............................................................. 269
10.2. Limiting Bandwidth in Both Directions ........................................................... 270
10.3. Setting up SLB ........................................................................................... 285
12.1. A simple ZoneDefense scenario .................................................................... 301
11
Preface
Intended Audience
The target audience for this reference guide is Administrators who are responsible for configuring
and managing D-Link Firewalls which are running the NetDefendOS operating system. This guide
assumes that the reader has some basic knowledge of networks and network security.
Text Structure and Conventions
The text is broken down into chapters and sub-sections. Numbered sub-sections are shown in the
table of contents at the beginning. An index is included at the end of the document to aid with
alphabetical lookup of subjects.
Where a "See chapter/section" link (such as: see ) is provided in the main text this can be clicked to
take the reader directly to that reference.
Text that may appear in the user interface of the product is designated by being in bold case. Where
is term is being introduced for the first time or being stressed it may appear in a italics.
Where console interaction is shown in the main text outside of an example this will appear in a box
with a gray background.
Where a web address reference is shown in the text this will open the specified URL in a browser in
anewwindowwhenclicked(somesystemsmaynotallowthis).Forexample:
http://www.dlink.com.
Examples
Examples in the text are denoted by the header Example and appear with a gray background as
shown below. They contain a CLI example and/or a Web Interface example as appropriate. (The
accompanying "CLI Reference Guide" documents all CLI commands).
Example 1. Example Notation
Information about what the example is trying to achieve is found here, sometimes with an explanatory image.
CLI
The Command Line Interface example would appear here. It would start with the command prompt followed by
the command:
gw-world:/> somecommand someparameter=somevalue
Web Interface
The Web Interface actions for the example are shown here. They are typically a numbered list showing what
items in the tree-view list at the left of the interface or in the menu bar or in a context menu need to be opened
followed by information about the data items that need to be entered:
1. Go to Item X > Item Y > Item Z
2. Now enter:
• DataItem1: datavalue1
• DataItem2: datavalue2
12
Highlighted ContentPreface
Highlighted Content
Special sections of text which the reader should pay special attention to are indicated by icons on the
left hand side of the page followed by a short paragraph in italicized text. Such sections are of the
following types with the following purposes:
Note
This indicates some piece of information that is an addition to the preceding text. It
may concern something that is being emphasized, or something that is not obvious or
explicitly stated in the preceding text.
Tip
This indicates a piece of non-critical information that is useful to know in certain
situations but is not essential reading.
Caution
This indicates where the reader should be careful with their actions as an undesirable
situation may result if care is not exercised.
Important
This is an essential point that the reader should read and understand.
Warning
This is essential reading for the user as they should be aware that a serious situation
may result if certain actions are taken or not taken.
13
Chapter 1. Product Overview
This chapter outlines the key features of NetDefendOS.
• About D-Link NetDefendOS, page 14
• NetDefendOS Architecture, page 16
• NetDefendOS State Engine Packet Flow, page 19
1.1. About D-Link NetDefendOS
D-Link NetDefendOS is the firmware, the software engine that drives and controls all D-Link
Firewall products.
Designed as a network security operating system, NetDefendOS features high throughput
performance with high reliability plus super-granular control. In contrast to products built on
standard operating systems such as Unix or Microsoft Windows, NetDefendOS offers seamless
integration of all subsystems, in-depth administrative control of all functionality as well as a
minimal attack surface which helps negate the risk of being a target for security attacks.
From the administrator's perspective the conceptual approach of NetDefendOS is to visualize
operations through a set of logical building blocks or objects, which allow the configuration of the
product in an almost limitless number of different ways. This granular control allows the
administrator to meet the requirements of the most demanding network security scenario.
NetDefendOS is an extensive and feature-rich network operating system. The list below presents the
most essential features:
IP Routing
Address Translation
Firewalling
NetDefendOS provides a variety of options for IP routing
including static routing, dynamic routing, as well as multicast
routing capabilities. In addition, NetDefendOS supports
features such as Virtual LANs, Route Monitoring, Proxy ARP
and Transparency.For more information,please see
Chapter 4, Routing.
For functionality as well as security reasons, NetDefendOS
supports policy-based address translation. Dynamic Address
Translation (NAT) as well as Static Address Translation
(SAT) is supported, and resolves most types of address
translation needs. This feature is covered in Chapter 7,
Address Translation.
At the heart of the product, NetDefendOS features stateful
inspection-based firewalling for common protocols such as
TCP, UDP and ICMP. As an administrator, you have the
possibility to define detailed firewalling policies based on
source and destination network and interface, protocol, ports,
user credentials, time-of-day and much more. Section 3.5,
“The IP Rule Set”, describes how to use the firewalling
aspects of NetDefendOS.
Intrusion Detection and
Prevention
To mitigate application-layer attacks towards vulnerabilities
in services and applications, NetDefendOS provides a
powerful Intrusion Detection and Prevention (IDP) engine.
The IDP engine is policy-based and is able to perform
high-performance scanning and detection of attacks and can
perform blocking and optional black-listing of attacking
14
1.1. About D-Link NetDefendOSChapter 1. Product Overview
hosts. For more information about the IDP capabilities of
NetDefendOS, please see Section 6.5, “Intrusion Detection
and Prevention”.
Anti-Virus
Web Content Filtering
Virtual Private Networking
Traffic Management
NetDefendOSfeaturesintegratedgatewayanti-virus
functionality. Traffic passing through the gateway can be
subjected to in-depth scanning for viruses, and attacking hosts
can be blocked and black-listed at your choice. Section 6.4,
“Anti-Virus Scanning”, provides more information about how
to use the integrated anti-virus feature.
NetDefendOS provides various mechanisms for filtering web
content that is deemed inappropriate according to your web
usage policy. Web content can be blocked based on category,
malicious objects can be removed and web sites can be
whitelisted or blacklisted in multiple policies. For more
information, please see Section 6.3, “Web Content Filtering”.
A device running NetDefendOS is highly suitable for
participatinginaVirtualPrivateNetwork(VPN).
NetDefendOS supports IPsec, L2TP and PPTP based VPNs
concurrently, can act as either server or client for all of the
VPN types, and can provide individual security policies for
each VPN tunnel. Virtual Private Networking is covered in
detail by Chapter 9, VPN.
With the support of Traffic Shaping, Threshold Rules and
Server Load Balancing features, NetDefendOS is optimal for
traffic management. The Traffic Shaping feature enables
fine-granular limiting and balancing of bandwidth; Threshold
Rules allows for implementing various types of thresholds
where to alarm or limit network traffic, and Server Load
Balancing enables a device running NetDefendOS to
distribute network load to multiple hosts. Chapter 10, TrafficManagement, provides more detailed information on the
various traffic management capabilities.
Operations and Maintenance
ZoneDefense
Reading through this documentation carefully will ensure that you get the most out of your
NetDefendOS product. In addition to this document, the reader should also be aware of the
companion volumes:
•The NetDefendOS CLI Guide which details all NetDefendOS console commands.
•The NetDefendOS Log Reference Guide which details all NetDefendOS log event messages.
These documents together form the essential documentation for NetDefendOS operation.
To facilitate management of a NetDefendOS device,
administrative control is enabled through a Web-based User
Interface or via the Command Line Interface. In addition,
NetDefendOS provides very detailed event and logging
capabilities and support for monitoring using standards such
as SNMP. For more information, please see Chapter 2,
Management and Maintenance.
NetDefendOS can be used to control D-Link switches using
the ZoneDefense feature.
Note
High Availability, Anti-Virus, Web Content Filtering and ZoneDefense are not
available with some models as specified in the chapters relating to those features.
The NetDefendOS architecture is centered around the concept of state-based connections.
Traditional IP routers or switches commonly inspect all packets and then perform forwarding
decisions based on information found in the packet headers. With this approach, packets are
forwarded without any sense of context which eliminates any possibility to detect and analyze
complex protocols and enforce corresponding security policies.
Stateful Inspection
NetDefendOS employs a technique called stateful inspection which means that it inspects and
forwards traffic on a per-connection basis. NetDefendOS detects when a new connection is being
established, and keeps a small piece of information or state in it's state table for the lifetime of that
connection. By doing this, NetDefendOS is able to understand the context of the network traffic,
which enables it to perform in-depth traffic scanning, apply bandwidth management and much
more.
The stateful inspection approach additionally provides high throughput performance with the added
advantage of a design that is highly scalable. The NetDefendOS subsystem that implements stateful
inspection will sometimes be referred to in documentation as the NetDefendOS state-engine.
1.2.2. NetDefendOS Building Blocks
The basic building blocks in NetDefendOS are interfaces, logical objects and various types of rules
(or rule sets).
Interfaces
Interfaces are the doorways for network traffic passing through, to or from the system. Without
interfaces, a NetDefendOS system has no means for receiving or sending traffic. Several types of
interfaces are supported; Physical Interfaces, Physical Sub-Interfaces and Tunnel Interfaces.
Physical interfaces corresponds to actual physical Ethernet ports; physical sub-interfaces include
VLAN and PPPoE interfaces while tunnel interfaces are used for receiving and sending traffic in
VPN tunnels.
Interface Symmetry
The NetDefendOS interface design is symmetric, meaning that the interfaces of the device are not
fixed as being on the "insecure outside" or "secure inside" of a network topology. The notion of
what is inside and outside is totally for the administrator to define.
Logical Objects
Logical objects can be seen as pre-defined building blocks for use by the rule sets. The address
book, for instance, contains named objects representing host and network addresses. Another
example of logical objects are services , representing specific protocol and port combinations. Also
important are the Application Layer Gateway (ALG) objects which are used to define additional
parameters on specific protocols such as HTTP, FTP, SMTP and H.323.
NetDefendOS Rule Sets
Finally, rules which are defined by the administrator in the various rule sets are used for actually
implementing NetDefendOS security policies. The most fundamental set of rules are the IP Rules,
which are used to define the layer 3 IP filtering policy as well as carrying out address translation and
server load balancing. The Traffic Shaping Rules define the policy for bandwidth management, the
IDP Rules control the behavior of the intrusion prevention engine and so on.
This section outlines the basic flow in the state-engine for packets received and forwarded by
NetDefendOS. Please note that this description is simplified and might not be fully applicable in all
scenarios. The basic principle, however, is still valid in all applications.
1.An Ethernet frame is received on one of the Ethernet interfaces in the system. Basic Ethernet
frame validation is performed and the packet is dropped if the frame is invalid.
2.The packet is associated with a Source Interface. The source interface is determined as follows:
•If the Ethernet frame contains a VLAN ID (Virtual LAN identifier), the system checks for a
configured VLAN interface with a corresponding VLAN ID. If one is found, that VLAN
interface becomes the source interface for the packet. If no matching interface is found, the
packet is dropped and the event is logged.
•If the Ethernet frame contains a PPP payload, the system checks for a matching PPPoE
interface. If one is found, that interface becomes the source interface for the packet. If no
matching interface is found, the packet is dropped and the event is logged.
•If none the above is true, the receiving Ethernet interface becomes the source interface for
the packet.
3.The IP datagram within the packet is passed on to the NetDefendOS Consistency Checker. The
consistency checker performs a number of sanity checks on the packet, including validation of
checksums, protocol flags, packet length and so on. If the consistency checks fail, the packet
gets dropped and the event is logged.
4.NetDefendOS now tries to lookup an existing connection by matching parameters from the
incoming packet. A number of parameters are used in the match attempt, including the source
interface, source and destination IP addresses and IP protocol.
If a match cannot be found, a connection establishment process starts which includes steps
from here to 9 below. If a match is found, the forwarding process continues at step 10 below.
5.The Access Rules are evaluated to find out if the source IP address of the new connection is
allowed on the received interface. If no Access Rule matches then a reverse route lookup will
be done. In other words, by default, an interface will only accept source IP addresses that
belong to networks routed over that interface. If the Access Rules or the reverse route lookup
determine that the source IP is invalid, then the packet is dropped and the event is logged.
6.A route lookup is being made using the appropriate routing table. The destination interface for
the connection has now been determined.
7.The IP rules are now searched for a rule that matches the packet. The following parameters are
part of the matching process:
•Source and destination interfaces
•Source and destination network
•IP protocol (for example TCP, UDP, ICMP)
•TCP/UDP ports
•ICMP types
•Point in time in reference to a pre-defined schedule
If a match cannot be found, the packet is dropped.
If a rule is found that matches the new connection, the Action parameter of the rule decides
what NetDefendOS should do with the connection. If the action is Drop, the packet is dropped
and the event is logged according to the log settings for the rule.
If the action is Allow, the packet is allowed through the system. A corresponding state will be
added to the connection table for matching subsequent packets belonging to the same
connection. In addition, the Service object which matched the IP protocol and ports might have
contained a reference to an Application Layer Gateway (ALG) object. This information is
recorded in the state so that NetDefendOS will know that application layer processing will have
to be performed on the connection.
Finally, the opening of the new connection will be logged according to the log settings of the
rule.
Note
There are actually a number of additional actions available such as address
translation and server load balancing. The basic concept of dropping and
allowing traffic is still the same.
8.The Intrusion Detection and Prevention (IDP) Rules are now evaluated in a similar way to the
IP rules. If a match is found, the IDP data is recorded with the state. By doing this,
NetDefendOS will know that IDP scanning is supposed to be conducted on all packets
belonging to this connection.
9.The Traffic Shaping and the Threshold Limit rule sets are now searched. If a match is found,
the corresponding information is recorded with the state. This will enable proper traffic
management on the connection.
10. From the information in the state, NetDefendOS now knows what to do with the incoming
packet:
•If ALG information is present or if IDP scanning is to be performed, the payload of the
packet is taken care of by the TCP Pseudo-Reassembly subsystem, which in turn makes use
of the different Application Layer Gateways, layer 7 scanning engines and so on, to further
analyze or transform the traffic.
•If the contents of the packet is encapsulated (such as with IPsec, L2TP/PPTP or some other
type of tunneled protocol), then the interface lists are checked for a matching interface. If
one is found, the packet is decapsulated and the payload (the plaintext) is sent into
NetDefendOS again, now with source interface being the matched tunnel interface. In other
words, the process continues at step 3 above.
•If traffic management information is present, the packet might get queued or otherwise be
subjected to actions related to traffic management.
11. Eventually, the packet will be forwarded out on the destination interface according to the state.
If the destination interface is a tunnel interface or a physical sub-interface, additional
processing such as encryption or encapsulation might occur.
The following section provides a set of diagrams which illustrate the flow of packets through
NetDefendOS.
18
1.3. NetDefendOS State Engine Packet
Flow
Chapter 1. Product Overview
1.3. NetDefendOS State Engine Packet Flow
The diagrams in this section provide a summary of the flow of packets through the NetDefendOS
state-engine. There are three diagrams, each flowing into the next.
Figure 1.1. Packet Flow Schematic Part I
The packet flow is continued on the following page.
19
1.3. NetDefendOS State Engine Packet
Flow
Figure 1.2. Packet Flow Schematic Part II
Chapter 1. Product Overview
The packet flow is continued on the following page.
Figure 1.3. Packet Flow Schematic Part III
20
1.3. NetDefendOS State Engine Packet
Flow
Chapter 1. Product Overview
21
1.3. NetDefendOS State Engine Packet
Flow
Chapter 1. Product Overview
22
Chapter 2. Management and Maintenance
This chapter describes the management, operations and maintenance related aspects of
NetDefendOS.
• Managing NetDefendOS, page 23
• Events and Logging, page 35
• RADIUS Accounting, page 39
• Monitoring, page 43
• Maintenance, page 45
2.1. Managing NetDefendOS
2.1.1. Overview
NetDefendOS is designed to give both high performance and high reliability. Not only does it
provide an extensive feature set, it also enables the administrator to be in full control of almost every
detail of the system. This means the product can be deployed in the most challenging environments.
A good understanding on how NetDefendOS configuration is performed is crucial for proper usage
of the system. For this reason, this section provides an in-depth presentation of the configuration
subsystem as well as a description of how to work with the various management interfaces.
Management Interfaces
NetDefendOS provides the following management interfaces:
The WebUI
The CLI
The Web User Interface (WebUI) provides a user-friendly and intuitive graphical
management interface, accessible from a standard web browser.
The Command Line Interface (CLI), accessible locally via serial console port or
remotely using the Secure Shell (SSH) protocol, provides the most fine-grain
control over all parameters in NetDefendOS.
Note
Microsoft Internet Explorer (version 6 and later), Firefox and Netscape (version 8 and
later) are the recommended web-browsers to use with the WebUI. Other browsers may
also provide full support.
Access to remote management interfaces can be regulated by a remote management policy so the
administrator can restrict management access based on source network, source interface and
credentials. Access to the web interface can be permitted for administrative users on a certain
network, while at the same time allowing CLI access for a remote administrator connecting through
a specific IPsec tunnel.
By default, Web User Interface access is enabled for users on the network connected via the LAN
interface of the firewall (on products where more than one LAN interface is available, LAN1 is the
default).
2.1.2. Default Administrator Accounts
23
2.1.3. The CLIChapter 2. Management and Maintenance
By default, NetDefendOS has a local user database, AdminUsers, with one user account pre-defined:
•Username admin with password admin.
This account has full administrative read/write privileges.
Important
For security reasons, it is recommended to change the default password of the default
account as soon as possible after connecting with the D-Link Firewall.
Creating New Accounts
Extra user accounts can be created if required. Accounts can either can belong to the
Administrators group of users in which case they have complete read/write administrative access,
or they can belong to the Auditors user group in which case they have read-only access.
2.1.3. The CLI
NetDefendOS provides a Command Line Interface (CLI) for administrators that prefer or require a
command-line approach, or who need more granular control of system configuration. The CLI is
available either locally through the serial console port, or remotely using the Secure Shell (SSH)
protocol.
The CLI provides a comprehensive set of commands that allow the display and modification of
configuration data as well as allowing runtime data to be displayed and allowing system
maintenance tasks to be performed.
This section only provides a summary only of using the CLI. For a complete reference for all CLI
commands see the separate D-Link CLI Reference Guide.
Serial Console CLI Access
The serial console port is a RS-232 port on the D-Link Firewall that allows access to the CLI
through a serial connection to a PC or terminal. To locate the serial console port on your D-Link
system, see the D-Link Quickstart Guide .
To use the console port, you need the following equipment:
•A terminal or a computer with a serial port and the ability to emulate a terminal (such as using
the Hyper Terminal software included in some Microsoft Windows editions). The serial console
port uses the following default settings: 9600 baud, No parity, 8 bits and 1 stop bit.
•A RS-232 cable with appropriate connectors. An appliance package includes a RS-232
null-modem cable.
To connect a terminal to the console port, follow these steps:
1.Set the terminal protocol as described previously.
2.Connect one of the connectors of the RS-232 cable directly to the console port on your system
hardware.
3.Connect the other end of the cable to the terminal or the serial connector of the computer
running the communications software.
4.Press the enter key on the terminal. The NetDefendOS login prompt should appear on the
terminal screen.
24
2.1.3. The CLIChapter 2. Management and Maintenance
SSH (Secure Shell) CLI Access
The SSH (Secure Shell) protocol can be used to access the CLI over the network from a remote
host. SSH is a protocol primarily used for secure communication over insecure networks, providing
strong authentication and data integrity. Many SSH clients are feely available for almost all
hardware platforms.
NetDefendOS supports version 1, 1.5 and 2 of the SSH protocol and SSH access is regulated by the
remote management policy in NetDefendOS, and is disabled by default.
Example 2.1. Enabling SSH Remote Access
This example shows how to enable remote SSH access from the lannet network through the lan interface by
adding a rule to the remote management policy.
1. Go to System > Remote Management > Add > Secure Shell Management
2. Enter a Name for the SSH remote management policy, eg. ssh_policy
3. Select the following from the dropdown lists:
• User Database: AdminUsers
• Interface: lan
• Network: lannet
4. Click OK
LocalUserDatabase=AdminUsers
Logging on to the CLI
When access to the CLI has been established to NetDefendOS through the serial console or an SSH
client, the administrator will need to logon to the system before being able to execute any CLI
command. This authentication step is needed to ensure that only trusted users can access the system,
as well as providing user information for auditing.
When accessing the CLI, the system will respond with a login prompt. Enter your username and
press Enter, followed by your password and then Enter again. After a successful logon you will see
the command prompt. If a welcome message has been set then it will be displayed directly after the
logon:
gw-world:/>
For security reasons, it can be advisable to disable or anonymize the CLI welcome message.
Changing the CLI Prompt
The default CLI prompt is
Device:/>
where Device is the model number of the D-Link Firewall. This can be customized, for example, to
gw-world:/>, by using the CLI command:
25
2.1.4. The WebUIChapter 2. Management and Maintenance
Device:/> set device name="gw-world"
The CLI Reference Guide uses the command prompt gw-world:/> throughout.
Note
When the command line prompt is changed to a new string value, this string also
appears as the new device name in the top level node of the WebUI tree-view.
Activate and Committing Changes
If any changes are made to the current configuration through the CLI, those changes won't be
uploaded to NetDefendOS until the command
gw-world:/> activate
is issued. Immediately following the activate command, the command:
gw-world:/> commit
should be issued to make those changes permanent. If a commit command is not issued within a
default time period of 30 seconds then the changes are automatically undone and the old
configuration restored.
Logging off from the CLI
After finishing working with the CLI, you should logout to avoid other people getting unauthorized
access to the system. Log off by using the exit or the logout command.
2.1.4. The WebUI
NetDefendOS provides a highly versatile web user interface (WebUI) for management of the
system using a standard web browser. This allows the administrator to perform remote management
from virtually anywhere in the world without having to install any third-party clients.
Logging on to the Web Interface
To access the web interface, launch a standard web browser and point the browser at the IP address
of the firewall. The factory default address for all D-Link Firewalls is 192.168.1.1.
When performing this initial connection to NetDefendOS, the administrator MUST use https:// as
the URL protocol in the browser (for example: https://192.168.1.1). Using HTTPS as the protocol
protects the username and password with encryption when they are sent to NetDefendOS.
If communication with the NetDefendOS is successfully established, a user authentication dialog
similar to the one shown below will then be shown in the browser window.
26
2.1.4. The WebUIChapter 2. Management and Maintenance
Enter your username and password and click the Login button. If the user credentials are correct,
you will be transferred to the main web interface page. This page, with its essential parts
highlighted, is shown below.
Multi-language Support
The WebUI login dialog offers the option to select a language other than english for the interface.
Language support is provided by a separate set of resource files provided with NetDefendOS.
It may occasionally be the case that a NetDefendOS upgrade might contain features that temporarily
lack a complete non-english translation because of time constraints. In this case the original english
will be used as a temporary solution.
The Web Browser Interface
On the left hand side of the WebUI is a tree which allows navigation to the various NetDefendOS
modules. The central area of the WebUI displays information about those modules. Current
performance information is shown by default.
For information about the default user name and password, please see Section 2.1.2, “Default
Administrator Accounts”.
Note
Access to the web interface is regulated by the remote management policy. By default,
the system will only allow web access from the internal network.
Interface Layout
The main web interface page is divided into three major sections:
Menu bar
The menu bar located at the top of the web interface contains a number of
buttons and drop-down menus that are used to perform configuration tasks as
well as for navigation to various tools and status pages.
27
2.1.4. The WebUIChapter 2. Management and Maintenance
•Home - Navigates to the first page of the web interface.
•Configuration
•Save and Activate - Saves and activates the configuration.
•Discard Changes - Discards any changes made to the configuration
during the current session.
•View Changes - List the changes made to the configuration since it was
last saved.
•Tools - Contains a number of tools that are useful for maintaining the system.
•Status - Provides various status pages that can be used for system
diagnostics.
•Maintenance
•Update Center - Manually update or schedule updates of the intrusion
detection and antivirus signatures.
•License - View license details or enter activation code.
•Backup - Make a backup of the configuration to your local computer or
restore a previously downloaded backup.
•Reset - Restart the firewall or reset to factory default.
•Upgrade - Upgrade the firewall's firmware.
Navigator
The navigator located on the left-hand side of the web interface contains a tree
representation of the system configuration. The tree is divided into a number of
sections corresponding to the major building blocks of the configuration. The tree
can be expanded to expose additional sections.
Main Window
The main window contains configuration or status details corresponding to the
section selected in the navigator or the menu bar.
Controlling Access to the Web Interface
By default, the web interface is accessible only from the internal network. If you need to enable
access from other parts of the network, you can do so by modifying the remote management policy.
Example 2.2. Enabling remote management via HTTPS.
1. Go to System > Remote Management > Add > HTTP/HTTPS Management
2. Enter a Name for the HTTP/HTTPS remote management policy, eg. https
3. Check the HTTPS checkbox
4. Select the following from the dropdown lists:
28
2.1.5. Working with ConfigurationsChapter 2. Management and Maintenance
• User Database: AdminUsers
• Interface: any
• Network: all-nets
5. Click OK
Caution
The above example is provided for informational purposes only. It is never
recommended to expose any management interface to any user on the Internet.
Logging out from the Web Interface
When you have finished working in the web interface, you should always logout to prevent other
users with access to your workstation to get unauthorized access to the system. Logout by clicking
on the Logout button at the right of the menu bar.
Tip
If there is a problem with the management interface when communicating alongside
VPN tunnels, check the main routing table and look for an all-nets route to the VPN
tunnel. If no specific route exists to the management interface then all management
traffic coming from NetDefendOS will automatically be routed to the VPN tunnel. If
this is the case then a route should be added by the administrator to route management
traffic destined for the management network to the correct interface.
2.1.5. Working with Configurations
The system configuration is built up by Configuration Objects, where each object represents a
configurable item of any kind. Examples of configuration objects are routing table entries, address
book entries, service definitions, IP rules and so on. Each configuration object has a number of
properties that constitute the values of the object.
A configuration object has a well-defined type. The type defines the properties that are available for
the configuration object, as well as the constraints for those properties. For instance, the IP4Address
type is used for all configuration objects representing a named IPv4 address.
In the web user interface the configuration objects are organized into a tree-like structure based on
the type of the object.
In the CLI similar configuration object types are grouped together in a category. These categories
are different from the structure used in the web user interface to allow quick access to the
configuration objects in the CLI. The IP4Address, IP4Group and EthernetAddress types are, for
instance, grouped in a category named Address, as they all represent different addresses.
Consequently, Ethernet and VLAN objects are all grouped in a category named Interface, as they
are all interface objects. The categories have actually no impact on the system configuration; they
are merely provided as means to simplify administration.
The following examples show how to manipulate objects.
Example 2.3. Listing Configuration Objects
To find out what configuration objects exist, you can retrieve a listing of the objects. This example shows how to
list all service objects.
CLI
29
2.1.5. Working with ConfigurationsChapter 2. Management and Maintenance
gw-world:/> show Service
A list of all services will be displayed, grouped by their respective type.
Web Interface
1. Go to Objects > Services
2. A web page listing all services will be presented.
A list contains the following basic elements:
• Add Button - Displays a dropdown menu when clicked. The menu will list all types of configuration items that
can be added to the list.
• Header - The header row displays the titles of the columns in the list. The tiny arrow images next to each title
can be used for sorting the list according to that column.
• Rows - Each row in the list corresponds to one configuration item. Most commonly, each row starts with the
name of the object (if the item has a name), followed by values for the columns in the list.
A single row in the list can be selected by clicking on the row on a spot where there is no hyperlink. The
background color of the row will turn dark blue. Right-clicking the row will bring up a menu where you can choose
to edit or delete the object as well as modify the order of the objects.
Example 2.4. Displaying a Configuration Object
The most simple operation on a configuration object is just to show its contents, in other words the values of the
object properties. This example shows how to display the contents of a configuration object representing the
telnet service.
CLI
gw-world:/> show Service ServiceTCPUDP telnet
----------------- ------DestinationPorts: 23
PassICMPReturn: No
The Property column lists the names of all properties in the ServiceTCPUDP class and the Value column lists the
corresponding property values.
Web Interface
1. Go to Objects > Services
2. Click on the telnet hyperlink in the list.
3. A web page displaying the telnet service will be presented.
Property Value
Name: telnet
SourcePorts: 0-65535
MaxSessions: 1000
Type: TCP
SYNRelay: No
ALG: (none)
Comments: Telnet
Note
When accessing object via the CLI you can omit the category name and just use the
type name. The CLI command in the above example, for instance, could be simplified
to:
gw-world:/> show ServiceTCPUDP telnet
30
Loading...
+ 325 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.