Available 17 files for D-Link DFL-260
Select Files
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 Firmware
Operating System
Firmware
Version
2.20.03
Size Driver
4.4MB
File Name
dfl-260_fw_2.20.03.zip
Observations
D-Link NetDefendOS Release Notes
Version: 2.20.03
Platform Compatibility: DFL-210/260/800/860/1600/2500
Hardware Version: A1 (for all models), A2/A3/A4 (for DFL-210/800/1600/2500)
Date: Oct 21, 2008
Important Note:
For DFL-210/260/800/860, both LAN and DMZ ports cannot support to manually configure
interface speed, since IXP4NPE driver only allows auto/auto configuration. If users try to configure
the interface speed manually, the configuration will revert back to auto/auto on Web GUI as a
dummy-proof mechanism in the firmware v2.20.03.
New Features and Enhancements
1. No new features were introduced in the 2.20.03 release.
Problems Resolved
1. Fixed issue with DHCP NAK reception during initial phase of reconfiguration.
2. Fixed issue in OSPF where an LSA could be incorrectly deleted after being re-originated.
3. The interface listings for Marvell Yukon interfaces showed incorrect IRQ values.
It affects in DFL-1600 and DFL-2500 only.
4. The amount of memory used by the IDP engine was too high. The memory consumption has
now been reduced.
5. E-mails from e-mail addresses in the whitelist were blocked if they were classified as spam
messages. Now all e-mails sent from whitelisted addresses will be let through, even if they are
classified as spam.
6. Fixed leap year problem where leap year day was added to January instead of February.
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 How to configure DNS Relay
Information
Manual
Operating System
Manual
Size Driver
167KB
File Name
dfl-800_1600_2500-how_to_configure_dns_relay.pdf
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 Portmapping a public IP
Information
Manual
Operating System
Manual
Size Driver
164KB
File Name
dfl-800_1600_2500-portmapping_a_public_ip.pdf
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 Transparent mode
Information
Manual
Operating System
Manual
Size Driver
1MB
File Name
dfl-800_1600_2500-transparent_mode.pdf
Observations
Overview
In this document, the notation Objects->Address book means that in the tree on the left
side of the screen Objects first should be clicked (expanded) and then Address Book.
Most of the examples in this document are adapted for the DFL-800. The same settings can
easily be used for all other models in the series. The only difference is the names of the
interfaces. Since the DFL-1600 and DFL-2500 has more than one lan interface, the lan
interfaces are named lan1, lan2 and lan3 not just lan.
The screenshots in this document is from firmware version 2.04.00. If you are using a later
version of the firmware, the screenshots may not be identical to what you see on your
browser.
To prevent existing settings to interfere with the settings in these guides, reset the
firewall to factory defaults before starting.
How to configure transparent mode
This scenario shows how a firewall in Transparent Mode can be placed into an
existing network between an Internet access router and LAN, without the need
to reconfigure clients in LAN.
The WAN and LAN interfaces of the firewall will be configured to operate in Transparent
Mode. It is preferred to configure IP addresses on the WAN and LAN interfaces, as this can
improve performance during automatic discovering of hosts.
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 Example on VPN connection from roaming NetDefend clients DS-601 or DS-605 to the DFL-800
Information
Manual
Operating System
Manual
Size Driver
461KB
File Name
dfl-800_1600_2500-vpn_ipsec_server_for_netdefend.pdf
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 VPN Setup LAN to LAN using PPTP/L2TP
Information
Manual
Operating System
Manual
Size Driver
1.1MB
File Name
dfl-800_1600_2500-vpn_using_a_pptp_l2tp_lan-to-lan_tunnel.pdf
Observations
Overview
In this document, the notation Objects->Address book means that in the tree on the left
side of the screen Objects first should be clicked (expanded) and then Address Book.
Most of the examples in this document are adapted for the DFL-800. The same settings can
easily be used for all other models in the series. The only difference is the names of the
interfaces. Since the DFL-1600 and DFL-2500 has more than one lan interface, the lan
interfaces are named lan1, lan2 and lan3 not just lan.
The screenshots in this document is from firmware version 2.04.00. If you are using a later
version of the firmware, the screenshots may not be identical to what you see on your
browser.
To prevent existing settings to interfere with the settings in these guides, reset the
firewall to factory defaults before starting.
Virtual private network using a PPTP (or L2TP) lan-tolan
tunnel
Crea
Fire
te one lan-to-lan PPTP VPN tunnel between firewall A and B.
wall B is the server and firewall A the client.
If a L2TP tunnel is going to be used, instead of PPTP, follow the steps
in this guide but change tunnel protocol from PPTP to L2TP in step 2 and 6. The other
settings are same in both cases.
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 How to configure Transparent mode in DHCP environment
Information
Manual
Operating System
Manual
Size Driver
188KB
File Name
dfl-800_1600_2500-transparent_mode_in_dhcp_network_environment.pdf
Observations
Overview
In this document, the notation Objects->Address book means that in the tree on the left
side of the screen Objects first should be clicked (expanded) and then Address Book.
Most of the examples in this document are adapted for the DFL-800. The same settings can
easily be used for all other models in the series. The only difference is the names of the
interfaces. Since the DFL-1600 and DFL-2500 has more than one lan interface, the lan
interfaces are named lan1, lan2 and lan3 not just lan.
The screenshots in this document is from firmware version 2.11.02. If you are using an
earlier version of the firmware, the screenshots may not be identical to what you see on
your browser.
To prevent existing settings to interfere with the settings in these guides, reset the
firewall to factory defaults before starting.
How to configure transparent mode in DHCP network
environment
This scenario shows how a firewall in Transparent Mode can be placed into an
existing DHCP network between an Internet access router and LAN, without the
need to reconfigure clients in LAN.
The WAN and LAN interfaces of the firewall will be configured to operate in Transparent
Mode. It is preferred to configure IP addresses on the WAN and LAN interfaces, as this can
improve performance during automatic discovering of hosts.
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 User Authentication for Web Access
Information
Manual
Operating System
Manual
Size Driver
828KB
File Name
dfl-800_1600_2500-user_authentication_for_web_access.pdf
Observations
Overview
In this document, the notation Objects->Address book means that in the tree on the left
side of the screen Objects first should be clicked (expanded) and then Address Book.
Most of the examples in this document are adapted for the DFL-800. The same settings can
easily be used for all other models in the series. The only difference is the names of the
interfaces. Since the DFL-1600 and DFL-2500 has more than one lan interface, the lan
interfaces are named lan1, lan2 and lan3 not just lan.
The screenshots in this document is from firmware version 2.11.02. If you are using an
earlier version of the firmware, the screenshots may not be identical to what you see on
your browser.
To prevent existing settings to interfere with the settings in these guides, reset the
firewall to factory defaults before starting.
Require user authentication for web access......................................................... 3
Require user authentication for web access
This scenario shows how to configure the firewall to require user authentication before
local users can browse the Internet. The user will automatically be redirected to the
login page if not already authenticated. In the end of this guide there is also an
explanation of an alternative set up - how to configure the firewall to use
authentication without the automatic redirection.
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 CLI Reference Manual v1.03
Information
Manual
Operating System
Manual
Size Driver
1.1MB
File Name
dfl_cli_reference_guide_v1.03.pdf
Observations
Preface ................................................................................................................ 9
1. Introduction .....................................................................................................11
1.1. Running a command ...............................................................................11
1.2. Help ....................................................................................................12
1.2.1. Help for commands ......................................................................12
1.2.2. Help for object types ....................................................................12
1.3. Function keys ........................................................................................13
1.4. Command line history .............................................................................14
1.5. Tab completion ......................................................................................15
1.5.1. Inline help ..................................................................................15
1.5.2. Autocompleting Current and Default value .......................................15
1.5.3. Configuration object type categories ................................................16
1.6. User roles .............................................................................................17
2. Command Reference .........................................................................................19
2.1. Configuration ........................................................................................19
2.1.1. activate ......................................................................................19
2.1.2. add ............................................................................................19
2.1.3. cancel ........................................................................................20
2.1.4. cc .............................................................................................21
2.1.5. commit ......................................................................................22
2.1.6. delete ........................................................................................22
2.1.7. pskgen .......................................................................................23
2.1.8. reject .........................................................................................23
2.1.9. reset ..........................................................................................25
2.1.10. set ...........................................................................................25
2.1.11. show ........................................................................................26
2.1.12. undelete ...................................................................................28
2.2. Runtime ...............................................................................................30
2.2.1. about .........................................................................................30
2.2.2. alarm .........................................................................................30
2.2.3. arp ............................................................................................30
2.2.4. arpsnoop ....................................................................................31
2.2.5. ats .............................................................................................32
2.2.6. bigpond .....................................................................................32
2.2.7. blacklist .....................................................................................33
2.2.8. buffers .......................................................................................34
2.2.9. cam ...........................................................................................35
2.2.10. certcache ..................................................................................35
2.2.11. cfglog ......................................................................................35
2.2.12. connections ...............................................................................36
2.2.13. cpuid .......................................................................................36
2.2.14. crashdump ................................................................................37
2.2.15. dconsole ...................................................................................37
2.2.16. dhcp ........................................................................................38
2.2.17. dhcprelay ..................................................................................38
2.2.18. dhcpserver ................................................................................39
2.2.19. dns ..........................................................................................40
2.2.20. dnsbl .......................................................................................40
2.2.21. dynroute ...................................................................................41
2.2.22. frags ........................................................................................41
2.2.23. ha ............................................................................................42
2.2.24. hostmon ...................................................................................42
2.2.25. httpposter .................................................................................43
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 Bandwidth Management
Information
Manual
Operating System
Manual
Size Driver
1.3MB
File Name
dfl-800_1600_2500-bandwidth_management.pdf
Observations
Overview
In this document, the notation Objects->Address book means that in the tree on the left
side of the screen Objects first should be clicked (expanded) and then Address Book.
Most of the examples in this document are adapted for the DFL-800. The same settings can
easily be used for all other models in the series. The only difference is the names of the
interfaces. Since the DFL-1600 and DFL-2500 has more than one lan interface, the lan
interfaces are named lan1, lan2 and lan3 not just lan.
The screenshots in this document is from firmware version 2.04.00. If you are using a later
version of the firmware, the screenshots may not be identical to what you see on your
browser.
To prevent existing settings to interfere with the settings in these guides, reset the
firewall to factory defaults before starting.
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 Portforwarding for incoming SMTP connections on a WAN interface
Information
Manual
Operating System
Manual
Size Driver
1.2MB
File Name
dfl-800_1600_2500-portforwarding_smtp.pdf
Observations
Log into the DFL-800 web management and select the 'IP Rules' menu.
Create a new IP Rule Folder by clicking on the 'Add' button and selecting 'IP Rule Folder'.
Give the folder a meaningful name.
(you will not yet have any rules in your new folder )
Click on the newly created folder and create a new rule by clicking on the 'Add' button and selecting
'IP Rule'.
On the 'General' tab, enter a name of your choice into the 'Name' field.
Select 'SAT' from the 'Action' drop down menu.
Select 'SMTP-IN' from the 'Service' drop down menu.
Change the 'Schedule' option as needed (Selecting 'None' will ensure this rule is always applicable)
Under the 'Address Filter' section select the following options as in the screen shot below:
Source Interface: WAN 1
Source Network: all-nets
Destination Interface: core
Destination Network: wan1_ip (the address of the DFL-800's WAN interface)
Click on the 'SAT' tab.
Select 'Destination IP Address'
In the 'New IP Address:' box enter the name of your SMTP-server
(this should have been created previously in the 'Address Book' under the 'Objects' menu)
Click on 'OK'
Create a new rule by clicking on the 'Add' button and selecting 'IP Rule'.
On the 'General' tab, enter a name of your choice into the 'Name' field.
Select 'Allow' from the 'Action' drop down menu.
Select 'SMTP-IN' from the 'Service' drop down menu.
Change the 'Schedule' option as needed (Selecting 'None' will ensure this rule is always applicable)
Under the 'Address Filter' section select the following options as in the screen shot below:
Source Interface: wan 1
Source Network: all-nets
Destination Interface: core
Destination Network: wan1_ip (the address of the DFL-800's WAN interface)
Click on 'OK'.
You should now have two rules in your folder as in the screen shot below
Click on 'Configuration' menu item and select the 'Save and Activate' option.
After a short wait while the rules are applied, the Firewall should pass SMTP traffic through to your
SMTP server.
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 Example on VPN connection from roaming PPTP clients to the DFL-800
Information
Manual
Operating System
Manual
Size Driver
1.1MB
File Name
dfl-800_1600_2500-vpn_pptp_server_for_remote_access.pdf
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 User's Manual v1.08
Information
Manual
Operating System
Manual
Size Driver
6.6MB
File Name
dfl_firewall_usermanual_v1.08.pdf
Observations
Preface ...............................................................................................................12
1. NetDefendOS Overview ....................................................................................14
1.1. Features ................................................................................................14
1.2. NetDefendOS Architecture ......................................................................17
1.2.1. State-based Architecture ...............................................................17
1.2.2. NetDefendOS Building Blocks .......................................................17
1.2.3. Basic Packet Flow ........................................................................18
1.3. NetDefendOS State Engine Packet Flow .....................................................20
2. Management and Maintenance ............................................................................25
2.1. Managing NetDefendOS ..........................................................................25
2.1.1. Overview ...................................................................................25
2.1.2. The Default Administrator Account .................................................26
2.1.3. The Web Interface .......................................................................26
2.1.4. The CLI .....................................................................................30
2.1.5. CLI Scripts .................................................................................36
2.1.6. Secure Copy ...............................................................................39
2.1.7. The Console Boot Menu ...............................................................41
2.1.8. Management Advanced Settings .....................................................43
2.1.9. Working with Configurations .........................................................44
2.2. Events and Logging ................................................................................49
2.2.1. Overview ...................................................................................49
2.2.2. Event Messages ...........................................................................49
2.2.3. Event Message Distribution ...........................................................49
2.2.4. Advanced Log Settings .................................................................52
2.3. RADIUS Accounting ..............................................................................54
2.3.1. Overview ...................................................................................54
2.3.2. RADIUS Accounting Messages ......................................................54
2.3.3. Interim Accounting Messages ........................................................56
2.3.4. Activating RADIUS Accounting .....................................................56
2.3.5. RADIUS Accounting Security ........................................................56
2.3.6. RADIUS Accounting and High Availability ......................................56
2.3.7. Handling Unresponsive Servers ......................................................57
2.3.8. Accounting and System Shutdowns .................................................57
2.3.9. Limitations with NAT ...................................................................57
2.3.10. RADIUS Advanced Settings ........................................................57
2.4. SNMP Monitoring ..................................................................................59
2.4.1. SNMP Advanced Settings .............................................................60
2.5. The pcapdump Command ........................................................................62
2.6. Maintenance ..........................................................................................65
2.6.1. Auto-Update Mechanism ...............................................................65
2.6.2. Creating Backup Files ...................................................................65
2.6.3. Configuration Backup and Restore ..................................................66
2.6.4. Restore to Factory Defaults ............................................................67
3. Fundamentals ...................................................................................................70
3.1. The Address Book ..................................................................................70
3.1.1. Overview ...................................................................................70
3.1.2. IP Addresses ...............................................................................70
3.1.3. Ethernet Addresses .......................................................................72
3.1.4. Address Groups ...........................................................................73
3.1.5. Auto-Generated Address Objects ....................................................73
3.1.6. Address Book Folders ...................................................................74
3.2. Services ................................................................................................75
3.2.1. Overview ...................................................................................75
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 VLAN and Route Failover
Information
Manual
Operating System
Manual
Size Driver
938KB
File Name
dfl-800_1600_2500-vlan_and_route_failover.pdf
Observations
How to configure VLAN and route failover
This example requires a DFL-1600 or 2500 to be fully implemented. Most settings can
however also be used on a DFL-210 or DFL-800.
Two tag based VLANs will be created on lan3, that connect to switch port with VLAN tag.
Details:
- From lan1, lan2 and lan3: HTTP, HTTPS and DNS connect to Internet via wan2.
- From dmz: inbound and outbound SMTP services connect to Internet via wan1.
- All internal nets can also access the Mail server in dmz.
- Only VLAN2 can access the FTP server in dmz.
- If anyone of the wan interfaces is disconnected, the traffic from that interface will be
redirected to the other wan interface.
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 VPN Setup LAN to LAN using IPsec
Information
Manual
Operating System
Manual
Size Driver
1.7MB
File Name
dfl-800_1600_2500-vpn_using_an_ipsec_lan-to-lan_tunnel.pdf
Observations
Overview
In this document, the notation Objects->Address book means that in the tree on the left
side of the screen Objects first should be clicked (expanded) and then Address Book.
Most of the examples in this document are adapted for the DFL-800. The same settings can
easily be used for all other models in the series. The only difference is the names of the
interfaces. Since the DFL-1600 and DFL-2500 has more than one lan interface, the lan
interfaces are named lan1, lan2 and lan3 not just lan.
The screenshots in this document is from firmware version 2.04.00. If you are using a later
version of the firmware, the screenshots may not be identical to what you see on your
browser.
To prevent existing settings to interfere with the settings in these guides, reset the
firewall to factory defaults before starting.
Virtual private network using an IPsec lan-to-lan
tunnel
Crea one lan-to-lan IPsec VPN tunnel between firewall A and B.
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 Log Reference Guide v1.03
Information
Manual
Operating System
Manual
Size Driver
2.3MB
File Name
dfl_log_reference_guide_v1.03.pdf
Observations
Preface ...............................................................................................................27
1. Introduction .....................................................................................................29
1.1. Log Message Structure ............................................................................29
1.2. Context Parameters .................................................................................31
1.3. Statistics (usage) ....................................................................................35
1.4. Severity levels .......................................................................................36
2. Log Message Reference .....................................................................................38
2.1. ALG ....................................................................................................39
2.1.1. alg_session_open (ID: 00200001) ...................................................39
2.1.2. alg_session_closed (ID: 00200002) .................................................40
2.1.3. max_line_length_exceeded (ID: 00200003) ......................................40
2.1.4. alg_session_allocation_failure (ID: 00200009) ..................................40
2.1.5. invalid_client_http_header_received (ID: 00200100) ..........................41
2.1.6. invalid_url_format (ID: 00200101) .................................................41
2.1.7. unknown_client_data_received (ID: 00200105) .................................41
2.1.8. suspicious_data_received (ID: 00200106) .........................................42
2.1.9. invalid_chunked_encoding (ID: 00200107) .......................................42
2.1.10. invalid_server_http_header_received (ID: 00200108) ........................43
2.1.11. compressed_data_received (ID: 00200109) .....................................43
2.1.12. max_http_sessions_reached (ID: 00200110) ....................................43
2.1.13. failed_create_new_session (ID: 00200111) .....................................44
2.1.14. failure_connect_http_server (ID: 00200112) ....................................44
2.1.15. content_type_mismatch (ID: 00200113) .........................................44
2.1.16. wcf_override_full (ID: 00200114) .................................................45
2.1.17. content_filtering_disabled (ID: 00200115) ......................................45
2.1.18. max_download_size_reached (ID: 00200116) ..................................45
2.1.19. blocked_filetype (ID: 00200117) ...................................................46
2.1.20. out_of_memory (ID: 00200118) ....................................................46
2.1.21. wcf_servers_unreachable (ID: 00200119) .......................................46
2.1.22. wcf_srv_connection_error (ID: 00200120) ......................................47
2.1.23. wcf_server_unreachable (ID: 00200121) ........................................47
2.1.24. wcf_connecting (ID: 00200122) ....................................................48
2.1.25. wcf_server_connected (ID: 00200123) ...........................................48
2.1.26. wcf_primary_fallback (ID: 00200124) ...........................................48
2.1.27. request_url (ID: 00200125) ..........................................................48
2.1.28. request_url (ID: 00200126) ..........................................................49
2.1.29. request_url (ID: 00200129) ..........................................................49
2.1.30. out_of_memory (ID: 00200130) ....................................................50
2.1.31. restricted_site_notice (ID: 00200132) ............................................50
2.1.32. url_reclassification_request (ID: 00200133) ....................................50
2.1.33. max_smtp_sessions_reached (ID: 00200150) ..................................51
2.1.34. maximum_email_per_minute_reached (ID: 00200151) ......................51
2.1.35. failed_create_new_session (ID: 00200152) .....................................52
2.1.36. failed_connect_smtp_server (ID: 00200153) ...................................52
2.1.37. invalid_server_response (ID: 00200155) .........................................52
2.1.38. sender_email_id_mismatched (ID: 00200157) .................................53
2.1.39. sender_email_id_is_in_blacklist (ID: 00200158) ..............................53
2.1.40. recipient_email_id_in_blacklist (ID: 00200159) ...............................53
2.1.41. some_recipient_email_ids_are_in_blocklist (ID: 00200160) ...............54
2.1.42. base64_decode_failed (ID: 00200164) ...........................................54
2.1.43. base64_decode_failed (ID: 00200165) ...........................................55
2.1.44. blocked_filetype (ID: 00200166) ...................................................55
Company
D-Link
Categories
Networks Cards
Model
D-Link DFL-260
Description
NetDefend UTM Firewall 260 VPN Setup LAN to Multi-LAN
Information
Manual
Operating System
Manual
Size Driver
1.2MB
File Name
dfl-800_1600_2500-vpn_lan_to_multi_lan.pdf
Observations
Overview
In this document, the notation Objects->Address book means that in the tree on the left
side of the screen Objects first should be clicked (expanded) and then Address Book.
Most of the examples in this document are adapted for the DFL-800. The same settings can
easily be used for all other models in the series. The only difference is the names of the
interfaces. Since the DFL-1600 and DFL-2500 has more than one lan interface, the lan
interfaces are named lan1, lan2 and lan3 not just lan.
The screenshots in this document is from firmware version 2.04.00. If you are using a later
version of the firmware, the screenshots may not be identical to what you see on your
browser.
To prevent existing settings to interfere with the settings in these guides, reset the
firewall to factory defaults before starting.
Configure lan-to-lan tunnels between a main office and two
remote offices (sometimes called Hub and Spoke).
This guide shows how to configure tunnels between three firewalls. First create
one tunnel from firewall A to firewall B and then a second tunnel from firewall A
to firewall C. Users behind firewall B should be able to reach resources behind
firewall C (and the other way around).
Access to Official Website D-Link
Welcome to the HelpDrivers, driver for printers.
Original files: In HelpDrivers, all drivers, manuals, BIOS, etc. are those originally provided by the official manufacturers. Click here to learn more
You can download by either clicking the 'Download' button. From the File Download window, verify that "Save" is selected and click OK.
Do not rename the file you're downloading, it may cause installation problems.