D-Link DFL-200 - Security Appliance User Manual

D-Link DFL-200 - Security Appliance User Manual

Network security firewall
Hide thumbs Also See for DFL-200 - Security Appliance:
Table of Contents

Advertisement

Quick Links

D-Link DFL-200
TM
Network Security Firewall
Manual
Building Networks for People
(04/18/2005)

Advertisement

Table of Contents
loading

Summary of Contents for D-Link DFL-200 - Security Appliance

  • Page 1 D-Link DFL-200 Network Security Firewall Manual Building Networks for People (04/18/2005)
  • Page 2: Table Of Contents

    Introduction to Local Area Networking ..........7 LEDs ..................... 8 Physical Connections................8 Package Contents ................. 9 System Requirements ................9 Managing D-Link DFL-200 ............10 Resetting the DFL-200................10 Administration Settings............... 11 Administrative Access ................11 Add ping access to an interface..............12 Add Admin access to an interface...............12...
  • Page 3 Firewall..................26 Policy....................26 Policy modes....................26 Action Types....................26 Source and Destination Filter..............26 Service Filter ....................27 Schedule .....................27 Intrusion Detection / Prevention..............27 Add a new policy ..................28 Change order of policy................29 Delete policy....................29 Configure Intrusion Detection ..............29 Configure Intrusion Prevention ..............29 Port mapping / Virtual Servers ............30 Add a new mapping ..................30 Delete mapping ...................31 Administrative users................
  • Page 4 Adding an L2TP/PPTP VPN Client .............49 Adding an L2TP/PPTP VPN Server............49 VPN – Advanced Settings ..............50 Limit MTU....................50 IKE Mode ....................50 IKE DH Group .....................50 PFS – Perfect Forward Secrecy ..............50 NAT Traversal .....................50 Keepalives....................50 Proposal Lists....................51 IKE Proposal List..................51 IPSec Proposal List..................51 Certificates ..................
  • Page 5 Upgrade IDS Signature-database...............64 Status ....................65 System ....................65 Interfaces .................... 66 VPN..................... 67 Connections ..................68 DHCP Server ..................69 How to read the logs..............70 USAGE events ..................70 DROP events ..................70 CONN events ..................71 Step by Step Guides ..............72 LAN-to-LAN VPN using IPSec ............
  • Page 6: Introduction

    Introduction The DFL-200 provides six 10/100Mbps Auto MDI/MDIX Ethernet network interface ports, which are (4) Internal/LAN, (1) External/WAN, and (1) DMZ port. In addition the DFL-200 also provides a user-friendly Web UI that allows users to set system parameters or monitor network activities using a Web browser supporting Java.
  • Page 7: Introduction To Local Area Networking

    Introduction to Local Area Networking Local Area Networking (LAN) is the term used when connecting several computers together over a small area such as a building or group of buildings. LANs can be connected over large areas. A collection of LANs connected over a large area is called a Wide Area Network (WAN).
  • Page 8: Leds

    LEDs Power: A solid light indicates a proper connection to the power supply. Status: A System status indicator that flashes occasionally to indicate a functional, active system. Solid illumination of the Status LED indicates a hardware/software critical failure. WAN, 4 x LAN, & DMZ: Bright Green illumination indicates a valid Ethernet Link on that respective port.
  • Page 9: Package Contents

    Package Contents Contents of Package: • D-Link DFL-200 Firewall • Manual and CD • Quick Installation Guide • 5V/3A AC Power adapter • Straight-through CAT-5 cable • RS-232 Null Modem Cable Note: Using a power supply with a different voltage rating than the one included with the DFL-200 will cause irreparable electrical damage and void the warranty for this product.
  • Page 10: Managing D-Link Dfl-200

    Managing D-Link DFL-200 When a change is made to the configuration, icon named Activate Changes will appear. When all changes made by the administrator complete, those changes need to be saved activated take effect by clicking on the Activate Changes button...
  • Page 11: Administration Settings

    Administration Settings Administrative Access Management UI Ports – The ports for the DFL-200’s Web Server Management UI (HTTP and HTTPS) can be customized if so desired. These values must change if User Authentication is enabled (User Authentication uses 80 and 443 to accomplish user login). Ping –...
  • Page 12: Add Ping Access To An Interface

    Add ping access to an interface To add ping access click on the interface you would like to add it to. Follow these steps to add ping access to an interface. Step 1. Click on the interface you would like to add it to. Step 2.
  • Page 13: Add Read-Only Access To An Interface

    Add Read-only access to an interface To add read-only access, click on the interface you would like to add it to. Note that if you only have read-only access enabled on an interface, all users will only have read-only access, even if they are administrators.
  • Page 14: System

    System Interfaces Click on System in the menu bar, and then click interfaces below it. Change IP of the LAN or DMZ interface Follow these steps to change the IP of the LAN or DMZ interface. Step 1. Choose which interface to view or change under the Available interfaces list. Step 2.
  • Page 15: Wan Interface Settings - Using Static Ip

    WAN Interface Settings – Using Static IP If you are using Static IP, you have to fill in the IP address information provided to you by your ISP. All fields are required except the Secondary DNS Server. Note: Do not use the numbers displayed in these fields, they are only used as an example.
  • Page 16: Wan Interface Settings - Using Pppoe

    WAN Interface Settings – Using PPPoE Use the following procedure to configure DFL-200 external interface to use PPPoE (Point-to-Point Protocol over Ethernet). This configuration is required if your ISP uses PPPoE to assign the IP address of the external interface. You will have to fill in the username and password provided to you by your ISP.
  • Page 17: Wan Interface Settings - Using Pptp

    WAN Interface Settings – Using PPTP PPTP over Ethernet connections are used in some DSL and cable modem networks. You need to enter your account details, possibly also configuration parameters actual physical interface that the PPTP tunnel runs over. Your ISP should supply this information.
  • Page 18: Wan Interface Settings - Using L2Tp

    WAN Interface Settings – Using L2TP L2TP over Ethernet connections are used in some DSL and cable modem networks. You need to enter your account details, possibly also configuration parameters actual physical interface that the L2TP tunnel runs over. Your ISP should supply this information.
  • Page 19: Wan Interface Settings - Using Bigpond

    WAN Interface Settings – Using BigPond The ISP Telstra BigPond uses BigPond for authentication; the IP is assigned with DHCP. • Username – The login or username supplied to you by your ISP. • Password – password supplied you by your ISP. MTU Configuration To improve the performance of your Internet connection, you can adjust the maximum transmission unit (MTU) of the packets that the DFL-200 transmits from its external interface.
  • Page 20: Routing

    Routing Click on System in the menu bar, and then click Routing below it; this will provide a list of all configured routes, and it will look something like this: The Routes configuration section describes the firewall’s routing table. The DFL-200 uses a slightly different method of describing routes compared to most other systems.
  • Page 21: Add A New Static Route

    Add a new Static Route Follow these steps to add a new route. Step 1. Go to System and Routing. Step 2. Click on Add new in the bottom of the routing table. Step 3. Choose the interface that the route should be sent through from the dropdown menu.
  • Page 22: Logging

    Logging, the ability to audit decisions made by the firewall, is a vital part in all network security products. The D-Link DFL-200 provides several options for logging activity. The D- Link DFL-200 logs activity by sending the log data to one or two log receivers in the network.
  • Page 23: Enable Logging

    The D-Link DFL-200 specifies a number of events that can be logged. Some of these events, such as startup and shutdown, are mandatory and will always generate log entries. Other events, for instance when allowed connections are opened and closed, are configurable.
  • Page 24: Time

    Time Click on System in the menu bar, and then click Time below it. This will give you the option to either set the system time by synchronizing with an Internet Network Time Server (NTP) or by entering the system time manually.
  • Page 25: Changing Time Zone

    Changing time zone Follow these steps to change the time zone. Step 1. Choose the correct time zone in the drop down menu. Step 2. Specify the dates to begin and end daylight saving time or choose no daylight saving time by checking the correct box. Click the Apply button below to apply the settings or click Cancel to discard changes.
  • Page 26: Firewall

    Firewall Policy The Firewall Policy configuration section is the "heart" of the firewall. The policies are the primary filter that is configured to allow or disallow certain types of network traffic through the firewall. The policies also regulate how bandwidth management, traffic shaping, is applied to traffic flowing through the WAN interface of the firewall.
  • Page 27: Service Filter

    IDS will send e-mails to the system administrators if e-mail alerting is enabled and configured. D-Link updates the attack database periodically. There are two modes that can be configured, either Inspection Only or Prevention. Inspection Only will...
  • Page 28: Add A New Policy

    only inspect the traffic, and if the DFL-200 detects anything it will log, e-mail an alert (if configured), and pass on the traffic. If Prevention is used the traffic will be dropped and logged and if configured, an e-mail alert will be sent. Add a new policy Follow these steps to add a new outgoing policy.
  • Page 29: Change Order Of Policy

    Change order of policy Follow these steps to change the order of a policy. Step 1. Choose the policy list for which you would like to change the order from the available policy lists. Step 2. Click on the Edit link corresponding to the rule you want to move. Step 3.
  • Page 30: Port Mapping / Virtual Servers

    Port mapping / Virtual Servers The Port mapping / Virtual Servers configuration section is where you can configure virtual servers (such as a LAN Web server) to allow WAN access to specified LAN or DMZ servers. It is also possible to use Intrusion Detection / Prevention on Port mapped services. These are applied in the same way as with policies.
  • Page 31: Delete Mapping

    Delete mapping Follow these steps to delete a mapping. Step 1. Choose the mapping list (WAN, LAN, or DMZ) you would like do delete the mapping from. Step 2. Click on the Edit link corresponding to the rule you want to delete. Step 3.
  • Page 32: Administrative Users

    Administrative users Click on Firewall in the menu bar, and then click Users below it. This will display all the users. The first section links to the administrative user. The password for the admin account may be changed at any time, however the username admin cannot be altered.
  • Page 33: Users

    Users User Authentication allows an administrator to grant or reject access to specific users from specific IP addresses, based on their user credentials. Before any traffic is allowed to pass through any policies configured with username or groups, the user must first authenticate him/her-self. The DFL-200 can either verify the user against a local database or pass along the user information to an external authentication server, which verifies the user and the given password, and transmits the result back to the firewall.
  • Page 34: Enable User Authentication Via Http / Https

    Enable User Authentication via HTTP / HTTPS Follow these steps to enable User Authentication. Step 1. Enable the checkbox for User Authentication. Step 2. Specify if HTTP and HTTPS or only HTTPS should be used for the login. Step 3. Specify the idle-timeout, the time a user can be idle before being logged out by the firewall.
  • Page 35: Add User

    Add User Follow these steps to add a new user. Step 1. Click on add corresponding to the type of user you would like to add, Admin or Read-only. Step 2. Fill in User name; make sure you are not trying to add one that already exists.
  • Page 36: Delete User

    Delete User To delete a user click on the user name and you will see the following screen. Follow these steps to delete a user. Step 1. Click on the user you would like to delete. Step 2. Enable the Delete user checkbox.
  • Page 37: Schedules

    Schedules It is possible to configure a schedule for policies to take effect. By creating a schedule, the DFL- allows firewall policies to be used only at those designated times. Any activities outside of the scheduled time slot will not follow the policies and therefore will likely...
  • Page 38: Add New One-Time Schedule

    Add new one-time schedule Follow these steps to create and add a new one-time schedule. Step 1. Go to Firewall and Schedules and choose Add new. Step 2. Choose the starting and ending date and hour when the schedule should be active. Step 3.
  • Page 39: Services

    Services A service is basically a definition of a specific IP protocol with corresponding parameters. The service http, for instance, is defined as using the TCP protocol with destination port 80. Services are simplistic, in that they cannot carry out any action in the firewall on their own. Thus, a service definition does not include any information whether the service should be allowed through the firewall or not.
  • Page 40: Adding Ip Protocol

    Adding IP Protocol When the type of the service is IP Protocol, an IP protocol number may be specified in the text field. To have the service match the GRE protocol, for example, the IP protocol should be specified as 47. A list of some defined IP protocols can be found in the appendix named “IP Protocol Numbers.”...
  • Page 41: Protocol-Independent Settings

    Protocol-independent settings Allow ICMP errors from the destination to the source – ICMP error messages are sent in several situations: for example, when an IP packet cannot reach its destination. The purpose of these error control messages is to provide feedback about problems in the communication environment.
  • Page 42: Vpn

    Introduction to IPSec This chapter introduces IPSec, the method, or rather set of methods used to provide VPN functionality. IPSec, Internet Protocol Security, is a set of protocols defined by the IETF, Internet Engineering Task Force, to provide IP security at the network layer. An IPSec based VPN, such as that of the DFL-200, is made up of two basic parts: •...
  • Page 43: Introduction To L2Tp

    Introduction to L2TP L2TP, Layer 2 Tunneling Protocol, a combination of Microsoft’s PPTP and Cisco’s L2F (Layer 2 Forwarding), is used to provide IP security at the network layer. An L2TP based VPN is made up by these parts: • Point-to-Point Protocol (PPP) •...
  • Page 44: Authentication Protocols

    Authentication Protocols PPP supports different authentication protocols, PAP, CHAP, MS-CHAP v1 and MSCHAP v2. The authentication protocol to be used is decided during LCP negotiation. PAP (Password Authentication Protocol) is a simple, plaintext authentication scheme, which means that both user name and password are sent over the tunnel plaintext. PAP is therefore not considered a secure authentication protocol.
  • Page 45: L2Tp/Pptp Clients

    L2TP/PPTP Clients Settings for L2TP/PPTP Client Configuration Name – Specifies a friendly name for the PPTP/L2TP Client tunnel. Username – Specify username for this PPTP/L2TP Client tunnel. Password/Confirm Password – The password to use for this PPTP/L2TP Client tunnel. Interface IP - Specifies if the L2TP/PPTP Client tunnel should use a Static IP or obtain a dynamic IP from the server.
  • Page 46: L2Tp/Pptp Servers

    L2TP/PPTP Servers Settings L2TP/PPTP Server Configuration Name – Specifies a name for this PPTP/L2TP Server. Outer IP - Specifies the IP that the PPTP/L2TP server should listen on, leave it Blank for the WAN IP. Inner IP - Specifies the internal IP of the VPN tunnel.
  • Page 47: Ipsec Vpn Between Two Networks

    IPSec VPN between two networks In the following example users on the main office internal network can connect to the branch office internal network and vice versa. Communication between the two networks takes place in an encrypted IPSec VPN tunnel DFL-200 Firewall that connects the two DFL-200 NetDefend Firewalls across the Internet.
  • Page 48: Vpn Between Client And An Internal Network

    VPN between client and an internal network In the following example users can connect to the main office internal network from anywhere on the Internet. Communication between the client and the internal network takes place in an encrypted VPN tunnel DFL-200 Firewall that connects the DFL-200 and the roaming users across the Internet.
  • Page 49: Adding An L2Tp/Pptp Vpn Client

    Adding an L2TP/PPTP VPN Client Follow these steps to add an L2TP or PPTP VPN Client configuration. Step 1. Go to Firewall and VPN and choose Add new PPTP client or Add new L2TP client in the L2TP/PPTP Clients section. Step 2.
  • Page 50: Vpn - Advanced Settings

    VPN – Advanced Settings Advanced settings for a VPN tunnel is used when the user needs to change some characteristics of the tunnel to, for example, try to connect to a third party VPN Gateway. The different settings per tunnel are: Limit MTU With this setting it is possible to limit the MTU (Max Transferable Unit) of the VPN tunnel.
  • Page 51: Proposal Lists

    Proposal Lists To agree on the VPN connection parameters, a negotiation process is performed. As the result of the negotiations, the IKE and IPSec security associations (SA) are established. As the name implies, a proposal is the starting point for the negotiation. A proposal defines encryption parameters, for instance encryption algorithm, life times etc, that the VPN gateway supports.
  • Page 52: Certificates

    Certificates A certificate is a digital proof of identity. It links an identity to a public key in a trustworthy manner. Certificates can be used to authenticate individual users or other entities. These types of certificates are commonly called end-entity certificates. Before a VPN tunnel with certificate based authentication can be set up, the firewall needs a certificate of its own and that of the remote firewall.
  • Page 53: Certificate Authorities

    Certificate Authorities This is a list of all CA certificates. To add a new Certificate Authority certificate, click Add new. The following pages will allow you to specify a name for the CA certificate and upload the certificate file. This certificate can be selected in the Certificates field on the VPN page. Note: If the uploaded certificate is a CA certificate, it will automatically be placed in the Certificate Authorities list, even if Add New was clicked in the Remote Peers list.
  • Page 54: Content Filtering

    Content Filtering DFL-200 HTTP content filtering may be configured to scan all HTTP protocol streams for URLs or for potentially dangerous Web page content. If a match is found between the requested URL and the URL Blacklist the DFL-200 will block the Web page. You can configure the URL Blacklist to block all or just some of the pages on a website.
  • Page 55: Edit The Url Global Blacklist

    Edit the URL Global Blacklist Follow these steps to add or remove a URL. Step 1. Navigate to Firewall Content Filtering and choose Edit global Blacklist. Step 2. Add or edit a URL that should be filtered and blocked. File extensions may also be defined to block download of specified file types.
  • Page 56: Servers

    Servers DHCP Server Settings The DFL-200 contains a DHCP server. DHCP (Dynamic Host Configuration Protocol) is a protocol that allows network administrators to automatically assign IP numbers to DHCP enabled computers on a network. The DFL-200 DHCP Server helps to minimize work necessary to administer...
  • Page 57: Enable Dhcp Server

    Enable DHCP Server To enable the DHCP Server on an interface, click on Servers in the menu bar, and then click DHCP Server below it. Follow these steps to enable the DHCP Server on the LAN interface. Step 1. Choose the LAN interface from the Available interfaces list. Step 2.
  • Page 58: Dns Relay Settings

    DNS Relay Settings Click on Servers in the menu bar, and then click DNS Relay below it. The DFL-200 contains a DNS Relay function that can be configured to relay DNS queries from the internal LAN to the DNS servers used by the firewall itself. Enable DNS Relayer Follow these steps to enable the DNS Relayer.
  • Page 59: Tools

    Tools Ping Click on Tools in the menu bar, and then click Ping below it. This tool is used to send a specified number of ICMP Echo Request packets to a given destination. All packets are sent in immediate succession rather than one per second. This method is the best suited for diagnosing connectivity problems.
  • Page 60: Dynamic Dns

    Dynamic DNS The Dynamic DNS (requires Dynamic DNS Service) allows you to alias a dynamic IP address to a static hostname, allowing your device to be more easily accessed by a specific name. When this function is enabled, the IP address in Dynamic DNS Server will be automatically updated with the new IP address provided by ISP.
  • Page 61: Backup

    Backup Click on Tools in the menu bar, and then click Backup below it. Here an administrator can backup restore configuration. configuration file stores system settings, addresses of the firewall’s network interfaces, address table, service table, IPSec settings, port mapping, policies.
  • Page 62: Restart/Reset

    Restart/Reset Restarting the DFL-200 Follow these steps restart the DFL-200. Step 1. Choose if you want to do a quick or full restart. Step 2. Click Restart Unit and the unit will restart.
  • Page 63: Restoring System Settings To Factory Defaults

    Restoring system settings to factory defaults Use the following procedure to restore system settings to the factory defaults. This procedure will possibly change the DFL-200 firmware version to a lower version if it has been upgraded. Make sure you have the current firmware file available for upload to the device in the case where the firmware version is defaulted to an older version.
  • Page 64: Upgrade

    Upgrade IDS Signature-database To upgrade the signature-database first download the newest IDS signatures from D-Link. After downloading the newest version of the software, connect to the firewall’s Web-based configuration GUI, enter Upgrade on the Tools menu, click Browse in the Upgrade Unit’s...
  • Page 65: Status

    Status In this section, the DFL-200 displays the status information about the Firewall. Administrator may use the Status section to check the System Status, Interface statistics, VPN status, IP connections, and DHCP Servers Status. System Click on Status in the menu bar, and then click System below it. A window will appear providing some information about the DFL-200.
  • Page 66: Interfaces

    Interfaces Click on Status in the menu bar, and then click Interfaces below it. A window will appear providing information about the interfaces on the DFL-200. By default, information about the LAN interface will be displayed. To see another one, click on that interface (WAN or DMZ). Interface –...
  • Page 67: Vpn

    Click on Status in the menu bar, and then click Interfaces below it. A window will appear providing information about the VPN connections on the DFL-200. By default information about the first VPN tunnel will be displayed. To see another one, click on that VPN tunnels name.
  • Page 68: Connections

    Connections Click on Status in the menu bar, and then click Connections below it. A window will appear providing information about the content of the state table. The state table shows the last 100 connections opened through firewall. Connections are created when traffic is permitted to pass via the policies.
  • Page 69: Dhcp Server

    DHCP Server Click on Status in the menu bar, and then click DHCP Server below it. A window will appear providing information about the configured DHCP Servers. By default, information about the LAN interface will be displayed. To see another one, click on that interface.
  • Page 70: How To Read The Logs

    How to read the logs Although the exact format of each log entry depends on how your SYSLog recipient works, most are very similar. The way in which logs are read is also dependent on how your SYSLog recipient works. SYSLog daemons on UNIX servers usually log to text files, line by line. Most SYSLog recipients preface each log entry with a timestamp and the IP address of the machine that sent the log data: Oct 20 2003 09:45:23 gateway...
  • Page 71: Conn Events

    CONN events These events are generated if auditing has been enabled. One event will be generated when a connection is established. This event will include information about the protocol, receiving interface, source IP address, source port, destination interface, destination IP address, and destination port. Open Example: Oct 20 2003 09:47:56 gateway EFW: CONN: prio=1 rule=Rule_8 conn=open connipproto=TCP connrecvif=lan connsrcip=192.168.0.10 connsrcport=3179 conndestif=wan...
  • Page 72: Step By Step Guides

    Step by Step Guides The following guides make use of example IP Addresses, users, sites and passwords. You will have to exchange the example information with your own values. Passwords used in these examples are not recommended for real life use. Strong passwords and keys should be chosen making use of symbols, letters, and numbers to decrease the likelihood of a brute force dictionary attack success.
  • Page 73: Lan-To-Lan Vpn Using Ipsec

    LAN-to-LAN VPN using IPSec Settings for Branch office 1. Setup interfaces, System->Interfaces: WAN IP: 194.0.2.10 LAN IP: 192.168.4.1, Subnet mask: 255.255.255.0 2. Setup IPSec tunnel, Firewall->VPN: Under IPSec tunnels click Add new Name the tunnel ToMainOffice Local net: 192.168.4.0/24 PSK: 1234567890 (Do not use this as your PSK) Retype PSK: 1234567890...
  • Page 74 Select Tunnel type: LAN-to-LAN tunnel Remote Net: 192.168.1.0/24 Remote Gateway: 194.0.2.20 Enable Automatically add a route for the remote network Click Apply 3. Setup policies for the new tunnel, Firewall->Policy: Click Global policy parameters Enable Allow all VPN traffic: internal->VPN, VPN->internal and VPN->VPN Click Apply 4.
  • Page 75: Settings For Main Office

    Settings for Main office 1. Setup interfaces, System->Interfaces: WAN IP: 194.0.2.20 LAN IP: 192.168.1.1, Subnet mask: 255.255.255.0 2. Setup IPSec tunnel, Firewall->VPN: Under IPSec tunnels click add new Name the tunnel ToBranchOffice Local net: 192.168.1.0/24 PSK: 1234567890 (Note! You should use a key that is hard to guess) Retype PSK: 1234567890 Select Tunnel type: LAN-to-LAN tunnel Remote Net: 192.168.4.0/24...
  • Page 76 3. Setup policies for the new tunnel, Firewall->Policy: Click Global policy parameters Enable Allow all VPN traffic: internal->VPN, VPN->internal and VPN->VPN Click Apply 4. Click Activate and wait for the firewall to restart This example will allow all traffic between the two offices. To get a more secure solution read A more secure LAN-to-LAN VPN solution section of this user guide.
  • Page 77: Lan-To-Lan Vpn Using Pptp

    LAN-to-LAN VPN using PPTP Settings for Branch office 1. Setup interfaces, System->Interfaces: WAN IP: 194.0.2.10 LAN IP: 192.168.4.1, Subnet mask: 255.255.255.0 2. Setup PPTP client, Firewall->VPN: Under PPTP/L2TP clients click Add new PPTP client Name the tunnel toMainOffice...
  • Page 78 Username: BranchOffice Password: 1234567890 (Note! You should use a password that is hard to guess) Retype password: 1234567890 Interface IP: leave blank Remote gateway: 194.0.2.20 Remote net: 192.168.1.0/24 Dial on demand: leave unchecked Under authentication MSCHAPv2 should be the only checked option.
  • Page 79: Settings For Main Office

    Under MPPE encryption 128 bit should be the only checked option. Leave Use IPSec encryption unchecked Click Apply 3. Setup policies for the new tunnel, Firewall->Policy: Click Global policy parameters Enable Allow all VPN traffic: internal->VPN, VPN->internal and VPN->VPN Click Apply 4.
  • Page 80 2. Setup PPTP server, Firewall->VPN: Under L2TP / PPTP Server click Add new PPTP server Name the server pptpServer Leave Outer IP and Inner IP blank Set client IP pool to 192.168.1.100 – 192.168.1.199 Check Proxy ARP dynamically added routes Check Use unit’s own DNS relayer addresses Leave WINS settings blank...
  • Page 81 Under authentication MSCHAPv2 should be the only checked option. Under MPPE encryption 128 bit should be the only checked option. Leave Use IPsec encryption unchecked Click Apply 3. Setup policies for the new tunnel, Firewall->Policy: Click Global policy parameters Enable Allow all VPN traffic: internal->VPN, VPN->internal and VPN->VPN Click Apply...
  • Page 82 4. Set up the authentication source, Firewall->Users: Select Local database Click Apply 5. Add a new user, Firewall->Users: Under Users in local database click Add new Name the new user BranchOffice Enter password: 1234567890 Retype password: 1234567890 Leave static client IP empty (could also be set to 192.168.1.200. If no IP is set here the IP pool from the PPTP server settings are used).
  • Page 83: Lan-To-Lan Vpn Using L2Tp

    LAN-to-LAN VPN using L2TP Settings for Branch office 1. Setup interfaces, System->Interfaces: WAN IP: 194.0.2.10 LAN IP: 192.168.4.1, Subnet mask: 255.255.255.0 2. Setup L2TP client, Firewall->VPN: Under L2TP / PPTP client click Add new L2TP client Name the server toMainOffice...
  • Page 84 Username: BranchOffice Password: 1234567890 (Note! You should use a password that is hard to guess) Retype password: 1234567890 Interface IP: leave blank Remote gateway: 194.0.2.20 Remote net: 192.168.1.0/24 Dial on demand: leave unchecked Under authentication only MSCHAPv2 should be checked...
  • Page 85 Under MPPE encryption only None should be checked Check Use IPsec encryption Enter key 1234567890 (Note! You should use a key that is hard to guess) Retype key 1234567890 Click Apply 3. Setup policies for the new tunnel, Firewall->Policy: Click Global policy parameters Enable Allow all VPN traffic: internal->VPN, VPN->internal and VPN->VPN Click Apply 4.
  • Page 86: Settings For Main Office

    Settings for Main office 1. Setup interfaces, System->Interfaces: WAN IP: 194.0.2.20 LAN IP: 192.168.1.1, Subnet mask: 255.255.255.0 2. Setup L2TP server, Firewall->VPN: Under L2TP / PPTP Server click Add new L2TP server Name the server l2tpServer Leave Outer IP and Inner IP blank Set client IP pool to 192.168.1.100 –...
  • Page 87 Under authentication MSCHAPv2 should be the only checked option. Under MPPE encryption None should be the only checked option. Check Use IPSec encryption Enter key 1234567890 (Note! You should not use this key) Retype key 1234567890 Click Apply...
  • Page 88 3. Setup policies for the new tunnel, Firewall->Policy: Click Global policy parameters Enable Allow all VPN traffic: internal->VPN, VPN->internal and VPN->VPN Click Apply 4. Set up authentication source, Firewall->Users: Select Local database Click Apply...
  • Page 89 5. Add a new user, Firewall->Users: Under Users in local database click Add new Name the new user BranchOffice Enter password: 1234567890 Retype password: 1234567890 Leave static client IP empty (could also be set to eg 192.168.1.200. If no IP is set here the IP pool from the L2TP server settings are used).
  • Page 90: A More Secure Lan-To-Lan Vpn Solution

    A more secure LAN-to-LAN VPN solution In order to establish a more secure LAN-to-LAN VPN connection, traffic policies should be created instead of allowing all traffic between the two private Networks. The following steps show how to enable some common services allowed through the VPN tunnel. In this example we have a mail server, ftp server and a web server (intranet) in the main office that we want to access from the branch office.
  • Page 91 4. Setup the new rule: Name the new rule: allow_pop3 Select action: Allow Select service: pop3 Select schedule: Always We don’t want any Intrusion detection for now, so leave this option unchecked. Click Apply...
  • Page 92 5. The first policy rule is now created. Repeat step 4 to create services named allow_imap, allow_ftp and allow_http. The services for these policies should be imap, ftp_passthrough and http respectively. The policy list for LAN->toMainOffice should now look like this. 6.
  • Page 93: Settings For Main Office

    Settings for Main office 1. Setup policies for the new tunnel, Firewall->Policy: Click Global policy parameters Disable Allow all VPN traffic: internal->VPN, VPN->internal and VPN->VPN Click Apply 2. Now it is possible to create policies for the VPN interfaces. Select from toBranchOffice to LAN and click Show.
  • Page 94: Windows Xp Client And Pptp Server

    Windows XP client and PPTP server Settings for the Windows XP client 1. Open the control panel (Start button -> Control panel). 2. If you are using the Category view, click on the Network and Internet Connections icon. Then click Create a connection to the network on your workplace and continue to step 6.
  • Page 95 5. Select Connect to the network at my workplace and click Next...
  • Page 96 6. Select Virtual Private Network connection and click Next...
  • Page 97 7. Name the connection MainOffice and click Next...
  • Page 98 8. Select Do not dial the initial connection and click Next...
  • Page 99 9. Type the IP address to the server, 194.0.2.20, and click Next 10. Click Finish...
  • Page 100 11. Type user name HomeUser and password 1234567890 (Note! You should use a password that is hard to guess) 12. Click Properties...
  • Page 101: Settings For Main Office

    13. Select the Networking tab and change Type of VPN to PPTP VPN. Click OK. All settings needed for the XP client are now complete. Once we have configured the server on the firewall you should be able to click Connect to establish the connection to the Main office.
  • Page 102 2. Setup PPTP server, Firewall->VPN: Under L2TP / PPTP Server click Add new PPTP server Name the server pptpServer Leave Outer IP and Inner IP blank Set client IP pool to 192.168.1.100 – 192.168.1.199 Check Proxy ARP dynamically added routes Check Use unit’s own DNS relayer addresses Leave WINS settings blank Under authentication MSCHAPv2 should be the only checked option.
  • Page 103 This example will allow all traffic from the client to the main office network. To get a more secure solution read the Settings for the Main office part of the A more secure LAN-to- LAN VPN solution section.
  • Page 104: Windows Xp Client And L2Tp Server

    Windows XP client and L2TP server The Windows XP client to L2TP server setup is quite similar to the PPTP setup above. Settings for the Windows XP client To setup a L2TP connection from Windows XP to the Main office firewall, please follow the steps in the PPTP guide above for the client side.
  • Page 105 2. Select the Security tab and click IPSec Settings 3. Check Use pre-shared key for authentication, type the key and click OK...
  • Page 106: Settings For Main Office

    Settings for Main office 1. Setup interfaces, System->Interfaces: WAN IP: 194.0.2.20 LAN IP: 192.168.1.1, Subnet mask: 255.255.255.0 2. Setup L2TP server, Firewall->VPN: Under L2TP / PPTP Server click Add new L2TP server Name the server l2tpServer Leave Outer IP and Inner IP blank Set client IP pool to 192.168.1.100 –...
  • Page 107 5. Add a new user, Firewall->Users: Under Users in local database click Add new Name the new user HomeUser Enter password: 1234567890 Retype password: 1234567890 Leave static client IP empty (could also be set to eg 192.168.1.200. If no IP is set here the IP pool from the PPTP server settings are used).
  • Page 108: Intrusion Detection And Prevention

    Intrusion Detection and Prevention Intrusion detection and prevention can be enabled for both policies and port mappings. In this example we are using a port mapping. The policy setup is quite similar. In this example a mail server with IP 192.168.2.4 and a web server with IP 192.168.2.5 is connected to the DMZ interface on the firewall.
  • Page 109 2. Set up the newly created port mapping: Name the rule map_www Select service http-in-all Enter pass to IP: 192.168.2.5 (the IP of the web server) Check the Intrusion detection / prevention option Select mode Prevention Enable email alerting by checking the Alerting box Click Apply...
  • Page 110 The new mapping is now in the list. 3. Setup email server and enable alerting, System->Logging: Check Enable E-mail alerting for IDS/IDP events Select sensitivity Normal Enter SMTP server IP (email server): 192.168.2.4 Enter sender: idsalert@examplecompany.com Enter E-mail address 1: webmaster@examplecompany.com Enter E-mail address 2: steve@examplecompany.com Click Apply 4.
  • Page 111: Appendixes

    Appendixes Appendix A: ICMP Types and Codes The Internet Control Message Protocol (ICMP) has many messages that are identified by a “type” field; many of these ICMP types have a "code" field. Here we list the types with their assigned code fields. Type Name Code...
  • Page 112 Redirect Datagram for the RFC792 Host Redirect Datagram for the RFC792 Type of Service and Network Redirect Datagram for the RFC792 Type of Service and Host Echo No Code RFC792 Router Advertisement Normal router advertisement RFC1256 Does not route common traffic RFC2002 Router Selection No Code...
  • Page 113: Appendix B: Common Ip Protocol Numbers

    Appendix B: Common IP Protocol Numbers These are some of the more common IP Protocols. For a list of all protocols, follow the link after the table. Decimal Keyword Description Reference ICMP Internet Control Message RFC792 IGMP Internet Group Management RFC1112 Gateway-to-Gateway RFC823...
  • Page 114: Appendix C: Multiple Public Ip Addresses

    Appendix C: Multiple Public IP addresses Mapping of a Public IP address other than that of the Firewall to a Server located on either internal interface can be accomplished in two basic steps (order does not matter): add a Port Mapping/Virtual Server rule that forwards specified services to a single LAN or DMZ host to be accessible through a WAN IP not used by the DFL-200;...
  • Page 115 To accomplish this we need to create the following firewall settings: Configure two static routes (one for each public IP we wish to forward) Create two port mappings (one for each public IP mapping to each private Server) Routing configuration: Static Route Configuration for a Server on the LAN: Navigate to the SYSTEM tab, then the ROUTING page of the Web-based configuration.
  • Page 116 Static Route Configuration for a Server on the DMZ: Navigate to the SYSTEM tab, then the ROUTING page of the Web-based configuration. Select the Add New link to create the second static route. Select the Interface that the Internal Server is connected to (LAN or DMZ). Specify the Public IP to be forwarded in the Network field.
  • Page 117 Configure Port Mapping/Virtual Server Rules for LAN Server: Virtual Server Configuration for a Server on the LAN: Navigate to the FIREWALL tab, PORT MAPPING page of the Web-based configuration. Click the Add New link to create a new Port Mapping. Input the Public IP address to be forwarded in the Destination IP field.
  • Page 118 Virtual Server Configuration for a Server on the DMZ: Navigate to the FIREWALL tab, PORT MAPPING page of the Web-based configuration. Click the Add New link to create a new Port Mapping. Input the Public IP address to be forwarded in the Destination IP field. Select the Service to be forwarded to the Internal Server (pre-defined or custom).
  • Page 119 Example Scenario using DMZ w/out NAT: An alternative method to that described in the preceding pages is to isolate publicly accessible servers to the DMZ interface with NAT disabled. This configuration requires multiple (at least 2) Public IP addresses to function, as the Firewall will assume one IP and the Server(s) will use the other(s).
  • Page 120 The default WAN route must be modified to enable Proxy ARP. The default route for any interface cannot be deleted or modified other than to enable the Proxy ARP feature. From the SYSTEM > ROUTING page select WAN to edit the default route of the WAN interface.
  • Page 121 Disable NAT on the DMZ Interface: By default the DFL-200 is enabled to perform NAT on both LAN and DMZ interfaces. Disable NAT on the DMZ interface. Navigate to Firewall > Policy in the web-based configuration. Click on DMZ->WAN to modify the behavior of the DMZ interface.
  • Page 122: Appendix D: Http Content Filtering

    Appendix D: HTTP Content Filtering HTTP Content Filtering Global Policy Protection from malicious or improper web content is a must for Business owners and concerned parents alike. There are numerous vehicles for hackers to damage or take control of one’s PC or even Network. Malicious code may be delivered in deviously crafted ActiveX controls, Java Scripts, cookies, or tainted file downloads.
  • Page 123 The Whitelist Items entered in the Whitelist will always be allowed through the firewall, assuming HTTP content filtering is enabled. This section should only be used to allow essential domains and servers, such as Microsoft.com and DLink.com to ensure the ability to locate and download critical updates or firmware is not hindered.
  • Page 124 Navigate to the Firewall tab, Content Filtering section of the web-administration. Click on Edit URL Black List to modify or append the contents of the filtering database. To allow an entire domain and all sub-domains use the following syntax dlink.com/* # Allows access to the domain dlink.com *.dlink.com/* # Allows access to all sub-domains in dlink.com...
  • Page 125 Navigate to the Firewall tab, Content Filtering section of the web-administration. Click on Edit URL Black List to modify or append the contents of the filtering database. To block an entire domain and all sub-domains use the following syntax casino.com/* # Blocks access to the domain casino.com *.casino.com/* # Blocks access to all sub-domains under casino.com...
  • Page 126 Navigate to the Firewall tab, Content Filtering section of the web-administration. Click the check box next to each filter you would like to enable. Once finished selecting additional filters, click Apply to save changes or Cancel to clear. HTTP Rule using the HTTP ALG Now that the content to be filtered has been decided on, a rule needs to be configured for each interface that this filtering should be applied to utilizing the HTTP ALG.
  • Page 127 Check the check box next to delete this rule. Click Apply. To allow DNS queries to pass through Navigate to the Firewall tab, Policy section of the web-administration. Select the appropriate policy based on desired effect (LAN->WAN or DMZ->WAN). Click Add New at the bottom of the list. Give the rule a friendly name, such as dns_out.
  • Page 128 To configure the HTTP Content Filtering rule - Navigate to the Firewall tab, Policy section of the web-administration. Select the appropriate policy based on desired effect (LAN->WAN or DMZ->WAN). Click Add New at the bottom of the list. Give the rule a friendly name, such as http_cntnt_filtr. Position does not matter, leave blank or choose a position.
  • Page 129: Warranty

    D-Link’s sole obligation shall be to repair or replace the defective Hardware during the Warranty Period at no charge to the original owner or to refund at D-Link’s sole discretion. Such repair or replacement will be rendered by D-Link at an Authorized D-Link Service Office. The replacement Hardware need not be new or have an identical make, model or part.
  • Page 130 RMA number must be prominently marked on the outside of the package. Do not include any manuals or accessories in the shipping package. D-Link will only replace the defective portion of the Product and will not ship back any accessories.
  • Page 131 Limitation of Liability: TO THE MAXIMUM EXTENT PERMITTED BY LAW, D-LINK IS NOT LIABLE UNDER ANY CONTRACT, NEGLIGENCE, STRICT LIABILITY OR OTHER LEGAL OR EQUITABLE THEORY FOR ANY LOSS OF USE OF THE PRODUCT, INCONVENIENCE OR DAMAGES OF ANY CHARACTER, WHETHER DIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL (INCLUDING, BUT...
  • Page 132 Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. For detailed warranty outside the United States, please contact corresponding local D- Link office.

This manual is also suitable for:

Netdefend dfl-200

Table of Contents