NETGEAR FVS338 - ProSafe VPN Firewall 50 Router Reference Manual

PDF

Document

FVS338 ProSafe VPN

Firewall 50 Reference

Manual

NETGEAR , Inc.

350 East Plumeria Drive

Santa Clara, CA 95134 USA

March 2009

202-10046-08 v1.0

Trademarks

NETGEAR, the NETGEAR logo and ProSafe are trademarks and/or registered trademarks of NETGEAR, Inc.

Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation.

Other brand and product names are registered trademarks or trademarks of their respective holders.

Statement of Conditions

In the interest of improving internal design, operational function, and/or reliability, NETGEAR reserves the right to make changes to the products described in this document without notice.

NETGEAR does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s) described herein.

Federal Communications Commission (FCC) Compliance Notice: Radio Frequency

Notice

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

• 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.

EU Regulatory Compliance Statement

ProSafe VPN Firewall 50 is compliant with the following EU Council Directives: 89/336/EEC and LVD 73/23/EEC.

Compliance is verified by testing to the following standards: EN55022 Class B, EN55024 and EN60950-1.

Bestätigung des Herstellers/Importeurs

Es wird hiermit bestätigt, daß das ProSafe VPN Firewall 50 gemäß der im BMPT-AmtsblVfg 243/1991 und Vfg 46/1992 aufgeführten Bestimmungen entstört ist. Das vorschriftsmäßige Betreiben einiger Geräte (z.B. Testsender) kann jedoch gewissen Beschränkungen unterliegen. Lesen Sie dazu bitte die Anmerkungen in der Betriebsanleitung.

Das Bundesamt für Zulassungen in der Telekommunikation wurde davon unterrichtet, daß dieses Gerät auf den Markt gebracht wurde und es ist berechtigt, die Serie auf die Erfüllung der Vorschriften hin zu überprüfen.

Certificate of the Manufacturer/Importer

It is hereby certified that the ProSafe VPN Firewall 50 has been suppressed in accordance with the conditions set out in the BMPT-AmtsblVfg 243/1991 and Vfg 46/1992. The operation of some equipment (for example, test transmitters) in accordance with the regulations may, however, be subject to certain restrictions. Please refer to the notes in the operating instructions. ii v1.0, March 2009

Federal Office for Telecommunications Approvals has been notified of the placing of this equipment on the market and has been granted the right to test the series for compliance with the regulations.

Voluntary Control Council for Interference (VCCI) Statement

This equipment is in the second category (information equipment to be used in a residential area or an adjacent area thereto) and conforms to the standards set by the Voluntary Control Council for Interference by Data Processing

Equipment and Electronic Office Machines aimed at preventing radio interference in such residential areas.

When used near a radio or TV receiver, it may become the cause of radio interference.

Read instructions for correct handling.

Additional Copyrights

TERMS

Redistribution and use in source and binary forms, with or without modification, are permitted subject to the following conditions:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. The copyright holder's name must not be used to endorse or promote any products derived from this software without his specific prior written permission.

This software is provided 'as is' with no express or implied warranties of correctness or fitness for purpose.

v1.0, March 2009 iii

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions * are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment: “This product includes software developed by the OpenSSL

Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)”

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL

Toolkit (http://www.openssl.org/)"

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY

EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS

CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR

PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY

OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING

NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young ([email protected]). This product includes software written by Tim Hudson ([email protected]).

iv v1.0, March 2009

MD5

PPP

Zlib

License to copy and use this software is granted provided that it is identified as the "RSA Data

Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing this software or this function. License is also granted to make and use derivative works provided that such works are identified as "derived from the RSA Data Security, Inc. MD5 Message-

Digest Algorithm" in all material mentioning or referencing the derived work.

RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It is provided "as is" without express or implied warranty of any kind.

These notices must be retained in any copies of any part of this documentation and/or software.

Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by Carnegie Mellon University. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED

WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF

MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.

zlib.h -- interface of the 'zlib' general purpose compression library version 1.1.4, March 11th,

This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.

Jean-loup Gailly: [email protected]; Mark Adler: [email protected]

The data format used by the zlib library is described by RFCs (Request for Comments) 1950 to 1952 in the files ftp://ds.internic.net/rfc/rfc1950.txt

(zlib format), rfc1951.txt (deflate format) and rfc1952.txt (gzip format) v v1.0, March 2009

Product and Publication Details

Model Number:

Publication Date:

FVS338

March 2009

Product Family:

Product Name:

VPN firewall

ProSafe VPN Firewall 50

Home or Business Product: Business

Language: English

Publication Part Number: 202-10046-08

Publication Version Number 1.0

vi v1.0, March 2009

About This Manual

Conventions, Formats and Scope ...................................................................................xiii

Revision History ...............................................................................................................xiv

Chapter 1

Introduction

Key Features ..................................................................................................................1-1

Full Routing on Both the Broadband and Serial WAN Ports ....................................1-2

A Powerful, True Firewall with Content Filtering ......................................................1-2

Security ....................................................................................................................1-3

Autosensing Ethernet Connections with Auto Uplink ...............................................1-3

Extensive Protocol Support ......................................................................................1-3

Easy Installation and Management ..........................................................................1-4

Maintenance and Support ........................................................................................1-5

Package Contents ..........................................................................................................1-6

Router Hardware Components .......................................................................................1-6

Router Front Panel ...................................................................................................1-6

Router Rear Panel ...................................................................................................1-8

Factory Default Login .....................................................................................................1-9

Chapter 2

Connecting the FVS338 to the Internet

Connecting the VPN Firewall to Your Network ...............................................................2-1

Logging in to the VPN Firewall ................................................................................2-1

Configuring your Internet Connection ......................................................................2-2

Broadband ISP Settings ....................................................................................2-2

Dialup ISP Serial WAN port Settings .................................................................2-4

Setting the Router’s MAC Address (Advanced Options) .........................................2-6

To Change the Router Default MAC Address ....................................................2-6

To Change the MTU Value for Your Dialup Modem: ..........................................2-7

Manually Configuring Your Internet Connection .......................................................2-8

Contents vii v1.0, March 2009

Manually Configure WAN1 ISP Settings: ...........................................................2-9

Programming the Traffic Meter (if Desired) ............................................................ 2-11

To Enable the Traffic Meter .............................................................................. 2-11

Configuring the WAN Mode ..........................................................................................2-13

Configuring Dynamic DNS (If Needed) .........................................................................2-14

Chapter 3

LAN Configuration

Choosing the Firewall DHCP Options ............................................................................3-1

Configuring the LAN Setup Options .........................................................................3-2

Configuring Multi-Home LAN IPs .............................................................................3-5

Managing Groups and Hosts ..........................................................................................3-6

Creating the Network Database ...............................................................................3-7

Setting Up Address Reservation ............................................................................3-10

Configuring Static Routes .............................................................................................3-10

Static Route Example ............................................................................................. 3-11

RIP Configuration ...................................................................................................3-12

Chapter 4

Firewall Protection and Content Filtering

About Firewall Security ...................................................................................................4-1

Using Rules to Block or Allow Specific Kinds of Traffic ............................................4-2

Services-Based Rules .......................................................................................4-2

Order of Precedence for Firewall Rules ............................................................4-6

Setting LAN WAN Rules .................................................................................................4-7

LAN WAN Outbound Services Rules .......................................................................4-8

LAN WAN Inbound Services Rules ..........................................................................4-9

Attack Checks ........................................................................................................4-10

Session Limit ..........................................................................................................4-12

Inbound Rules Examples .......................................................................................4-13

Hosting A Local Public Web Server .................................................................4-13

Allowing Videoconference from Restricted Addresses ....................................4-13

Setting Up One-to-One NAT Mapping .............................................................4-14

Specifying an Exposed Host ............................................................................4-15

Outbound Rules Example – Blocking Instant Messenger ......................................4-16

Adding Customized Services ........................................................................................4-17

Specifying Quality of Service (QoS) Priorities ..............................................................4-19 viii Contents v1.0, March 2009

Setting a Schedule to Block or Allow Specific Traffic ....................................................4-20

Setting Block Sites (Content Filtering) ..........................................................................4-20

Enabling Source MAC Filtering ....................................................................................4-23

IP/MAC Binding ......................................................................................................4-24

Setting Up Port Triggering ............................................................................................4-26

Bandwidth Limiting .......................................................................................................4-28

E-Mail Notifications of Event Logs and Alerts ...............................................................4-30

Administrator Information .............................................................................................4-34

Chapter 5

Virtual Private Networking

Considerations for Dual WAN Port Systems ..................................................................5-1

Using the VPN Wizard for Client and Gateway Configurations ......................................5-2

Creating Gateway to Gateway VPN Tunnels with the Wizard .................................5-2

Creating a Client to Gateway VPN Tunnel ...............................................................5-5

Use the VPN Wizard Configure the Gateway for a Client Tunnel ......................5-6

Use the NETGEAR VPN Client Security Policy Editor to Create a Secure Connection

5-7

Testing the Connections and Viewing Status Information ............................................. 5-11

NETGEAR VPN Client Status and Log Information ............................................... 5-11

FVS338 VPN Connection Status and Logs ............................................................5-13

IKE Policies ..................................................................................................................5-14

IKE Policy Operation ..............................................................................................5-14

IKE Policy Table .....................................................................................................5-15

VPN Policies .................................................................................................................5-16

VPN Policy Operation ............................................................................................5-16

VPN Policy Table ....................................................................................................5-16

VPN Tunnel Connection Status ..............................................................................5-17

Extended Authentication (XAUTH) Configuration .........................................................5-18

Configuring XAUTH for VPN Clients ......................................................................5-19

User Database Configuration .................................................................................5-20

RADIUS Client Configuration .................................................................................5-21

Assigning IP Addresses to Remote Users (ModeConfig) .............................................5-23

ModeConfig Operation ...........................................................................................5-24

Setting Up ModeConfig ..........................................................................................5-24

Configuring the ProSafe VPN Client for ModeConfig .............................................5-28

Contents ix v1.0, March 2009

Certificates ....................................................................................................................5-31

Trusted Certificates (CA Certificates) .....................................................................5-32

Self Certificates ......................................................................................................5-33

Managing your Certificate Revocation List (CRL) ..................................................5-36

Chapter 6

Router and Network Management

Performance Management .............................................................................................6-1

VPN Firewall Features That Reduce Traffic .............................................................6-1

Service Blocking ................................................................................................6-1

Block Sites .........................................................................................................6-3

Source MAC Filtering ........................................................................................6-4

VPN Firewall Features That Increase Traffic ...........................................................6-4

Port Forwarding .................................................................................................6-4

Port Triggering ...................................................................................................6-6

VPN Tunnels ......................................................................................................6-6

Using QoS to Shift the Traffic Mix ............................................................................6-6

Tools for Traffic Management ...................................................................................6-7

Administration .................................................................................................................6-7

Changing Passwords and Settings ..........................................................................6-7

RADIUS Server External Authentication ..................................................................6-9

Enabling Remote Management Access .................................................................6-10

Using a SNMP Manager ........................................................................................6-13

Settings Backup and Firmware Upgrade ...............................................................6-15

Backup and Restore Settings ..........................................................................6-15

Router Upgrade ...............................................................................................6-16

Setting the Time Zone ............................................................................................6-17

Monitoring the Router ...................................................................................................6-18

Enabling the Traffic Meter ......................................................................................6-19

Setting Login Failures and Attacks Notification ......................................................6-20

Viewing Port Triggering Status ...............................................................................6-22

Viewing Router Configuration and System Status .................................................6-23

Monitoring WAN Ports Status .................................................................................6-24

Monitoring VPN Tunnel Connection Status ............................................................6-25

VPN Logs ...............................................................................................................6-26

DHCP Log ..............................................................................................................6-26 x Contents v1.0, March 2009

Performing Diagnostics ..........................................................................................6-27

Chapter 7

Troubleshooting

Basic Functions ..............................................................................................................7-1

Power LED Not On ...................................................................................................7-1

LEDs Never Turn Off ................................................................................................7-2

LAN or Internet Port LEDs Not On ...........................................................................7-2

Troubleshooting the Web Configuration Interface ..........................................................7-2

Troubleshooting the ISP Connection ..............................................................................7-4

Troubleshooting a TCP/IP Network Using a Ping Utility .................................................7-5

Testing the LAN Path to Your Firewall ......................................................................7-5

Testing the Path from Your PC to a Remote Device ................................................7-6

Restoring the Default Configuration and Password ........................................................7-7

Problems with Date and Time .........................................................................................7-7

Appendix A

Default Settings and Technical Specifications

Appendix B

System Logs and Error Messages

System Log Messages .................................................................................................. B-1

System Startup ........................................................................................................ B-1

Reboot ..................................................................................................................... B-2

NTP ......................................................................................................................... B-2

Login/Logout ........................................................................................................... B-3

Firewall Restart ....................................................................................................... B-3

IPSec Restart .......................................................................................................... B-4

WAN Status ............................................................................................................. B-4

Auto Rollover .................................................................................................... B-4

PPP Logs .......................................................................................................... B-5

Web Filtering and Content Filtering Logs ................................................................ B-7

Traffic Metering Logs ............................................................................................... B-9

Unicast Logs ........................................................................................................... B-9

ICMP Redirect Logs ......................................................................................... B-9

FTP Logging .......................................................................................................... B-10

Invalid Packet Logging .......................................................................................... B-10

Routing Logs ............................................................................................................... B-13

Contents v1.0, March 2009 xi

LAN to WAN Logs ................................................................................................. B-14

WAN to LAN Logs ................................................................................................. B-14

Appendix C

Related Documents

Appendix D

Two Factor Authentication

Why do I need Two-Factor Authentication? ................................................................... D-1

What are the benefits of Two-Factor Authentication? ............................................. D-1

What is Two-Factor Authentication ......................................................................... D-2

NETGEAR Two-Factor Authentication Solutions ........................................................... D-2

Index xii v1.0, March 2009

Contents

About This Manual

The NETGEAR® ProSafe™ VPN Firewall 50 FVS338 Reference Manual describes how to install, configure and troubleshoot the ProSafe VPN Firewall 50. The information in this manual is intended for readers with intermediate computer and Internet skills.

Conventions, Formats and Scope

The conventions, formats, and scope of this manual are described in the following paragraphs.

• Typographical Conventions. This manual uses the following typographical conventions

Italics

Bold

Fixed italics

Emphasis, books, CDs, file and server names, extensions

User input, IP addresses, GUI screen text

Command prompt, CLI text, code

URL links

• Formats. This manual uses the following formats to highlight special messages:

Note: This format is used to highlight information of importance or special interest.

Tip: This format is used to highlight a procedure that will save time or resources.

Warning: Ignoring this type of note may result in a malfunction or damage to the equipment.

xiii v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Danger: This is a safety warning. Failure to take heed of this notice may result in personal injury or death.

For more information about network, Internet, firewall, and VPN technologies, see the links to the

NETGEAR website in Appendix C, “Related Documents” .

Note: Updates to this product are available on the NETGEAR, Inc. website at http://kbserver.netgear.com/products/FVS338.asp

Revision History

Part Number

202-10046-02 1.0

202-10046-03 1.0

202-10046-04 1.0

202-10046-05 1.0

202-10046-05

202-10046-06

202-10046-08

Version

Number

Description

1.1

1.2

1.0

Product update: New firmware and new user Interface

Remove Trend Micro

Updated features

New features: IP/MAC Binding; Bandwidth Limits; Session Limits; IKE Keep

Alive; Dead Peer Detection; Oray support

Document corrections

Document additions to Appendix B

Maintenance release

Adds these corrections and topics for the March 2009 firmware maintenance release:

• WIKID 2 factor authentication

• SIP AGL support

• DHCP Relay support

• Update VPN configuration procedure topics

• Update the Certificate management topic

• Correct the firewall scheduling topic xiv About This Manual v1.0, March 2009

Chapter 1 Introduction

The ProSafe VPN Firewall 50 with 8 port switch connects your local area network (LAN) to the

Internet through an external access device such as a cable modem or DSL modem.

The FVS338 is a complete security solution that protects your network from attacks and intrusions. For example, the FVS338 provides support for Stateful Packet Inspection, Denial of

Service (DoS) attack protection and multi-NAT support.The VPN firewall supports multiple Web content filtering options, plus browsing activity reporting and instant alerts—both, via e-mail.

Network administrators can establish restricted access policies based on time-of-day, Website addresses and address keywords, and share high-speed cable/DSL Internet access for a local network.

The FVS338 is a plug-and-play device that can be installed and configured within minutes.

This chapter contains the following sections:

• “Key Features” on page 1-1

• “Package Contents” on page 1-6

• “Router Hardware Components” on page 1-6

• “Factory Default Login” on page 1-9

Key Features

The VPN firewall provides the following features:

• One 10/100 Mbps port for an Ethernet connection to a broadband WAN device, such as a cable modem or DSL modem, and one serial port for a dial-up modem connection to the Internet through the public switched telephone network (PSTN).

• Dual WAN ports (one broadband and one serial) provide for increased system reliability.

• Support for up to 50 VPN tunnels.

• Support for up to 400 internal LAN users (and 50K connections).

• Easy, web-based setup for installation and management.

• URL keyword Content Filtering and Site Blocking Security.

• Quality of Service (QoS) support for traffic prioritization.

Introduction 1-1 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

• Built in 8-port 10/100 Mbps switch.

• Extensive Protocol Support.

• Login capability.

• SNMP for manageability.

• Front panel LEDs for easy monitoring of status and activity.

• Flash memory for firmware upgrade.

Full Routing on Both the Broadband and Serial WAN Ports

You can install, configure, and operate the FVS338 to take full advantage of a variety of routing options on both the serial and broadband WAN ports, including:

• Internet access via either the serial or broadband port.

• Auto rollover connectivity (fail-over) through an analog modem connected to the serial port

If the broadband Internet connection fails, after waiting for an pre-specified amount of time the FVS338 can automatically establish a backup dial-up Internet connection via the serial port on the firewall.

A Powerful, True Firewall with Content Filtering

Unlike simple Internet sharing NAT routers, the FVS338 is a true firewall, using stateful packet inspection to defend against hacker attacks. Its firewall features include:

• DoS protection. Automatically detects and thwarts DoS attacks such as Ping of Death, SYN

Flood, LAND Attack, and IP Spoofing.

• Blocks unwanted traffic from the Internet to your LAN.

• Blocks access from your LAN to Internet locations or services that you specify as off-limits.

• Logs security incidents. The FVS338 will log security events such as blocked incoming traffic, port scans, attacks, and administrator logins. You can configure the firewall to email the log to you at specified intervals. You can also configure the firewall to send immediate alert messages to your email address or email pager whenever a significant event occurs.

• With its URL keyword filtering feature, the FVS338 prevents objectionable content from reaching your PCs. The firewall allows you to control access to Internet content by screening for keywords within Web addresses. You can configure the firewall to log and report attempts to access objectionable Internet sites.

1-2 Introduction v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Security

The VPN firewall is equipped with several features designed to maintain security, as described in this section.

• PCs Hidden by NAT. NAT opens a temporary path to the Internet for requests originating from the local network. Requests originating from outside the LAN are discarded, preventing users outside the LAN from finding and directly accessing the PCs on the LAN.

• Port Forwarding with NAT. Although NAT prevents Internet locations from directly accessing the PCs on the LAN, the firewall allows you to direct incoming traffic to specific

PCs based on the service port number of the incoming request. You can specify forwarding of single ports or ranges of ports.

• Exposed Host (Software DMZ). Incoming traffic from the Internet is normally discarded by the firewall unless the traffic is a response to one of your local computers or a service for which you have configured an inbound rule. Instead of discarding this traffic, you can have it forwarded to one computer on your network.

Autosensing Ethernet Connections with Auto Uplink

With its internal 8-port 10/100 switch, the FVS338 can connect to either a 10 Mbps standard

Ethernet network or a 100 Mbps Fast Ethernet network. Both the LAN and WAN interfaces are autosensing and capable of full-duplex or half-duplex operation.

The firewall incorporates Auto Uplink TM technology. Each Ethernet port will automatically sense whether the Ethernet cable plugged into the port should have a ‘normal’ connection such as to a

PC or an ‘uplink’ connection such as to a switch or hub. That port will then configure itself to the correct configuration. This feature also eliminates the need to worry about crossover cables, as

Auto Uplink will accommodate either type of cable to make the right connection.

Extensive Protocol Support

The VPN firewall supports the Transmission Control Protocol/Internet Protocol (TCP/IP) and

Routing Information Protocol (RIP).

• IP Address Sharing by NAT.

The VPN firewall allows several networked PCs to share an

Internet account using only a single IP address, which may be statically or dynamically assigned by your Internet service provider (ISP). This technique, known as NAT, allows the use of an inexpensive single-user ISP account.

Introduction 1-3 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

• Automatic Configuration of Attached PCs by DHCP.

The VPN firewall dynamically assigns network configuration information, including IP, gateway, and domain name server

(DNS) addresses, to attached PCs on the LAN using the Dynamic Host Configuration Protocol

(DHCP). This feature greatly simplifies configuration of PCs on your local network.

• DNS Proxy.

When DHCP is enabled and no DNS addresses are specified, the firewall provides its own address as a DNS server to the attached PCs. The firewall obtains actual DNS addresses from the ISP during connection setup and forwards DNS requests from the LAN.

• PPP over Ethernet (PPPoE).

PPPoE is a protocol for connecting remote hosts to the Internet over a DSL connection by simulating a dial-up connection. This feature eliminates the need to run a login program such as EnterNet or WinPOET on your PC.

Easy Installation and Management

You can install, configure, and operate the ProSafe VPN Firewall 50 within minutes after connecting it to the network. The following features simplify installation and management tasks:

• Browser-based management . Browser-based configuration allows you to easily configure your firewall from almost any type of personal computer, such as Windows, Macintosh, or

Linux. A user-friendly Setup Wizard is provided and online help documentation is built into the browser-based Web Management Interface.

• Smart Wizard . The VPN firewall automatically senses the type of Internet connection, asking you only for the information required for your type of ISP account.

• VPN Wizard . The VPN firewall includes the NETGEAR VPN Wizard to easily configure

VPN tunnels according to the recommendations of the Virtual Private Network Consortium

(VPNC) to ensure the VPN tunnels are interoperable with other VPNC-compliant VPN routers and clients.

• SNMP.

The VPN firewall supports the Simple Network Management Protocol (SNMP) to let you monitor and manage log resources from an SNMP-compliant system manager. The SNMP system configuration lets you change the system variables for MIB2.

• Diagnostic functions. The firewall incorporates built-in diagnostic functions such as Ping,

Trace Route, DNS lookup, and remote reboot.

• Remote management.

The firewall allows you to securely login to the Web Management

Interface from a remote location on the Internet. For additional security, you can limit remote management access to a specified remote IP address or range of addresses, and you can choose a nonstandard port number.

• Visual monitoring.

The VPN firewall’s front panel LEDs provide an easy way to monitor its status and activity.

1-4 Introduction v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Maintenance and Support

NETGEAR offers the following features to help you maximize your use of the VPN firewall:

• Flash memory for firmware upgrade

• Free technical support seven days a week, twenty-four hours a day

Introduction v1.0, March 2009

1-5

FVS338 ProSafe VPN Firewall 50 Reference Manual

Package Contents

The product package should contain the following items:

• ProSafe VPN Firewall 50.

• AC power adapter.

• Category 5 Ethernet cable.

• Resource CD , including:

– Application Notes and other helpful information.

– ProSafe VPN Client Software – one user license.

• Warranty and Support Information Card.

If any of the parts are incorrect, missing, or damaged, contact your NETGEAR dealer. Keep the carton, including the original packing materials, in case you need to return the firewall for repair.

Router Hardware Components

Following is a description of the front and rear panels of the FVS338, including instructions for installing the FVS338 using the rack mounting hardware.

Router Front Panel

The ProSafe VPN Firewall 50 front panel shown below contains the port connections, status

LEDs, and the factory defaults reset button.

Figure 1-1

Power

LED

Test

LED

Modem

LED

Internet

LEDs

1-6 v1.0, March 2009

Local

LEDs

Introduction

FVS338 ProSafe VPN Firewall 50 Reference Manual

The table below describes each item on the front panel and its operation.

Table 1-1.

Object Descriptions

Object Activity

Power LED On (Green)

Off

Test LED On (Amber)

Blinking (Amber)

Off

MDM LED On (Green)

Description

Power is supplied to the router.

Power is not supplied to the router.

Test mode: The system is initializing or the initialization has failed.

Writing to Flash memory (during upgrading or resetting to defaults).

The system has booted successfully.

The serial port has successfully connected to an ISP and received an

IP Address.

Server data is being transmitted or received by the serial port.

The serial port has no link.

Internet

LEDs

Blinking (Green)

Off

Link/Act LED

On (Green)

Blinking (Green)

Off

100 LED

On (Green)

Off

Local LEDs Link/Act LED

On (Green)

Blinking (Green)

Off

100 LED

On (Green)

Off

The WAN port has detected a link with a connected Ethernet device.

Data is being transmitted or received by the WAN port.

The WAN port has no link.

The WAN port is operating at 100 Mbps.

The WAN port is operating at 10 Mbps.

The LAN port has detected a link with a connected Ethernet device.

Data is being transmitted or received by the LAN port.

The LAN port has no link.

The LAN port is operating at 100 Mbps.

The LAN port is operating at 10 Mbps.

Introduction v1.0, March 2009

1-7

FVS338 ProSafe VPN Firewall 50 Reference Manual

Router Rear Panel

The rear panel of the ProSafe VPN Firewall 50 ( Figure 1-2 ) contains the On/Off switch and AC power connection.

Figure 1-2

Viewed from left to right, the rear panel contains the following elements:

• Modem port – serves as the WAN2 Internet port through the public switched telephone network (PSTN).

• Factory Defaults reset button.

• Local ports – 8-port RJ-45 10/100 Mbps Fast Ethernet Switch, N-way automatic speed negotiation, auto MDI/MDIX.

• Internet port – serves as the WAN1 Internet port. One RJ-45 WAN port, N-way automatic speed negotiation, Auto MDI/MDIX.

• On/Off switch

• DC power in (12 VDC, 1.2A)

1-8 v1.0, March 2009

Introduction

FVS338 ProSafe VPN Firewall 50 Reference Manual

Factory Default Login

Check the label on the bottom of the FVS338’s enclosure if you forget the following factory default information:

• IP Address: http://192.168.1.1

to reach the Web-based GUI from the LAN

• User name: admin

• Password: password

LAN IP Address

User Name

Password

Figure 1-3

To log in to the FVS338 once it is connected:

Go to http://192.168.1.1

Figure 1-4

Enter admin for User Name and password for Password

Introduction v1.0, March 2009

1-9

FVS338 ProSafe VPN Firewall 50 Reference Manual

1-10 v1.0, March 2009

Introduction

Chapter 2 Connecting the FVS338 to the Internet

This section provides instructions for connecting the VPN firewall, including these topics:

• “Connecting the VPN Firewall to Your Network” on page 2-1

• “Configuring the WAN Mode” on page 2-13

• “Configuring Dynamic DNS (If Needed)” on page 2-14

Setting up VPN tunnels are covered in Chapter 5, “Virtual Private Networking” :

Connecting the VPN Firewall to Your Network

To physically connect your VPN firewall, refer to the I FVS338 ProSafe VPN Firewall 50

Installation Guide (a copy is also available on your Resource CD).

Logging in to the VPN Firewall

Note: To connect to the firewall, your computer needs to be configured to obtain an IP address automatically via DHCP.

To log in to the VPN firewall:

Step 1.

Open a Internet Explorer, Netscape® Navigator, or Firefox browser. In the browser window, enter http://192.168.1.1 in the address field. The FVS338 login screen will display.

Figure 2-1

2-1 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Enter admin for the User Name and password for the Password, both in lower case letters.The firewall user name and password are not the same as any user name or password you may use to log in to your Internet connection.

Click Login. The Broadband ISP Settings screen will display.

Note: See “Enabling Remote Management Access” on page 6-10 for more information on Remote management enable. If you enable remote management, change your password to a more secure one than the standard factory default (see “Changing Passwords and Settings” on page 6-7 ).

Configuring your Internet Connection

You can configure both Broadband ISP Settings and Dialup ISP Settings.from the WAN Settings menu.

Broadband ISP Settings

Step 1.

Select Network Configuration from the main menu and WAN Settings from the submenu.

The Broadband ISP Settings screen will display.

Figure 2-2

2-2 v1.0, March 2009

Connecting the FVS338 to the Internet

FVS338 ProSafe VPN Firewall 50 Reference Manual

Click Auto Detect at the bottom of the screen to automatically detect the type of Internet connection provided by your ISP. Auto Detect will probe for different connection methods and suggest one that your ISP will most likely support.

When Auto Detect successfully detects an active Internet service, it reports which connection type it discovered. The options are described in the following table.

Table 2-1. Internet connection methods

Connection Method Data Required

PPPoE

PPTP

BigPond Cable

DHCP (Dynamic IP)

Fixed IP

No data is required.

IP address and related data supplied by your ISP.

Click Broadband Status at the top right of the screen to verify your Broadband connection status. Click Connect if connection not already present.

Figure 2-3

If Auto Detect does not find a connection, you will be prompted to check the physical connection between your firewall and the cable or DSL line or to check your Router’s MAC address (see “Setting the Router’s MAC Address (Advanced Options)” on page 2-6 ).

Connecting the FVS338 to the Internet v1.0, March 2009

2-3

FVS338 ProSafe VPN Firewall 50 Reference Manual

Set up the traffic meter for ISP1 if desired. See “Programming the Traffic Meter (if Desired)” on page 2-11 .

Note: At this point in the configuration process, you are now connected to the Internet through the broadband Ethernet WAN. Optionally, you can continue with the configuration of the dialup ISP serial WAN interface.

The Dialup Settings screen will assist you in setting up the router to access the Internet connection using a dialup modem. Since the Dialup ISP Settings must be configured manually, you will need all of your ISP settings information before you begin.

Dialup ISP Serial WAN port Settings

Step 1.

Select Network Configuration from the main menu, WAN Settings from the submenu and click the Dialup ISP Settings tab to display the Dialup settings screen.

Figure 2-4

Enter the following Dialup Account settings: a. Account/User name : Enter the account name or the user name provided by your ISP. This name will be used to log in to the ISP server. b. Password : The account password for the dialup ISP

2-4 Connecting the FVS338 to the Internet v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual c.

Telephone : The telephone number or access number to dial for connectivity. Type in the number using the format described in your modem's user manual. d. Alternative Telephone : An alternative number which will be dialed if the first is not available (optional).

Specify the method to use for your Dial-up Connection Status.

The VPN firewall can automatically dial to the ISP when a connection is needed or can be configured to wait for manual intervention.: a.

Check the Connect automatically disconnect after idle for ___ min. radios box for the modem to connect automatically. Specify the idle minute amount. The router will connect whenever an outbound connection request is made from a computer on the LAN. The connection will be terminated if there is no data transfer during the specified time interval. b.

Check the Connect and disconnect manually radio box to disable auto dialing and allow manual control over connecting via dial-up. To connect manually, click the DIAL-Up

Status link at the top and then click Connect or Disconnect .

Internet (IP Address). DialUp ISPs usually assign the IP address automatically when connecting. a.

The default setting of Get Dynamically from ISP will configure the router to accept the

ISP assigned IP address. b.

If your ISP has assigned a static IP address, select the Use Static IP Address radio box and enter the IP address in the IP Address field.

Check the Get Automatically From ISP radio box to use ISP assigned DNS server addresses

(default). To use different DNS addresses, check the Use These DNS Servers radio box and type in the DNS server IP addresses in the Primary DNS Server and Secondary DNS Server

(optional) fields.

Click Apply to save your settings or Cancel to revert to the previous settings.

Enter any modem specific parameters to tune the router for different modems: a. Serial Line Speed : Select the baud rate with which the serial port of the router and the modem connect. Available speeds range from 4.8Kbps to 460.8Kbps. b. Modem Type : If your modem type is listed in the pull-down menu, select it. For most

56Kbps modems, the U.S. Robotics 56K FAX EXT PnP selection should work. If this does not work, select User Defined Modem and type in the Initial String for your modem.

The Initial string is usually defined in the modem’s user manual.

Connecting the FVS338 to the Internet v1.0, March 2009

2-5

FVS338 ProSafe VPN Firewall 50 Reference Manual c.

Dial-up Type : Check the Tone radio box if your phone line supports touch tone dialing; select Pulse for pulse mode dialing. Select Other – use Dial String to configure additional options such as Auto-Answer, etc. (consult your modem manual for dial strings).

Set up the traffic meter for the Dialup ISP if desired (see “Programming the Traffic Meter (if

Desired)” on page 2-11 ).

Note: The response time of your serial port Internet connection will be slower than a broadband Internet connection.

Tip: If you experience connectivity problems with the Dialup ISP, try a different baud rate setting and ensure that the modem parameters you selected match the modem connected to the FVS338.

Setting the Router’s MAC Address (Advanced Options)

Each computer or router on your network has a unique 48-bit local Ethernet address. This is also referred to as the computer's MAC (Media Access Control) address. The default is set to Use

Default Address . If your ISP requires MAC authentication and another MAC address has been previously registered with your ISP, then you must enter that address.

To Change the Router Default MAC Address

Step 1.

Select Network Configuration from the main menu, Broadband ISP Settings from the submenu and click the Advanced link. Check the radio box for either: a. Use This computer’s MAC address, if this is the address your ISP expects, or b. Use this MAC Address and enter the MAC address that your ISP expects.

The format for the MAC address is XX:XX:XX:XX:XX:XX where X is a number from 0 to 9

(inclusive) or an alphabetical letter between A and F (inclusive).

Click Apply to save your settings or Cancel to revert to the previous settings

You may also change the default MTU Size and Port Speed for the Broadband link on this screen, based on the following criteria:

• MTU Size . The standard MTU (Maximum Transmit Unit) value for Ethernet networks is either 1500 Bytes or 1492 Bytes for PPPoE connections. Some ISPs may ask you to reduce the

MTU, but this is rarely required, and should not be done unless required by your ISP.

2-6 Connecting the FVS338 to the Internet v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

• Port Speed . In most cases, your router can automatically determine the connection speed of the Internet (WAN) port. If you cannot establish an Internet connection and the Internet LED blinks continuously, you may need to manually select the port speed.

This could occur on some older broadband modems. If you know that the Ethernet port on your broadband modem supports 100BaseT, select 100BaseT; otherwise, select 10BaseT. Use the half-duplex settings if full-duplex modes do not work.

Figure 2-5

You can also change the standard MTU (Maximum Transmit Unit) value for dialup modems from the Dialup ISP Settings screen. THe standard value is 576 bytes, but some ISPs may require that you reduce the MTU. However, this is rarely required, and should not be done unless specifically required by the ISP,

To Change the MTU Value for Your Dialup Modem:

Step 1.

Select Network Configuration from the main menu, WAN Settings from the submenu and the Dialup ISP Settings tab. Click the Advanced link on the Dialup ISP Settings screen.

Select the Custom radio button and enter the MTU value, in bytes.

Click Apply to save your settings.

Connecting the FVS338 to the Internet v1.0, March 2009

2-7

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 2-6

Manually Configuring Your Internet Connection

If you know your Broadband ISP connection type, you can bypass the Auto Detect feature and connect your router manually. Ensure that you have all of the relevant connection information such as IP Addresses, account information, type of ISP connection, etc., before you begin. Unless your

ISP automatically assigns your configuration automatically via DHCP, you will need the configuration parameters from your ISP

2-8 v1.0, March 2009

Connecting the FVS338 to the Internet

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 2-7

Manually Configure WAN1 ISP Settings:

Step 1.Does your Internet connection require a login ? If you need to enter login information every time you connect to the Internet through your ISP, select Yes. Otherwise, select No.

2. What type of IPS connection do you use? If your connection is PPPoE, PPTP or BigPond

Cable, then you must login. Check the Yes radio box. The text box fields that require data entry will be highlighted, based on the connection that you selected. If your ISP has not assigned any login information, then choose the No radio box and skip this section. For example:

• Austria (PPTP) : If your ISP is Austria Telecom or any other ISP that uses PPTP for login, select this. Then, fill in the following highlighted fields:

– Account Name (also known as Host Name or System Name): Enter the valid account name for the PPTP connection (usually your email “ID” assigned by your ISP). Some

ISPs require entering your full email address here.

– Domain Name : Your domain name or workgroup name assigned by your ISP, or your

ISPs domain name. You may leave this field blank.

– Idle Timeout : Check the Keep Connected radio box to keep the connection always on. To logout after the connection is idle for a period of time, select Idle Time and enter the number of minutes to wait before disconnecting in the timeout field. This is useful if your ISP charges you based on the amount of time you have logged in.

Connecting the FVS338 to the Internet v1.0, March 2009

2-9

FVS338 ProSafe VPN Firewall 50 Reference Manual

– My IP Address: IP address assigned by the ISP to make the connection with the ISP server.

– Server IP Address : IP address of the PPTP server.

• Other (PPPoE) : If you have installed login software such as WinPoET or Enternet, then your connection type is PPPoE. Select this connection and configure the following fields:

– Account Name : Valid account name for the PPPoE connection

– Domain Name: Name of your ISPs domain or your domain name if your ISP has assigned one. You may leave this field blank.

– Idle Timeout: Select Keep Connected, to keep the connection always on. To logout after the connection is idle for a period of time, select Idle Time and enter the number of minutes to wait before disconnecting, in the timeout field.

If your ISP has assigned a fixed (static or permanent) IP address, select the Use Static IP

Address radio box and fill in the following fields: a. IP Address: Static IP address assigned to you. This will identify the router to your ISP. b. Subnet Mask : This is usually provided by the ISP or your network administrator. c.

Gateway IP Address : IP address of the ISP’s gateway. This is usually provided by the ISP or your network administrator.

If your ISP has not assigned a Static IP address, select the Get dynamically from ISP radio box. The ISP will automatically assign an IP address to the router using DHCP network protocol.

If your ISP has not assigned any Domain Name Servers (DNS) addresses, select the Get dynamically from ISP radio box. If your ISP has assigned DNS addresses, select the Use these DNS Servers radio box. Ensure that you fill in valid DNS server IP addresses in the fields. Incorrect DNS entries may cause connectivity issues.

Note: Domain name servers (DNS) convert Internet names such as www.google.com, www.netgear.com, etc. to Internet addresses called IP addresses. Incorrect settings here will result in connectivity problems.

Click Apply to save the settings or click Cancel to revert to the previous settings.

Click Test to try and connect to the NETGEAR Web site. If you connect successfully and your settings work, then you may click Logout or go on and configure additional settings.

You can also click on the Broadband Status link or the Current IP Address link to check on connection status and current IP address.

2-10 Connecting the FVS338 to the Internet v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Programming the Traffic Meter (if Desired)

The traffic meter is useful when an ISP charges by traffic volume over a given period of time or if you want to look at traffic types over a period of time.

To Enable the Traffic Meter

Step 1.

From the primary menu, select Monitoring , and then select Traffic Meter from the secondary menu. The Broadband Traffic Meter screen will display. Fill out the information described in Table 2-2 .

Click Apply to apply the settings or click Cancel to return to the previous settings.

Select the Dialup Traffic Meter tab and repeat steps 1 through 3 to set the Traffic Meter the the Dialup port (if required).

Figure 2-8

Connecting the FVS338 to the Internet v1.0, March 2009

2-11

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table 2-2. Traffic Meter Settings

Parameter Description

Enable Traffic Meter Check this if you wish to record the volume of Internet traffic passing through the

Router's Broadband or Dialup port. Broadband or Dialup can be selected by clicking the appropriate tap; the entire configuration is specific to each interface.

• No Limit - If this is selected specified restriction will not be applied when traffic limit is reached.

• Download only - If this is selected the specified restriction will be applied to the incoming traffic only

• Both Directions - If this is selected the specified restriction will be applied to both incoming and outgoing traffic only

Enable Monthly Limit Use this if your ISP charges for additional traffic. If enabled, enter the monthly volume limit and select the desired behavior when the limit is reached.

Note : Both incoming and outgoing traffic are included in the limit.

Increase this month's limit

Use this to temporarily increase the Traffic Limit if you have reached the monthly limit, but need to continue accessing the Internet. Check the checkbox and enter the desired increase. (The checkbox will automatically be cleared when saved so the increase is only applied once.)

This month's limit

Restart traffic counter

This displays the limit for the current month.

This determines when the traffic counter restarts. Choose the desired time and day of the month.

Restart Counter at a

Specific Time

Check this radio button to restart the Traffic Counter at a specific time and day of the month. Fill in the time fields and select AM or PM and the day of the month from the pull-down menus.

Send E-mail Report before restarting counter

When limit is reached

If checked, an E-mail report will be sent immediately before restarting the counter.

You must configure the E-mail screen in order for this function to work (see “E-Mail

Notifications of Event Logs and Alerts” on page 4-30 ).

Select the desired option:

• Block all traffic – all access to and from the Internet will be blocked.

• Block all traffic except E-mail – Only E-mail traffic will be allowed. All other traffic will be blocked.

• If using this option, you may also select the Send E-mail alert option. You must configure the E-mail screen in order for this function to work.

Internet Traffic

Statistics

This displays statistics on Internet Traffic via the WAN port. If you have not enabled the Traffic Meter, these statistics are not available.

Traffic by Protocol Click this link if you want to know more details of the Internet Traffic. The volume of traffic for each protocol will be displayed in a sub-window.Traffic counters are updated in MBytes scale, counter starts only when traffic passed is at least 1MB.

2-12 v1.0, March 2009

Connecting the FVS338 to the Internet

FVS338 ProSafe VPN Firewall 50 Reference Manual

Configuring the WAN Mode

The WAN Mode screen allows you to configure how your router uses your external Internet connections; for example, your WAN port or dialup modem connections.

• NAT. NAT is the technology which allows all PCs on your LAN to share a single Internet IP address. Viewed from the Internet, the WAN port on the VPN firewall is configured with a single IP address—the “public” address. PCs on your LAN can use any “private” IP address range, and these IP addresses are not visible from the Internet.

– The Router uses NAT to select the correct PC (on your LAN) to receive any incoming data and hides internal IP addresses from computers on the Internet.

– If you only have a single Internet IP address, you MUST use NAT.

NAT is the default setting. Select NAT if your ISP has assigned only one IP address to you.

The computers that connect through the router must then be assigned IP addresses from a private subnet (for example: 192.168.1.0).

• Classical Routing. In this mode, the Router performs Routing, but without NAT. To gain

Internet access, each PC on your LAN must have a valid Internet IP address.

If your ISP has allocated many IP addresses to you, and you have assigned one of these addresses to each PC, you can choose Classical Routing. Or, you can use Classical Routing for routing private IP addresses within a campus environment. Otherwise, selecting this method will not allow Internet access through this Router.

Note: The router will delete all inbound firewall rules when switching between NAT and Classical Routing.

To configure the WAN Mode:

Step 1.

Select Network Configuration from the main menu and WAN Mode from the submenu.

The WAN Mode screen will display.

Check either the NAT or Classical Routing radio box. NAT is the default.

Select the Port Mode. The Port Mode settings allow you to configure your router to use only one WAN port or to select the Dialup port as a backup.

• If you are connected to only one ISP, then check the Use only single WAN port and select the WAN port that is connected to your ISP from the pull down menu.

Connecting the FVS338 to the Internet v1.0, March 2009

2-13

FVS338 ProSafe VPN Firewall 50 Reference Manual

• If you have both ISP links connected for Internet connectivity, check the Primary

Broadband with Dialup as backup for auto-rollover .

The WAN Failure Detection Method must be configured to notify the router of a link failure if you are using Dialup as a backup to engage auto-rollover. The router checks the connection of the primary link at regular intervals to detect its status. Check the radio box of one the following methods to detect link failure:

• Select DNS lookup using configured DNS Servers to detect failure of the Broadband link, using the DNS servers configured in the Broadband ISP Settings screen.

• Select DNS lookup using this DNS Server and enter the IP address of the DNS server to specify a DNS server for detecting WAN failure

• Select Ping to this IP address and enter an IP address to detect WAN failure by pinging to an IP address. Ensure that this destination host is reliable.

If a failure is detected on the primary broadband connection, the secondary dialup connection connects to the Internet. When the primary connection is detected as back online, the secondary dialup connection disconnects.

Enter a Test Period, in seconds, to tell the router how often it should run the configured detection method. The default is 30 seconds.

Enter the number of router failures that should occur before the router rolls-over to the Dialup port. The default is 4.

Enter Apply to save your settings or Cancel to revert to the previous settings.

Configuring Dynamic DNS (If Needed)

Note: If your ISP assigns a private WAN IP address such as 192.168.x.x or 10.x.x.x, the dynamic DNS service will not be available since private addresses cannot be routed on the Internet.

Dynamic DNS (DDNS) is an Internet service that allows routers with varying public IP addresses to be located using Internet domain names. To use DDNS, you must setup an account with a

DDNS provider such as DynDNS.org, TZO.com, or Oray.net.

Once you have registered your domain name to their IP address, all FQDN traffic will be directed to your frequently-changing IP address. (For rollover mode, you will need a fully qualified domain name to implement features such as exposed hosts and virtual private networks regardless of whether you have a fixed or dynamic IP address.)

2-14 v1.0, March 2009

Connecting the FVS338 to the Internet

FVS338 ProSafe VPN Firewall 50 Reference Manual

This router firmware includes software that notifies dynamic DNS servers of changes in the WAN

IP address, so that the services running on this network can be accessed by others on the Internet.

After you have configured your account information in the firewall, whenever your ISP-assigned

IP address changes, your firewall will automatically contact your dynamic DNS service provider, log in to your account, and register your new IP address.

To configure a Dynamic DNS address:

Step 1.

Select Network Configuration from the main menu and Dynamic DNS from the submenu. The Dynamic DNS Configuration screen displays. The WAN Mode section displays the currently configured WAN Mode: Single Port or Auto-Rollover. A tab is provided for each supported DNS service provider. In the example shown, supported DNS providers are

DynDNS.org (Dynamic DNS tab), TZO.com (tab DNS TZO), and Oray.net (tab DNS Oray).

Figure 2-9

If you have configured Single Port, select the tab for a DNS service provider, then fill out the

DDNS section for that port. If you have enabled Auto-Rollover, choose a service provider and complete both sections. (Only those options that match the configured WAN Mode will be accessible.)

Check the Dynamic DNS Service radio box you want to enable. The fields corresponding to the selection you have selected will be highlighted. Each DNS service provider requires its own parameters.

Connecting the FVS338 to the Internet v1.0, March 2009

2-15

FVS338 ProSafe VPN Firewall 50 Reference Manual

Access the Web site of one of the DDNS service providers and set up an account. A link to each DDNS provider is near the top right of the window opposite to the DDNS service provider tabs. The link is encircled with a dashed line in Figure 2-9 .

After setting up your account, return to the Dynamic DNS Configuration screen and fill in the required fields for the DDNS service you selected: a.

In the Host and Domain Name field, enter the entire FQDN name that your dynamic DNS service provider gave you (for example: < yourname> .dyndns.org).

Enter the User Name, User email Address, or Account Name requested by the DDNS

Service to identify you when logging into your DDNS account.

Enter the Password, or User Key, for your DDNS account.

If your dynamic DNS provider allows the use of wild cards in resolving your URL, you may check the Use wildcards radio box to activate this feature.

For example, the wildcard feature will cause *.yourhost.dyndns.org

to be aliased to the same IP address as yourhost.dyndns.org

Click Apply to save your configuration or click Cancel to revert to the previous settings.

2-16 v1.0, March 2009

Connecting the FVS338 to the Internet

Chapter 3 LAN Configuration

This chapter describes how to configure LAN Setup, LAN Groups and Routing (Static IP) features of your ProSafe VPN Firewall 50, including the following sections:

• “Choosing the Firewall DHCP Options” on page 3-1

• “Managing Groups and Hosts” on page 3-6

• “Configuring Static Routes” on page 3-10

Choosing the Firewall DHCP Options

By default, the firewall will function as a DHCP (Dynamic Host Configuration Protocol) server, allowing it to assign IP, DNS server, WINS Server, and default gateway addresses to all computers connected to the firewall LAN. The assigned default gateway address is the LAN address of the firewall. IP addresses will be assigned to the attached PCs from a pool of addresses specified in this menu. Each pool address is tested before it is assigned to avoid duplicate addresses on the

LAN. The DHCP options are available for both the LAN and DMZ settings.

For most applications, the default DHCP and TCP/IP settings of the firewall are satisfactory. See the link to “Preparing a Computer for Network Access” in Appendix C, “Related Documents” for an explanation of DHCP and information about how to assign IP addresses for your network.

If another device on your network will be the DHCP server, or if you will manually configure the network settings of all of your computers, clear the Enable DHCP server radio box by selecting the Disable DHCP Server radio box. Otherwise, leave it checked.

Specify the pool of IP addresses to be assigned by setting the Starting IP Address and Ending IP

Address. These addresses should be part of the same IP address subnet as the firewall’s LAN IP address. Using the default addressing scheme, you should define a range between 192.168.1.2 and

192.168.1.100, although you may wish to save part of the range for devices with fixed addresses.

The firewall will deliver the following parameters to any LAN device that requests DHCP:

• An IP Address from the range you have defined.

• Subnet Mask.

• Gateway IP Address (the firewall’s LAN IP address).

• Primary DNS Server (the firewall’s LAN IP address).

LAN Configuration 3-1 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

• WINS Server (if you entered a WINS server address in the DHCP Setup menu).

• Lease Time (date obtained and duration of lease).

DHCP Relay options allow you to make the firewall a dhcp relay agent. The DHCP Relay Agent makes it possible for DHCP broadcast messages to be sent over routers that do not support forwarding of these types of messages. The DHCP Relay Agent is therefore the routing protocol that enables DHCP clients to obtain IP addresses from a DHCP server on a remote subnet, or which is not located on the local subnet. If you have no configured DHCP Relay Agent, your clients would only be able to obtain IP addresses from the DHCP server which is on the same subnet. To enable clients to obtain IP addresses from a DHCP server on a remote subnet, you have to configure the DHCP Relay Agent on the subnet that contains the remote clients, so that it can relay DHCP broadcast messages to your DHCP server.

When the DNS Proxy option is enabled, the router will act as a proxy for all DNS requests and communicate with the ISP’s DNS servers (as configured in the WAN settings page). All DHCP clients will receive the Primary/Secondary DNS IP along with the IP where the DNS Proxy is running, i.e. the box's LAN IP. When disabled, all DHCP clients will receive the DNS IP addresses of the ISP excluding the DNS Proxy IP address. The feature is particularly useful in Auto Rollover mode. For example, if the DNS servers for each connection are different, then a link failure may render the DNS servers inaccessible. However, when the DNS proxy is enabled, then clients can make requests to the router and the router, in turn, sends those requests to the DNS servers of the active connection.

Configuring the LAN Setup Options

The LAN IP Setup menu allows configuration of LAN IP services such as DHCP and allows you to configure a secondary or “multi-home” LAN IP setup in the LAN. The default values are suitable for most users and situations. Disable the DNS Proxy if you are using a dual WAN configuration with route diversity and failover. These are advanced settings most usually configured by a network administrator.

Note: If you enable the DNS Relay feature, you will not use the FVS338 as a DHCP server but rather as a DHCP relay agent for a DHCP server somewhere else on your network.

3-2 v1.0, March 2009

LAN Configuration

FVS338 ProSafe VPN Firewall 50 Reference Manual

Select Network Configuration from the primary menu and LAN Setup from the submenu.

The LAN Setup screen will display.

Figure 3-1

Enter the IP Address of your router (factory default: 192.168.1.1

). (Always make sure that the

LAN Port IP address and DMZ port IP address are in different subnets.)

Enter the IP Subnet Mask . The subnet mask specifies the network number portion of an IP address. Your router will automatically calculate the subnet mask based on the IP address that you assign. Unless you are implementing subnetting, use 255.255.255.0 as the subnet mask

(computed by the router).

Check the Enable DHCP Server radio button. By default, the router will function as a DHCP

(Dynamic Host Configuration Protocol) server, providing TCP/IP configuration for all computers connected to the router's LAN. If another device on your network will be the DHCP server, or if you will manually configure all devices, check the Disable DHCP Server radio button. Enable DHCP Server is the default. If Enabled is selected, enter the following parameters: a.

Enter the Domain Name of the router (this is optional).

LAN Configuration 3-3 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual b.

Enter the Starting IP Address . This address specifies the first of the contiguous addresses in the IP address pool. Any new DHCP client joining the LAN will be assigned an IP address between this address and the Ending IP Address. The IP address 192.168.1.2 is the default start address. c.

Enter the Ending IP Address . This address specifies the last of the contiguous addresses in the IP address pool. Any new DHCP client joining the LAN will be assigned an IP address between the Starting IP address and this IP address. The IP address 192.168.1.100 is the default ending address.

Note: The Starting and Ending DHCP addresses should be in the same “network” as the LAN TCP/IP address of the router (the IP Address in LAN TCP/IP

Setup section).

• Primary DNS Server . (Optional) If an IP address is specified, the VPN firewall will provide this address as the primary DNS server IP address. If no address is specified, the

VPN firewall will provide its own LAN IP address as the primary DNS server IP address.

• Secondary DNS Server . (Optional) If an IP address is specified, the VPN firewall will provide this address as the secondary DNS server IP address.

Enter a WINS Server IP address. This box can specify the Windows NetBios Server IP if one is present in your network. This field is optional.

Enter a Lease Time. This specifies the duration for which IP addresses will be leased to clients.

To enable the DHCP server to provide LDAP server information, check the Enable LDAP

Information checkbox and fill in the fields accordingly.

Check the Enable DNS Proxy radio box. This is optional—the default is enabled. If enabled, the VPN firewall will provide a LAN IP Address for DNS address name resolution.

Note: If you change the LAN IP address of the firewall while connected through the browser, you will be disconnected. You must then open a new connection to the new IP address and log in again. For example, if you change the default IP address 192.168.1.1 to 10.0.0.1, you must enter http://10.0.0.1

in your browser to reconnect to the web management interface.

3-4 LAN Configuration v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

The feature is particularly useful in Auto Rollover mode. For example, if the DNS servers for each connection are different, then a link failure may render the DNS servers inaccessible. However, when the DNS proxy is enabled, then clients can make requests to the router and the router, in turn, sends those requests to the DNS servers of the active connection.

– When enabled, the router will act as a proxy for all DNS requests and communicate with the ISP’s DNS servers (as configured in the WAN settings page).

– When disabled, all DHCP clients will receive the DNS IP addresses of the ISP.

Click Apply to save your settings.

Click Reset to discard any changes and revert to the previous configuration.

Note: Once you have completed the LAN IP setup, all outbound traffic is allowed and all inbound traffic is discarded. To change these traffic rules, refer to

Chapter 4, “Firewall Protection and Content Filtering .

Configuring Multi-Home LAN IPs

If you have computers using different IP networks in the LAN, (for example., 172.16.2.0,

10.0.0.0), then you can add aliases to the LAN port and give computers on those networks access to the Internet.

Figure 3-2

The Available Secondary LAN IPs table lists the secondary LAN IP addresses added to the router.

• IP Address : The IP address alias added to the LAN port of the router. This is the gateway for computers that need to access the Internet.

LAN Configuration 3-5 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

• Subnet Mask : IPv4 Subnet Mask.

• Action/Edit : Click to make changes to the selected entry.

• Select All : Selects all the entries in the Available Secondary LAN IPs table.

• Delete : Deletes selected entries from the Available Secondary LAN IPs table.

To add a secondary LAN IP address:

Type in the IP Address and the Subnet Mask in the respective text fields.

Click Add .

Note: Additional IP addresses cannot be configured in the DHCP server. The hosts on the secondary subnets must be manually configured with the IP addresses, gateway IP and DNS server IPs.

Warning: Make sure the secondary IP addresses are different from the LAN, WAN,

DMZ, and any other subnet attached to this router.

Example:

WAN1 IP address: 10.0.0.1 with subnet 255.0.0.0

WAN2 IP address: 20.0.0.1 with subnet 255.0.0.0

DMZ IP address: 192.168.10.1 with subnet 255.255.255.0

LAN IP address: 192.168.1.1 with subnet 255.255.255.0

Secondary LAN IP: 192.168.20.1 with subnet 255.255.255.0

Managing Groups and Hosts

The Known PCs and Devices table on the Groups and Hosts screen contains a list of all known

PCs and network devices, as well as hosts, that are assigned dynamic IP addresses by this router.

Collectively, these entries make up the Network Database. The Network Database is created in two ways:

• Using the DHCP Server.

The router’s DHCP server will accept and respond to DHCP client requests from PCs and other network devices. Every computer that is responded to will be added to the Network Database in the Known PCs and Devices table.

3-6 LAN Configuration v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

• Scanning the Network . The router will scan the local network periodically, using standard methods such as ARP and NetBIOS, to detect active computers or devices which are not

DHCP clients. For computers that do not support the NetBIOS protocol, the name will be displayed in the known PCs and Devices table as “Unknown”.

Creating the Network Database

The Network Database offers a number of advantages:

• Generally, you do not need to enter either IP address or MAC addresses. Instead, you can just select the desired PC or device.

• No need to reserve an IP address for a PC in the DHCP Server. All IP address assignments made by the DHCP Server will be maintained until the PC or device is removed from the database, either by expiry (inactive for a long time) or by you.

• No need to use a Fixed IP on PCs. Because the address allocated by the DHCP Server will never change, you don't need to assign a fixed IP to a PC to ensure it always has the same IP address.

• MAC-level Control over PCs. The Network Database uses the MAC address to identify each

PC or device. So changing a PC's IP address does not affect any restrictions on that PC.

• Group and Individual Control over PCs

– You can assign PCs to Groups and apply restrictions to each Group using the Firewall

Rules screen (see “Services-Based Rules” on page 4-2 ).

– You can also select the Groups to be covered by the Block Sites feature (see “Setting

Block Sites (Content Filtering)” on page 4-20 ).

– If necessary, you can also create Firewall Rules to apply to a single PC (see “Enabling

Source MAC Filtering” on page 4-23 ). Because the MAC address is used to identify each

PC, users cannot avoid these restrictions by changing their IP address.

• A computer is identified by its MAC address—not its IP address. Hence, changing a computer’s IP address does not affect any restrictions applied to that PC.

The LAN Groups screen contains a list of all known PCs and network devices, as well as hosts that are assigned dynamic IP addresses by this router.

LAN Configuration 3-7 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 3-3

The Network Database is created by:

• Using the DHCP Server : The router’s DHCP server is configured, by default, to respond to

DHCP requests from clients on the LAN. Every computer that receives a response from the router will be added to the Network Database. Because of this, leaving the DHCP Server feature enabled (on the LAN Setup screen) is strongly recommended.

• Scanning the Network : The router also scans the local network periodically using protocols such as ARP and NetBIOS to detect active computers or devices that are not DHCP clients.

For computers that do not support the NetBIOS protocol, the name will be displayed as

Unknown.

The Known PCs and Devices table lists the entries in the Network Database. For each computer or device, the following fields are displayed:

3-8 LAN Configuration v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

• Name : The name of the computer or device. Computers that do not support the NetBIOS protocol will be listed as Unknown. In this case, the name can be edited manually for easier management. If the computer was assigned an IP address by the DHCP server, then an asterisk is be appended to the name.

• IP Address : The current IP address of the computer. For DHCP clients of the router, this IP address will not change. If a computer is assigned a static IP address, you must to update this entry manually when the IP address of the computer changes.

• MAC Address : The MAC address of the computer’s network interface.

• Group : Each PC or device can be assigned to a single group. By default, a computer is assigned to the first group (Group 1). To change the group assignment, click Edit .

• Action/Edit : Allows modification of the selected entry.

To add known PCs and devices:

To add computers to the network database manually, fill in the following fields:

• Name : The name of the PC or device.

• IP Address Type :

– Select Reserved (DHCP Client) to direct the router to reserve the IP address for allocation by the DHCP server.

– Select Fixed (Set on PC) if the IP address is statically assigned on the computer itself.

• IP Address : The IP address that this computer or device is assigned. If the IP Address

Type is Reserved (DHCP Client) , the router will reserve the IP address for the associated

MAC address.

• MAC Address : The MAC address of the computer’s network interface. The MAC address should be in the form: xx:xx:xx:xx:xx:xx (for example., 00:80:48:2a:8b:c0)

• Group : The group to which the computer has to be assigned.

Click Add to add the new entry to the network database.

To edit the names of any of the eight available groups:

Select the group by checking the adjacent radio button and typing in a suitable name in the associated field.

Click Apply to save the settings or click Reset to revert to the previous settings.

LAN Configuration 3-9 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Setting Up Address Reservation

When you specify a reserved IP address for a device on the LAN (based on the MAC address of the device), that computer or device will always receive the same IP address each time it accesses the firewall’s DHCP server. Reserved IP addresses should be assigned to servers or access points that require permanent IP settings. The Reserved IP address that you select must be outside of the

DHCP Server pool.

To reserve an IP address, use the Groups and Hosts screen under the Network Configuration menu , LAN Groups submenu (see “Creating the Network Database” on page 3-7 ).

Note: The reserved address will not be assigned until the next time the PC contacts the firewall's DHCP server. Reboot the PC or access its IP configuration and force a

DHCP release and renew.

Configuring Static Routes

Static Routes provide additional routing information to your firewall. Under normal circumstances, the firewall has adequate routing information after it has been configured for

Internet access, and you do not need to configure additional static routes. You must configure static routes only for unusual cases such as multiple firewalls or multiple IP subnets located on your network.

To add or edit a Static Route:

Select Network Configuration from the main menu and Routing from the submenu. The

Routing screen will display.

Click Add. The Add Static Route screen will display.

Enter a name for the static route in the Route Name field (for identification purpose only).

Determine whether the route is

• Active or Inactive . A route can be added to the table and made inactive, if not needed.

This allows routes to be used as needed without deleting the entry and re-adding it. An inactive route is not broadcast if RIP is enabled. Select the Active radio box to make this route effective.

• Private : Determine whether the route can be shared with other routers when RIP is enabled. If Yes, then the route will not be shared in a RIP broadcast or multicast. Check the Private radio box if you want to limit access to the LAN only. The static route will not be advertised in RIP.

3-10 LAN Configuration v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Type the Destination IP Address or network of the route’s final destination.

Enter the IP Subnet Mask for this destination. If the destination is a single host, enter

255.255.255.255.

Figure 3-4

From the Interface pull-down menu, selection the physical network interface (Broadband,

Dialup, or LAN) through which this route is accessible.

Enter the Gateway IP Address (which must be a firewall on the same LAN segment as the firewall) of the gateway through which the destination host or network can be reached.

Enter the Metric value that determines the priority of the route. If multiple routes to the same destination exist, the route with the lowest metric is chosen. Usually, a setting of 2 or 3 works, but if this is a direct connection, set it to 1.

10.

Click Apply to save the static route to the Static Routes table.

Static Route Example

For example, a static route is needed if:

• Your primary Internet access is through a cable modem to an ISP.

LAN Configuration 3-11 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

• You have an ISDN firewall on your home network for connecting to the company where you are employed. This firewall’s address on your LAN is 192.168.1.100.

• Your company’s network is 134.177.0.0.

When you first configured your firewall, two implicit static routes were created. A default route was created with your ISP as the gateway, and a second static route was created to your local network for all 192.168.1.x addresses. With this configuration, if you attempt to access a device on the 134.177.0.0 network, your firewall will forward your request to the ISP. The ISP forwards your request to the company where you are employed, and the request will likely be denied by the company’s firewall.

In this case you must define a static route, telling your firewall that 134.177.0.0 should be accessed through the ISDN firewall at 192.168.1.100.

In this example:

• The Destination IP Address and IP Subnet Mask fields specify that this static route applies to all 134.177.x.x addresses.

• The Gateway IP Address fields specifies that all traffic for these addresses should be forwarded to the ISDN firewall at 192.168.1.100.

• A Metric value of 1 will work since the ISDN firewall is on the LAN.

• Private is selected only as a precautionary security measure in case RIP is activated.

RIP Configuration

RIP (Routing Information Protocol, RFC 2453) is an Interior Gateway Protocol (IGP) and is commonly used in internal networks. It allows a router to exchange its routing information automatically with other routers, and allows it to dynamically adjust its routing tables and adapt to changes in the network. RIP is disabled by default.

3-12 v1.0, March 2009

LAN Configuration

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 3-5

To enable RIP:

Select Network Configuration from the main menu and Routing from the submenu. The

Routing screen will display.

Click the RIP Configuration link. The RIP Configuration screen will display.

From the RIP Direction pull-down menu, select the direction for the router to send and receive RIP packets:

• Both – the router broadcasts its routing table and also processes RIP information received from other routers.

• Out Only – the router broadcasts its routing table periodically but does not accept RIP information from other routers.

• In Only – the router accepts RIP information from other routers, but does not broadcast its routing table.

LAN Configuration 3-13 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

• None – the router neither broadcasts its route table nor does it accept any RIP packets from other routers. This effectively disables RIP.

Select the RIP Version from the pull-down menu:

• RIP-1 – classful routing and does not include subnet information. This is the most commonly supported version.

• RIP-2 – supports subnet information. Both RIP-2B and RIP-2M send the routing data in

RIP-2 format:

• RIP-2B – uses subnet broadcasting.

• RIP-2M – uses multicasting (see Note below).

RIP authentication is disabled by default. To enable authentication for RIP-2B or RIP-2M, a.

Check the Yes radio button.

Input MD5 keys and effective and end dates for the First Key Parameters and Second

Key Parameters for MD5 based authentication between routers.

Click Apply to save your settings.

Note: Multicasting can reduce the load on non-router machines because they do not listen to the RIP multicast address and will not receive the RIP packets.

However, if one router uses multicasting, then all routers on your network must use multicasting. For RIP-2B and RIP-2M you can select the type of authentication as NONE or MD5. If you select MD5 then you need to enter additional parameters.

3-14 v1.0, March 2009

LAN Configuration

Chapter 4 Firewall Protection and Content Filtering

The ProSafe VPN Firewall 50 provides you with Web content filtering options such as Block Sites and Keyword Blocking. This chapter includes the following sections:

• “About Firewall Security” on page 4-1

• “Adding Customized Services” on page 4-17

• “Specifying Quality of Service (QoS) Priorities” on page 4-19

• “Setting a Schedule to Block or Allow Specific Traffic” on page 4-20

• “Setting Block Sites (Content Filtering)” on page 4-20

• “Enabling Source MAC Filtering” on page 4-23

• “Setting Up Port Triggering” on page 4-26

• “Bandwidth Limiting” on page 4-28

• “E-Mail Notifications of Event Logs and Alerts” on page 4-30

• “Administrator Information” on page 4-34

About Firewall Security

A firewall is a special category of router that protects one network (the “trusted” network, such as your LAN) from another (the untrusted network, such as the Internet), while allowing communication between the two.

A firewall incorporates the functions of a NAT (Network Address Translation) router, while adding features for dealing with a hacker intrusion or attack, and for controlling the types of traffic that can flow between the two networks. Unlike simple Internet sharing NAT routers, a firewall uses a process called stateful packet inspection to protect your network from attacks and intrusions. NAT performs a very limited stateful inspection in that it considers whether the incoming packet is in response to an outgoing request, but true Stateful Packet Inspection goes far beyond NAT.

Firewall Protection and Content Filtering v1.0, March 2009

4-1

FVS338 ProSafe VPN Firewall 50 Reference Manual

Using Rules to Block or Allow Specific Kinds of Traffic

Firewall rules are used to block or allow specific traffic passing through from one side to the other.

You can configure up to 600 rules on the FVS338. Inbound rules (WAN to LAN) restrict access by outsiders to private resources, selectively allowing only specific outside users to access specific resources. Outbound rules (LAN to WAN) determine what outside resources local users can have access to.

A firewall has two default rules, one for inbound traffic and one for outbound. The default rules of the FVS338 are:

• Inbound : Block all access from outside except responses to requests from the LAN side.

• Outbound : Allow all access from the LAN side to the outside.

Services-Based Rules

The rules to block traffic are based on the traffic’s category of service.

• Inbound Rules (port forwarding ). Inbound traffic is normally blocked by the firewall unless the traffic is in response to a request from the LAN side. The firewall can be configured to allow this otherwise blocked traffic.

• Outbound Rules (service blocking).

Outbound traffic is normally allowed unless the firewall is configured to disallow it.

• Customized Services . Additional services can be added to the list of services in the factory default list. These added services can then have rules defined for them to either allow or block that traffic.

• Quality of Service (QoS) . Each service at its own native priority that impacts its quality of performance and tolerance for jitter or delays. You can change this QoS priority if desired to change the traffic mix through the system.

Outbound Rules (Service Blocking). The FVS338 allows you to block the use of certain

Internet services by PCs on your network. This is called service blocking or port filtering.

Note: See “Enabling Source MAC Filtering” on page 4-23 for yet another way to block outbound traffic from selected PCs that would otherwise be allowed by the firewall.

4-2 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table 4-1.

Outbound Rules Fields

Item

Services

Action

Select Schedule

LAN users

WAN Users

Description

Select the desired Service or application to be covered by this rule. If the desired service or application does not appear in the list, you must define it using the

Services menu (see “Adding Customized Services” on page 4-17 ).

Select the desired action for outgoing connections covered by this rule:

• BLOCK always

• BLOCK by schedule, otherwise Allow

• ALLOW always

• ALLOW by schedule, otherwise Block

Note : Any outbound traffic which is not blocked by rules you create will be allowed by the Default rule.

ALLOW rules are only useful if the traffic is already covered by a BLOCK rule. That is, you wish to allow a subset of traffic that is currently blocked by another rule.

Select the desired time schedule (i.e., Schedule1, Schedule2, or Schedule3) that will be used by this rule.

• This drop down menu gets activated only when “BLOCK by schedule, otherwise

Allow” or “ALLOW by schedule, otherwise Block” is selected as Action.

• Use schedule page to configure the time schedules (see “Setting a Schedule to

Block or Allow Specific Traffic” on page 4-20 ).

These settings determine which computers on your network are affected by this rule.

Select the desired options:

• Any – All PCs and devices on your LAN.

• Single address - Enter the required address and the rule will be applied to that particular PC.

• Address range – If this option is selected, you must enter the start and finish fields.

• Groups – Select the Group you wish this rule to apply to. You can use the Network

Database screen to assign PCs to Groups. See “Managing Groups and Hosts” on page 3-6 .

These settings determine which Internet locations are covered by the rule, based on their IP address. Select the desired option:

• Any – All Internet IP address are covered by this rule.

• Single address – Enter the required address in the start fields.

• Address range – If this option is selected, you must enter the start and finish fields.

Firewall Protection and Content Filtering v1.0, March 2009

4-3

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table 4-1.

Outbound Rules Fields (continued)

Item

QoS Priority

Log

Description

This setting determines the priority of a service, which in turn, determines the quality of that service for the traffic passing through the firewall. By default, the priority shown is that of the selected service. The user can change it accordingly. If the user does not make a selection (i.e, leaves it as None), then the native priority of the service will be applied to the policy. 6 is the highest priority. See “Specifying Quality of

Service (QoS) Priorities” on page 4-19 .

This determines whether packets covered by this rule are logged. Select the desired action:

• Always – always log traffic considered by this rule, whether it matches or not. This is useful when debugging your rules.

• Never – never log traffic considered by this rule, whether it matches or not.

Inbound Rules (Port Forwarding). Because the FVS338 uses Network Address Translation

(NAT), your network presents only one IP address to the Internet and outside users cannot directly address any of your local computers. However, by defining an inbound rule you can make a local server (for example, a Web server or game server) visible and available to the Internet. The rule tells the firewall to direct inbound traffic for a particular service to one local server based on the destination port number. This is also known as port forwarding.

Whether or not DHCP is enabled and how the PCs will access the server’s LAN address impact the

Inbound Rules. For example:

• If your external IP address is assigned dynamically by your ISP (DHCP enabled), the IP address may change periodically as the DHCP lease expires. Consider using Dyamic DNS

(under Network Configuration) so that external users can always find your network (see

“Configuring Dynamic DNS (If Needed)” on page 2-14 .

• If the IP address of the local server PC is assigned by DHCP, it may change when the PC is rebooted. To avoid this, use the Reserved IP address feature in the LAN Groups menu (under

Network Configuration) to keep the PC’s IP address constant (see “Setting Up Address

Reservation” on page 3-10 ).

• Local PCs must access the local server using the local LAN address of the PC. Attempts by local PCs to access the server using the external WAN IP address will fail

Note: See “Setting Up Port Triggering” on page 4-26 for yet another way to allow certain types of inbound traffic that would otherwise be blocked by the firewall.

4-4 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table 4-2.

Inbound Rules Fields

Item Description

Services

Action

Select Schedule

LAN Server

Translate to Port

Number

WAN Users

Select the desired Service or application to be covered by this rule. If the desired service or application does not appear in the list, you must define it using the

Services menu (see “Adding Customized Services” on page 4-17 ).

Select the desired action for packets covered by this rule:

• BLOCK always

• BLOCK by schedule, otherwise Allow

• ALLOW always

• ALLOW by schedule, otherwise Block

Note : Any inbound traffic which is not allowed by rules you create will be blocked by the Default rule.

Select the desired time schedule (i.e., Schedule1, Schedule2, or Schedule3) that will be used by this rule.

• This drop down menu gets activated only when “BLOCK by schedule, otherwise

Allow” or “ALLOW by schedule, otherwise Block” is selected as Action.

• Use schedule page to configure the time schedules.

This LAN address determines which computer on your network is hosting this service rule. (You can also translate this address to a port number.).

Check the “Translate to Port Number” and enter a port number if you want to assign the LAN Server to a specific port.

These settings determine which Internet locations are covered by the rule, based on their IP address. Select the desired option:

• Any – All Internet IP address are covered by this rule.

• Single address – Enter the required address in the start fields.

• Address range – If this option is selected, you must enter the start and finish fields.

WAN Destination IP

Address

QoS Priority

Log

These settings determine the destination IP address applicable to incoming traffic.

This is the public IP address that will map to the internal server; it can either be the address of the WAN1 or WAN2 ports or another public IP address .

Priorities” on page 4-19 .

This determines whether packets covered by this rule are logged. Select the desired action:

• Always – always log traffic considered by this rule, whether it matches or not. This is useful when debugging your rules.

• Never – never log traffic considered by this rule, whether it matches or not.

Firewall Protection and Content Filtering v1.0, March 2009

4-5

FVS338 ProSafe VPN Firewall 50 Reference Manual

Note: Some residential broadband ISP accounts do not allow you to run any server processes (such as a Web or FTP server) from your location. Your ISP may periodically check for servers and may suspend your account if it discovers any active services at your location. If you are unsure, refer to the Acceptable Use

Policy of your ISP.

Remember that allowing inbound services opens holes in your VPN firewall. Only enable those ports that are necessary for your network. It is also advisable to turn on the server application security and invoke the user password or privilege levels, if provided.

Order of Precedence for Firewall Rules

As you define new rules, they are added to the tables in the Rules menu, as shown in Figure 4-1

Figure 4-1

For any traffic attempting to pass through the firewall, the packet information is subjected to the rules in the order shown in the Rules Table, beginning at the top and proceeding to the default rules at the bottom. In some cases, the order of precedence of two or more rules may be important in determining the disposition of a packet. For example, you should place the most strict rules at the top (those with the most specific services or addresses). The Up and Down buttons allow you to relocate a defined rule to a new position in the table.

4-6 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

Setting LAN WAN Rules

The Default Outbound Policy is to allow all traffic from and to the Internet to pass through.

Firewall rules can then be applied to block specific types of traffic from either going out from the

LAN to the Internet (Outbound) or coming in from the Internet to the LAN (Inbound). The default policy can be changed to block all outbound traffic and enable only specific services to pass through the router.

To change the Default Outbound Policy:

Select Security from the main menu and Firewall Rules from the submenu. The LAN WAN

Rules screen will display.

Change the Default Outbound Policy by selecting Block Always from the drop-down menu and click Apply .

Figure 4-2

To make changes to an existing outbound or inbound service rule:

In the Action column adjacent to the rule click:

• Edit – to make any changes to the rule definition of an existing rule. The Outbound

Service screen will display containing the data for the selected rule (see Figure 4-3 on page 4-9 ).

Firewall Protection and Content Filtering v1.0, March 2009

4-7

FVS338 ProSafe VPN Firewall 50 Reference Manual

• Up – to move the rule up one position in the table rank.

• Down – to move the rule down one position in the table rank.

Check the radio box adjacent to the rule and click:

• Click Disable to disable the rule. The “!” Status icon will change from green to grey, indicating that the rule is disabled. (By default, when a rule is added to the table it is automatically enabled.)

• Click Delete to delete the rule.

Click Select All to select all rules. A check will appear in the radio box for each rule.

LAN WAN Outbound Services Rules

You may define additional rules that will specify exceptions to the default rules. By adding custom rules, you can block or allow access based on the service or application, source or destination IP addresses, and time of day.

You can also tailor these rules to your specific needs (see “Administrator Information” on page 4-

34 ).

Note: This feature is for Advanced Administrators only! Incorrect configuration will cause serious problems.

To create a new outbound service rule:

Click Add under the Outbound Services Table. The Add LAN WAN Outbound Service screen will display.

Complete the Outbound Service screen, and save the data (see Table 4-1 on page 4-3 ).

Click Reset to cancel your settings and return to the previous settings.

Click Apply to save your changes and reset the fields on this screen. The new rule will be listed on the Outbound Services table.

4-8 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 4-3

LAN WAN Inbound Services Rules

This Inbound Services Rules table lists all existing rules for inbound traffic. If you have not defined any rules, no rules will be listed. By default, all inbound traffic is blocked. WAN Users :

Whether all WAN addresses or specific IP addresses are included in the rule.

To create a new inbound service rule:

Click Add under the Inbound Services Table. The Add LAN WAN Inbound Service screen will display.

Complete the Add WAN LAN Inbound Services screen (see Table 4-2 on page 4-5 ).

Click Reset to cancel your settings and return to the previous settings.

Click Apply to save your changes and reset the fields on this screen. The new rule will be listed on the Inbound Services table.

Click Apply to save your settings. The new rule will be added to the Inbound Services table.

Firewall Protection and Content Filtering v1.0, March 2009

4-9

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 4-4

Attack Checks

This screen allows you to specify whether or not the router should be protected against common attacks in the LAN and WAN networks. The various types of attack checks are listed on the

Attack Checks screen and defined below:

• WAN Security Checks

– Respond To Ping On Internet Ports . When enabled, the router will respond to a “Ping” from the Internet. This can be used as a diagnostic tool and shouldn’t be used unless you have a specific diagnostic reason to do so.

– Enable Stealth Mode . If enabled, the router will not respond to port scans from the WAN, thus making it less susceptible to discovery and attacks.

– Block TCP Flood. A SYN flood is a form of denial of service attack in which an attacker sends a succession of SYN requests to a target system. When the system responds, the attacker doesn’t complete the connections, thus leaving the connection half-open and flooding the server with SYN messages. No legitimate connections can then be made.

When enabled, the router will drop all invalid TCP packets and will be protected from a

SYN flood attack.

• LAN Security Checks. A UDP flood is a form of denial of service attack that can be initiated when one machine sends a large number of UDP packets to random ports on a remote host. As a result, the distant host will (1) check for the application listening at that port, (2) verify that no application is listening at that port, and then (3) reply with an ICMP Destination

Unreachable packet.

4-10 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

When the victimized system is flooded, it is forced to send many ICMP packets, eventually making it unreachable by other clients. The attacker may also spoof the IP address of the UDP packets, ensuring that the excessive ICMP return packets do not reach him, thus making the attacker’s network location anonymous.

If enabled, the router will not accept more than 20 simultaneous, active UDP connections from a single computer on the LAN.

• VPN Pass through . When the router is in NAT mode, all packets going to the Remote VPN

Gateway are first filtered through NAT and then encrypted per the VPN policy.

For example, if a VPN Client or Gateway on the LAN side of this router wants to connect to another VPN endpoint on the WAN (placing this router between two VPN end points), encrypted packets will be sent to this router. Since this router filters the encrypted packets through NAT, the packets will become invalid unless VPN Pass through is enabled.

When enabled, the VPN tunnel will pass the VPN traffic without any filtering. Tunnels can be

– IPSec

– PPTP

– L2TP

To select the appropriate checkbox for your requirement:

Select Security from the main menu, Firewall Rules from the submenu and then the Attack

Checks tab. The Attack Checks screen will display.

Check the radio boxes of the Attack Checks you wish to initiate.

Click Apply to save your settings.

Figure 4-5

Firewall Protection and Content Filtering v1.0, March 2009

4-11

FVS338 ProSafe VPN Firewall 50 Reference Manual

Session Limit

Session Limit allows you to specify the total number of sessions per user over an IP (Internet

Protocol) connection allowed across the router. This feature can be enabled on the Session Limit screen and is shown below (Session Limit is disabled by default):

Figure 4-6

To enable Session Limit :

Click the Yes radio button under Do you want to enable Session Limit ?

From the User Limit Parameter drop-down list, define the maximum number of sessions per

IP either as a percentage of maximum sessions or as an absolute value.

The percentage is computed on the total connection capacity of the device.

Enter the User Limit . If the User Limit Parameter is set to Percentage of Max Sessions , the limit is the maximum number of sessions allowed from a single source machine as a percentage of the total connection capacity. (Session Limit is a machine-based value.)

Otherwise, when the User Limit Parameter is set to Number of Sessions , the limit is an absolute value.

Note: Some protocols (such as FTP or RSTP) create two sessions per connection which should be considered when configuring Session Limiting.

Total Number of Packets Dropped due to Session Limit : Shows total number of packets dropped when session limit is reached.

4-12 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

In the Session Timeout section, modify TCP, UDP, and ICMP timeouts as required. A session will time out if it does not receive any data for the duration of the specified timeout. The default values are 1200 seconds for TCP, 180 seconds for UDP, and 8 seconds for ICMP.

Click Apply to save your settings.

Inbound Rules Examples

Hosting A Local Public Web Server

If you host a public Web server on your local network, you can define a rule to allow inbound Web

(HTTP) requests from any outside IP address to the IP address of your Web server at any time of day. This rule is shown in Figure 4-7 :

Figure 4-7

Allowing Videoconference from Restricted Addresses

If you want to allow incoming videoconferencing to be initiated from a restricted range of outside

IP addresses, such as from a branch office, you can create an inbound rule. In the example shown to the right, CU-SeeMe connections are allowed only from a specified range of external IP addresses.

Firewall Protection and Content Filtering v1.0, March 2009

4-13

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 4-8

Setting Up One-to-One NAT Mapping

In this example, we will configure multi-NAT to support multiple public IP addresses on one WAN interface. By creating an inbound rule, we will configure the firewall to host an additional public

IP address and associate this address with a Web server on the LAN.

Tip: If your ISP allows you to have more than one public IP address for your use, you can use the additional public IP addresses to map to servers on your LAN. One of these public IP addresses will be used as the primary IP address of the router. This address will be used to provide Internet access to your LAN PCs through NAT. The other addresses are available to map to your servers.

To configure the FVS338 for additional IP addresses:

Select Security from the main menu and Firewall Rules from the submenu.

Click Add under the Inbound Services table. The Add LAN WAN Inbound Service screen will display.

From the service pull-down menu, select the HTTP service for a Web server.

From the Action pull-down menu, select Allow Always.

In the Send to LAN Server field, enter the local IP address of your Web server PC.

From the Public Destination IP Address pull down menu, choose Other Public IP Address.

Enter one of your public Internet addresses that will be used by clients on the Internet to reach your Web server.

4-14 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

Click Apply. The rule will display in the Inbound Services table shown in Figure 4-10 .

Figure 4-9

Your rule will now appear in the Inbound Services table of the Rules menu (see Figure 4-10 ).

This rule is different from a normal inbound port forwarding rule in that the Destination box contains an IP Address other than your normal WAN IP Address.

Figure 4-10

To test the connection from a PC on the Internet, type http://<IP_address> , where

<IP_address> is the public IP address you have mapped to your Web server. You should see the home page of your Web server.

Specifying an Exposed Host

Specifying an exposed host allows you to set up a computer or server that is available to anyone on the Internet for services that you have not yet defined.

To expose one of the PCs on your LAN as this host:

Firewall Protection and Content Filtering v1.0, March 2009

4-15

FVS338 ProSafe VPN Firewall 50 Reference Manual

Create an inbound rule that allows all protocols.

Place the rule below all other inbound rules.

Note: For security, NETGEAR strongly recommends that you avoid creating an exposed host. When a computer is designated as the exposed host, it loses much of the protection of the firewall and is exposed to many exploits from the Internet. If compromised, the computer can be used to attack your network.

1. Select All protocols and ALLOW Always (or Allow by Schedule)

2. Place rule below all other inbound rules

Figure 4-11

Outbound Rules Example – Blocking Instant Messenger

Outbound rules let you prevent users from using applications such as AOL Instant Messenger,

Real Audio or other non-essential sites.

If you want to block AOL Instant Messenger usage by employees during working hours, you can create an outbound rule to block that application from any internal IP address to any external address according to the schedule that you have created in the Schedule menu. You can also have the firewall log any attempt to use Instant Messenger during that blocked period.

4-16 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 4-12

Adding Customized Services

Services are functions performed by server computers at the request of client computers. You can configure up to 125 custom services.

For example, Web servers serve Web pages, time servers serve time and date information, and game hosts serve data about other players’ moves. When a computer on the Internet sends a request for service to a server computer, the requested service is identified by a service or port number. This number appears as the destination port number in the transmitted IP packets. For example, a packet that is sent with destination port number 80 is an HTTP (Web server) request.

The service numbers for many common protocols are defined by the Internet Engineering Task

Force (IETF) and published in RFC1700, “Assigned Internet Protocol Numbers.” Service numbers for other applications are typically chosen from the range 1024 to 65535 by the authors of the application.

Although the FVS338 already holds a list of many service port numbers, you are not limited to these choices. Use the Services menu to add additional services and applications to the list for use in defining firewall rules. The Services menu shows a list of services that you have defined, as shown in Figure 4-13 .

Firewall Protection and Content Filtering v1.0, March 2009

4-17

FVS338 ProSafe VPN Firewall 50 Reference Manual

To define a new service, first you must determine which port number or range of numbers is used by the application. This information can usually be determined by contacting the publisher of the application or from user groups of newsgroups. When you have the port number information, you can enter it on the Services screen.

Figure 4-13

To add a service:

Select Security from the main menu and Services from the submenu. The Services screen will display.

In the Add Custom Service table, enter a descriptive name for the service (this is for your convenience).

Select the Layer 3 Protocol that the service uses as its transport protocol. It can be TCP, UDP or ICMP.

Enter the first TCP or UDP port of the range that the service uses. If the service uses only one port, then the Start Port and the Finish Port will be the same.

Enter the last port of the range that the service uses. If the service only uses a single port number, enter the same number in both fields.

Click Add . The new custom service will be added to the Custom Services Table.

To edit the parameters of a service:

In the Custom Services Table, click the Edit icon adjacent to the service you want to edit. The

Edit Service screen will display.

Modify the parameters you wish to change.

Click Reset to cancel the changes and restore the previous settings.

Click Apply to confirm your changes. The modified service will display in the Custom

Services Table.

4-18 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

Specifying Quality of Service (QoS) Priorities

The Quality of Service (QoS) Priorities setting determines the priority of a service, which in turn, determines the quality of that service for the traffic passing through the firewall. The user can change this priority:

• On the Services screen in the Customer Services Table for customized services (see

Figure 4-13 ).

• On the LAN WAN Outbound Services screen (see Figure 4-12 ).

The QoS priority definition for a service determines the queue that is used for the traffic passing through the VPN firewall. A priority is assigned to IP packets using this service. Priorities are defined by the “Type of Service (ToS) in the Internet Protocol Suite” standards, RFC 1349. A ToS priority for traffic passing through the VPN firewall is one of the following:

• Normal-Service: No special priority given to the traffic. The IP packets for services with this priority are marked with a ToS value of 0.

• Minimize-Cost: Used when data has to be transferred over a link that has a lower “cost”. The

IP packets for services with this priority are marked with a ToS value of 1.

• Maximize-Reliability: Used when data needs to travel to the destination over a reliable link and with little or no retransmission. The IP packets for services with this priority are marked with a ToS value of 2.

• Maximize-Throughput : Used when the volume of data transferred during an interval is important even if the latency over the link is high. The IP packets for services with this priority are marked with a ToS value of 4.

• Minimize-Delay: Used when the time required (latency) for the packet to reach the destination must be low. The IP packets for services with this priority are marked with a ToS value of 8.

Firewall Protection and Content Filtering v1.0, March 2009

4-19

FVS338 ProSafe VPN Firewall 50 Reference Manual

Setting a Schedule to Block or Allow Specific Traffic

Schedules define the timeframes under which firewall rules may be applied.

Figure 4-14

Three schedules, Schedule 1, Schedule 2 and Schedule3 can be defined, and any one of these can be selected when defining firewall rules.

To invoke rules based on a schedule, follow these steps:

Select Security from the main menu and Schedule from the sub-menu. The Schedule 1 screen will display.

Check the radio button for All Days or Specific Days. If you chose Specific Days, check the radio button for each day you want the schedule to be in effect.

Check the radio button to schedule the time of day: All Day, or Specific Times. If you chose

Specific Times, enter the Start Time and End Time fields (Hour, Minute, AM/PM), which will limit access during certain times for the selected days.

Click Apply to save your settings to Schedule 1.

Repeat these steps to set to a schedule for Schedule 2 and Schedule 3.

Setting Block Sites (Content Filtering)

If you want restrict internal LAN users from access to certain sites on the Internet, you can use the

VPN firewall’s Content Filtering and Web Components filtering. By default, these features are disabled; all requested traffic from any Web site is allowed. If you enable one or more of these features and users try to access a blocked site, they will see a “Blocked by NETGEAR” message.

4-20 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

Several types of blocking are available:

• Web Components blocking. You can block the following Web component types: Proxy, Java,

ActiveX, and Cookies. Even sites on the Trusted Domains list will be subject to Web

Components blocking when the blocking of a particular Web component is enabled.

• Keyword (and domain name) blocking. You can specify up to 32 words that, should they appear in the Web site name (URL) or in a newsgroup name, will cause that site or newsgroup to be blocked by the VPN firewall.

You can apply the keywords to one or more groups. Requests from the PCs in the groups for which keyword blocking has been enabled will be blocked. Blocking does not occur for the

PCs that are in the groups for which keyword blocking has not been enabled.

You can bypass Keyword blocking for trusted domains by adding the exact matching domain to the list of Trusted Domains. Access to the domains or keywords on this list by PCs, even those in the groups for which keyword blocking has been enabled, will still be allowed without any blocking.

Keyword Blocking application examples:

• If the keyword “XXX” is specified, the URL <http://www.badstuff.com/xxx.html> is blocked, as is the newsgroup alt.pictures.XXX.

• If the keyword “.com” is specified, only Web sites with other domain suffixes (such as .edu or.gov) can be viewed.

• If you wish to block all Internet browsing access, enter the keyword “.”.

To enable Content Filtering:

Select Security from the main menu and Block Sites from the sub-menu. The Block Sites screen will display.

Check the Yes radio button to enable Content Filtering.

Check the radio boxes of any Web Components you wish to block.

Check the radio buttons of the groups to which you wish to apply Keyword Blocking. Click

Enable to activate Keyword blocking (or disable to deactivate Keyword Blocking).

Build your list of blocked Keywords or Domain Names in the Blocked Keyword fields. After each entry, click Add. The Keyword or Domain name will be added to the Blocked Keywords table. (You can also edit an entry by clicking Edit in the Action column adjacent to the entry.)

Build a list of Trusted Domains in the Trusted Domains fields. After each entry, click Add.

The Trusted Domain will appear in the Trusted Domains table. (You can also edit any entry by clicking Edit in the Action column adjacent to the entry.)

Firewall Protection and Content Filtering v1.0, March 2009

4-21

FVS338 ProSafe VPN Firewall 50 Reference Manual

Click Reset to cancel your changes and revert to the previous settings.

Click Apply to save your settings.

4-22

Figure 4-15 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

Enabling Source MAC Filtering

Source MAC Filter allows you to filter out traffic coming from certain known machines or devices.

• By default, the source MAC address filter is disabled. All the traffic received from PCs with any MAC address is allowed by default.

• When enabled, traffic will be dropped coming from any computers or devices whose MAC addresses are listed in Available MAC Addresses to be Blocked table.

Figure 4-16

Note: For additional ways of restricting outbound traffic, see “LAN WAN Outbound

Services Rules” on page 4-8 .

To enable MAC filtering and add MAC addresses to be blocked:

Select Security from the main menu and Source MAC Filter from the sub-menu. The Source

MAC Filter screen will display.

Check the Yes radio box in the MAC Filtering Enable section.

Build your list of Source MAC Addresses to be block by entering the first MAC address in the

MAC Address field in the form xx:xx:xx:xx:xx:xx where x is a numeric (0 to 9) or an alphabet between and a and f (inclusive), for example: 00:e0:4c:69:0a:

Firewall Protection and Content Filtering v1.0, March 2009

4-23

FVS338 ProSafe VPN Firewall 50 Reference Manual

Click Add. The Mac Address will be added to the Available MAC Addresses to be Blocked table. (You can edit the MAC address by clicking Edit in the Action column adjacent to the

MAC Address.)

Click Reset to cancel a MAC address entry before adding it to the table.

When you have completed adding MAC addresses, click Apply to save your settings.

IP/MAC Binding

IP/MAC Binding allows you to bind an IP to a MAC address and vice-versa. Some machines are configured with static addresses. To prevent users from changing their static IP addresses, IP/MAC

Binding must be enabled on the router. If the router sees packets with a matching IP address, but with an inconsistent MAC address (or vice-versa), it will drop these packets. If users have enabled the logging option for IP/MAC Binding, these packets will be logged before they are dropped. The router will then display the total number of dropped packets that violated either the IP-to-MAC

Binding or the MAC-to-IP Binding.

Example : If three computers on the LAN are set up as follows:

• Host1: MAC address (00:01:02:03:04:05) and IP address (192.168.10.10)

• Host2: MAC address (00:01:02:03:04:06) and IP address (192.168.10.11)

• Host3: MAC address (00:01:02:03:04:07) and IP address (192.168.10.12)

If all the above host entries are added to the IP/MAC Binding table, the following scenarios indicate the possible outcome.

• Host1: Matching IP & MAC address in IP/MAC Table.

• Host2: Matching IP but inconsistent MAC address in IP/MAC Table.

• Host3: Matching MAC but inconsistent IP address in IP/MAC Table.

The router will block the traffic coming from Host2 and Host3, but allow the traffic coming from

Host1 to any external network. The total count of dropped packets will be displayed.

To invoke the IP/MAC Binding Table screen:

Select Security from the main menu and IP/MAC Binding from the sub-menu. The IP/MAC

Binding screen will display.

4-24 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 4-17

The IP/MAC Binding Table lists the currently defined IP/MAC Bind rules:

• Name : Displays the user-defined name for this rule.

• MAC Addresses : Displays the MAC Addresses for this rule.

• IP Addresses : Displays the IP Addresses for this rule.

• Log Dropped Packets : Displays the logging option for this rule.

To add an IP/MAC Bind rule, enter: a. Name : Specify easily identifiable name for this rule.

b. MAC Address : Specify the MAC Address for this rule.

IP Addresses : Specify the IP Address for this rule.

d. Log Dropped Packets : Specify the logging option for this rule.

To edit an IP/MAC Bind rule, click Edit adjacent to the entry:

The following fields of an existing IP/MAC Bind rule can be modified: a. MAC Address : Specify the MAC Address for this rule.

b. IP Addresses : Specify the IP Address for this rule.

Log Dropped Packets : Specify the logging option for this rule.

To remove an entry from the table, select the IP/MAC Bind entry and click Delete .

Click Apply to save your settings.

Firewall Protection and Content Filtering v1.0, March 2009

4-25

FVS338 ProSafe VPN Firewall 50 Reference Manual

Setting Up Port Triggering

Port triggering allows some applications running on a LAN network to be available to external applications that would otherwise be partially blocked by the firewall. Using this feature requires that you know the port numbers used by the Application.

Once configured, Port Triggering operates as follows:

1. A PC makes an outgoing connection using a port number defined in the Port Triggering table.

2. The VPN firewall records this connection, opens the an INCOMING port or ports associated with this entry in the Port Triggering table, and associates them with the PC.

3. The remote system receives the PCs request and responds using the different port numbers that you have now opened.

4. The VPN firewall matches the response to the previous request, and forwards the response to the PC.

Without Port Triggering, this response would be treated as a new connection request rather than a response. As such, it would be handled in accordance with the Port Forwarding rules:

• Only one PC can use a Port Triggering application at any time.

• After a PC has finished using a Port Triggering application, there is a Time-out period before the application can be used by another PC. This is required because this Router cannot be sure when the application has terminated.

Note: For additional ways of allowing inbound traffic, see “LAN WAN Inbound

Services Rules” on page 4-9 .

To add a Port triggering rule:

Select Security from the main menu and Port Triggering from the submenu. The Port

Triggering screen will display.

Enter a user-defined name for this rule in the Name field.

4-26 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

From the Enable pull-down menu, indicate if the rule is enabled or disabled.

Figure 4-18

From the Protocol pull-down menu, select either TCP or UDP protocol.

In the Outgoing (Trigger) Port Range fields; a.

Enter the Start Port range (1 - 65534).

Enter the End Port range (1 - 65534).

In the Incoming (Response) Port Range fields: a.

Enter the Start Port range (1 - 65534).

Firewall Protection and Content Filtering v1.0, March 2009

4-27

FVS338 ProSafe VPN Firewall 50 Reference Manual b.

Enter the End Port range (1 - 65534).

Click Add. The Port Triggering Rule will be added to the Port Triggering Rules table.

To edit or modify a rule:

Click Edit in the Action column opposite the rule you wish to edit. The Edit Port Triggering

Rule screen will display.

Modify any of the fields for this rule.

Click Reset to cancel any changes and return to the previous settings.

Click Apply to save your modifications. Your changes will appear in the Port Triggering

Rules table.

To check the status of the Port Triggering rules, click the Status link on the Port Triggering screen..

Figure 4-19

Bandwidth Limiting

Bandwidth limiting determines the way in which the data is communicated with your host. The purpose of bandwidth limiting is to provide a solution for limiting the traffic, thus preventing the

LAN users from consuming all the bandwidth on your WAN link.

Bandwidth limiting does not apply to the DMZ interface.

4-28 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

Example : When a new connection is established by a device, the device will locate the firewall rule corresponding to the following connections.

• If the rule has a bandwidth profile specification, then the device will create a bandwidth class in the kernel.

• If multiple connections correspond to the same firewall rule, they will share the same class.

An exception occurs in the case of an individual type bandwidth profile if the classes are per source IP. The source IP is the IP of the first packet of the connection.

The class is deleted when all the connections using the class expire.

To add a Bandwidth Profile:

Select Security from the main menu and Bandwidth Profile from the submenu. The

Bandwidth Profile screen will display.

Figure 4-20

The Bandwidth Profile table lists the currently defined bandwidth profiles:

• Name : Displays the user-defined name for this bandwidth profile.

• Bandwidth Range : Displays the range for the bandwidth profile.

• Type : Displays the type of bandwidth profile.

• Direction : Displays the direction of the bandwidth profile.

• WAN : Displays the WAN interface for the Load Balancing mode.

Click Add to add a new Bandwidth Profile. When the Add New Bandwidth Profile screen displays, enter the following: a. Name : Specify an easily identifiable name for the profile.

b. Minimum Bandwidth : Specify the minimum bandwidth value in Kbps for the profile.

Maximum Bandwidth : Specify the maximum bandwidth value in Kbps for the profile.

Firewall Protection and Content Filtering v1.0, March 2009

4-29

FVS338 ProSafe VPN Firewall 50 Reference Manual d. Type : Specify the type of profile.

Direction : Specify the direction for the profile.

WAN : Specify the WAN interface (if in Load Balancing Mode) for the profile.

Click Apply to save your settings. Your new Bandwidth Profile will be added to the

Bandwidth Profile Table.

To edit a Bandwidth Profile:

Click Edit adjacent to the profile you want to edit. The Edit Bandwidth Profile screen will display.

Modify any of the following fields: a. Minimum Bandwidth : Specify the minimum bandwidth value in Kbps for the profile.

b. Maximum Bandwidth : Specify the maximum bandwidth value in Kbps for the profile.

Type : Specify the type for the profile.

d. Direction : Specify the direction for the profile.

WAN : Specify WAN in case of Load Balancing mode for the profile.

Click Apply . Your modified profile will display in the Bandwidth Profile table.

To remove an entry from the table, select the profile and click Delete .

To remove all the profiles, click Select All and then click Delete .

E-Mail Notifications of Event Logs and Alerts

The Firewall Logs can be configured to log and then e-mail denial of access, general attack information, and other information to a specified email address. For example, your VPN firewall will log security-related events such as: accepted and dropped packets on different segments of your LAN; denied incoming and outgoing service requests; hacker probes and Login attempts; and other general information based on the settings you input on the Firewall Logs &

E-mail screen. In addition, if you have set up Content Filtering on the Block Sites screen (see

“Setting Block Sites (Content Filtering)” on page 4-20 ), a log will be generated when someone on your network tries to access a blocked site.

You must have e-mail notification enabled to receive the logs in an e-mail message. If you don't have e-mail notification enabled, you can view the logs on the Logs screen (see Figure 4-21 on page 4-31 ). Selecting all events will increase the size of the log, so it is good practice to select only those events which are required.

4-30 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 4-21

To set up Firewall Logs and E-mail alerts:

Select Monitoring from the main menu and then Firewall Logs & E-mail from the submenu.

The Firewall Logs & E-mail screen will display.

Enter the name of the log in the Log Identifier field. Log Identifier is a mandatory field used to identify the log messages. The ID appended to log messages.

Enter a Schedule for sending the logs. From the Unit pull-down menu, select: Never, Hourly,

Daily, or Weekly. Then fill in the Day and Time fields that correspond to your selection.

In the Security Logs section, check the network segments radio box for which you would like logs to be sent (for example, LAN to WAN under Dropped Packets).

Firewall Protection and Content Filtering v1.0, March 2009

4-31

FVS338 ProSafe VPN Firewall 50 Reference Manual

In the System Logs section, check the radio box for the type of system events to be logged.

Check the Yes radio box to enable E-mail Logs. Then enter: a. E-mail Server address – Enter the outgoing E-mail SMTP mail server address of your

ISP (for example, 172.16.1.10). If you leave this box blank, no logs will be sent to you. b. Return E-mail Address – Enter the e-mail address of the user. c.

Send To E-mail Address – Enter the e-mail address where the logs and alerts should be sent. You must use the full e-mail address (for example, [email protected]).

The No Authentication radio box is checked by default. If your SMTP server authenticates users, uncheck the radio box by selecting the authentication type—either Login Plain or

CRAM-MD5 —based on your SMTP server requirements. Then enter the user name and password to be used for authentication.

If you want to respond to IDENT protocol, check the Respond to Identd from SMTP Server radio box. The Ident Protocol is an Internet protocol that helps identify the user of a particular

TCP connection (a common daemon program for providing the ident service is identd).

You can configure the firewall to send system logs to an external PC that is running a syslog logging program. Click the Yes radio box to enable SysLogs and send messages to the syslog server, then: a.

Enter your Syslog Server IP address b.

Select the appropriate syslog severity from the SysLog Severity pull-down menu. The

SysLog levels of severity are as follows:

• LOG_EMERG (System is unusable)

• LOG_ALERT (Action must be taken immediately)

• LOG_CRITICAL (Critical conditions)

• LOG_ERROR (Error conditions)

• LOG_WARNING (Warning conditions)

• LOG_NOTICE (Normal but significant conditions)

• LOG_INFO (Informational messages)

• LOG_DEBUG (Debug level messages)

10.

Click Reset to cancel your changes and return to the previous settings.

11.

Click Apply to save your settings.

To view the Firewall logs:

4-32 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

Click on the View Log icon opposite the Firewall Logs & E-mail tab. The Logs screen will display.

If the E-mail Logs options as been enabled, you can send a copy of the log by clicking send log.

Click refresh log to retrieve the latest update; and click clear log to delete all entries.

Log entries are described in Table 4-3 . Refer to Appendix B, “System Logs and Error Messages” for more information about log entry messages.

Figure 4-22

Table 4-3.

Log Entry Descriptions

Field Description

Date and Time The date and time the log entry was recorded.

Description or Action The type of event and what action was taken if any.

Source IP

Source port and interface

Destination

Destination port and interface

The IP address of the initiating device for this log entry.

The service port number of the initiating device, and whether it originated from the

LAN, WAN or DMZ.

The name or IP address of the destination device or Web site.

The service port number of the destination device, and whether it’s on the LAN,

WAN or DMZ.

Firewall Protection and Content Filtering v1.0, March 2009

4-33

FVS338 ProSafe VPN Firewall 50 Reference Manual

Administrator Information

Consider the following operational items:

1. As an option, you can enable remote management if you have to manage distant sites from a central location (see “Enabling Remote Management Access” on page 6-10 ).

2. Although setting firewall rules (see “Using Rules to Block or Allow Specific Kinds of Traffic” on page 4-2 ) is the basic way of managing the traffic through your system, you can further refine your control with the following features of the VPN firewall:

– Groups and hosts (see “Managing Groups and Hosts” on page 3-6 )

– Services (see “Services-Based Rules” on page 4-2 )

– Schedules (see “Setting a Schedule to Block or Allow Specific Traffic” on page 4-20 )

– Block sites (see “Setting Block Sites (Content Filtering)” on page 4-20 )

– Source MAC filtering (see “Enabling Source MAC Filtering” on page 4-23 )

– Port triggering (see “Setting Up Port Triggering” on page 4-26 )

4-34 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

Firewall Protection and Content Filtering v1.0, March 2009

4-35

FVS338 ProSafe VPN Firewall 50 Reference Manual

4-36 v1.0, March 2009

Firewall Protection and Content Filtering

FVS338 ProSafe VPN Firewall 50 Reference Manual

Firewall Protection and Content Filtering v1.0, March 2009

4-37

FVS338 ProSafe VPN Firewall 50 Reference Manual

4-38 v1.0, March 2009

Firewall Protection and Content Filtering

Chapter 5 Virtual Private Networking

This chapter describes how to use the Virtual Private Networking (VPN) features of the VPN firewall. This chapter includes the following sections:

• “Considerations for Dual WAN Port Systems” on page 5-1

• “Using the VPN Wizard for Client and Gateway Configurations” on page 5-2

• “Testing the Connections and Viewing Status Information” on page 5-11

• “IKE Policies” on page 5-14

• “VPN Policies” on page 5-16

• “Extended Authentication (XAUTH) Configuration” on page 5-18

• “Assigning IP Addresses to Remote Users (ModeConfig)” on page 5-23

• “Certificates” on page 5-31

Considerations for Dual WAN Port Systems

If both of the WAN ports of the VPN firewall are configured, you can enable either Auto-Rollover mode for increased system reliability or Load Balancing mode for optimum bandwidth efficiency.

This WAN mode choice impacts how the VPN features must be configured.

The use of fully qualified domain names in VPN policies is mandatory when the WAN ports are in rollover mode.

The diagram and table below shows how the WAN mode selection relates to VPN configuration.

Firewall

Rest of

Firewall

Functions

Firewall

WAN Port

Functions

Firewall

Rollover

Control

WAN Auto-Rollover: FQDN Required for VPN

WAN 1 Port

Internet

WAN 2 Port

Same FQDN required for both WAN ports

Figure 5-1

Virtual Private Networking 5-1 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table 5-1 summarizes the WAN addressing requirements for either dual WAN mode.

Table 5-1. IP Addressing for VPNs in Dual WAN Port Systems

Configuration WAN IP address Rollover Mode a

VPN Road Warrior (client-to-gateway)

VPN Gateway-to-Gateway

Fixed or DHCP

FQDN required

VPN Telecommuter (client-to-gateway NAT router) Fixed or DHCP FQDN required a. All tunnels must be re-established after a rollover using the new WAN IP address.

Using the VPN Wizard for Client and Gateway Configurations

You use the VPN Wizard to configure multiple gateway or client VPN tunnel policies.

The section below provides wizard and NETGEAR VPN Client configuration procedures for the following scenarios:

• Using the wizard to configure a VPN tunnel between 2 VPN gateways

• Using the wizard to configure a VPN tunnel between a VPN gateway and a VPN client

Configuring a VPN tunnel connection requires that all settings and parameters on both sides of the

VPN tunnel match or mirror each other precisely, which can be a daunting task. The VPN Wizard efficiently guides you through the setup procedure with a series of questions that will determine the IPsec keys and VPN policies it sets up. The VPN Wizard will also set the parameters for the network connection: Security Association, traffic selectors, authentication algorithm, and encryption. The parameters used by the VPN wizard are based on the recommendations of the

VPN Consortium (VPNC), an organization that promotes multi-vendor VPN interoperability.

Creating Gateway to Gateway VPN Tunnels with the Wizard

Figure 5-2

Follow these steps to set up a gateway VPN tunnel using the VPN Wizard.

5-2 Virtual Private Networking v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Select VPN > IPsec VPN > VPN Wizard to display the VPN Wizard tab page.

To view the wizard default settings, click the VPN Default values link. You can modify these settings after completing the wizard.

• Gateway connection

• Connection name

• Pre-shared key

• Remote and local

WAN addresses

• Remote LAN IP address and subnet

Figure 5-3

Select Gateway as your connection type.

Create a Connection Name . Enter a descriptive name for the connection. This name used to help you manage the VPN settings; is not supplied to the remote VPN endpoint.

Enter a Pre-shared Key . The key must be entered both here and on the remote VPN gateway, or the remote VPN client. This key must be a minimum of 8 characters and should not exceed

49 characters.

Enter the Remote and Local WAN IP Addresses or Internet Name s of the gateways which will connect.

• Both the remote WAN address and your local WAN address are required.

Virtual Private Networking v1.0, March 2009

5-3

FVS338 ProSafe VPN Firewall 50 Reference Manual

• The remote WAN IP address must be a public address or the Internet name of the remote gateway. The Internet name is the Fully Qualified Domain Name (FQDN) as registered in a Dynamic DNS service. Both local and remote endpoints should be defined as either

FQDN or IP addresses. A combination of IP address and FQDN is not allowed.

Tip: For DHCP WAN configurations, first, set up the tunnel with IP addresses.

Once you validate the connection, use the wizard to create new policies using FQDN for the WAN addresses.

Enter the local LAN IP and Subnet Mask of the remote gateway in the Remote LAN IP

Address and Subnet Mask fields.

Note: The Remote LAN IP address must be in a different subnet than the Local LAN

IP address. For example, if the local subnet is 192.168.1.x, then the remote subnet could be 192.168.10.x. but could not be 192.168.1.x. If this information is incorrect, the tunnel will fail to connect.

Click Apply to save your settings: the VPN Policies page shows the policy is now enabled.

Figure 5-4

If you are connecting to another NETGEAR VPN firewall, use the VPN Wizard to configure the second VPN firewall to connect to the one you just configured.

After both firewalls are configured, go to VPN > IPsec VPN > Connection Status to display the status of your VPN connections.

5-4

Figure 5-5 v1.0, March 2009

Virtual Private Networking

FVS338 ProSafe VPN Firewall 50 Reference Manual

The tunnel will automatically establish when both the local and target gateway policies are appropriately configured and enabled,

Note: When using FQDN, if the dynamic DNS service is slow to update their servers when your DHCP WAN address changes, the VPN tunnel will fail because the

FQDN does not resolve to your new address. If you have the option to configure the update interval, set it to an appropriately short time.

Creating a Client to Gateway VPN Tunnel

Figure 5-6

Follow these steps to configure the a VPN client tunnel:

• Configure the client policies on the gateway.

• Configure the VPN client to connect to the gateway.

Virtual Private Networking v1.0, March 2009

5-5

FVS338 ProSafe VPN Firewall 50 Reference Manual

Use the VPN Wizard Configure the Gateway for a Client Tunnel

From the main menu, go to VPN > IPSec VPN > VPN Wizard . The VPN Wizard displays.

• VPN Client connection

• Connection name

• Pre-shared key: r3m0+eC1ient

• Remote identifier

• Local identifier

Figure 5-7

Select VPN Client as your VPN tunnel connection.

Create a Connection Name like “Client to GW1”.

This descriptive name is not supplied to the remote VPN client; it is only for your reference.

Enter a Pre-shared Key ; in this example, we are using r3m0+eC1ient, which must also be entered in the VPN client software. The key length must be 8 characters minimum and cannot exceed 49 characters.

The public Remote and Local Identifier are automatically filled in by pre-pending the first several letters of the model number of your gateway to form FQDNs used in the VPN policies.

In this example, we are using GW1_remote.com, and GW1_local.com.

5-6 v1.0, March 2009

Virtual Private Networking

FVS338 ProSafe VPN Firewall 50 Reference Manual

Click Apply to save your settings: the VPN Policies page shows the policy is now enabled.

Figure 5-8

Use the NETGEAR VPN Client Security Policy Editor to Create a Secure Connection

From a PC with the NETGEAR Prosafe VPN Client installed, configure a VPN client policy to connect to the FVS338. Follow these steps to configure your VPN client.

Right-click on the VPN client icon in your Windows toolbar, choose Security Policy Editor, and verify that the Options > Secure > Specified Connections selection is enabled.

Figure 5-9

Virtual Private Networking v1.0, March 2009

5-7

FVS338 ProSafe VPN Firewall 50 Reference Manual

In the upper left of the Policy Editor window, click the New Document icon (the first on the left) to open a New Connection. Give the New Connection a name; in this example, we are using gw1 .

5-8

Figure 5-10

Fill in the other options according to the instructions below.

• Under Connection Security, verify that the Secure radio button is selected.

• From the ID Type pull-down menu, choose IP Subnet .

• Enter the LAN IP Subnet Address and Subnet Mask of the FVS338 LAN; in this example, we are using 192.168.2.0.

• Check the Use checkbox and choose Secure Gateway Tunnel from the pull-down menu.

• From the first ID Type pull-down menus, choose Domain Name.

Enter the FQDN address which the FVS338 VPN Wizard provided; in this example, we are using gw1_local.com.

• From the second ID Type pull-down menu, choose Gateway IP Address and enter the

WAN IP Gateway address of the FVS338; in this example, we are using 21.208.216.81.

v1.0, March 2009

Virtual Private Networking

FVS338 ProSafe VPN Firewall 50 Reference Manual

In the left frame, click My Identity . Fill in the options according to the instructions below. r3m0+eC1ient

Figure 5-11

• From the Select Certificate pull-down menu, choose None .

• Click Pre-Shared Key to enter the key you provided in the VPN Wizard; in this example, we are using r3m0+eC1ient .

• From the ID Type pull-down menu, choose Domain Name.

• Leave Virtual Adapter disabled.

• In Network Adapter select the adapter you will use; the IP address of the selected adapter will display.

Virtual Private Networking v1.0, March 2009

5-9

FVS338 ProSafe VPN Firewall 50 Reference Manual

Verify the Security Policy settings; no changes are needed.

Figure 5-12

• On the left, click Security Policy to view the settings: no changes are needed.

• On the left, expand Authentication (Phase 1) and click Proposal 1 : no changes are needed.

• On the left, expand Key Exchange (Phase 2) and click Proposal 1 . No changes are needed.

In the upper left of the window, click the disk icon to save the policy.

5-10 v1.0, March 2009

Virtual Private Networking

FVS338 ProSafe VPN Firewall 50 Reference Manual

Testing the Connections and Viewing Status Information

Both the NETGEAR VPN Client and the FVS338 provide VPN connection and status information. This information is useful for verifying the status of a connection and troubleshooting problems with a connection.

NETGEAR VPN Client Status and Log Information

To test a client connection and view the status and log information, follow these steps.

1. To test the client connection, from your PC, right-click on the VPN client icon in your

Windows toolbar and choose Connect...

, then My Connections\gw1 .

Figure 5-13

Within 30 seconds you should receive the message “Successfully connected to My

Connections\gw1”.

Figure 5-14

The VPN client icon in the system tray should say On:

Virtual Private Networking v1.0, March 2009

5-11

FVS338 ProSafe VPN Firewall 50 Reference Manual

2. To view more detailed additional status and troubleshooting information from the NETGEAR

VPN client, follow these steps.

• Right-click the VPN Client icon in the system tray and select Log Viewer.

Figure 5-15

• Right-click the VPN Client icon in the system tray and select Connection Monitor.

5-12

Figure 5-16 v1.0, March 2009

Virtual Private Networking

FVS338 ProSafe VPN Firewall 50 Reference Manual

The VPN client system tray icon provides a variety of status indications, which are listed below.

Table 5-2.

System Tray Icon Status

The client policy is deactivated.

The client policy is deactivated but not connected.

The client policy is activated and connected.

A flashing vertical bar indicates traffic on the tunnel.

FVS338 VPN Connection Status and Logs

To view FVS338 VPN connection status, go to VPN > Connection Status .

Figure 5-17

Virtual Private Networking v1.0, March 2009

5-13

FVS338 ProSafe VPN Firewall 50 Reference Manual

To view FVS338 VPN logs, go to Monitoring > VPNLogs .

Figure 5-18

IKE Policies

The IKE (Internet Key Exchange) protocol performs negotiations between the two VPN

Gateways, and provides automatic management of the Keys used in IPSec. It is important to remember that:

• “Auto” generated VPN policies must use the IKE negotiation protocol.

• “Manual” generated VPN policies cannot use the IKE negotiation protocol.

IKE Policy Operation

IKE Policies are activated when:

1. The VPN Policy Selector determines that some traffic matches an existing VPN Policy. If the

VPN policy is of type “Auto”, then the Auto Policy Parameters defined in the VPN Policy are accessed which specify which IKE Policy to use.

2. If the VPN Policy is a “Manual” policy, then the Manual Policy Parameters defined in the

VPN Policy are accessed and the first matching IKE Policy is used to start negotiations with the remote VPN Gateway.

• If negotiations fail, the next matching IKE Policy is used.

• If none of the matching IKE Policies are acceptable to the remote VPN Gateway, then a

VPN tunnel cannot be established.

5-14 Virtual Private Networking v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

3. An IKE session is established, using the SA (Security Association) parameters specified in a matching IKE Policy:

• Keys and other parameters are exchanged.

• An IPsec SA (Security Association) is established, using the parameters in the VPN

Policy.

The VPN tunnel is then available for data transfer.

IKE Policy Table

When you use the VPN Wizard to set up a VPN tunnel, an IKE Policy is established and populated in the Policy Table and is given the same name as the new VPN connection name. You can also edit exiting policies or add new IKE policies directly on the Policy Table Screen. Each policy contains the following data:

• Name . Uniquely identifies each IKE policy. The name is chosen by you and used for the purpose of managing your policies; it is not supplied to the remote VPN Server. If the Policy is a Client Policy, it will be prepended by an “*”.

• Mode . Two modes are available: either “Main” or “Aggressive”.

– Main Mode is slower but more secure.

– Aggressive mode is faster but less secure. (If specifying either a FQDN or a User FQDN name as the Local ID/Remote ID, aggressive mode is automatically selected.)

• Local ID . The IKE/ISAKMP identify of this device. (The remote VPN must have this value as their “Remote ID”.)

• Remote ID . The IKE/ISAKMP identify of the remote VPN Gateway. (The remote VPN must have this value as their “Local ID”.)

• Encr . Encryption Algorithm used for the IKE SA. The default setting using the VPN Wizard is

3DES. (This setting must match the Remote VPN.)

• Auth . Authentication Algorithm used for the IKE SA. The default setting using the VPN

Wizard is SHA1. (This setting must match the Remote VPN.)

• DH . Diffie-Hellman Group. The Diffie-Hellman algorithm is used when exchanging keys. The

DH Group sets the number of bits. The VPN Wizard default setting is Group 2. (This setting must match the Remote VPN.)

• Enable Dead Peer Detection : Dead Peer Detection is used to detect whether the peer is alive or not. If the peer is detected as dead, the IPSec and IKE Security Association are deleted.

Virtual Private Networking 5-15 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

To gain a more complete understanding of the encryption, authentication and DH algorithm technologies, see Appendix C, “Related Documents” .

VPN Policies

You can create two types of VPN Policies. When using the VPN Wizard to create a VPN policy, only the Auto method is available.

• Manual . All settings (including the keys) for the VPN tunnel are manually input at each end

(both VPN endpoints). No third party server or organization is involved.

• Auto . Some parameters for the VPN tunnel are generated automatically by using the IKE

(Internet Key Exchange) protocol to perform negotiations between the two VPN endpoints

(the Local ID Endpoint and the Remote ID Endpoint).

In addition, a CA (Certificate Authority) can also be used to perform authentication (see

“Certificates” on page 5-31 ). To use a CA, each VPN Gateway must have a Certificate from the

CA. For each Certificate, there is both a “Public Key” and a “Private Key”. The “Public Key” is freely distributed, and is used to encrypt data. The receiver then uses their “Private Key” to decrypt the data (without the Private Key, decryption is impossible). CAs can be beneficial since using them reduces the amount of data entry required on each VPN Endpoint.

VPN Policy Operation

The VPN Policies screen allows you to add additional policies—either Auto or Manual—and to manage the VPN policies already created. You can edit policies, enable or disable them, or delete them entirely. The rules for VPN policy use conform to:

1. Traffic covered by a policy will automatically be sent via a VPN tunnel.

2. The VPN tunnel is created according to the parameters in the SA (Security Association).

3. The remote VPN Endpoint must have a matching SA, or it will refuse the connection.

VPN Policy Table

When you use the VPN Wizard to set up a VPN tunnel, both a VPN Policy and an IKE Policy is established and populated in both Tables on the VPN Policies screen. The name you selected as the

VPN Tunnel connection name during Wizard setup identifies both the VPN Policy and IKE Policy.

You can also edit exiting policies, add new VPN policies directly or change the policy hierarchy to the Policy Table. The Policy Table contains the following fields:

5-16 Virtual Private Networking v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

• ! (Status) . Indicates whether the policy is enabled (green circle) or disabled (grey circle). To

Enable or Disable a Policy, check the radio box adjacent to the circle and click Enable or

Disable , as required.

• Name . Each policy is given a unique name (the Connection Name when using the VPN

Wizard). Client Policies are annotated by an “*”.

• Type . The Type is “Auto” or “Manual” as described previously (Auto is used during VPN

Wizard configuration).

• Keep alive : It periodically sends ping packets to the host on the peer side of the network to keep the tunnel alive.

– Enable Keep Alive : Check to enable.

– Ping IP Address : Enter the IP Address to which ping packets need to be sent.

– Detection period : Router sends ping packets periodically at regular intervals of time which is specified by the user.

– Reconnect after failure count : Fresh negotiation starts when no acknowledgement is received for the specified number of consecutive packets.

• Local . IP address (either a single address, range of address or subnet address) on your local

LAN. Traffic must be from (or to) these addresses to be covered by this policy. (Subnet address is the default IP address when using the VPN Wizard).

• Remote . IP address or address range of the remote network. Traffic must be to (or from) these addresses to be covered by this policy. (The VPN Wizard default requires the remote LAN IP address and subnet mask for a gateway policy).

• AH . Authentication Header. This specifies the authentication protocol for the VPN header

(VPN Wizard default is disabled).

• ESP . Encapsulating Security Payload. This specifies the encryption protocol used for the VPN data (VPN Wizard default is enabled).

VPN Tunnel Connection Status

Recent VPN tunnel activity is shown on the IPSec Connection Status screen (accessed by selecting VPN from the main menu and Connection Status from the submenu).You can set a Poll

Interval (in seconds) to check the connection status of all active IKE Policies to obtain the latest

VPN tunnel activity. The Active IPSec (SA)s table also lists current data for each active IPSec SA

(Security Association):

• Policy Name. The name of the VPN policy associated with this SA.

Virtual Private Networking 5-17 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

• Endpoint . The IP address on the remote VPN Endpoint.

• Tx (KBytes) . The amount of data transmitted over this SA.

• Tx (Packets). The number of packets transmitted over this SA.

• State . The current state of the SA. Phase 1 is “Authentication phase” and Phase 2 is “Key

Exchange phase”.

• Action . Allows you to terminate or build the SA (connection), if required.

Extended Authentication (XAUTH) Configuration

When connecting many VPN clients to a VPN gateway router, an administrator may want a unique user authentication method beyond relying on a single common preshared key for all clients.

Although the administrator could configure a unique VPN policy for each user, it is more convenient for the VPN gateway router to authenticate users from a stored list of user accounts.

XAUTH provides the mechanism for requesting individual authentication information from the user, and a local User Database or an external authentication server, such as a RADIUS server, provides a method for storing the authentication information centrally in the local network.

XAUTH is enabled when adding or editing an IKE Policy. Two types of XAUTH are available:

• Edge Device. If this is selected, the router is used as a VPN concentrator where one or more gateway tunnels terminate. If this option is chosen, you must specify the authentication type to be used in verifying credentials of the remote VPN gateways: User Database, RADIUS-PAP, or RADIUS-CHAP.

• IPSec Host. If you want authentication by the remote gateway, enter a User Name and

Password to be associated with this IKE policy. If this option is chosen, the remote gateway must specify the user name and password used for authenticating this gateway.

Note: If a RADIUS-PAP server is enabled for authentication, XAUTH will first check the local User Database for the user credentials. If the user account is not present, the router will then connect to a RADIUS server.

5-18 v1.0, March 2009

Virtual Private Networking

FVS338 ProSafe VPN Firewall 50 Reference Manual

Configuring XAUTH for VPN Clients

Once the XAUTH has been enabled, you must establish user accounts on the Local Database to be authenticated against XAUTH, or you must enable a RADIUS-CHAP or RADIUS-PAP server.

Note: If you are modifying an existing IKE Policy to add XAUTH , if it is in use by a

VPN Policy, the VPN policy must be disabled before you can modify the IKE

Policy.

To enable and configure XAUTH:

Select VPN from the main menu and Policies from the submenu. The IKE Policies screen will display.

You can either modify an existing IKE Policy by clicking Edit adjacent to the policy, or create a new IKE Policy by clicking Add.

Note: If the IKE policy is in use by a VPN Policy, you must either disable or delete the VPN policy before making changes to the IKE Policy.

In the Extended Authentication section, select the Authentication Type from the pull-down menu which will be used to verify user account information. Select

• Edge Device to use this router as a VPN concentrator where one or more gateway tunnels terminate. When this option is chosen, you will need to specify the authentication type to be used in verifying credentials of the remote VPN gateways.

– User Database to verify against the router’s user database. Users must be added through the User Database screen (see “User Database Configuration” on page 5-20 ).

– RADIUS–CHAP or RADIUS–PAP (depending on the authentication mode accepted by the RADIUS server) to add a RADIUS server. If RADIS–PAP is selected, the router will first check in the User Database to see if the user credentials are available.

If the user account is not present, the router will then connect to the RADIUS server

(see “RADIUS Client Configuration” on page 5-21 ).

• IPSec Host if you want to be authenticated by the remote gateway. In the adjacent

Username and Password fields, type in the information user name and password associated with the IKE policy for authenticating this gateway (by the remote gateway).

Virtual Private Networking 5-19 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Click Apply to save your settings.

Figure 5-19

User Database Configuration

The User Database Screen is used to configure and administer VPN Client users for use by the

XAUTH server. Whether or not you use an external RADIUS server, you may want to have some users authenticated locally. These users must be added to the User Database Configured Users table.

To add a new user:

Select VPN from the main menu and VPN Client from the submenu. The User Database screen will display.

Enter a User Name . This is the unique ID of a user which will be used in the User Name field of the VPN client.

Enter a Password for the user, and reenter the password in the Confirm Password field.

5-20 Virtual Private Networking v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Click Add. The User Name will be added to the Configured Hosts table.

Figure 5-20

To edit the user name or password:

Click Edit opposite the user’s name. The Edit User screen will display.

Make the required changes to the User Name or Password and click Apply to save your settings or Reset to cancel your changes and return to the previous settings . The modified user name and password will display in the Configured Users table.

RADIUS Client Configuration

RADIUS (Remote Authentication Dial In User Service, RFC 2865) is a protocol for managing

Authentication, Authorization and Accounting (AAA) of multiple users in a network. A RADIUS server will store a database of user information, and can validate a user at the request of a gateway or server in the network when a user requests access to network resources. During the establishment of a VPN connection, the VPN gateway can interrupt the process with an XAUTH

(eXtended AUTHentication) request. At that point, the remote user must provide authentication information such as a username/password or some encrypted response using his username/

Virtual Private Networking 5-21 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual password information. The gateway will try and verify this information first against a local User

Database (if RADIUS-PAP is enabled) and then by relaying the information to a central authentication server such as a RADIUS server.

To configure the Primary RADIUS Server:

Select VPN from the main menu, VPN Client from the submenu and then select the RADIUS

Client tab. The RADIUS Client screen will display.

Enable the Primary RADIUS server by checking the Yes radio box.

Enter the Primary RADIUS Server IP address .

Enter a Secret Phrase . Transactions between the client and the RADIUS server are authenticated using a shared secret phrase, so the same Secret Phrase must be configured on both client and server.

Enter the Primary Server NAS Identifier (Network Access Server). This Identifier MUST be present in a RADIUS request. Ensure that NAS Identifier is configured as the same on both client and server.

The FVS338 is acting as a NAS (Network Access Server), allowing network access to external users after verifying their authentication information. In a RADIUS transaction, the NAS must provide some NAS Identifier information to the RADIUS Server. Depending on the configuration of the RADIUS Server, the router's IP address may be sufficient as an identifier, or the Server may require a name, which you would enter here. This name would also be configured on the RADIUS Server, although in some cases it should be left blank on the

RADIUS Server.

Enable a Backup RADIUS Server (if required) by following steps 2 through 5.

Set the Time Out Period , in seconds, that the router should wait for a response from the

RADIUS server.

Set the Maximum Retry Count.

This is the number of tries the router will make to the

RADIUS server before giving up.

Click Reset to cancel any changes and revert to the previous settings.

10.

Click Apply to save the settings.

Note: The Authentication Protocol, usually PAP or CHAP, is configured in the

XAUTH section of the VPN Client screen.

5-22 Virtual Private Networking v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 5-21

Assigning IP Addresses to Remote Users (ModeConfig)

To simply the process of connecting remote VPN clients to the FVS338, the ModeConfig module can be used to assign IP addresses to remote users, including a network access IP address, subnet mask, and name server addresses from the router. Remote users are given IP addresses available in secured network space so that remote users appear as seamless extensions of the network.

In the following example, we configured the VPN firewall using ModeConfig, and then configured a PC running ProSafe VPN Client software using these IP addresses.

• NETGEAR ProSafe VPN Firewall 50

– WAN IP address: 172.21.4.1

– LAN IP address/subnet: 192.168.2.1/255.255.255.0

• NETGEAR ProSafe VPN Client software IP address: 192.168.1.2

Virtual Private Networking v1.0, March 2009

5-23

FVS338 ProSafe VPN Firewall 50 Reference Manual

ModeConfig Operation

After IKE Phase 1 is complete, the VPN connection initiator (remote user/client) asks for IP configuration parameters such as IP address, subnet mask and name server addresses. The

ModeConfig module will allocate an IP address from the configured IP address pool and will activate a temporary IPSec policy using the template security proposal information configured in the ModeConfig record.

Note: After configuring a Mode Config record, you must go to the IKE Policies menu and configure an IKE policy using the newly-created Mode Config record as the

Remote Host Configuration Record. The VPN Policies menu does not need to be edited.

Setting Up ModeConfig

Two menus must be configured—the ModeConfig menu and the IKE Policies menu.

To configure the ModeConfig menu:

Select VPN from the main menu and Mode Config from the submenu. The Mode Config screen will display.

Click Add.

The Add Mode Config Record screen will display.

Enter a descriptive Record Name such as “Remote Users”.

Assign at least one range of IP Pool addresses in the First IP Pool field to give to remote VPN clients.

Note: The IP Pool should not be within your local network IP addresses. Use a different range of private IP addresses such as 172.20.xx.xx.

If you have a WINS Server on your local network, enter its IP address.

Enter one or two DNS Server IP addresses to be used by remote VPN clients.

If you enable Perfect Forward Secrecy (PFS), select DH Group 1 or 2. This setting must match exactly the configuration of the remote VPN client,

Specify the Local IP Subnet to which the remote client will have access. Typically, this is your router’s LAN subnet, such as 192.168.2.1/255.255.255.0. (If not specified, it will default to the

LAN subnet of the device.)

5-24 Virtual Private Networking v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Specify the VPN policy settings. These settings must match the configuration of the remote

VPN client. Recommended settings are:

• SA Lifetime: 3600 seconds

• Authentication Algorithm: SHA-1

• Encryption Algorithm: 3DES

10.

Click Apply . The new record should appear in the VPN Remote Host Mode Config Table (a sample record is shown below).

Figure 5-22

To configure an IKE Policy:

From the main menu, select VPN . The IKE Policies screen will display showing the current policies in the List of IKE Policies Table.

Virtual Private Networking 5-25 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Click Add to configure a new IKE Policy. The Add IKE Policy screen will display.

Enable Mode Config by checking the Yes radio box and selecting the Mode Config record you just created from the pull-down menu. (You can view the parameters of the selected record by clicking the View selected radio box.)

Mode Config works only in Aggressive Mode, and Aggressive Mode requires that both ends of the tunnel be defined by a FQDN.

In the General section: a.

Enter a description name in the Policy Name Field such as “salesperson”. This name will be used as part of the remote identifier in the VPN client configuration.

Set Direction/Type to Responder. c.

By default, the Exchange Mode is set to Aggressive.

For Local information: d.

Select Fully Qualified Domain Name for the Local Identity Type.

Enter an identifier in the Remote Identity Data field that is not used by any other IKE policies. This identifier will be used as part of the local identifier in the VPN client configuration.

Specify the IKE SA parameters. These settings must be matched in the configuration of the remote VPN client. Recommended settings are:

• Encryption Algorithm: 3DES

• Authentication Algorithm: SHA-1

• Diffie-Hellman: Group 2

• SA Lifetime: 3600 seconds

Enter a Pre-Shared Key that will also be configured in the VPN client.

XAUTH is disabled by default. To enable XAUTH, select:

• the Edge Device radio button to use this router as a VPN concentrator where one or more gateway tunnels terminate. (If selected, you must specify the Authentication Type to be used in verifying credentials of the remote VPN gateways.)

• the IPsec Host radio button if you want this gateway to be authenticated by the remote gateway. Enter a Username and Password to be associated with the IKE policy. When this option is chosen, you will need to specify the user name and password to be used in authenticating this gateway (by the remote gateway).

5-26 Virtual Private Networking v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

If Edge Device was enabled, select the Authentication Type from the pull down menu which will be used to verify account information: User Database, RADIUS-CHAP or RADIUS-PAP.

Users must be added thorough the User Database screen (see “User Database Configuration” on page 5-20 or “RADIUS Client Configuration” on page 5-21 ).

Note: If RADIUS-PAP is selected, the router will first check the User Database to see if the user credentials are available. If the user account is not present, the router will then connect to the RADIUS server.

10.

Click Apply.

The new policy will appear in the IKE Policies Table (a sample policy is shown below)

Figure 5-23

Virtual Private Networking v1.0, March 2009

5-27

FVS338 ProSafe VPN Firewall 50 Reference Manual

Configuring the ProSafe VPN Client for ModeConfig

From a client PC running NETGEAR ProSafe VPN Client software, configure the remote VPN client connection.

To configure the client PC:

Right-click the VPN client icon in the Windows toolbar. In the upper left of the Policy Editor window, click the New Policy editor icon.

Give the connection a descriptive name such as “modecfg_test” (this name will only be used internally).

From the ID Type pull-down menu, select IP Subnet.

Enter the IP Subnet and Mask of the VPN firewall (this is the LAN network IP address of the gateway).

Check the Connect using radio button and select Secure Gateway Tunnel from the pulldown menu.

From the ID Type pull-down menu, select Domain name and enter the FQDN of the VPN firewall; in this example it is “local_id.com”.

Select Gateway IP Address from the second pull-down menu and enter the WAN IP address of the VPN firewall; in this example it is “172.21.4.1”.

Figure 5-24

From the left side of the menu, click My Identity and enter the following information: a.

Click Pre-Shared Key and enter the key you configured in the FVS338 IKE menu.

5-28 Virtual Private Networking v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual b.

From the Select Certificate pull-down menu, select None.

From the ID Type pull-down menu, select Domain Name and create an identifier based on the name of the IKE policy you created; for example “remote_id.com”.

Under Virtual Adapter pull-down menu, select Preferred. The Internal Network IP

Address should be 0.0.0.0.

Note: If no box is displayed for Internal Network IP Address, go to Options/

Global Policy Settings, and check the box for “Allow to Specify Internal

Network Address.” e.

Select your Internet Interface adapter from the Name pull-down menu. remote_id.com

Figure 5-25

On the left-side of the menu, select Security Policy.

Under Security Policy, Phase 1 Negotiation Mode, check the Aggressive Mode radio button.

Check the Enable Perfect Forward Secrecy (PFS) radio button, and select the Diffie-

Hellman Group 2 from the PFS Key Group pull-down menu.

Enable Replay Detection should be checked.

Click on Authentication (Phase 1) on the left-side of the menu and select Proposal 1. Enter the

Authentication values to match those in the VPN firewall ModeConfig Record menu.

Virtual Private Networking 5-29 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 5-26

Click on Key Exchange (Phase 2) on the left-side of the menu and select Proposal 1. Enter the values to match your configuration of the VPN firewall ModeConfig Record menu. (The SA

Lifetime can be longer, such as 8 hours (28800 seconds)).

Figure 5-27

Click the Save icon to save the Security Policy and close the VPN ProSafe VPN client.

5-30 Virtual Private Networking v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

To test the connection:

Right-click on the VPN client icon in the Windows toolbar and select Connect. The connection policy you configured will appear; in this case “My Connections\modecfg_test”.

Click on the connection. Within 30 seconds the message “Successfully connected to

MyConnections/modecfg_test will display and the VPN client icon in the toolbar will read

“On”.

From the client PC, ping a computer on the VPN firewall LAN.

Certificates

Digital Certificates (also known as X509 Certificates) are used to authenticate the identity of users and systems, and are issued by various CAs (Certification Authorities). Digital Certificates are used by this router during the IKE (Internet Key Exchange) authentication phase as an alternative authentication method. Trusted Certificates are issued to you by various CAs (Certification

Authorities).

The FVS338 uses Digital Certificates during the Internet Key Exchange (IKE) authentication phase to authenticate connecting VPN gateways or clients, or to be authenticated by remote entities. The same Digital Certificates are extended for secure web access connections over

HTTPS.

Digital Certificates can be either self signed or can be issued by Certification Authorities (CA) such as via an in-house Windows server, or by an external organization such as Verisign or

Thawte.

However, if the Digital Certificates contain the extKeyUsage extension then the certificate must be used for one of the purposes defined by the extension. For example, if the Digital Certificate contains the extKeyUsage extension defined to SNMPV2 then the same certificate cannot be used for secure web management.

The extKeyUsage would govern the certificate acceptance criteria in the FVS338 when the same digital certificate is being used for secure web management.

In the FVS338, the uploaded digital certificate is checked for validity and also the purpose of the certificate is verified. Upon passing the validity test and the purpose matches its use (has to be SSL and VPN) the digital certificate is accepted. The additional check for the purpose of the uploaded digital certificate must correspond to use for VPN and secure web remote management via

HTTPS. If the purpose defined is for VPN & HTTPS then the certificate is uploaded to the HTTPS certificate repository and as well in the VPN certificate repository. If the purpose defined is ONLY

Virtual Private Networking 5-31 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual for VPN then the certificate is only uploaded to the VPN certificate repository. Thus, certificates used by HTTPS and IPSec will be different if their purpose is not defined to be VPN and HTTPS.

Trusted Certificates (CA Certificates)

Trusted Certificates are used to verify the validity of certificates issued to an organization and signed by the issuing CA authority. When a certificate is generated, it is signed by a publiclyknown authority called the Certificate Authority.

The Trusted Certificates table shows the Trusted Certificates issued by the various CAs

(Certification Authorities). For each Certificate, the following data is listed in the Trusted

Certificates table:

• CA Identity (Subject Name) . The organization or name to whom the certificate has been issued.

• Issuer Name. The name of the CA that issued the certificate.

• Expiry Time. The date when the certificate becomes invalid.

New certificates can be uploaded to the router when they are received.

To upload a Trusted Certificate:

Select VPN from the main menu and Certificates from the submenu. The Certificates screen will display.

Click Browse to locate the trusted certificate on your computer and then click Upload . The certificate will be stored on the router and will display in the Trusted Certificates table.

Figure 5-28

5-32 v1.0, March 2009

Virtual Private Networking

FVS338 ProSafe VPN Firewall 50 Reference Manual

Self Certificates

Active Self certificates are certificates issued to you by the various Certificate Authorities (CAs) that are available for presentation to peer IKE servers. Each active self certificate is listed in the

Active Self Certificates table. The data consists of:

• Name. A unique given by you to identify the certificate.

• Subject Name . The name which other organizations will see as the Holder (owner) of this

Certificate. This should be your registered business name or official company name.

Generally, all Certificates should have the same value in the Subject field.

• Serial Number . This is the serial number maintained by the CA. It is used to identify the certificate with in the CA.

• Issuer Name.

The name of the CA which issued the Certificate.

• Expiry Time . The date on which the Certificate expires. You should renew the Certificate before it expires.

To use a Certificate, you must first generate and request the certificate from the CA from the computer or device that will be using the CA. The Certificate Signing Request (CSR) file must be filled out and submitted to the CA who will then generate a certificate for this device.

To request a Certificate from the CA:

From the main menu under VPN , select the Certificates submenu. The Certificates screen will display.

In the Generate Self Certificate Request, enter the required data:

• Name – Enter a name that will identify this Certificate.

• Subject – This is the name which other organizations will see as the Holder (owner) of the

Certificate. Since this name will be seen by other organizations, you should use your registered business name or official company name.

This information must be submitted in the following format: C= <country> , ST= <state> ,

L= <city> , O= <organization>, OU= <department>, CN= <device name>. In the following example: C=USA, ST=CA, L=Santa Clara, O=NETGEAR, OU=XX,

CN=FVS338)

• From the pull-down menus, select the following values:

– Hash Algorithm: MD5 or SHA2.

– Signature Algorithm: RSA.

Virtual Private Networking 5-33 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

– Signature Key Length: 512, 1024, 2048. (Larger key sizes may improve security, but may also impact performance.)

Complete the Optional fields, if desired, with the following information:

• IP Address – If you have a fixed IP address, you may enter it here. Otherwise, you should leave this field blank.

• Domain Name – If you have a Domain name, you can enter it here. Otherwise, you should leave this field blank.

• E-mail Address – Enter your e-mail address in this field.

Click Generate . Your request will display in the Self Certificate Requests table.

View the request by clicking View in the Action column. The Self Certificate Request screen will display.

The Self Certificate Request data screen will display the data required for submission to the

CA. Copy the data in the Data to supply to CA field data into a file, including all of the data contained in “----BEGIN CERTIFICATE REQUEST---” and “---END CERTIFICATE

REQUEST---”

Following the instructions of the CA to complete the certificate request process.

5-34 v1.0, March 2009

Virtual Private Networking

FVS338 ProSafe VPN Firewall 50 Reference Manual

Save to file

Figure 5-29

To submit your Self Certificate request to a CA:

Connect to the web site of the CA.

Start the Self Certificate request procedure.

When prompted for the requested data, copy the data from your saved data file (including “---

-BEGIN CERTIFICATE REQUEST---” and “---END CERTIFICATE REQUEST’).

Submit the CA form. If no problems ensue, the Certificate will be issued.

Virtual Private Networking 5-35 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

When you obtain the certificate from the CA, you can then upload it to your computer. Click

Browse to locate the Certificate file and then click Upload. The certificate will display in the

Active Self Certificates table (see Figure 5-28 ).

Certificates are updated by their issuing CA authority on a regular basis. You should track all of your CAs to ensure that you have the latest version and/or that your certificate has not been revoked. To track your CAs, you must upload the Certificate Identify for each CA to the CRL.

Managing your Certificate Revocation List (CRL)

CRL (Certificate Revocation List) files show Certificates which are active and certificates which have been revoked, and are no longer valid. Each CA issues their own CRLs.

It is important that you keep your CRLs up-to-date. You should obtain the CRL for each CA regularly.

The CRL table lists your active CAs and their critical release dates:

• CA Identity – The official name of the CA which issued this CRL.

• Last Update – The date when this CRL was released.

• Next Update – The date when the next CRL will be released.

To upload a Certificate Identity to the CRL:

Click Browse , and then locate the file you previously downloaded from a CA.

Select the Certificate Identity file. The name will appear in the “File to upload” field. Click

Upload. The new Certificate Identity will appear in the Certification Revocation Lists table.

If you have a previous CA Identity from the same CA, it should now be deleted.

5-36 v1.0, March 2009

Virtual Private Networking

Chapter 6 Router and Network Management

This chapter describes how to use the network management features of your ProSafe VPN

Firewall 50. This chapter includes the following sections:

• “Performance Management” on page 6-1

• “Administration” on page 6-7

• “Monitoring the Router” on page 6-18

Performance Management

Performance management consists of controlling the traffic through the VPN firewall so that the necessary traffic gets through when there is a bottleneck and either reducing unnecessary traffic or rescheduling some traffic to low-peak times to prevent bottlenecks from occurring in the first place. The VPN firewall has the necessary features and tools to help the network manager accomplish these goals.

VPN Firewall Features That Reduce Traffic

Features of the VPN firewall that can be called upon to decrease WAN-side loading are as follows:

• Service Blocking

• Block Sites

• Source MAC Filtering

Service Blocking

You can control specific outbound traffic (for example., from LAN to WAN). Outbound Services lists all existing rules for outbound traffic. If you have not defined any rules, only the default rule will be listed. The default rule allows all outgoing traffic.

Warning: This feature is for Advanced Administrators only! Incorrect configuration will cause serious problems.

Router and Network Management v1.0, March 2009

6-1

FVS338 ProSafe VPN Firewall 50 Reference Manual

Each rule lets you specify the desired action for the connections covered by the rule:

• BLOCK always

• BLOCK by schedule, otherwise Allow

• ALLOW always

• ALLOW by schedule, otherwise Block

As you define your firewall rules, you can further refine their application according to the following criteria:

• LAN Users – These settings determine which computers on your network are affected by this rule. Select the desired options:

– Any: All PCs and devices on your LAN.

– Single address: The rule will be applied to the address of a particular PC.

– Address range: The rule is applied to a range of addresses.

– Groups: The rule is applied to a Group (you use the Network Database to assign PCs to

Groups—see “Managing Groups and Hosts” on page 3-6 ).

• WAN Users – These settings determine which Internet locations are covered by the rule, based on their IP address.

– Any: The rule applies to all Internet IP address.

– Single address: The rule applies to a single Internet IP address.

– Address range: The rule is applied to a range of Internet IP addresses.

• Services – You can specify the desired Services or applications to be covered by this rule. If the desired service or application does not appear in the list, you must define it using the

Services menu (see “Services-Based Rules” on page 4-2 ).

• Schedule – You can specify whether the rule is to be applied on the Schedule 1, Schedule 2, or

Schedule 3 time schedule (see “Setting a Schedule to Block or Allow Specific Traffic” on page 4-20 ).

See “Using Rules to Block or Allow Specific Kinds of Traffic” on page 4-2 for the procedure on how to use this feature.

Services. The Rules menu contains a list of predefined Services for creating firewall rules. If a service does not appear in the predefined Services list, you can define the service. The new service will then appear in the Rules menu's Services list.

See “Services-Based Rules” on page 4-2 for the procedure on how to use this feature.

6-2 Router and Network Management v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Groups and Hosts. You can apply these rules selectively to groups of PCs to reduce the outbound or inbound traffic. The Network Database is an automatically-maintained list of all known PCs and network devices. PCs and devices become known by the following methods:

• DHCP Client Request – By default, the DHCP server in this Router is enabled, and will accept and respond to DHCP client requests from PCs and other network devices. These requests also generate an entry in the Network Database. Because of this, leaving the DHCP

Server feature (on the LAN screen) enabled is strongly recommended.

• Scanning the Network – The local network is scanned using standard methods such as ARP.

This will detect active devices which are not DHCP clients. However, sometimes the name of the PC or device cannot be accurately determined, and will be shown as Unknown.

See “Managing Groups and Hosts” on page 3-6 for the procedure on how to use this feature.

Schedule. If you have set firewall rules on the Rules screen, you can configure three different schedules (i.e., schedule 1, schedule 2, and schedule 3) for when a rule is to be applied. Once a schedule is configured, it affects all Rules that use this schedule. You specify the days of the week and time of day for each schedule.

See “Setting a Schedule to Block or Allow Specific Traffic” on page 4-20 for the procedure on how to use this feature.

Block Sites

If you want to reduce traffic by preventing access to certain sites on the Internet, you can use the

VPN firewall's filtering feature. By default, this feature is disabled; all requested traffic from any

Web site is allowed.

• Keyword (and Domain Name) Blocking – You can specify up to 32 words that, should they appear in the Web site name (URL) or in a newsgroup name, will cause that site or newsgroup to be blocked by the VPN firewall.

You can apply the keywords to one or more groups. Requests from the PCs in the groups for which keyword blocking has been enabled will be blocked. Blocking does not occur for the

PCs that are in the groups for which keyword blocking has not been enabled.

You can bypass keyword blocking for trusted domains by adding the exact matching domain to the list of Trusted Domains. Access to the domains on this list by PCs even in the groups for which keyword blocking has been enabled will still be allowed without any blocking.

• Web Component Blocking – You can block the following Web component types: Proxy,

Java, ActiveX, and Cookies. Sites on the Trusted Domains list are still subject to Web component blocking when the blocking of a particular Web component has been enabled.

Router and Network Management 6-3 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

See “Setting Block Sites (Content Filtering)” on page 4-20 for the procedure on how to use this feature.

Source MAC Filtering

If you want to reduce outgoing traffic by preventing Internet access by certain PCs on the LAN, you can use the source MAC filtering feature to drop the traffic received from the PCs with the specified MAC addresses. By default, this feature is disabled; all traffic received from PCs with any MAC address is allowed.

See “Enabling Source MAC Filtering” on page 4-23 for the procedure on how to use this feature.

VPN Firewall Features That Increase Traffic

Features that tend to increase WAN-side loading are as follows:

• Port forwarding

• Port triggering

• DMZ port

• Exposed hosts

• VPN tunnels

Port Forwarding

The firewall always blocks DoS (Denial of Service) attacks. A DoS attack does not attempt to steal data or damage your PCs, but overloads your Internet connection so you can not use it (i.e., the service is unavailable). You can also create additional firewall rules that are customized to block or allow specific traffic.

Warning: This feature is for Advanced Administrators only! Incorrect configuration will cause serious problems.

You can control specific inbound traffic (i.e., from WAN to LAN and from WAN to DMZ).

Inbound Services lists all existing rules for inbound traffic. If you have not defined any rules, only the default rule will be listed. The default rule blocks all inbound traffic.

Each rule lets you specify the desired action for the connections covered by the rule:

• BLOCK always

• BLOCK by schedule, otherwise Allow

• ALLOW always

6-4 Router and Network Management v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

• ALLOW by schedule, otherwise Block

You can also enable a check on special rules:

• VPN Passthrough – Enable this to pass the VPN traffic without any filtering, specially used when this firewall is between two VPN tunnel end points.

• Drop fragmented IP packets – Enable this to drop the fragmented IP packets.

• UDP Flooding – Enable this to limit the number of UDP sessions created from one LAN machine.

• TCP Flooding – Enable this to protect the router from Syn flood attack.

• Enable DNS Proxy – Enable this to allow the incoming DNS queries.

• Enable Stealth Mode – Enable this to set the firewall to operate in stealth mode.

As you define your firewall rules, you can further refine their application according to the following criteria:

• LAN Users – These settings determine which computers on your network are affected by this rule. Select the desired IP Address in this field.

• WAN Users – These settings determine which Internet locations are covered by the rule, based on their IP address.

– Any: The rule applies to all Internet IP address.

– Single address: The rule applies to a single Internet IP address.

– Address range: The rule is applied to a range of Internet IP addresses.

• Destination Address – These settings determine the destination IP address for this rule which will be applicable to incoming traffic, this rule will be applied only when the destination IP address of the incoming packet matches the IP address of the WAN interface selected or

Specific IP address entered in this field.Selecting ANY enables the rule for any IP in destination field.similarly WAN1 and WAN2 corresponds to respective wan interfaces.

• Services – You can specify the desired Services or applications to be covered by this rule. If the desired service or application does not appear in the list, you must define it using the

Services menu (see “Adding Customized Services” on page 4-17 ).

• Schedule – You can specify whether the rule is to be applied on the Schedule 1, Schedule 2, or

Schedule 3 time schedule (see “Setting a Schedule to Block or Allow Specific Traffic” on page 4-20 ).

See “Using Rules to Block or Allow Specific Kinds of Traffic” on page 4-2 for the procedure on how to use this feature.

Router and Network Management 6-5 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Port Triggering

Port triggering allows some applications to function correctly that would otherwise be partially blocked by the firewall. Using this feature requires that you know the port numbers used by the

Application.

Once configured, operation is as follows:

• A PC makes an outgoing connection using a port number defined in the Port Triggering table.

• This Router records this connection, opens the additional INCOMING port or ports associated with this entry in the Port Triggering table, and associates them with the PC.

• The remote system receives the PCs request and responds using the different port numbers that you have now opened.

• This Router matches the response to the previous request and forwards the response to the PC.

Without Port Triggering, this response would be treated as a new connection request rather than a response. As such, it would be handled in accordance with the Port Forwarding rules.

– Only one PC can use a Port Triggering application at any time.

– After a PC has finished using a Port Triggering application, there is a time-out period before the application can be used by another PC. This is required because the firewall cannot be sure when the application has terminated.

See “Setting Up Port Triggering” on page 4-26 for the procedure on how to use this feature.

VPN Tunnels

The VPN firewall permits up to 200 VPN tunnels at a time. Each tunnel requires extensive processing for encryption and authentication.

See Chapter 5, “Virtual Private Networking ” for the procedure on how to use this feature.

Using QoS to Shift the Traffic Mix

The QoS priority settings determine the priority and, in turn, the quality of service for the traffic passing through the firewall. The QoS is set individually for each service.

• You can accept the default priority defined by the service itself by not changing its QoS setting.

• You can change the priority to a higher or lower value than its default setting to give the service higher or lower priority than it otherwise would have.

The QoS priority settings conform to the IEEE 802.1D-1998 (formerly 802.1p) standard for class of service tag.

6-6 Router and Network Management v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

You will not change the WAN bandwidth used by changing any QoS priority settings. But you will change the mix of traffic through the WAN ports by granting some services a higher priority than others. The quality of a service is impacted by its QoS setting, however.

See “Specifying Quality of Service (QoS) Priorities” on page 4-19 for the procedure on how to use this feature.

Tools for Traffic Management

The ProSafe VPN Firewall 50 includes several tools that can be used to monitor the traffic conditions of the firewall and control who has access to the Internet and the types of traffic they are allowed to have. See “Viewing Router Configuration and System Status” on page 6-23 for a discussion of the tools.

Administration

You can change the administrator and guest passwords and settings, configure an SNMP manager, backup settings and upgrade firmware, and enable remote management. Administrator access is read/write and guest access is read-only.

Changing Passwords and Settings

The default passwords for the firewall’s Web Configuration Manager is password . Netgear recommends that you change this password to a more secure password. You can also configure a separate password for guests.

To modify User or Admin settings:

Router and Network Management v1.0, March 2009

6-7

FVS338 ProSafe VPN Firewall 50 Reference Manual

Select Users from the main menu and Local Authentication from the submenu.

Figure 6-1

Select the Settings you wish to edit by checking either the Edit Admin Settings or Edit Guest

Settings radio box.

Change the password by first entering the old password, and then entering the new password twice.

Click Apply to save your settings or Cancel to return to your previous settings.

Change the Idle Logout Time field to the number of minutes you require. The default is 5 minutes.

Note: If you make the administrator login time-out value too large, you will have to wait a long time before you are able to log back into the router if your previous login was disrupted (i.e., you did not click Logout on the Main Menu bar to log out).

Click Apply to save this setting.

6-8 v1.0, March 2009

Router and Network Management

FVS338 ProSafe VPN Firewall 50 Reference Manual

Note: The password and time-out value you enter will be changed back to password and 5 minutes, respectively, after a factory defaults reset.

RADIUS Server External Authentication

For authentication to RADIUS or WIKID, you can define the authentication type.

Figure 6-2

When a user logs in, the VPN firewall will validate with the appropriate RADIUS or WIKID server that the user is authorized to log in.

Router and Network Management v1.0, March 2009

6-9

FVS338 ProSafe VPN Firewall 50 Reference Manual

When specifying RADIUS domain authentication, you are presented with several authentication protocol choices, as summarized in the following table:

Table 6-1.

Authentication

Protocol

Description

PAP

CHAP

MIAS

WiKID

Password Authentication Protocol (PAP) is a simple protocol in which the client sends a password in clear text.

Challenge Handshake Authentication Protocol (CHAP) executes a three-way handshake in which the client and server trade challenge messages, each responding with a hash of the other’s challenge message that is calculated using a shared secret value.

Network validated PAP or CHAP password based authentication scheme.

WiKID is a PAP or CHAP key-based two-factor authentication method using public key cryptography. The client sends an encrypted PIN to the WiKID server and receives a onetime passcode with a short expiration period. The client logs in with the passcode. See

Appendix D, “Two Factor Authentication” for more on WiKID authentication.

The chosen authentication protocol must be configured on the RADIUS server and on the authenticating client devices.

Enabling Remote Management Access

Using the Remote Management page, you can allow an administrator on the Internet to configure, upgrade, and check the status of your VPN firewall. You must be logged in locally to enable remote management (see “Logging in to the VPN Firewall” on page 2-1 ).

Note: Be sure to change the firewall default configuration password to a very secure password. The ideal password should contain no dictionary words from any language, and should be a mixture of letters (both upper and lower case), numbers, and symbols. Your password can be up to 30 characters. See “Changing Passwords and Settings” on page 6-7 for the procedure on how to do this.

6-10 v1.0, March 2009

Router and Network Management

FVS338 ProSafe VPN Firewall 50 Reference Manual https://194.177.0.123:8080

Figure 6-3

To configure your firewall for Remote Management:

Select the Turn Remote Management On check box.

Specify what external addresses will be allowed to access the firewall’s remote management.

Note: For enhanced security, restrict access to as few external IP addresses as practical.

To allow access from any IP address on the Internet, select Everyone. c.

To allow access from a range of IP addresses on the Internet, select IP address range.

Enter a beginning and ending IP address to define the allowed range. d.

To allow access from a single IP address on the Internet, select Only this PC.

Enter the IP address that will be allowed access.

Router and Network Management 6-11 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Specify the Port Number that will be used for accessing the management interface.

Web browser access normally uses the standard HTTP service port 80. For greater security, you can change the remote management Web interface to a custom port by entering that number in the box provided. Choose a number between 1024 and 65535, but do not use the number of any common service port. The default is 8080, which is a common alternate for

HTTP.

Click Apply to have your changes take effect.

When accessing your firewall from the Internet, the Secure Sockets Layer (SSL) will be enabled.

You will enter https:// and type the WAN IP address of your firewall into your browser, followed by a colon (:) and the custom port number. For example, if your WAN IP address is 134.177.0.123 and you use port number 8080, enter the following in your browser: https://134.177.0.123:8080

The remote URL login of the router is https://IP_address:port_number or https://FullyQualifiedDomainName:port_number .

If you do not use the SSL https://address , but rather use http://address , the FVS338 will automatically attempt to redirect to https://address.

Note: The first time you remotely connect the FVS338 with a browser via SSL, you may get a message regarding the SSL certificate. If you are using a Windows computer with Internet Explorer 5.5 or higher, simply click Yes to accept the certificate.

Note: If you are using a dynamic DNS service such as TZO, you can always identify the

IP address of your FVS338 by running tracert from the Windows Run menu.

For example, renter tracert yourFVS338.mynetgear.net

and you will see the IP address your ISP assigned to the FVS338.

To configure your firewall for Telnet Management:

Select Administration from the main menu and Remote Management from the submenu.

The Remote Management screen will display.

Check the Allow Telnet Management radio box.

6-12 v1.0, March 2009

Router and Network Management

FVS338 ProSafe VPN Firewall 50 Reference Manual

Specify what external addresses will be allowed to access the firewall’s remote management.

Note: For enhanced security, restrict access to as few external IP addresses as practical.

To allow access from any IP address on the Internet, select Everyone . b.

To allow access from a range of IP addresses on the Internet, select IP address range .

Enter a beginning and ending IP address to define the allowed range. c.

To allow access from a single IP address on the Internet, select Only this PC .

Enter the IP address that will be allowed access.

Click Apply to have your changes take effect.

Using a SNMP Manager

Simple Network Management Protocol (SNMP) lets you monitor and manage your router from an

SNMP Manager. It provides a remote means to monitor and control network devices, and to manage configurations, statistics collection, performance, and security.

The SNMP Configuration table lists the SNMP configurations by:

• IP Address : The IP address of the SNMP manager.

• Port : The trap port of the configuration.

• Community : The trap community string of the configuration.

To create a new SNMP configuration entry:

Select Administration from the main menu and SNMP from the submenu. The SNMP screen will display.

Under Create New SNMP Configuration Entry, enter the IP Address of the SNMP manager in the IP Address field and the Subnet Mask in the Subnet Mask field.

• If you want to allow only the host address to access the VPN firewall and receive traps (for example, see Figure 6-4 ), enter an IP Address of, for example, 192.168.1.100 with a

Subnet Mask of 255.255.255.

255 .

• If you want to allow a subnet access to the VPN firewall through SNMP, enter an IP address of, for example,192.168.1.100 with a Subnet Mask of 255.255.255.

0 . The traps will still be received on 192.168.1.100, but the entire subnet will have access through the community string.

Router and Network Management 6-13 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

• If you want to make the VPN firewall globally accessible using the community string, but still receive traps on the host, enter 0.0.0.0 as the Subnet Mask and an IP Address for where the traps will be received.

Enter the trap port number of the configuration in the Port field. The default is 162.

Enter the trap community string of the configuration in the Community field.

Click Add to create the new configuration. The entry will display in the SNMP

Configuration table.

Click Edit in the Action column adjacent to the entry to modify or change the selected configuration.

Figure 6-4

The SNMP System Info link displays the VPN firewall identification information available to the

SNMP Manager. System Contact, System Location, and System name.

To modify the SNMP System contact information:

Click the SNMP System Info link. The SNMP SysConfiguration screen will display.

Modify any of the contact information that you want the SNMP Manager to use.

Click Apply to save your settings.

6-14 Router and Network Management v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Settings Backup and Firmware Upgrade

Once you have installed the VPN firewall and have it working properly, you should back up a copy of your setting so that it is if something goes wrong. When you backup the settings, they are saved as a file on your computer. You can then restore the VPN firewall settings from this file. The

Settings Backup & Upgrade screen allows you to:

• Back up and save a copy of your current settings

• Restore saved settings from the backed-up file.

• Revert to the factory default settings.

• Upgrade the VPN firewall firmware from a saved file on your hard disk to use a different firmware version.

Backup and Restore Settings

To backup and restore settings:

Select Administration from the main menu and Settings Backup & Upgrade from the submenu. THe Settings Backup and Firmware Upgrade screen will display.

Click backup to save a copy of your current settings.

If your browser isn’t set up to save downloaded files automatically, locate where you want to save the file, specify file name, and click Save. If you have your browser set up to save downloaded files automatically, the file will be saved to your browser's download location on the hard disk.

Warning: Once you start restoring settings or erasing the router, do NOT interrupt the process. Do not try to go online, turn off the router, shutdown the computer or do anything else to the router until it finishes restarting!

To restore settings from a backup file:

Click Browse . Locate and select the previously saved backup file (by default, netgear.cfg).

When you have located the file, click restore .

An Alert page will appear indicating the status of the restore operation. You must manually restart the VPN firewall for the restored settings to take effect.

To reset the router to the original factory default settings, click default

Router and Network Management v1.0, March 2009

6-15

FVS338 ProSafe VPN Firewall 50 Reference Manual

You must manually restart the VPN firewall in order for the default settings to take effect. After rebooting, the router's password will be password and the LAN IP address will be 192.168.1.1.

The VPN firewall will act as a DHCP server on the LAN and act as a DHCP client to the Internet.

Warning: When you click default, your router settings will be erased. All firewall rules,

VPN policies, LAN/WAN settings and other settings will be lost. Please backup your settings if you intend on using them!

Figure 6-5

Router Upgrade

You can install a different version of the VPN firewall firmware from the Settings Backup &

Upgrade screen. To view the current version of the firmware that your VPN firewall is running, select Monitoring from the main menu. The Router Status screen on the will display all of the

VPN firewall router statistics. When you upgrade your firmware, the Firmware Version will change to reflect the new version.

To download a firmware version:

Go to the NETGEAR Web site at http://www.netgear.com/support and click on Downloads.

From the Product Selection pull-down menu, select your product. Select the software version and follow the To Install steps to download your software.

After downloading an upgrade file, you may need to unzip (uncompress) it before upgrading the router. If Release Notes are included in the download, read them before continuing.

6-16 Router and Network Management v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Warning: Once you click Upload do NOT interrupt the router!

To upgrade router software:

Select Administration from the main menu and Settings Backup & Upgrade from the submenu. The Settings Backup and Firmware Upgrade screen will display.

Click Browse in the Router Upgrade section.

Locate the downloaded file and click upload. This will start the software upgrade to your VPN firewall router. This may take some time. At the conclusion of the upgrade, your router will reboot.

Warning: Do not try to go online, turn off the router, shutdown the computer or do anything else to the router until the router finishes the upgrade! When the

Test light turns off, wait a few more seconds before doing anything.

After the VPN firewall has rebooted, select Monitoring and confirm the new firmware version to verify that your router now has the new software installed.

Note: In some cases, such as a major upgrade, it may be necessary to erase the configuration and manually reconfigure your router after upgrading it. Refer to the Release Notes included with the software to find out if this is required.

Setting the Time Zone

Date, time and NTP Server designations can be input on the Time Zone screen. Network Time

Protocol (NTP) is a protocol that is used to synchronize computer clock times in a network of computers.

To set Time, Date and NTP servers:

Select Administration from the main menu and Time Zone from the submenu. The Time

Zone screen will display.

From the Date/Time pull-down menu, select the Local Time Zone. This is required in order for scheduling to work correctly. The VPN firewall includes a Real-Time Clock (RTC), which it uses for scheduling.

Router and Network Management v1.0, March 2009

6-17

FVS338 ProSafe VPN Firewall 50 Reference Manual

If supported in your region, check the Automatically Adjust for Daylight Savings Time radio box.

Select a NTP Server option by checking one of the following radio boxes:

• Use Default NTP Servers : If this is enabled, then the RTC (Real-Time Clock) is updated regularly by contacting a Default Netgear NTP Server on the Internet.

• Use Custom NTP Servers : If you prefer to use a particular NTP server, enable this instead and enter the name or IP address of an NTP Server in the Server 1 Name/IP

Address field.

If required, you can also enter the address of another NTP server in the Server 2 Name/IP

Address field. If you select this option and leave either the Server 1 or Server 2 fields empty, they will be set to the Default Netgear NTP servers.

Click Apply to save your settings or click Cancel to revert to your previous settings.

Figure 6-6

Monitoring the Router

You can be alerted to important events such as WAN port rollover, WAN traffic limits reached, and login failures and attacks. You can also view status information about the firewall, WAN ports,

LAN ports, and VPN tunnels.

6-18 v1.0, March 2009

Router and Network Management

FVS338 ProSafe VPN Firewall 50 Reference Manual

Enabling the Traffic Meter

To monitor traffic limits on each of the WAN ports, select Administration from the main menu and Traffic Meter from the submenu. The Broadband Traffic Meter screen will display. (The

Broadband and Dialup ports are programmed separately.) A WAN port shuts down once its traffic limit is reached if the Block all traffic feature is enabled.

The Traffic Meter screen also provides the following information:

• Internet Traffic Statistics – Displays statistics on Internet Traffic via the WAN port. If you have not enabled the Traffic Meter, these statistics are not available.

Each WAN port is programmed separately.

WAN port shuts down once traffic limit reached. An e-mail can be sent.

Traffic Counter settings

Internet Traffic

Statistics

Figure 6-7

• Traffic by Protocol – Click this button to display Internet Traffic details. The volume of traffic for each protocol will be displayed in a sub-window. Traffic counters are updated in

MBytes scale and the counter starts only when traffic passed is at least 1 MB

Router and Network Management 6-19 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 6-8

Setting Login Failures and Attacks Notification

Figure 6-9 shows the Firewall Logs & E-mail screen that is invoked by selecting Monitoring from the main menu and selecting Firewall Logs & E-mail from the submenu.

You can send a System log of firewall activities to an email address or a log of the firewall activities can be viewed, saved to a syslog server, and then sent to an email address. You can view the logs by clicking View Logs.

6-20 v1.0, March 2009

Router and Network Management

FVS338 ProSafe VPN Firewall 50 Reference Manual

View System Logs

Select the types of events to email.

Select the segments to track for System

Log events.

Enable email alerts.

Syslog Server enabled

Figure 6-9

Router and Network Management v1.0, March 2009

6-21

FVS338 ProSafe VPN Firewall 50 Reference Manual

Viewing Port Triggering Status

You can view the status of Port Triggering by selecting Security from the main menu and Port

Triggering from the submenu. When the Port Triggering screen display, click the Status link.

Figure 6-10

Table 6-2. Port Triggering Status data

Item

Rule

LAN IP Address

Open Ports

Time Remaining

Description

The name of the Rule.

The IP address of the PC currently using this rule.

The Incoming ports which are associated the this rule. Incoming traffic using one of these ports will be sent to the IP address above.

The time remaining before this rule is released, and thus available for other PCs.

This timer is restarted whenever incoming or outgoing traffic is received.

6-22 v1.0, March 2009

Router and Network Management

FVS338 ProSafe VPN Firewall 50 Reference Manual

Viewing Router Configuration and System Status

The Router Status menu provides status and usage information. From the main menu of the browser interface, click on Management , then select Router Status , The Router Status screen will display.

Figure 6-11

Table 6-3. Router Configuration Status Fields

Item

System Name

Firmware Version

LAN Port

Description

This is the Account Name that you entered in the Basic Settings page.

This is the current software the router is using. This will change if you upgrade your router.

Displays the current settings for MAC address, IP address, DHCP role and IP Subnet

Mask that you set in the LAN IP Setup page. DHCP can be either Server or None.

Router and Network Management v1.0, March 2009

6-23

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table 6-3. Router Configuration Status Fields

Item Description

Broadband

Configuration

Indicates whether the WAN Mode is Single or Rollover, and whether the WAN State is UP or DOWN. If the WAN State is up, it also displays

• NAT: Enabled or Disabled.

• Connection Type: DHCP enabled or disabled.

• Connection State: Connected or Disconnected

• WAN IP Address

• Subnet Mask

• Gateway Address

• Primary and Secondary DNS Server Addresses

• MAC Address.

Dialup Configuration Displays the same details as for WAN1 Configuration.

Note: The Router Status screen displays current settings and statistics for your router. As this information is read-only, any changes must be made on other pages.

Monitoring WAN Ports Status

You can monitor the status of both of the WAN connections, the Dynamic DNS Server connections, and the DHCP Server connections. Select Network Configuration from the main menu and WAN Settings from the submenu. The Broadband ISP Settings screen will display.

Click the Broadband Status link to obtain status on the Broadband port. Select the Dialup ISP

Settings tab and click the Dialup Status link to obtain status on the Dialup port.

6-24 v1.0, March 2009

Router and Network Management

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 6-12

Monitoring VPN Tunnel Connection Status

You can view the status of the VPN tunnels by selecting VPN from the main menu and

Connection Status from the submenu. The IPSec Connection Status screen will display.

Figure 6-13

Table 6-4. IPSec Connection Status Fields

Item

Policy Name

Endpoint

Description

The name of the VPN policy associated with this SA.

The IP address on the remote VPN Endpoint.

Router and Network Management v1.0, March 2009

6-25

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table 6-4. IPSec Connection Status Fields (continued)

Item

Tx (KB)

Tx (Packets)

State

Action

Description

The amount of data transmitted over this SA.

The number of IP packets transmitted over this SA.

The current status of the SA.Phase 1 is Authentication phase and Phase 2 is Key

Exchange phase.

Use this button to terminate/build the SA (connection) if required.

VPN Logs

The VPN Logs screen gives log details for recent VPN activity. Select Monitoring from the main menu and VPN Logs from the submenu to view the VPN Logs. You can refresh the log display to view the most recent entries, or clear the log display to delete all the log entries.

Figure 6-14

DHCP Log

You can view the DHCP log from the LAN Setup screen. Select Network Configuration from the main menu and Lan Setup from the submenu. When the LAN Setup screen displays, click the

DHCP Log link.

6-26 v1.0, March 2009

Router and Network Management

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 6-15

Performing Diagnostics

You can perform diagnostics such as pinging an IP address, performing a DNS lookup, displaying the routing table, rebooting the firewall, and capturing packets. Select Monitoring from the main menu and Diagnostics from the submenu. The Diagnostics screen will display.

Note: For normal operation, diagnostics are not required.

Router and Network Management v1.0, March 2009

6-27

FVS338 ProSafe VPN Firewall 50 Reference Manual

Figure 6-16

Table 6-5. Diagnostics Fields

Item Description

Ping or Trace an IP address

Ping – Used to send a ping packet request to a specified IP address—most often, to test a connection. If the request times out (no reply is received), it usually means that the destination is unreachable. However, some network devices can be configured not to respond to a ping. The ping results will be displayed in a new screen; click “Back” on the Windows menu bar to return to the Diagnostics screen.

Traceroute (often called Trace Route) – Lists all Routers between the source (this device) and the destination IP address. The Trace Route results will be displayed in a new screen; click “Back” on the Windows menu bar to return to the Diagnostics screen.

Perform a DNS Lookup A DNS (Domain Name Server) converts the Internet name (e.g. www.netgear.com) to an IP address. If you need the IP address of a Web, FTP, Mail or other Server on the Internet, you can do a DNS lookup to find the IP address.

Display the Routing

Table

This operation will display the internal routing table. This information is used, most often, by Technical Support.

6-28 Router and Network Management v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table 6-5. Diagnostics Fields

Item

Reboot the Router

Packet Trace

Description

Used to perform a remote reboot (restart). You can use this if the Router seems to have become unstable or is not operating normally.

Note : Rebooting will break any existing connections either to the Router (such as this one) or through the Router (for example, LAN users accessing the Internet).

However, connections to the Internet will automatically be re-established when possible.

Packet Trace selects the interface and starts the packet capture on that interface.

Router and Network Management v1.0, March 2009

6-29

FVS338 ProSafe VPN Firewall 50 Reference Manual

6-30 v1.0, March 2009

Router and Network Management

Chapter 7 Troubleshooting

This chapter provides troubleshooting tips and information for your ProSafe VPN Firewall 50.

This chapter includes the following sections:

• “Basic Functions” on page 7-1

• “Troubleshooting the Web Configuration Interface” on page 7-2

• “Troubleshooting the ISP Connection” on page 7-4

• “Troubleshooting a TCP/IP Network Using a Ping Utility” on page 7-5

• “Restoring the Default Configuration and Password” on page 7-7

• “Problems with Date and Time” on page 7-7

Basic Functions

After you turn on power to the firewall, the following sequence of events should occur:

1. When power is first applied, verify that the PWR LED is on.

2. After approximately 10 seconds, verify that: a.

The TEST LED is not lit.

b. The LAN port LEDs are lit for any local ports that are connected.

The Internet port LED is lit.

If a port’s LED is lit, a link has been established to the connected device. If a LAN port is connected to a 100 Mbps device, verify that the port’s LED is green. If the port is 10 Mbps, the

LED will be amber.

If any of these conditions does not occur, refer to the appropriate following section.

Power LED Not On

If the Power and other LEDs are off when your firewall is turned on:

• Make sure that the power cord is properly connected to your firewall and that the power supply adapter is properly connected to a functioning power outlet.

Troubleshooting 7-1 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

• Check that you are using the 12 V DC power adapter supplied by NETGEAR for this product.

If the error persists, you have a hardware problem and should contact technical support.

LEDs Never Turn Off

When the firewall is turned on, the LEDs turns on for about 10 seconds and then turn off. If all the

LEDs stay on, there is a fault within the firewall.

If all LEDs are still on one minute after power up:

• Cycle the power to see if the firewall recovers.

• Clear the firewall’s configuration to factory defaults. This will set the firewall’s IP address to

192.168.1.1. This procedure is explained in “Restoring the Default Configuration and

Password” on page 7-7 .

If the error persists, you might have a hardware problem and should contact technical support.

LAN or Internet Port LEDs Not On

If either the LAN LEDs or Internet LED do not light when the Ethernet connection is made, check the following:

• Make sure that the Ethernet cable connections are secure at the firewall and at the hub or workstation.

• Make sure that power is turned on to the connected hub or workstation.

• Be sure you are using the correct cable:

When connecting the firewall’s Internet port to a cable or DSL modem, use the cable that was supplied with the cable or DSL modem. This cable could be a standard straight-through

Ethernet cable or an Ethernet crossover cable.

Troubleshooting the Web Configuration Interface

If you are unable to access the firewall’s Web Configuration interface from a PC on your local network, check the following:

• Check the Ethernet connection between the PC and the firewall as described in the previous section.

7-2 Troubleshooting v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

• Make sure your PC’s IP address is on the same subnet as the firewall. If you are using the recommended addressing scheme, your PC’s address should be in the range of 192.168.0.2 to

192.168.0.254.

Note: If your PC’s IP address is shown as 169.254.x.x: Recent versions of Windows and MacOS will generate and assign an IP address if the computer cannot reach a DHCP server. These auto-generated addresses are in the range of

169.254.x.x. If your IP address is in this range, check the connection from the

PC to the firewall and reboot your PC.

• If your firewall’s IP address has been changed and you don’t know the current IP address, clear the firewall’s configuration to factory defaults. This will set the firewall’s IP address to

192.168.1.1. This procedure is explained in “Restoring the Default Configuration and

Password” on page 7-7 .

Tip: If you don’t want to revert to the factory default settings and lose your configuration settings, you can reboot the router and use sniffer to capture packets sent during the reboot. Look at the ARP packets to locate the router’s

LAN interface address.

• Make sure your browser has Java, JavaScript, or ActiveX enabled. If you are using Internet

Explorer, click Refresh to be sure the Java applet is loaded.

• Try quitting the browser and launching it again.

• Make sure you are using the correct login information. The factory default login name is admin and the password is password . Make sure that CAPS LOCK is off when entering this information.

If the firewall does not save changes you have made in the Web Configuration Interface, check the following:

• When entering configuration settings, be sure to click the APPLY button before moving to another menu or tab, or your changes are lost.

• Click the Refresh or Reload button in the Web browser. The changes may have occurred, but the Web browser may be caching the old configuration.

Troubleshooting 7-3 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Troubleshooting the ISP Connection

If your firewall is unable to access the Internet, you should first determine whether the firewall is able to obtain a WAN IP address from the ISP. Unless you have been assigned a static IP address, your firewall must request an IP address from the ISP. You can determine whether the request was successful using the Web Configuration Manager.

To check the WAN IP address:

1. Launch your browser and select an external site such as www.netgear.com

2. Access the Main Menu of the firewall’s configuration at http://192.168.1.1

3. Under the Monitoring menu, select Router Status

4. Check that an IP address is shown for the WAN Port

If 0.0.0.0 is shown, your firewall has not obtained an IP address from your ISP.

If your firewall is unable to obtain an IP address from the ISP, you may need to force your cable or

DSL modem to recognize your new firewall by performing the following procedure:

1. Turn off power to the cable or DSL modem.

2. Turn off power to your firewall.

3. Wait five minutes and reapply power to the cable or DSL modem.

4. When the modem’s LEDs indicate that it has reacquired sync with the ISP, reapply power to your firewall.

If your firewall is still unable to obtain an IP address from the ISP, the problem may be one of the following:

• Your ISP may require a login program.

Ask your ISP whether they require PPP over Ethernet (PPPoE) or some other type of login.

• If your ISP requires a login, you may have incorrectly set the login name and password.

• Your ISP may check for your PC's host name.

Assign the PC Host Name of your ISP account as the Account Name in the Basic Settings menu.

• Your ISP only allows one Ethernet MAC address to connect to the Internet, and may check for your PC’s MAC address. In this case:

– Inform your ISP that you have bought a new network device, and ask them to use the firewall’s MAC address; or

7-4 Troubleshooting v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

– Configure your firewall to spoof your PC’s MAC address. This can be done in the Basic

Settings menu. Refer to “Configuring your Internet Connection” on page 2-2 .

If your firewall can obtain an IP address, but your PC is unable to load any Web pages from the

Internet:

• Your PC may not recognize any DNS server addresses.

A DNS server is a host on the Internet that translates Internet names (such as www addresses) to numeric IP addresses. Typically your ISP will provide the addresses of one or two DNS servers for your use. You may configure your PC manually with DNS addresses, as explained in your operating system documentation .

• Your PC may not have the firewall configured as its TCP/IP gateway.

Troubleshooting a TCP/IP Network Using a Ping Utility

Most TCP/IP terminal devices and firewalls contain a ping utility that sends an echo request packet to the designated device. The device then responds with an echo reply. Troubleshooting a TCP/IP network is made very easy by using the Ping utility in your PC or workstation.

Testing the LAN Path to Your Firewall

You can ping the firewall from your PC to verify that the LAN path to your firewall is set up correctly.

To ping the firewall from a PC running Windows 95 or later:

1. From the Windows toolbar, click on the Start button and select Run.

2. In the field provided, type Ping followed by the IP address of the firewall, as in this example: ping 192.168.1.1

3. Click on OK.

You should see a message like this one:

Pinging <IP address> with 32 bytes of data

If the path is working, you see this message:

Reply from < IP address >: bytes=32 time=NN ms TTL=xxx

If the path is not working, you see this message:

Request timed out

Troubleshooting 7-5 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

If the path is not functioning correctly, you could have one of the following problems:

• Wrong physical connections

– Make sure the LAN port LED is on. If the LED is off, follow the instructions in “LAN or Internet Port LEDs Not On ” on page 7-2 .

– Check that the corresponding Link LEDs are on for your network interface card and for the hub ports (if any) that are connected to your workstation and firewall.

• Wrong network configuration

– Verify that the Ethernet card driver software and TCP/IP software are both installed and configured on your PC or workstation.

– Verify that the IP address for your firewall and your workstation are correct and that the addresses are on the same subnet.

Testing the Path from Your PC to a Remote Device

After verifying that the LAN path works correctly, test the path from your PC to a remote device.

From the Windows run menu, type:

PING -n 10 < IP address > where < IP address > is the IP address of a remote device such as your ISP’s DNS server.

If the path is functioning correctly, replies as in the previous section are displayed. If you do not receive replies:

• Check that your PC has the IP address of your firewall listed as the default gateway. If the IP configuration of your PC is assigned by DHCP, this information will not be visible in your

PC’s Network Control Panel.

• Check to see that the network address of your PC (the portion of the IP address specified by the netmask) is different from the network address of the remote device.

• Check that your cable or DSL modem is connected and functioning.

• If your ISP assigned a host name to your PC, enter that host name as the Account Name in the

Basic Settings menu.

• Your ISP could be rejecting the Ethernet MAC addresses of all but one of your PCs. Many broadband ISPs restrict access by only allowing traffic from the MAC address of your broadband modem, but some ISPs additionally restrict access to the MAC address of a single

PC connected to that modem. If this is the case, you must configure your firewall to “clone” or

“spoof” the MAC address from the authorized PC. Refer to “Manually Configuring Your

Internet Connection” on page 2-8 .

7-6 Troubleshooting v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Restoring the Default Configuration and Password

This section explains how to restore the factory default configuration settings, changing the firewall’s administration password to password and the IP address to 192.168.1.1. You can erase the current configuration and restore factory defaults in two ways:

• Use the Erase function of the firewall (see “Backup and Restore Settings” on page 6-15 ).

• Use the reset button on the rear panel of the firewall. Use this method for cases when the administration password or IP address is not known.

To restore the factory default configuration settings without knowing the administration password or IP address, you must use the reset button on the rear panel of the firewall.

1. Press and hold the reset button until the Test LED turns on and begins to blink (about 10 seconds).

2. Release the reset button and wait for the firewall to reboot.

Problems with Date and Time

The E-Mail menu in the Time Zone section displays the current date and time of day. The VPN firewall uses the Network Time Protocol (NTP) to obtain the current time from one of several

Network Time Servers on the Internet. Each entry in the log is stamped with the date and time of day. Problems with the date and time function can include:

• Date and time shown is Thu Jan 01 00:01:52 GMT 1970. Cause: The firewall has not yet successfully reached a Network Time Server. Check that your Internet access settings are configured correctly. If you have just completed configuring the firewall, wait at least five minutes and check the date and time again.

• Time is off by one hour. Cause: The firewall does not automatically sense Daylight Savings

Time. In the E-Mail menu, check or uncheck the box marked “Adjust for Daylight Savings

Time”.

Troubleshooting v1.0, March 2009

7-7

FVS338 ProSafe VPN Firewall 50 Reference Manual

7-8 v1.0, March 2009

Troubleshooting

Appendix A

Default Settings and Technical Specifications

You can use the reset button located on the front of your device to reset all settings to their factory defaults. This is called a hard reset.

• To perform a hard reset, push and hold the reset button for approximately 5 seconds (until the

TEST LED blinks rapidly). Your device will return to the factory configuration settings shown in Table A-1 below.

• Pressing the reset button for a shorter period of time will simply cause your device to reboot.

Table A-1. FVS338 Default Settings

Feature

Router Login

User Login URL

User Name (case sensitive)

Internet Connection

WAN MAC Address

WAN MTU Size

Port Speed

Local Network (LAN)

Lan IP

Subnet Mask

RIP Direction

RIP Version

RIP Authentication

DHCP Server

DHCP Starting IP Address

DHCP Ending IP Address

Default Behavior http://192.168.1.1

admin password

Use Default address

1500

AutoSense

192.168.1.1

255.255.255.0

None

Disabled

Enabled

192.168.1.2

192.168.1.100

Default Settings and Technical Specifications v1.0, March 2009

A-1

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table A-1. FVS338 Default Settings (continued)

Feature Default Behavior

Time Zone

Time Zone Adjusted for Daylight Saving

Time

SNMP

Remote Management

GMT

Disabled

Firewall

Inbound (communications coming in from the Internet)

Disabled (except traffic on port 80, the http port)

Outbound (communications going out to the Internet)

Enabled (all)

Source MAC filtering

Stealth Mode

Disabled

Enabled

Technical Specifications for the ProSafe VPN Firewall 50 are listed in the following table.

Table A-2. VPN firewall Default Technical Specifications

Feature Specification

Network Protocol and Standards Compatibility

Data and Routing Protocols TCP/IP, RIP-1, RIP-2, DHCP

PPP over Ethernet (PPPoE

Power Adapter

North America:

United Kingdom, Australia:

Europe:

Japan:

Physical Specifications

Dimensions:

Weight:

120V, 60 Hz, input

240V, 50 Hz, input

230V, 50 Hz, input

100V, 50/60 Hz, input

1.1 x 6.89 x 4.65 in.

0.3 kg (0.66 lb)

A-2 Default Settings and Technical Specifications v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table A-2. VPN firewall Default Technical Specifications

Specification Feature

Environmental Specifications

Operating temperature:

Operating humidity:

Electromagnetic Emissions

Meets requirements of:



to 40



C (32º to 104º F)

90% maximum relative humidity, noncondensing

FCC Part 15 Class B

VCCI Class B

EN 55 022 (CISPR 22), Class B

Interface Specifications

LAN:

WAN:

10BASE-T or 100BASE-Tx, RJ-45

10BASE-T or 100BASE-Tx, and 9-pin DIN Serial

Default Settings and Technical Specifications v1.0, March 2009

A-3

FVS338 ProSafe VPN Firewall 50 Reference Manual

A-4 Default Settings and Technical Specifications v1.0, March 2009

Appendix B

System Logs and Error Messages

This appendix uses the following log parameter terms.

Table B-1. Log Parameter Terms

Term

[FVS338]

[kernel]

CODE

DEST

DPT

OUT

PROTO

SELF

SPT

SRC

TYPE

Description

System identifier

Message from the kernel.

Protocol code (e.g., protocol is ICMP, type 8) and CODE=0 means successful reply.

Destination IP Address of the machine to which the packet is destined.

Destination port.

Incoming interface for packet.

Outgoing interface for packet.

Protocol used.

Packet coming from the system only.

Source port

Source IP Address of machine from where the packet is coming.

Protocol type

System Log Messages

This section describes log messages that belong to one of the following categories:

• Logs generated by traffic that is meant for the device.

• Logs generated by traffic that is routed or forwarded through the device.

• Logs generated by system daemons NTP, WAN daemon and others.

System Startup

This section describes log messages generated during system startup.

System Logs and Error Messages v1.0, March 2009

B-1

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table B-2. System Logs: System Startup

Message

Explanation

Recommended Action

Jan 1 15:22:28 [FVS338] [ledTog] [SYSTEM START-UP] System Started

Log generated when the system is started.

None

Reboot

This section describes log messages generated during system reboot.

Table B-3. System Logs: Reboot

Message

Explanation

Recommended Action

Nov 25 19:42:57 [FVS338] [reboot] Rebooting in 3 seconds

Log generated when the system is rebooted from the web management.

None

NTP

This section describes log messages generated by the NTP daemon during synchronization with the NTP server.

• The fixed time and date before NTP synchronizes with any of the servers is:

Thu Jan 01 00:01:52 GMT 1970.

• The resynchronization interval is governed by the specification defined in:

DOC-00045_Ntp_Spec.pdf.

B-2 v1.0, March 2009

System Logs and Error Messages

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table B-4. System Logs: NTP

Message

Explanation

Recommended Action

Nov 28 12:31:13 [FVS338] [ntpdate] Looking Up time-f.netgear.com

Nov 28 12:31:13 [FVS338] [ntpdate] Requesting time from time-f.netgear.com

Nov 28 12:31:14 [FVS338] [ntpdate] adjust time server 69.25.106.19 offset

0.140254 sec

Nov 28 12:31:14 [FVS338] [ntpdate] Synchronized time with time-f.netgear.com

Nov 28 12:31:16 [FVS338] [ntpdate] Date and Time Before Synchronization:

Tue Nov 28 12:31:13 GMT+0530 2006

Nov 28 12:31:16 [FVS338] [ntpdate] Date and Time After Synchronization: Tue

Nov 28 12:31:16 GMT+0530 2006

Nov 28 12:31:16 [FVS338] [ntpdate] Next Synchronization after 2 Hours

Message1: DNS resolution for the NTP server (time-f.netgear.com)

Message2: request for NTP update from the time server.

Message3: Adjust time by re-setting system time.

Message4: Display date and time before synchronization, that is when resynchronization started

Message5: Display the new updated date and time.

Message6: Next synchronization will be after the specified time mentioned.

Example: In the above logs the next synchronization will be after two hours.

The synchronization time interval is configurable via the CLI

None

Login/Logout

This section describes logs generated by the administrative interfaces of the device.

Table B-5. System Logs: Login/Logout

Message

Explanation

Recommended Action

Message

Explanation

Recommended Action

Nov 28 14:45:42 [FVS338] [login] Login succeeded: user admin from

192.168.10.10

None

Nov 28 14:55:09 [FVS338] [seclogin] Logout succeeded for user admin

Nov 28 14:55:13 [FVS338] [seclogin] Login succeeded: user admin from

192.168.1.214

Secure login/logout of user admin from host with IP address 192.168.1.214.

None

Firewall Restart

This logging is always done.

System Logs and Error Messages B-3 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table B-6. System Logs: Firewall Restart

Message

Explanation

Recommended Action

Jan 23 16:20:44 [FVS338] [wand] [FW] Firewall Restarted

Log generated when the firewall is restarted.

This log is logged when firewall restarts after applying any changes in the configuration.

None

IPSec Restart

This logging is always done.

Table B-7. System Logs: IPSec Restart

Message

Explanation

Recommended Action

Jan 23 16:20:44 [FVS338] [wand] [IPSEC] IPSEC Restarted

Log generated when the IPSEC is restarted.

This log is logged when IPSEC restarts after applying any changes in the configuration.

None

WAN Status

This section describes the logs generated by the WAN component.

If there are two ISP links for Internet connectivity, the router can be configured in Auto Rollover

Mode.

Auto Rollover

When WAN mode is configured to Auto Rollover, primary link is active and secondary acts as a backup. When primary link goes down, secondary becomes active until primary comes up. The device monitors the status of the primary link by the configured WAN Failure Detection method.

This section describes the logs generated when the WAN mode is set to auto rollover.

B-4 v1.0, March 2009

System Logs and Error Messages

FVS338 ProSafe VPN Firewall 50 Reference Manual

System Logs: WAN Status, Auto Rollover

Message

Explanation

Recommended Action

Nov 17 09:59:09 [FVS338] [wand] [LBFO] WAN1 Test Failed 1 of 3 times_

Nov 17 09:59:39 [FVS338] [wand] [LBFO] WAN1 Test Failed 2 of 3 times_

Nov 17 10:00:09 [FVS338] [wand] [LBFO] WAN1 Test Failed 3 of 3 times_

Nov 17 10:01:01 [FVS338] [wand] [LBFO] WAN1 Test Failed 4 of 3 times_

Nov 17 10:01:35 [FVS338] [wand] [LBFO] WAN1 Test Failed 5 of 3 times_

Nov 17 10:01:35 [FVS338] [wand] [LBFO] WAN1(DOWN), WAN2(UP),

ACTIVE(WAN2)_

Nov 17 10:02:25 [FVS338] [wand] [LBFO] WAN1 Test Failed 6 of 3 times_

Nov 17 10:02:25 [FVS338] [wand] [LBFO] Restarting WAN1_

Nov 17 10:02:57 [FVS338] [wand] [LBFO] WAN1 Test Failed 7 of 3 times_

Nov 17 10:03:27 [FVS338] [wand] [LBFO] WAN1 Test Failed 8 of 3 times_

Nov 17 10:03:57 [FVS338] [wand] [LBFO] WAN1 Test Failed 9 of 3 times_

Nov 17 10:03:57 [FVS338] [wand] [LBFO] Restarting WAN1_

The Logs suggest that the fail-over was detected after 5 attempts instead of 3.

However, the reason the messages appear as above is because of the WAN state transition logic which is part of the failover algorithm. The above logs can be interpreted as below. The primary link failure is properly detected after the

3rd attempt. Thereafter the algorithm attempts to restart WAN and checks once again to see if WAN1 is still down. This results in the 4th failure detection message. If it is then it starts secondary link and once secondary link is up, secondary link is marked as active. Meanwhile secondary link has failed once more and that results 5th failure detection message. Please note that the 5th failure detection and the message suggesting secondary link is active have the same timestamp and so they happen in the same algorithm state-machine cycle. So although it appears that the failover did not happen immediately after

3 failures, internally, the failover process is triggered after the 3rd failure and transition to secondary link is completed by the 5th failure. The primary link is also restarted every 3 failures till it is functional again. In the above log, primary link was restarted after the 6th failure i.e. 3 failures after the failover process was triggered.

Check the WAN settings and WAN failure detection method configured for the primary link.

PPP Logs

This section describes the WAN PPP connection logs. The PPP type can be configured from the web management.

System Logs and Error Messages v1.0, March 2009

B-5

FVS338 ProSafe VPN Firewall 50 Reference Manual

PPPoE Idle-Timeout Logs.

Table B-8. System Logs: WAN Status, PPE, PPPoE Idle-Timeout

Message

Explanation

Recommended Action

Nov 29 13:12:46 [FVS338] [pppd] Starting connection

Nov 29 13:12:49 [FVS338] [pppd] Remote message: Success

Nov 29 13:12:49 [FVS338] [pppd] PAP authentication succeeded

Nov 29 13:12:49 [FVS338] [pppd] local IP address 50.0.0.62

Nov 29 13:12:49 [FVS338] [pppd] remote IP address 50.0.0.1

Nov 29 13:12:49 [FVS338] [pppd] primary DNS address 202.153.32.3

Nov 29 13:12:49 [FVS338] [pppd] secondary DNS address 202.153.32.3

Nov 29 11:29:26 [FVS338] [pppd] Terminating connection due to lack of activity.

Nov 29 11:29:28 [FVS338] [pppd] Connect time 8.2 minutes.

Nov 29 11:29:28 [FVS338] [pppd] Sent 1408 bytes, received 0 bytes.

Nov 29 11:29:29 [FVS338] [pppd] Connection terminated.

Message 1: PPPoE connection establishment started.

Message 2: Message from PPPoE server for correct login

Message 3: Authentication for PPP succeeded.

Message 4: Local IP address assigned by the server.

Message 5: Server side IP address.

Message 6: primary DNS configured in WAN status page.

Message 7: secondary DNS configured in WAN status page.

Message 8: The PPP link has transitioned to idle mode. This event occurs if there is no traffic from the LAN network.

Message 9: The time in minutes for which the link has been up.

Message 10: Data sent and received at the LAN side during the link was up.

Message 11: PPP connection terminated after idle timeout

To reconnect during idle mode, initiate traffic from the LAN side.

B-6 v1.0, March 2009

System Logs and Error Messages

FVS338 ProSafe VPN Firewall 50 Reference Manual

PPTP Idle-Timeout Logs.

Table B-9. System Logs: WAN Status, PPE, PPTP Idle-Timeout

Message

Explanation

Recommended Action

Nov 29 11:19:02 [FVS338] [pppd] Starting connection

Nov 29 11:19:05 [FVS338] [pppd] CHAP authentication succeeded

Nov 29 11:19:05 [FVS338] [pppd] local IP address 192.168.200.214

Nov 29 11:19:05 [FVS338] [pppd] remote IP address 192.168.200.1

Nov 29 11:19:05 [FVS338] [pppd] primary DNS address 202.153.32.2

Nov 29 11:19:05 [FVS338] [pppd] secondary DNS address 202.153.32.2

Nov 29 11:20:45 [FVS338] [pppd] No response to 10 echo-requests

Nov 29 11:20:45 [FVS338] [pppd] Serial link appears to be disconnected.

Nov 29 11:20:45 [FVS338] [pppd] Connect time 1.7 minutes.

Nov 29 11:20:45 [FVS338] [pppd] Sent 520 bytes, received 80 bytes.

Nov 29 11:20:51 [FVS338] [pppd] Connection terminated.

Message 1: Starting PPP connection process

Message 2: Message from server for authentication success

Message 3: Local IP address assigned by the server.

Message 4: Server side IP address.

Message 5: primary DNS configured in WAN status page.

Message 6: secondary DNS configured in WAN status page.

Message 7: Sensing idle link

Message 8: Idle link sensed

Message 9: Data sent and received at the LAN side during the link was up.

Message 10: PPP connection terminated after idle timeout

To reconnect during idle mode, initiate traffic from the LAN side.

PPP Authentication Logs.

Table B-10. System Logs: WAN Status, PPE, PPP Authentication

Message

Explanation

Recommended Action

Nov 29 11:29:26 [FVS338] [pppd] Starting link

Nov 29 11:29:29 [FVS338] [pppd] Remote message: Login incorrect

Nov 29 11:29:29 [FVS338] [pppd] PAP authentication failed

Nov 29 11:29:29 [FVS338] [pppd] Connection terminated.WAN2(DOWN)_

Starting link: Starting PPPoE connection process

Remote message: Login incorrect: Message from PPPoE server for incorrect login

PAP authentication failed: PPP authentication failed due to incorrect login

Connection terminated: PPP connection terminated

If authentication fails, then check the login/password and enter the correct one.

Web Filtering and Content Filtering Logs

To enable web keyword filtering logs, set value of keywordLog to 1 from CLI.

Command to set this value from CLI: monitor/firewallLogs/logger/loggerConfig keywordLog 1

System Logs and Error Messages B-7 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table B-11. System Logs: Web Filtering and Content Filtering

Message

Explanation

Recommended Action

Message

Explanation

Recommended Action

Message

Explanation

Recommended Action

Message

Explanation

Recommended Action

Jan 23 16:36:35 [FVS338] [kernel] [KEYWORD_BLOCKED] [URL]==>[ www.redhat.com/ ] IN=SELF OUT=SELF SRC=192.168.10.210

DST=209.132.177.50 PROTO=TCP SPT=4282 DPT=80

• This packet is blocked by keyword blocking

• The URL blocked due to keyword blocking is shown by [URL] along with source and destination IP addressed, protocol, source port and destination port.

• For other parameters, refer to Table B-1 .

None

Jan 23 16:53:32 [FVS338] [kernel] [JAVA_BLOCKED] [URL]==>[ www.java.com/js/css.js ] IN=SELF OUT=SELF SRC=192.168.10.210

DST=72.5.124.95 PROTO=TCP SPT=4294 DPT=80

• This packet is blocked by content filtering with java components

• The URL blocked due to java content filtering is [URL] along with source and destination IP addressed, protocol, source port and destination port.

• For other parameters, refer to Table B-1 .

None

Jan 23 16:56:08 [FVS338] [kernel] [COOKIE_BLOCKED] [URL]==>[ www.java.com/en/img/headline/340x155_sportsforeveryone.jpg ] IN=SELF

OUT=SELF SRC=192.168.10.210 DST=72.5.124.95 PROTO=TCP SPT=4321

DPT=80

• This packet is blocked by content filtering for cookies

• The URL blocked due to cookie filtering shown by [URL] along with source and destination IP addressed, protocol, source port and destination port.

• For other parameters, refer to Table B-1 .

None

Jan 23 16:53:32 [FVS338] [kernel] [JAVA_BLOCKED] [URL]==>[ www.java.com/js/css.js ] IN=SELF OUT=SELF SRC=192.168.10.210

DST=72.5.124.95 PROTO=TCP SPT=4294 DPT=80

• This packet is blocked by content filtering with java components

• The URL blocked due to java content filtering is [URL] along with source and destination IP addressed, protocol, source port and destination port.

• For other parameters, refer to Table B-1 .

None

B-8 v1.0, March 2009

System Logs and Error Messages

FVS338 ProSafe VPN Firewall 50 Reference Manual

Traffic Metering Logs

Table B-12. System Logs: Traffic Metering

Message

Explanation

Recommended Action

Jan 23 19:03:44 [TRAFFIC_METER] TRAFFIC_METER: Monthly Limit of 10

MB has reached for WAN1._

Traffic limit to WAN1 that was set as 10Mb has been reached.

This stops all the incoming and outgoing traffic if configured like that in “When

Limit is reached” on Traffic Meter web page.

To start the traffic, restart the Traffic Limit Counter.

Unicast Logs

Table B-13. System Logs: Unicast

Message

Explanation

Recommended Action

Nov 24 11:52:55 [FVS338] [kernel] UCAST IN=SELF OUT=WAN SRC=192.168.10.1

DST=192.168.10.10 PROTO=UDP SPT=800 DPT=2049

• This packet (Unicast) is destined to the device from the WAN network.

• For other parameters, refer to Table B-1 .

None

ICMP Redirect Logs

Table B-14. System Logs: Unicast, Redirect

Message

Explanation

Recommended Action

Feb 2007 22 14:36:07 [FVS338] [kernel] [LOG_PACKET] SRC=192.168.1.49

DST=192.168.1.124 PROTO=ICMP TYPE=5 CODE=1

• This packet is ICMP Redirect message sent to the router bye another router.

• For other parameters, refer to Table B-1 .

To enable these logs, from CLI command prompt of the router, enter this command: monitor/firewallLogs/logger/loggerConfig logIcmpRedirect 1

And to disable it, monitor/firewallLogs/logger/loggerConfig logIcmpRedirect 0

System Logs and Error Messages v1.0, March 2009

B-9

FVS338 ProSafe VPN Firewall 50 Reference Manual

Multicast/Broadcast Logs

Table B-15. System Logs: Multicast/Broadcast

Message

Explanation

Recommended Action

Jan 1 07:24:13 [FVS338] [kernel] MCAST-BCAST IN=WAN OUT=SELF

SRC=192.168.1.73 DST=192.168.1.255 PROTO=UDP SPT=138 DPT=138

• This packet (Broadcast) is destined to the device from the WAN network.

• For other parameters, refer to Table B-1 .

None

FTP Logging

Table B-16. System Logs: FTP

Message

Explanation

Recommended Action

Feb 2007 22 14:46:56 [FVS338] [kernel] [FTP-ACTIVE] SRC=192.168.10.211

DST=192.168.1.97 PROTO=TCP SPT=1983 DPT=21

Feb 2007 22 14:46:56 [FVS338] [kernel] [FTP-PASSIVE] SRC=192.168.10.211

DST=192.168.1.97 PROTO=TCP SPT=1984 DPT=21

Feb 2007 22 19:48:17 [FVS338] [kernel] [FTP-DATA][ACCEPT]

SRC=192.168.10.10 DST=192.168.20.10 PROTO=TCP SPT=54879

DPT=6459

• These packets are active and passive FTP session data transfers respectively.

• For other parameters, refer to Table B-1 .

To enable these logs, from CLI command prompt of the router, enter this command: monitor/firewallLogs/logger/loggerConfig logFtp 1

And to disable it, monitor/firewallLogs/logger/loggerConfig logFtp 0

Invalid Packet Logging

Table B-17. System Logs: Invalid Packets

Message

Explanation

2007 Oct 1 00:44:17 [FVS338] [kernel] [INVALID]

[NO_CONNTRACK_ENTRY] [DROP] SRC=192.168.20.10

DST=192.168.20.2 PROTO=TCP SPT=23 DPT=54899

No Connecrtion Tracking entry exists

B-10 v1.0, March 2009

System Logs and Error Messages

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table B-17. System Logs: Invalid Packets (continued)

Recommended Action

Message

Explanation

Recommended Action

Message

Explanation

Recommended Action

Message

Explanation

Recommended Action

Message

Explanation

1. Invalid packets are dropped.

2. Use this command to enable dropping and logging of the invalid packets: fw/rules/attackChecks/configure dropInvalid 1

To allow invalid packet and disable logging: fw/rules/attackChecks/configure dropInvalid 0

2007 Oct 1 00:44:17 [FVS338] [kernel]

[INVALID][RST_PACKET][DROP] SRC=192.168.20.10

DST=192.168.20.2 PROTO=TCP SPT=23 DPT=54899

Invalid RST packet

1. Invalid packets are dropped.

2. Use this command to enable dropping and logging of the invalid packets: fw/rules/attackChecks/configure dropInvalid 1

To allow invalid packet and disable logging: fw/rules/attackChecks/configure dropInvalid 0

2007 Oct 1 00:44:17 [FVS338] [kernel]

[INVALID][ICMP_TYPE][DROP] SRC=192.168.20.10

DST=192.168.20.2 PROTO=ICMP TYPE=19 CODE=0

Invalid ICMP Type

1. Invalid packets are dropped.

2. Use this command to enable dropping and logging of the invalid packets: fw/rules/attackChecks/configure dropInvalid 1

To allow invalid packet and disable logging: fw/rules/attackChecks/configure dropInvalid 0

2007 Oct 1 00:44:17 [FVS338] [kernel]

[INVALID][TCP_FLAG_COMBINATION][DROP] SRC=192.168.20.10

DST=192.168.20.2 PROTO=TCP SPT=23 DPT=54899

Invalid TCP flag combination

1. Invalid packets are dropped.

2. Use this command to enable dropping and logging of the invalid packets: fw/rules/attackChecks/configure dropInvalid 1

To allow invalid packet and disable logging: fw/rules/attackChecks/configure dropInvalid 0

2007 Oct 1 00:44:17 [FVS338] [kernel]

[INVALID][BAD_CHECKSUM]DROP] SRC=192.168.20.10

DST=192.168.20.2 PROTO=TCP SPT=23 DPT=54899

Bad Checksum

System Logs and Error Messages v1.0, March 2009

B-11

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table B-17. System Logs: Invalid Packets (continued)

Recommended Action

Message

Explanation

Recommended Action

Message

Explanation

Recommended Action

Message

Explanation

Recommended Action

Message

Explanation

Recommended Action

1. Invalid packets are dropped.

2. Use this command to enable dropping and logging of the invalid packets: fw/rules/attackChecks/configure dropInvalid 1

To allow invalid packet and disable logging: fw/rules/attackChecks/configure dropInvalid 0

2007 Oct 1 00:44:17 [FVS338] [kernel]

[INVALID][BAD_HW_CHECKSUM][DROP] SRC=192.168.20.10

DST=192.168.20.2 PROTO=ICMP TYPE=3 CODE=0

Bad Hardware Checksum for ICMP packets

1. Invalid packets are dropped.

2. Use this command to enable dropping and logging of the invalid packets: fw/rules/attackChecks/configure dropInvalid 1

To allow invalid packet and disable logging: fw/rules/attackChecks/configure dropInvalid 0

[INVALID][MALFORMED_PACKET][DROP] SRC=192.168.20.10

DST=192.168.20.2 PROTO=TCP SPT=23 DPT=54899

Malformed packet

1. Invalid packets are dropped.

2. Use this command to enable dropping and logging of the invalid packets: fw/rules/attackChecks/configure dropInvalid 1

To allow invalid packet and disable logging: fw/rules/attackChecks/configure dropInvalid 0

2007 Oct 1 00:44:17 [FVS338] [kernel]

[INVALID][SHORT_PACKET][DROP] SRC=192.168.20.10

DST=192.168.20.2 PROTO=TCP SPT=23 DPT=54899

Short packet

1. Invalid packets are dropped.

2. Use this command to enable dropping and logging of the invalid packets: fw/rules/attackChecks/configure dropInvalid 1

To allow invalid packet and disable logging: fw/rules/attackChecks/configure dropInvalid 0

[INVALID][ INVALID_STATE][DROP] SRC=192.168.20.10

DST=192.168.20.2 PROTO=TCP SPT=23 DPT=54899

Packet with Invalid State

1. Invalid packets are dropped.

2. Use this command to enable dropping and logging of the invalid packets: fw/rules/attackChecks/configure dropInvalid 1

To allow invalid packet and disable logging: fw/rules/attackChecks/configure dropInvalid 0

B-12 System Logs and Error Messages v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Table B-17. System Logs: Invalid Packets (continued)

Message

Explanation

Recommended Action

Message

Explanation

Recommended Action

Message

Explanation

Recommended Action

2007 Oct 1 00:44:17 [FVS338] [kernel]

[INVALID][REOPEN_CLOSE_CONN][DROP] SRC=192.168.20.10

DST=192.168.20.2 PROTO=TCP SPT=23 DPT=54899

Attempt to re-open/close session

1. Invalid packets are dropped.

2. Use this command to enable dropping and logging of the invalid packets: fw/rules/attackChecks/configure dropInvalid 1

To allow invalid packet and disable logging: fw/rules/attackChecks/configure dropInvalid 0

2007 Oct 1 00:44:17 [FVS338] [kernel]

[INVALID][OUT_OF_WINDOW][DROP] SRC=192.168.20.10

DST=192.168.20.2 PROTO=TCP SPT=23 DPT=54899

Packet not in TCP window

1. Invalid packets are dropped.

2. Use this command to enable dropping and logging of the invalid packets: fw/rules/attackChecks/configure dropInvalid 1

To allow invalid packet and disable logging: fw/rules/attackChecks/configure dropInvalid 0

2007 Oct 1 00:44:17 [FVS338] [kernel]

[INVALID][ERR_HELPER_ROUTINE][DROP] SRC=192.168.20.10

DST=192.168.20.2 PROTO=TCP SPT=23 DPT=54899

Error returned from helper routine

1. Invalid packets are dropped.

2. Use this command to enable dropping and logging of the invalid packets: fw/rules/attackChecks/configure dropInvalid 1

To allow invalid packet and disable logging: fw/rules/attackChecks/configure dropInvalid 0

Routing Logs

This section is used to configure the logging options for each network segment like LAN-WAN for debugging purposes. This may generate a significant volume of log messages.

System Logs and Error Messages v1.0, March 2009

B-13

FVS338 ProSafe VPN Firewall 50 Reference Manual

LAN to WAN Logs

Table B-18. Routing Logs: LAN to WAN

Message

Explanation

Recommended Action

Nov 29 09:19:43 [FVS338] [kernel] LAN2WAN[ACCEPT] IN=LAN OUT=WAN

SRC=192.168.10.10 DST=72.14.207.99 PROTO=ICMP TYPE=8 CODE=0

• This packet from LAN to WAN has been allowed by the firewall.

• For other parameters, refer to Table B-1 .

None

WAN to LAN Logs

Table B-19. Routing Logs: WAN to LAN

Message

Explanation

Recommended Action

Nov 29 10:05:15 [FVS338] [kernel] WAN2LAN[ACCEPT] IN=WAN OUT=LAN

SRC=192.168.1.214 DST=192.168.10.10 PROTO=ICMP TYPE=8 CODE=0

• This packet from LAN to WAN has been allowed by the firewall

• For other parameters, refer to Table B-1 .

None

B-14 v1.0, March 2009

System Logs and Error Messages

Appendix C

Appendix D

Two Factor Authentication

This appendix provides an overview of two factor authentication, and an example of how to implement the WiKID solution.

This appendix contains the following sections:

• “Why do I need Two-Factor Authentication?” on page D-1

• “NETGEAR Two-Factor Authentication Solutions” on page D-2

Why do I need Two-Factor Authentication?

In today’s market, online identity theft and online fraud continue to be one of the fast-growing cyber crime activities used by many unethical hackers and cyber criminals to steal digital assets for financial gains. Many companies and corporations are losing millions of dollars and running into risks of revealing their trade secrets and other proprietary information as the results of these cyber crime activities. Security threats and hackers have becoming more sophisticated where user names, encrypted passwords and the presence of firewalls are no longer enough to protect the networks from being compromised. IT professionals and security experts have recognized the need to go beyond the traditional authentication process by introducing and requiring additional factors to the authentication process. NETGEAR has also recognized the need to provide more than just a firewall to protect the networks. As part the new maintenance firmware release,

NETGEAR has implemented a more robust authentication system known as Two-Factor

Authentication (2FA or T-FA) on its SSL and IPSec VPN firewall product line to help address the fast-growing network security issues.

What are the benefits of Two-Factor Authentication?

• Stronger security . Passwords cannot efficiently protect the corporate networks because attackers can easily guess simple passwords or users cannot remember complex and unique passwords. One-time passcode (OTP) strengthens and replaces the need to remember complex password.

• No need to replace existing hardware . Two-Factor Authentication can be added to existing

NETGEAR products through via firmware upgrade.

D-1 v1.3, March 2009

ProSafe Dual WAN Gigabit Firewall with SSL & IPsec VPN FVS336G Reference Manual

• Quick to deploy and manage . The WiKID solution integrates seamlessly with the

NETGEAR SSL and VPN firewall products.

• Proven regulatory compliance . Two-Factor Authentication has been used as a mandatory authentication process for many corporations and enterprises worldwide.

What is Two-Factor Authentication

Two-Factor Authentication is a new security solution that enhances and strengthens security by implementing multiple factors to the authentication process that challenge and confirm the users identities before they can gain access to the network. There are several factors that are used to validate the users to make that you are who you said you are. These factors are:

Something you know – for example, your password or your PIN

Something you have – for example, a token with generated passcode that is either 6 to 8 digits in length.

Something you are – fox example, biometrics such as fingerprints or retinal.

We will only focus and discuss the first two factors – something you know and something you have. This new security method can be viewed as a two-tiered authentication approach because it typically relies on what you know and what you have. A common example of two-factor authentication is a bank (ATM) card that has been issued by a bank institute:

• The PIN to access your account is “ something you know ”

• The ATM card is “ something you have ”

You must have both of these factors to gain access to your bank account. Similar to the ATM card, access to the corporate networks and data can also be strengthen using combination of the multiple factors such as a PIN and a token (hardware or software) to validate the users and reduce the incidence of online identity theft.

NETGEAR Two-Factor Authentication Solutions

NETGEAR has implemented 2 Two-Factor Authentication solutions from WiKID. WiKID is the software-based token solution. So instead of using Windows Active Directory or LDAP as the authentication server, administrators now have the option to use WiKID to do Two-Factor

Authentication on NETGEAR SSL and VPN firewall products.

D-2 Two Factor Authentication v1.3, March 2009

ProSafe Dual WAN Gigabit Firewall with SSL & IPsec VPN FVS336G Reference Manual

The WiKID solution is based on a request-response architecture where a one-time passcode

(OTP), that is time synchronized with the authentication server, is generated and sent to the user once the validity of a user credential has been confirmed by the server. The request-response architecture is capable of self-service initialization by end-users, dramatically reducing implementation and maintenance costs. Here is a quick example of how WiKID work.

The user launches the WiKID token software, enter the PIN that has been given to them

( something they know ) and then press “continue” to receive the one-time passcode (OTP) from the WiKID authentication server:

Figure D-1

Two Factor Authentication v1.3, March 2009

D-3

ProSafe Dual WAN Gigabit Firewall with SSL & IPsec VPN FVS336G Reference Manual

A one-time passcode ( something they have ) is generated for this user.

Figure D-2

Note: The one-time passcode is time synchronized to the authentication server so that the OTP can only be used once and must be used before the expiration time. If a user does not use this passcode before it is expired, the user will need to go through the request process again to generate a new OTP.

D-4 v1.3, March 2009

Two Factor Authentication

ProSafe Dual WAN Gigabit Firewall with SSL & IPsec VPN FVS336G Reference Manual

The user then goes to the two factor login page and enters the generated one-time passcode as the login password.

Figure D-3

Two-Factor Authentication is a new and easy way to enhance networking security products without having to replace the existing hardware. To obtain and try the new Two-Factor

Authentication solution on your products, visit NETGEAR Support website at http://kbserver.netgear.com

Two Factor Authentication v1.3, March 2009

D-5

ProSafe Dual WAN Gigabit Firewall with SSL & IPsec VPN FVS336G Reference Manual

D-6 v1.3, March 2009

Two Factor Authentication

Index

A

Add LAN WAN Inbound Service screen 4-9 , 4-14

Add LAN WAN Outbound Service screen 4-8 address reservation 3-10

VPN Policies, use with 5-17

ARP 3-7

Attack Checks

Block TCP Flood 4-10

Respond To Ping On Internet 4-10

Stealth Mode 4-10

Attack Checks screen 4-10 , 4-11

Attacks Notification 6-20 authentication

WiKID 6-10

Authentication Header. See AH.

Auto Uplink 1-3

Auto VPN Policies 5-16

Auto-Rollover

Dual WAN ports 5-1

B

backup and restore settings configuration of 6-15

Bandwidth Profile screen 4-29

Block Sites 6-3

Content Filtering 4-20 reducing traffic 6-3

Block Sites screen

Content Filtering 4-21

Block TCP Flood

Attack Checks 4-10 block traffic with schedule 4-20

Broadband Status monitoring 6-24

Broadband Traffic Meter screen 6-19

C

VPN gateway, use with 5-16

CA Certificates about 5-32

Certificate Authority. See CA

Certificate Identity file 5-36

Certificate Revocation List. See CRL.

Certificates screen 5-32

Self Certificates 5-33

Certification Authorities. See CA.

common protocols definitions 4-17 configuration automatic by DHCP 1-4 configuration backup 6-15

Content Filtering 1-2 , 4-1

Block Sites 4-20 enabling 4-21

Keyword Blocking 4-21

Web Components 4-20 , 4-21 content filtering

Blocked Sites 4-1

Keyword Blocking 4-1

CRL lists managing 5-36 crossover cable 1-3 , 7-2

Customized Services 4-2 service port numbers 4-17 v1.0, March 2009

Index-1

FVS338 ProSafe VPN Firewall 50 Reference Manual

D

date troubleshooting 7-7

Daylight Savings Time setting 6-18

Dead Peer Detection 5-15 default configuration restoring 7-7 default firewall rules 4-2

Inbound 4-2

Outbound 4-2

Default Outbound Policy

LAN WAN 4-7 denial of service attack 4-10

UDP flood 4-10

Denial of Service. See DoS.

DH use with ModeConfig 5-24

DHCP

DNS server address 3-4

DHCP Address Pool 3-4

DHCP IP Address pool 3-1

DHCP log 6-26 monitoring 6-26

DHCP server about 3-1

Diagnostics

DNS lookup 6-27

Packet Trace 6-29 pinging an IP address 6-27

Reboot the Router 6-29

Diagnostics Fields descriptions of 6-28

Diagnostics screen 6-27

Dialup ISP Status monitoring 6-24

Diffie-Hellman Group use in IKE Policy 5-15

Digital 5-31

Digital Certificates 5-31

Disable DHCP Server 3-1 , 3-3

Index-2

DNS server IP address 3-4

DNS lookup 6-27

DNS Proxy 1-4

Domain Name router 3-3

Domain Name Blocking 6-3 domain name blocking. See Keyword Blocking

DOS protection download firmware steps to 6-16

Dual WAN Port systems

VPN Tunnel addresses 5-2

Dynamic DNS configuration of 2-14

E

Edge Device

XAUTH, use with 5-18

Edit Service screen 4-18

E-mail alerts configuring 4-31 scheduling 4-31

Enable DHCP Server 3-3

Enable DHCP server 3-1

Enable DNS Proxy 3-4

Encapsulating Security Payload. See ESP.

Ending IP Address

DHCP Address Pool 3-4

ESP

VPN Policies, use with 5-17

Ethernet 1-3

Exposed Host 4-15

Extended Authentication. See XAUTH.

F

filtering traffic by MAC address

Source MAC filtering 4-23 firewall v1.0, March 2009

alerts, emailing of 4-30 connecting 2-1 , 2-2 logging in to 2-1 rear panel 1-8 security, about 4-1 status 6-23 technical specifications A-1 firewall access remote management 6-10

Firewall Logs configuring 4-31 emailing of 4-30

Firewall Logs & E-mail screen 4-30 , 6-20 firewall protection 4-1 firewall rules about 4-2 ordering 4-6 firmware upgrade 6-15

G

Generate Self Certificate Request 5-33

Groups managing 3-7 rules, covered by 6-3

Groups and Hosts

About 3-6

I

ICMP Destination Unreachable 4-10

IKE Policies auto, rules of 5-14 field definitions 5-15 manual, rules of 5-14 use with ModeConfig 5-25

IKE/ISAKMP use in IKE Policy 5-15

Inbound Rules 4-2 about 4-4 configuring DHCP 4-4 examples of 4-13

Fields, definition of 4-5 firewall 4-2

FVS338 ProSafe VPN Firewall 50 Reference Manual

Port Forwarding 4-4

Increased Traffic

Port Triggering 6-6

Increased traffic

Port Forwarding 6-4

VPN tunnels 6-6 installation 1-4

Internet configuring the connection manually 2-8 connection configuration 2-2 traffic information 6-26

Internet Protocol Numbers 4-17

IP Address router default 3-3

IP Address Pool use with ModeConfig 5-24

IP addresses auto-generated 7-3

DHCP address pool 3-1 how to assign 3-1 reserved 3-10

IP Subnet Mask router default 3-3

IP/MAC Binding screen 4-24

IPSec

Connection Status Fields, description of 6-25

VPN Tunnel, use with 4-11

IPSec Connection Status screen 5-17 , 6-25

IPSec Host authentication 5-19

XAUTH, use with 5-18 , 5-19

ISP connection troubleshooting 7-4

K

Keep alive 5-17

Keyword Blocking 6-3

Content Filtering 4-21 examples of 4-21

Index-3 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

L

L2TP

VPN Tunnel 4-11

LAN configuration 3-1 ports and attached devices 6-26 using LAN IP setup options 3-2

LAN Security Checks

UDP flood 4-10

LAN Setup screen 3-3

LAN Users

Service Blocking 6-2

LAN WAN Inbound Rules configuring 4-9

LAN WAN Outbound Rules configuring 4-8

LAN WAN Rules about 4-7

LAN WAN Rules screen 4-7

LEDs explanation of 1-6 troubleshooting 7-2

LEDs Never Turn Off 7-2

Local Public Web Server 4-13

Log Entry Descriptions 4-33 , B-1

Login Failures notification of 6-20

Logs screen 4-33

M

MAC address 7-6 spoofing 7-5

Manual VPN Policies creating 5-16

Mode Config screen 5-24

ModeConfig about 5-23 , 5-24 configuration example 5-23 guidelines 5-24

VPN Client configuration, example 5-28 modem 1-2

Index-4 monitoring devices by DHCP Client Requests 3-8 by Scanning the Network 3-8 multicasting guidelines 3-14

N

NAS Identifier use with RADIUS 5-22

NAT 4-1 , 4-4

NetBIOS 3-7

Network 4-1

Network Access Server 5-22

Network Address Translation 1-3

Network Address Translation. See NAT.

Network Database creating 3-7

Network Time Protocol. See NTP.

newsgroup 4-21

NTP servers, configuring 6-17 troubleshooting 7-7

O

One-to-One NAT Mapping 4-14

Outbound Rules 4-2 examples of 4-16

Fields, description of 4-3 firewall 4-2 port filtering 4-2 service blocking 4-2

P

package contents 1-6

Packet Trace 6-29

Passwords restoring 7-7 passwords and login timeout changing 6-7 performance management 6-1 v1.0, March 2009

Ping

Troubleshooting TCP/IP 7-5 pinging an IP address 6-27 port filtering 4-2

Outbound Rules 4-2

Port Forwarding 4-2 , 4-4 , 6-4

Inbound Rules 4-4 port forwarding 6-4 port numbers 4-17 port service numbers common protocols 4-17

Port Triggering 6-6 about 4-26 guidelines 4-26

Status 4-28 status 6-22

Port Triggering screen 4-26 , 6-22

Power LED Not On 7-1

PPP over Ethernet 1-4

PPPoE 1-4

PPTP

VPN Tunnel 4-11 protocols

Routing Information 1-3

Q

QoS 4-2 about 4-19 managing, shifting traffic mix 6-6 service levels 4-19

Quality of Service. See QoS

R

RADIUS

WiKID 6-10

RADIUS Client screen 5-22

RADIUS server configuring 5-21

RADIUS-CHAP

XAUTH, use with 5-19

FVS338 ProSafe VPN Firewall 50 Reference Manual

RADIUS-PAP

XAUTH, use with 5-19

Reboot the Router 6-29 reducing traffic

Block Sites 6-1

Service Blocking 6-1

Source MAC filtering 6-1 remote management 6-9 , 6-10 access 6-10 configuration 6-11 telnet 6-12

Reserved IP address about 3-10

Reserved IP adresses 3-10

Respond To Ping On Internet Ports

Attack Checks 4-10

RFC 1349

ToS 4-19

RFC 2453

RIP 3-12

RIP 1-3 about 3-12 enabling 3-13 multicasting guidelines 3-14

RIP Configuration screen 3-13

Router Status 6-23

Router Status screen 6-23

Router Upgrade 6-16

Routing Information Protocol. See RIP

Routing log messages B-13

Routing screen 3-10 rules allowing traffic 4-2 blocking traffic 4-2 service blocking 4-2 services-based 4-2

S

Schedule rules, covered by 6-2 schedule blocking traffic 4-20

Index-5 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Schedule 1 screen 4-20

Security 1-3

Self Certificate format of 5-33

Request, generating 5-33

Self Certificate request submitting 5-35

Self Certificates about 5-33

Service Blocking 4-2 , 6-1

LAN Users 6-2 rules 6-1

WAN Users 6-2 service blocking 4-2

Services common protocol numbers 4-17 rules, covered by 6-2

Services screen 4-18

Session Limit screen 4-12 settings backup 6-15

Simple Network Management Protocol. See SNMP.

SMTP server, requirements of 4-32

SNMP about 6-13 configuring 6-13

SNMP screen 6-13

SNMP SysConfiguration screen 6-14

Source MAC Filter screen 4-23

Source MAC Filtering 4-23 , 6-4 enabling 4-23 reducing traffic 6-4 spoof MAC address 7-5 spoofing

UDP flood 4-11

Starting IP Address

DHCP Address Pool 3-4 stateful packet inspection 1-2 , 4-1

Static Route example of 3-11 static routes

Index-6 v1.0, March 2009 configuring 3-10 example 3-11

Stealth Mode

Attack Checks 4-10

SYN flood denial of service attack 4-10

Syslog Server 4-32

System log messages B-1

T

TCP/IP network, Troubleshooting 7-5 time daylight savings 7-7 troubleshooting 7-7

Time Zone setting of 6-17

Time Zone screen 6-17

ToS service levels 4-19 used with QoS 4-19

Traffic features that increase 6-4 management of 6-7 reducing 6-1

Traffic Meter about 6-19 traffic meter programming 2-11

Troubleshooting 7-1

Date and Time 7-7

ISP connection 7-4

LEDs 7-2

LEDs Never Turn Off 7-2

NTP 7-7

Power LED Not On 7-1

Web configuration 7-2

Trusted Certificates 5-32 about 5-32 two-factor authentication

WiKID 6-10

U

UDP flood denial of service attack 4-10 upgrade firmware 6-15 upgrade router steps to 6-17

User Database configuring 5-20

XAUTH, use with 5-19

User Database screen 5-20

V

Videoconferencing from restricted addresses 4-13

Virtual Private Networking. See VPN

VPN activity, monitoring 6-26

VPN Client configuring 5-5

VPN Logs screen 6-26

VPN Pass through 4-11

VPN Policies about 5-16

Auto 5-16 fields, definitions of 5-16

Manual method 5-16

VPN Policies screen 5-4 , 5-7

VPN policy rules of use 5-16

VPN Tunnel connection status, monitoring 6-25

IP Sec 4-11

L2TP 4-11

PPTP 4-11

VPN Tunnel addresses

Dual WAN Port systems 5-2

VPN Tunnels 6-6

VPN Wizard

Gateway tunnel 5-2

VPN Client, configuring 5-5

VPNC 5-2

FVS338 ProSafe VPN Firewall 50 Reference Manual

W

WAN port connection status 6-26

WAN Ports Status monitoring 6-24

WAN Users

Service Blocking 6-2

Web Component Blocking 6-3

Web Components content filtering 4-21

Web configuration troubleshooting 7-2

WiKID 6-10 with 1-2

X

XAUTH about 5-18 configuring 5-19

Edge Device 5-18

IPSec Host 5-18

RADIUS-CHAP 5-19

RADIUS-PAP 5-19

User Database 5-19

Index-7 v1.0, March 2009

FVS338 ProSafe VPN Firewall 50 Reference Manual

Index-8 v1.0, March 2009