



350 East Plumeria Drive San Jose, CA 95134 USA
July, 2012 202-10836-04 v1.0

© 2011–2012 NETGEAR, Inc. All rights reserved.
No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form or by any means without the written permission of NETGEAR, Inc.
Thank you for choosing NETGEAR. To register your product, get the latest product updates, get support online, or for more information about the topics covered in this manual, visit the Support website at http://support.netgear.com
Phone (Other Countries): Check the list of phone numbers at http://support.netgear.com/app/answers/detail/a_id/984.
NETGEAR, the NETGEAR logo, and Connect with Innovation are trademarks and/or registered trademarks of NETGEAR, Inc. and/or its subsidiaries in the United States and/or other countries. Information is subject to change without notice. Other brand and product names are registered trademarks or trademarks of their respective holders. © 2012 NETGEAR, Inc. All rights reserved.
To improve 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.
Version Publish Date Comments

202-10836-01 1.0 September 2011 First publication


This chapter provides an overview of the features and capabilities of the ProSafe Wireless-N 8-Port Gigabit VPN Firewall FVS318N and explains how to log in to the device and use its web management interface. The chapter contains the following sections:
the FVS318N support website at http://support.netgear.com.
The ProSafe Wireless-N 8-Port Gigabit VPN Firewall FVS318N, hereafter referred to as the wireless VPN firewall, connects your local area network (LAN) and wireless LAN (WLAN) to the Internet through an external broadband access device such as a cable or DSL modem, satellite or wireless Internet dish, or another router. A 2.4-GHz radio supports wireless connections in 802.11n mode with support for legacy clients in 802.11b and 802.11g mode.
The wireless VPN firewall routes both IPv4 and IPv6 traffic. A powerful, flexible firewall protects your IPv4 and IPv6 networks from denial of service (DoS) attacks, unwanted traffic, and traffic with objectionable content. IPv6 traffic is supported through 6to4 and Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) tunnels.

The wireless VPN firewall provides advanced IPSec and SSL VPN technologies with support for up to 12 IPSec VPN tunnels and 5 SSL VPN tunnels, as well as L2TP support for easy and secure remote connections. The use of Gigabit Ethernet WAN and LAN ports ensures high data transfer speeds.
The wireless VPN firewall provides the following key features and capabilities:
The wireless VPN firewall supports the following features:
Introduction

The wireless VPN firewall supports IPSec and SSL virtual private network (VPN) connections:
- IPSec VPN with broad protocol support for secure connection to other IPSec gateways and clients.
- Up to 12 simultaneous IPSec VPN connections.
- Bundled with a 30-day trial license for the ProSafe VPN Client software (VPN01L).
- Uses the familiar Secure Sockets Layer (SSL) protocol, commonly used for e-commerce transactions, to provide client-free access with customizable user portals and support for a wide variety of user repositories.
- Up to five simultaneous SSL VPN connections.
- Allows browser-based, platform-independent remote access through a number of popular browsers, such as Microsoft Internet Explorer, Mozilla Firefox, and Apple Safari.
- Provides granular access to corporate resources based on user type or group membership.
Unlike simple NAT routers, the wireless VPN firewall is a true firewall, using stateful packet inspection (SPI) to defend against hacker attacks. Its firewall features have the following capabilities:
Introduction

The wireless VPN firewall is equipped with several features designed to maintain security:
With its internal eight-port 10/100/1000 Mbps switch and 10/100/1000 WAN port, the wireless VPN firewall can connect to either a 10 Mbps standard Ethernet network, a 100 Mbps Fast Ethernet network, or a 1000 Mbps Gigabit Ethernet network. The LAN and WAN interfaces are autosensing and capable of full-duplex or half-duplex operation.
The wireless VPN firewall incorporates Auto UplinkTM technology. Each Ethernet port automatically senses whether the Ethernet cable plugged into the port should have a normal connection such as to a computer or an uplink connection such as to a switch or hub. That port then configures itself correctly. This feature eliminates the need for you to think about crossover cables, as Auto Uplink accommodates either type of cable to make the right connection.
The wireless VPN firewall supports the Transmission Control Protocol/Internet Protocol (TCP/IP) and Routing Information Protocol (RIP). The wireless VPN firewall provides the following protocol support:
Introduction

Dynamic Host Configuration Protocol (DHCP). This feature greatly simplifies configuration of computers on your local network.
You can install, configure, and operate the wireless VPN firewall within minutes after connecting it to the network. The following features simplify installation and management tasks:
Introduction

NETGEAR offers the following features to help you maximize your use of the wireless VPN firewall:
The wireless VPN firewall product package contains the following items:
- Application Notes and other helpful information
- 30-day trial license for the ProSafe VPN Client software (VPN01L)
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 product for repair.
The front panel ports and LEDs, rear panel ports, and bottom label of the wireless VPN firewall are described in the following sections.
Viewed from left to right, the wireless VPN firewall front panel contains the following ports:
Introduction

The front panel also contains three groups of status indicator light-emitting diodes (LEDs), including Power and Test LEDs, LAN LEDs, and WAN LEDs, all of which are explained in detail in the following table. Some LED explanation is provided on the front panel.

(green, one for each port)
(one for each port)
Test LED DMZ LED
The following table describes the function of each LED.
Table 1. LED descriptions
Power LED On (green) Power is supplied to the wireless VPN firewall.
Off Power is not supplied to the wireless VPN firewall.
Test LED On (amber) during startup.
Test mode. The wireless VPN firewall is initializing. After approximately 2 minutes, when the wireless VPN firewall has completed its initialization, the Test LED goes off.
On (amber) during any other time
The initialization has failed, or a hardware failure has occurred.
Blinking (amber) The wireless VPN firewall is writing to flash memory (during upgrading or resetting to defaults).
Off The wireless VPN firewall has booted successfully.

Table 1. LED descriptions (continued)
Left LED Off The LAN port has no link.
On (green) The LAN port has detected a link with a connected Ethernet device.
Blinking (green) Data is being transmitted or received by the LAN port.
Right LED Off The LAN port is operating at 10 Mbps.
On (amber) The LAN port is operating at 100 Mbps.
On (green) The LAN port is operating at 1000 Mbps.
DMZ LED Off Port 8 is operating as a normal LAN port.
On (green) Port 8 is operating as a dedicated hardware DMZ port.
Left LED Off The WAN port has no physical link, that is, no Ethernet cable is plugged into the wireless VPN firewall.
On (green) The WAN port has a valid connection with a device that provides an Internet connection.
Blinking (green) Data is being transmitted or received by the WAN port.
Right LED Off The WAN port is operating at 10 Mbps.
On (amber) The WAN port is operating at 100 Mbps.
On (green) The WAN port is operating at 1000 Mbps.
Active LED Off There is no link to the Internet.
On (green) There is a link to the Internet.

The rear panel of the wireless VPN firewall includes the antennas, a cable lock receptacle, a console port, a Reset button, a DC power connection, and a power switch.

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

The product label on the bottom of the wireless VPN firewall’s enclosure displays factory defaults settings, regulatory compliance, and other information.

The wireless VPN firewall is suitable for use in an office environment where it can be freestanding (on its runner feet) or mounted into a standard 19-inch equipment rack. Alternatively, you can rack-mount the wireless VPN firewall in a wiring closet or equipment room.
Consider the following when deciding where to position the wireless VPN firewall:
Introduction

connect the cables and restart your network according to the instructions in the ProSafe Wireless-N 8-Port Gigabit VPN Firewall FVS318N Installation Guide. A PDF of this guide is on the NETGEAR support website at http://support.netgear.com/app/products/model/a_id/19435.
To configure the wireless VPN firewall, you need to use a web browser such as Microsoft Internet Explorer 7.0 or later, Mozilla Firefox 4.0 or later, or Apple Safari 3.0 or later with JavaScript, cookies, and SSL enabled. (Google Chrome is not supported at this time.)
Although these web browsers are qualified for use with the wireless VPN firewall’s web management interface, SSL VPN users should choose a browser that supports JavaScript, Java, cookies, SSL, and ActiveX to take advantage of the full suite of applications. Note that Java is required only for the SSL VPN portal, not for the web management interface.
To log in to the wireless VPN firewall:
If you change the IP address, you need to use the IP address that you assigned to the wireless VPN firewall to log in to the wireless VPN firewall.
Introduction


same as any user name or password you might use to log in to your Internet connection.
automatically logged out.
Introduction


The following figure shows the menu at the top the web management interface:

1st level: Main navigation menu link (orange) 2nd level: Configuration menu link (gray) 3rd level: Submenu tab (blue) Option arrows: Additional screen for submenu item
The web management interface menu consists of the following components:
IP radio buttons · Introduction

- Both buttons are operational. You can configure the feature onscreen for IPv4 functionality or for IPv6 functionality. After you have correctly configured the feature for both IP versions, the feature can function with both IP versions simultaneously.
- The IPv4 button is operational but the IPv6 button is disabled. You can configure the feature onscreen for IPv4 functionality only.
- The IPv6 button is operational but the IPv4 button is disabled. You can configure the feature onscreen for IPv6 functionality only.
- Both buttons are disabled. IP functionality does not apply.
The bottom of each screen provides action buttons. The nature of the screen determines which action buttons are shown. The following figure shows an example:

Any of the following action buttons might display onscreen (this list might not be complete):
When a screen includes a table, table buttons display to let you configure the table entries. The nature of the screen determines which table buttons are shown. The following figure shows an example:

Introduction

Any of the following table buttons might display onscreen:
Almost all screens and sections of screens have an accompanying help screen. To open the help screen, click the (question mark) icon.
To connect to the wireless VPN firewall, your computer needs to be configured to obtain an IP address automatically from the wireless VPN firewall, either an IPv4 address through DHCP or an IPv6 address through DHCPv6, or both.
The fourth octet of an IP address needs to be between 0 and 255 (both inclusive). This requirement applies to any IP address that you enter on a screen of the web management interface.
IPv6 addresses are denoted by eight groups of hexadecimal quartets that are separated by colons. Any four-digit group of zeroes within an IPv6 address can be reduced to a single zero or altogether omitted.
The following errors invalidate an IPv6 address:
IPv4 · IPv6 · Introduction

This chapter explains how to configure the Internet and WAN settings. The chapter contains the following sections:
The tasks that are required to complete the Internet connection of your wireless VPN firewall depend on whether you use an IPv4 connection or an IPv6 connection to your Internet service provider (ISP).
connections.
Complete these four tasks:
You can also program the WAN traffic meter if you wish: see Enable the WAN Traffic Meter on page 346.

Complete these four tasks:
To set up your wireless VPN firewall for secure IPv4 Internet connections, you need to determine the IPv4 WAN mode (see the next section) and then configure the IPv4 Internet connection to your ISP on the WAN port. The web management interface offers two connection configuration options, discussed in the following sections:
IPv4 and IPv6 Internet and Broadband Settings

By default, IPv4 is supported and functions in NAT mode but can also function in classical routing mode. IPv4 functions the same way in IPv4-only mode that it does in IPv4 / IPv6 mode. The latter mode adds IPv6 functionality (see Configure the IPv6 Routing Mode on page 38).
Network Address Translation (NAT) allows all computers on your LAN to share a single public Internet IP address. From the Internet, there is only a single device (the wireless VPN firewall) and a single IP address. Computers on your LAN can use any private IP address range, and these IP addresses are not visible from the Internet.
In classical routing mode, the wireless VPN firewall performs routing, but without NAT. To gain Internet access, each computer on your LAN needs to have a valid static Internet IP address.
If your ISP has allocated a number of static IP addresses to you, and you have assigned one of these addresses to each computer, you can choose classical routing. Or you can use classical routing for routing private IP addresses within a campus environment.
To view the status of the WAN ports, you can view the Router Status screen (see View the System Status on page 356).
Configure the IPv4 Routing Mode
To configure the IPv4 routing mode:
IPv4 and IPv6 Internet and Broadband Settings
Network Address Translation · Classical Routing


Changing the WAN mode causes all LAN WAN and DMZ WAN inbound rules to revert to default settings.
Let the Wireless VPN Firewall Automatically Detect and Configure an IPv4 Internet Connection
To automatically configure the WAN port for an IPv4 connection to the Internet:
IPv4 and IPv6 Internet and Broadband Settings


The autodetect process returns one of the following results:
IPv4 and IPv6 Internet and Broadband Settings

Table 2. IPv4 Internet connection methods
Connection Method Manual Data Input Required
DHCP (Dynamic IP) No manual data input is required.

IPv4 and IPv6 Internet and Broadband Settings

The Connection Status screen should show a valid IP address and gateway, and you are connected to the Internet. If the configuration was not successful, skip ahead to Manually Configure an IPv4 Internet Connection on page 31, or see Troubleshoot the ISP Connection on page 382.
the WAN Port Status on page 367.
Unless your ISP automatically assigns your configuration through a DHCP server, you need to obtain configuration parameters from your ISP to manually establish an Internet connection. The required parameters for various connection types are listed in Table 2 on page 30.
To manually configure the IPv4 broadband ISP settings:

In the ISP Login section, select one of the following options:
IPv4 and IPv6 Internet and Broadband Settings


Table 3. PPTP and PPPoE settings
If your ISP is Austria Telecom or any other ISP that uses PPTP for login, select this radio button, and enter the following settings:
Account Name The account name is also known as the 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 you to enter your full email address here.
Domain Name Your domain name or workgroup name assigned by your ISP, or your ISP’s domain name. You can leave this field blank.
Idle Timeout Select the Keep Connected radio button to keep the connection always on. To log out after the connection is idle for a period, select the Idle Timeout radio button and, in the Idle Timeout field, enter the number of minutes to wait before disconnecting. This is useful if your ISP charges you based on the period that you have logged in.
My IP Address The IP address assigned by the ISP to make the connection with the ISP server.
The IP address of the PPTP server.
IPv4 and IPv6 Internet and Broadband Settings
Setting Description · Austria (PPTP) · Server IP Address

Table 3. PPTP and PPPoE settings (continued)
If you have installed login software, then your connection type is PPPoE. Select this radio button, and enter the following settings:
Account Name The valid account name for the PPPoE connection.
Domain Name The name of your ISP’s domain or your domain name if your ISP has assigned one. You can leave this field blank.
Idle Timeout Select the Keep Connected radio button to keep the connection always on. To log out after the connection is idle for a period, select the Idle Timeout radio button and, in the Idle Timeout field, enter the number of minutes to wait before disconnecting. This is useful if your ISP charges you based on the period that you have logged in.
Select the Connection Reset check box to specify a time when the PPPoE WAN connection is reset, that is, the connection is disconnected momentarily and then reestablished. Then specify the disconnect time and delay.
Specify the hour and minutes when the connection should be disconnected.
Delay Specify the period in seconds after which the connection should be reestablished.

IPv4 and IPv6 Internet and Broadband Settings

Table 4. Internet IP address settings
Get Dynamically from ISP
If your ISP has not assigned you a static IP address, select the Get Dynamically from ISP radio button. The ISP automatically assigns an IP address to the wireless VPN firewall using DHCP network protocol.
Client Identifier If your ISP requires the client identifier information to assign an IP address using DHCP, select the Client Identifier check box.
Vendor Class Identifier If your ISP requires the vendor class identifier information to assign an IP address using DHCP, select the Vendor Class Identifier check box.
Use Static IP Address
If your ISP has assigned you a fixed (static or permanent) IP address, select the Use Static IP Address radio button, and enter the following settings:
IP Address The static IP address assigned to you. This address identifies the wireless VPN firewall to your ISP.
IP Subnet Mask The subnet mask is usually provided by your ISP.
Gateway IP Address The IP address of the ISP’s gateway is usually provided by your ISP.

Table 5. DNS server settings
Get Automatically from ISP
If your ISP has not assigned any Domain Name Server (DNS) addresses, select the Get Automatically from ISP radio button.
Use These DNS Servers
If your ISP has assigned DNS addresses, select the Use These DNS Servers radio button. Make sure that you fill in valid DNS server IP addresses in the fields. Incorrect DNS entries might cause connectivity issues.
Primary DNS Server The IP address of the primary DNS server.
Secondary DNS Server The IP address of the secondary DNS server.
IPv4 and IPv6 Internet and Broadband Settings
Setting Description · Setting Description


has been previously registered with your ISP, then you need to enter that address on the Broadband Advanced Options screen for the WAN interface (see Configure Advanced WAN Options and Other Tasks on page 50).
Dynamic DNS (DDNS) is an Internet service that allows devices with varying public IPv4 addresses to be located using Internet domain names. To use DDNS, you need to set up an account with a DDNS provider such as DynDNS.org, TZO.com, Oray.net, or 3322.org. (Links to DynDNS, TZO, Oray, and 3322 are provided for your convenience as option arrows on the DDNS configuration screens.) The wireless VPN firewall firmware includes software that notifies DDNS servers of changes in the WAN IP address so that the services running on this network can be accessed by others on the Internet.
If your network has a permanently assigned IP address, you can register a domain name and have that name linked with your IP address by public Domain Name Servers (DNS). However, if your Internet account uses a dynamically assigned IP address, you will not know in advance what your IP address will be, and the address can change frequently—hence, the need for a commercial DDNS service, which allows you to register an extension to its domain, and restores DNS requests for the resulting fully qualified domain name (FQDN) to your frequently changing IP address.
IPv4 and IPv6 Internet and Broadband Settings

After you have configured your account information on the wireless VPN firewall, when your ISP-assigned IP address changes, your wireless VPN firewall automatically contacts your DDNS service provider, logs in to your account, and registers your new IP address.
or 10.x.x.x, the DDNS service does not work because private addresses are not routed on the Internet.
To configure DDNS:


IPv4 and IPv6 Internet and Broadband Settings

Table 6. DDNS service settings
Change DNS to (DynDNS, TZO, Oray, or 3322)
Select the Yes radio button to enable the DDNS service. The fields that display on the screen depend on the DDNS service provider that you have selected. Enter the following settings:
Host and Domain Name The host and domain name for the DDNS service.
Username or User Email Address
The user name or email address for DDNS server authentication.
Password or User Key The password that is used for DDNS server authentication.
Change DNS to (DynDNS, TZO, Oray, or 3322) (continued)
Use wildcards If your DDNS provider allows the use of wildcards in resolving your URL, you can select the Use wildcards check box to activate this feature. For example, the wildcard feature causes *.yourhost.dyndns.org to be aliased to the same IP address as yourhost.dyndns.org.
Update every 30 days If your WAN IP address does not change often, you might need to force a periodic update to the DDNS service to prevent your account from expiring. If the Update every 30 days check box displays, select it to enable a periodic update.
The nature of your IPv6 network determines how you need to configure the IPv6 Internet connection:
IPv4 and IPv6 Internet and Broadband Settings
Setting Description

network with IPv4 and IPv6 devices.
After you have configured the IPv6 routing mode (see the next section), you need to configure the WAN port with a global unicast address to enable secure IPv6 Internet connections on your wireless VPN firewall. A global unicast address is a public and routable IPv6 WAN address that can be statically or dynamically assigned. The web management interface offers two connection configuration options:
By default, the wireless VPN firewall supports IPv4 only. To use IPv6, you need to enable the wireless VPN firewall to support both devices with IPv4 addresses and devices with IPv6 addresses. The routing mode does not include an IPv6-only option; however, you can still configure a native IPv6 network if your ISP supports IPv6. These are the options:
interface and the LAN interfaces; NAT does not apply to IPv6.
To configure the IPv6 routing mode:
IPv4 and IPv6 Internet and Broadband Settings

Changing the IP routing mode causes the wireless VPN firewall to reboot.
The wireless VPN firewall can autoconfigure its ISP settings through a DHCPv6 server by using either stateless or stateful address autoconfiguration:
Router advertisements include a prefix that identifies the subnet that is associated with the WAN port. The IP address is formed by combining this prefix and the MAC address of the WAN port. The IP address is a dynamic address.
As an option for stateless address autoconfiguration, the ISP’s stateful DHCPv6 server can assign a prefix through prefix delegation. The wireless VPN firewall’s own stateless DHCPv6 server can assign this prefix to its IPv6 LAN clients. For more information about prefix delegation, see Stateless DHCPv6 Server With Prefix Delegation on page 74.
IPv4 and IPv6 Internet and Broadband Settings

To automatically configure the WAN port for an IPv6 connection to the Internet:

IPv4 and IPv6 Internet and Broadband Settings

5. As an optional step: If you have selected the Stateless Address Auto Configuration radio button, you can select the Prefix Delegation check box: • Prefix delegation check box is selected. A prefix is assigned by the ISP’s stateful DHCPv6 server through prefix delegation, for example, 2001:db8:: /64. The wireless VPN firewall’s own stateless DHCPv6 server can assign this prefix to its IPv6 LAN clients. For more information about prefix delegation, see Stateless DHCPv6 Server With Prefix Delegation on page 74.

The Connection Status screen should show a valid IP address and gateway, and you are connected to the Internet. If the configuration was not successful, see Troubleshoot the ISP Connection on page 382.
the WAN Port Status on page 367.
To configure a static IPv6 or PPPoE IPv6 Internet connection, you need to enter the IPv6 address information that you should have received from your ISP.
To configure static IPv6 broadband ISP settings:
IPv4 and IPv6 Internet and Broadband Settings


Table 7. Broadband ISP Settings screen settings for a static IPv6 address
IPv6 Prefix Length The prefix length that your ISP assigned to you, typically 64.
Default IPv6 Gateway The IPv6 IP address of the ISP’s default IPv6 gateway.
Primary DNS Server The IPv6 IP address of the ISP’s primary DNS server.
Secondary DNS Server The IPv6 IP address of the ISP’s secondary DNS server.
IPv4 and IPv6 Internet and Broadband Settings
Setting Description


The Connection Status screen should show a valid IP address and gateway, and you are connected to the Internet. If the configuration was not successful, see Troubleshoot the ISP Connection on page 382.
the WAN Port Status on page 367.
has been previously registered with your ISP, then you need to enter that address on the Broadband Advanced Options screen for the corresponding WAN interface (see Configure Advanced WAN Options and Other Tasks on page 50).
To configure a PPPoE IPv6 Internet connection, you need to enter the PPPoE IPv6 information that you should have received from your ISP.
To configure PPPoE IPv6 broadband ISP settings:
IPv4 and IPv6 Internet and Broadband Settings


Table 8. Broadband ISP Settings screen settings for a PPPoE IPv6 connection
User Name The PPPoE user name that is provided by your ISP.
Password The PPPoE password that is provided by your ISP.
IPv4 and IPv6 Internet and Broadband Settings
Setting Description

Table 8. Broadband ISP Settings screen settings for a PPPoE IPv6 connection (continued)
Primary DNS Server If you have selected the Disable-DHCPv6 from the DHCPv6 Options drop-down list, the IPv6 IP address of the ISP’s primary DNS server.
Secondary DNS Server If you have selected the Disable-DHCPv6 from the DHCPv6 Options drop-down list, the IPv6 IP address of the ISP’s secondary DNS server.
The Connection Status screen should show a valid IP address and gateway, and you are connected to the Internet. If the configuration was not successful, see Troubleshoot the ISP Connection on page 382.
the WAN Port Status on page 367.
has been previously registered with your ISP, then you need to enter that address on the Broadband Advanced Options screen for the corresponding WAN interface (see Configure Advanced WAN Options and Other Tasks on page 50).
IPv4 and IPv6 Internet and Broadband Settings
Setting Description

If your network is an isolated IPv6 network that is not connected to an IPv6 ISP, you need to make sure that the IPv6 packets can travel over the IPv4 Internet backbone by enabling automatic 6to4 tunneling.
6to4 is a WAN tunnel mechanism for automatic tunneling of IPv6 traffic between a device with an IPv6 address and a device with an IPv4 address, or the other way around. 6to4 tunneling is used to transfer IPv6 traffic between LAN IPv6 hosts and WAN IPv6 networks over the IPv4 network.
With 6to4 tunnels, IPv6 packets are embedded within the IPv4 packet and then transported over the IPv4 network. You do not need to specify remote tunnel endpoints, which are automatically determined by relay routers on the Internet. You cannot use 6to4 tunnels for traffic between IPv4-only devices and IPv6-only devices.
tunnels in your network, make sure that the wireless VPN firewall has a static IPv4 address (see Manually Configure an IPv4 Internet Connection on page 31). A dynamic IPv4 address can cause routing problems on the 6to4 tunnels.
configure the Router Advertisement Daemon (RADVD), and set up 6to4 advertisement prefixes for 6to4 tunneling to function correctly. For more information, see Manage the IPv6 LAN on page 73.
Typically, 6to4 tunnel addresses start with a 2002 prefix (decimal notification). On the wireless VPN firewall, a 6to4 tunnel is indicated by sit0-WAN1 (see View the Tunnel Status and IPv6 Addresses on page 49).
To enable 6to4 automatic tunneling:

IPv4 and IPv6 Internet and Broadband Settings

If your network is an IPv4 network or IPv6 network that consists of both IPv4 and IPv6 devices, you need to make sure that the IPv6 packets can travel over the IPv4 intranet by enabling and configuring Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) tunneling.
ISATAP is a LAN tunnel mechanism in which the IPv4 network functions as a virtual IPv6 local link. Each IPv4 address is mapped to a link-local IPv6 address, that is, the IPv4 address is used in the interface portion of the IPv6 address. ISATAP tunneling is used intra-site, that is, between addresses in the LAN. For more information about link-local addresses, see Manage the IPv6 LAN on page 73.
configure the Router Advertisement Daemon (RADVD), and set up ISATAP advertisement prefixes (which are referred to as Global/Local/ISATAP prefixes) for ISATAP tunneling to function correctly. For more information, see Manage the IPv6 LAN on page 73.
The wireless VPN firewall determines the link-local address by concatenating the IPv6 address with the 32 bits of the IPv4 host address:
To configure an ISATAP tunnel:
IPv4 and IPv6 Internet and Broadband Settings



Table 9. Add ISATAP Tunnel screen settings
ISATAP Subnet Prefix The IPv6 prefix for the tunnel.
Local End Point Address
IPv4 Address If you select Other IP from the Local End Point Address drop-down list, enter the IPv4 address.
To edit an ISATAP tunnel:
IPv4 and IPv6 Internet and Broadband Settings
Setting Description

To delete one or more tunnels:
The IPv6 Tunnel Status screen displays the status of all active 6to4 and ISATAP tunnels and their IPv6 addresses.
To view the status of the tunnels and IPv6 addresses:
Select Monitoring > Router Status > Tunnel Status. The Tunnel Status screen displays:

The IPv6 Tunnel Status table shows the following fields:
Stateless IP/ICMP Translation (SIIT) is a transition mechanism algorithm that translates between IPv4 and IPv6 packet headers. Using SIIT, an IPv6 device that does not have a permanently assigned IPv4 addresses can communicate with an IPv4-only device.
SIIT functions with IPv4-translated addresses, which are addresses of the format 0::ffff:0:0:0/96 for IPv6-enabled devices. You can substitute an IPv4 address in the format a.b.c.d for part of the IPv6 address so that the IPv4-translated address becomes 0::ffff:0:a.b.c.d/96.
IPv4 and IPv6 Internet and Broadband Settings

For SIIT to function, the routing mode needs to be IPv4 / IPv6. NETGEAR’s implementation of SIIT lets you enter a single IPv4 address on the SIIT screen. This IPv4 address is then used in the IPv4-translated address for IPv6 devices to enable communication between IPv4-only devices on the wireless VPN firewall’s LAN and IPv6-only devices on the WAN.
To configure SIIT:

The advanced options include configuring the maximum transmission unit (MTU) size, port speed, and wireless VPN firewall’s MAC address, and setting a rate limit on the traffic that is being forwarded by the wireless VPN firewall.
only through the Broadband ISP Settings (IPv4) screen, the advanced options apply to both IPv4 and IPv6 WAN connections.
To configure advanced WAN options:
IPv4 and IPv6 Internet and Broadband Settings


Table 10. Broadband Advanced Options screen settings
MTU Size Make one of the following selections:
Default Select the Default radio button for the normal maximum transmit unit (MTU) value. For most Ethernet networks, this value is 1500 bytes, or 1492 bytes for PPPoE connections.
Custom Select the Custom radio button, and enter an MTU value in the Bytes field. For some ISPs, you might need to reduce the MTU. This is rarely required, and should not be done unless you are sure that it is necessary for your ISP connection.
IPv4 and IPv6 Internet and Broadband Settings
Setting Description

Table 10. Broadband Advanced Options screen settings (continued)
Router’s MAC Address Each computer or router on your network has a unique 48-bit local Ethernet address. This is also referred to as the computer’s Media Access Control (MAC) address. The default is set to Use Default Address. Make one of the following selections:
Use Default Address Each computer or router on your network has a unique 32-bit local Ethernet address. This is also referred to as the computer’s Media Access Control (MAC) address. To use the wireless VPN firewall’s own MAC address, select the Use Default Address radio button.
Use this computer’s MAC Address
Select the Use this computer’s MAC Address radio button to allow the wireless VPN firewall to use the MAC address of the computer you are now using to access the web management interface. This setting is useful if your ISP requires MAC authentication.
Use this MAC Address Select the Use this MAC Address radio button, and manually enter the MAC address in the field next to the radio button. You would typically enter the MAC address that your ISP is requiring for MAC authentication.
IPv4 and IPv6 Internet and Broadband Settings
Setting Description · Speed

If you want the ability to manage the wireless VPN firewall remotely, enable remote management (see Configure Remote Management Access on page 331). If you enable remote management, NETGEAR strongly recommends that you change your password (see Change Passwords and Administrator and Guest Settings on page 329).
You can set up the traffic meter for the WAN interface, if you wish. See Enable the WAN Traffic Meter on page 346.
Test the wireless VPN firewall before deploying it in a live production environment. Verify that network traffic can pass through the wireless VPN firewall:
You have completed setting up the WAN connection for the wireless VPN firewall. The following chapters and sections describe important tasks that you need to address before you deploy the wireless VPN firewall in your network:
IPv4 and IPv6 Internet and Broadband Settings

This chapter describes how to configure the LAN features of your wireless VPN firewall. The chapter contains the following sections:
A local area network (LAN) can generally be defined as a broadcast domain. Hubs, bridges, or switches in the same physical segment or segments connect all end node devices. Endpoints can communicate with each other without the need for a router. Routers connect LANs together, routing the traffic to the appropriate port.
A virtual LAN (VLAN) is a local area network with a definition that maps workstations on some basis other than geographic location (for example, by department, type of user, or primary application). To enable traffic to flow between VLANs, traffic needs to go through a router, as if the VLANs were on two separate LANs.
A VLAN is a group of computers, servers, and other network resources that behave as if they were connected to a single network segment—even though they might not be. For example, all marketing personnel might be spread throughout a building. Yet if they are all assigned to a single VLAN, they can share resources and bandwidth as if they were connected to the

same segment. The resources of other departments can be invisible to the marketing VLAN members, accessible to all, or accessible only to specified individuals, depending on how the IT manager has set up the VLANs.
VLANs have a number of advantages:
The wireless VPN firewall supports port-based VLANs. Port-based VLANs help to confine broadcast traffic to the LAN ports. Even though a LAN port can be a member of more than one VLAN, the port can have only one VLAN ID as its port VLAN identifier (PVID). By default, all eight LAN ports of the wireless VPN firewall are assigned to the default VLAN, or VLAN 1. Therefore, by default, all eight LAN ports have the default PVID 1. However, you can assign another PVID to a LAN port by selecting a VLAN profile from the drop-down list on the LAN Setup screen.
After you have created a VLAN profile and assigned one or more ports to the profile, you need to enable the profile to activate it.
The wireless VPN firewall’s default VLAN cannot be deleted. All untagged traffic is routed through the default VLAN (VLAN1), which you need to assign to at least one LAN port.
LAN Configuration

When you create a VLAN profile, assign LAN ports to the VLAN, and enable the VLAN, the LAN ports that are members of the VLAN can send and receive both tagged and untagged packets. Untagged packets that enter these LAN ports are assigned to the default PVID 1; packets that leave these LAN ports with the same default PVID 1 are untagged. All other packets are tagged according to the VLAN ID that you assigned to the VLAN when you created the VLAN profile.
This is a typical scenario for a configuration with an IP phone that has two Ethernet ports, one of which is connected to the wireless VPN firewall, the other one to another device:
Packets coming from the IP phone to the wireless VPN firewall LAN port are tagged. Packets passing through the IP phone from the connected device to the wireless VPN firewall LAN port are untagged. When you assign the wireless VPN firewall LAN port to a VLAN, packets entering and leaving the port are tagged with the VLAN ID. However, untagged packets entering the wireless VPN firewall LAN port are forwarded to the default VLAN with PVID 1; packets that leave the LAN port with the same default PVID 1 are untagged.
explained in Configure the IPv4 Internet Connection and WAN Settings on page 26. For information about how to add and edit a VLAN profile, including its DHCP options, see Configure a VLAN Profile on page 59.
To assign VLAN profiles to the LAN ports and manage VLAN profiles:
LAN Configuration


For each VLAN profile, the following fields display in the VLAN Profiles table:
- Green circle. The VLAN profile is enabled.
- Gray circle. The VLAN profile is disabled.
For each VLAN, you need to specify the Dynamic Host Configuration Protocol (DHCP) options (see Configure a VLAN Profile on page 59). The configuration of the DHCP options for the wireless VPN firewall’s default VLAN, or VLAN 1, is explained in Configure the IPv4 Internet Connection and WAN Settings on page 26. This section provides further information about the DHCP options.
LAN Configuration

The default VLAN (VLAN 1) has the DHCP server option enabled by default, allowing the wireless VPN firewall to assign IP, DNS server, WINS server, and default gateway addresses to all computers connected to the wireless VPN firewall’s LAN. The assigned default gateway address is the LAN address of the wireless VPN firewall. IP addresses are assigned to the attached computers from a pool of addresses that you need to specify. Each pool address is tested before it is assigned to avoid duplicate addresses on the LAN. When you create a new VLAN, the DHCP server option is disabled by default.
For most applications, the default DHCP server and TCP/IP settings of the wireless VPN firewall are satisfactory.
The wireless VPN firewall delivers the following settings to any LAN device that requests DHCP:
DHCP relay options allow you to make the wireless VPN firewall a DHCP relay agent for a VLAN. 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. If you do not configure a DHCP relay agent for a VLAN, its clients can obtain IP addresses only from a DHCP server that is on the same subnet. To enable clients to obtain IP addresses from a DHCP server on a remote subnet, you need to configure the DHCP relay agent on the subnet that contains the remote clients, so that the DHCP relay agent can relay DHCP broadcast messages to your DHCP server.
When the DNS proxy option is enabled for a VLAN, the wireless VPN firewall acts as a proxy for all DNS requests and communicates with the ISP’s DNS servers (as configured on the Broadband ISP Settings screens). All DHCP clients receive the primary and secondary DNS IP addresses along with the IP address where the DNS proxy is located (that is, the wireless VPN firewall’s LAN IP address). When the DNS proxy option is disabled for a VLAN, all DHCP clients receive the DNS IP addresses of the ISP but without the DNS proxy IP address.

A Lightweight Directory Access Protocol (LDAP) server allows a user to query and modify directory services that run over TCP/IP. For example, clients can query email addresses, contact information, and other service information using an LDAP server. For each VLAN, you can specify an LDAP server and a search base that defines the location in the directory (that is, the directory tree) from which the LDAP search begins.
For each VLAN on the wireless VPN firewall, you can configure its profile, port membership, LAN TCP/IP settings, DHCP options, DNS server, and inter-VLAN routing capability.
To add a VLAN profile:
VLANs on page 55. The following information describes how to configure a VLAN profile.
LDAP Server · LAN Configuration


LAN Configuration

Table 11. Add VLAN Profile screen settings
Profile Name Enter a unique name for the VLAN profile.
VLAN ID Enter a unique ID number for the VLAN profile. No two VLANs can have the same VLAN ID number.
Port 1, Port 2, Port 3, Port 4, Port 5, Port 6, Port 7, and Port 8 / DMZ
Select one, several, or all port check boxes to make the ports members of this VLAN.
IP Address Enter the IP address of the wireless VPN firewall (the factory default address is 192.168.1.1).
Note: If you change the LAN IP address of the VLAN while being connected through the browser to the VLAN, you are disconnected. You then need to 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 now need to enter https://10.0.0.1 in your browser to reconnect to the web management interface.
Subnet Mask Enter the IP subnet mask. The subnet mask specifies the network number portion of an IP address. Based on the IP address that you assign, the wireless VPN firewall automatically calculates the subnet mask. Unless you are implementing subnetting, use 255.255.255.0 as the subnet mask (computed by the wireless VPN firewall).
Disable DHCP Server If another device on your network is the DHCP server for the VLAN, or if you will manually configure the network settings of all of your computers, select the Disable DHCP Server radio button to disable the DHCP server. Except for the default VLAN for which the DHCP server is enabled, this is the default setting.

Table 11. Add VLAN Profile screen settings (continued)
Enable DHCP Server Select the Enable DHCP Server radio button to enable the wireless VPN firewall to function as a Dynamic Host Configuration Protocol (DHCP) server, providing TCP/IP configuration for all computers connected to the VLAN. (For the default VLAN, the DHCP server is enabled by default.) Enter the following settings:
Domain Name This setting is optional. Enter the domain name of the wireless VPN firewall.
Start IP Address Enter the start IP address. This address specifies the first of the contiguous addresses in the IP address pool. Any new DHCP client joining the LAN is assigned an IP address between this address and the end IP address. For the default VLAN, the default start IP address is 192.168.1.100.
End IP Address Enter the end IP address. This address specifies the last of the contiguous addresses in the IP address pool. Any new DHCP client joining the LAN is assigned an IP address between the start IP address and this IP address. For the default VLAN, the default end IP address is 192.168.1.254. The start and end DHCP IP addresses should be in the same network as the LAN IP address of the wireless VPN firewall (that is, the IP address in the IP Setup section as described earlier in this table).
This setting is optional. If an IP address is specified, the wireless VPN firewall provides this address as the primary DNS server IP address. If no address is specified, the wireless VPN firewall uses the VLAN IP address as the primary DNS server IP address.
This setting is optional. If an IP address is specified, the wireless VPN firewall provides this address as the secondary DNS server IP address.
WINS Server This setting is optional. Enter a WINS server IP address to specify the Windows NetBIOS server, if one is present in your network.
Lease Time Enter a lease time. This specifies the duration for which IP addresses are leased to clients.
DHCP Relay To use the wireless VPN firewall as a DHCP relay agent for a DHCP server somewhere else in your network, select the DHCP Relay radio button. Enter the following setting:
Relay Gateway The IP address of the DHCP server for which the wireless VPN firewall serves as a relay.

Table 11. Add VLAN Profile screen settings (continued)
To enable the DHCP server to provide Lightweight Directory Access Protocol (LDAP) server information, select the Enable LDAP information check box. Enter the following settings.
LDAP Server The IP address or name of the LDAP server.
Port The port number for the LDAP server. The default setting is 0 (zero).
Enable DNS Proxy This setting is optional. To enable the wireless VPN firewall to provide a LAN IP address for DNS address name resolution, select the Enable DNS Proxy check box. This setting is disabled by default.
Enable Inter VLAN Routing
This setting is optional. To ensure that traffic is routed only to VLANs for which inter-VLAN routing is enabled, select the Enable Inter VLAN Routing check box. This setting is disabled by default. When the Enable Inter VLAN Routing check box is not selected, traffic from this VLAN is not routed to other VLANs, and traffic from other VLANs is not routed to this VLAN.
allowed and all inbound traffic is discarded except responses to requests from the LAN side. For information about how to change these default traffic rules, see Chapter 5, Firewall Protection.

To edit a VLAN profile:
To enable, disable, or delete one or more VLAN profiles:
By default, all configured VLAN profiles share the same single MAC address as the LAN ports. (All LAN ports share the same MAC address.) However, you can change the VLAN MAC settings to allow up to 16 VLANs to each be assigned a unique MAC address.
You can also enable or disable the broadcast of Address Resolution Protocol (ARP) packets for the default VLAN. If the broadcast of ARP packets is enabled, IP addresses can be mapped to physical addresses (that is, MAC addresses).
To configure a VLAN to have a unique MAC address:
LAN Configuration


address for VLANs is set to Unique on the LAN Advanced screen, the MAC addresses that are assigned to each VLAN might no longer be distinct.
If you have computers using different IPv4 networks in the LAN (for example, 172.124.10.0 or 192.168.200.0), you can add aliases to the LAN ports and give computers on those networks access to the Internet, but you can do so only for the default VLAN. The IP address that is assigned as a secondary IP address needs to be unique and cannot be assigned to a VLAN.
Make sure that any secondary LAN addresses are different from the primary LAN, WAN, and DMZ IP addresses and subnet addresses that are already configured on the wireless VPN firewall. The following is an example of correctly configured IPv4 addresses:
LAN Configuration

To add a secondary LAN IPv4 address:

The Available Secondary LAN IPs table displays the secondary LAN IP addresses added to the wireless VPN firewall.
Repeat Step 2 and Step 3 for each secondary IP address that you want to add to the Available Secondary LAN IPs table.
The hosts on the secondary subnets need to be manually configured with the IP addresses, gateway IP address, and DNS server IP addresses.
To edit a secondary LAN IP address:
LAN Configuration

To delete one or more secondary LAN IP addresses:
The Known PCs and Devices table on the LAN Groups (IPv4) screen (see Figure 35 on page 68) contains a list of all known computers and network devices that are assigned dynamic IP addresses by the wireless VPN firewall, have been discovered by other means, or were entered manually. Collectively, these entries make up the network database.
The network database is updated by these methods:
traffic.
it might not be able to determine the device name if the software firewall of the device blocks the name.
These are some advantages of the network database:
LAN Configuration

- You can assign computers to groups (see Manage the Network Database on this page) and apply restrictions (outbound rules and inbound rules) to each group (see Overview of Rules to Block or Allow Specific Kinds of Traffic on page 129).
- You can select groups that are allowed access to URLs that you have blocked for other groups, or the other way around, block access to URLs that you have allowed access to for groups (see Configure Content Filtering on page 178).
- If necessary, you can also create firewall rules to apply to a single computer (see Enable Source MAC Filtering on page 183). Because the MAC address is used to identify each computer, users cannot avoid these restrictions by changing their IP address.
You can view the network database, manually add or remove database entries, and edit database entries.
To view the network database, select Network Configuration > LAN Setup > LAN Groups. The LAN Groups screen displays. (The following figure shows some manually added devices in the Known PCs and Devices table as an example.)

LAN Configuration

The Known PCs and Devices table lists the entries in the network database. For each computer or device, the following fields display:
Add Computers or Devices to the Network Database
To add computers or devices manually to the network database:
Table 12. Add Known PCs and Devices section settings
Name Enter the name of the computer or device.
Setting Description · LAN Configuration

Table 12. Add Known PCs and Devices section settings (continued)
MAC Address Enter the MAC address of the computer’s or device’s network interface. The MAC address format is six colon-separated pairs of hexadecimal characters (0–9 and a–f), such as 01:23:d2:6f:89:ab.
Group From the drop-down list, select the group to which the computer or device is assigned. (Group 1 is the default group.)
Profile Name From the drop-down list, select the name of the VLAN profile to which the computer or device is assigned.
(see Figure 99 on page 186).
Edit Computers or Devices in the Network Database
To edit computers or devices manually in the network database:
Setting Description · LAN Configuration


Deleting Computers or Devices from the Network Database
To delete one or more computers or devices from the network database:
the LAN Groups screen, make sure that you also delete the binding on the IP/MAC Binding screen (see Figure 99 on page 186).
By default, the groups are named Group1 through Group8. You can change these group names to be more descriptive, such as GlobalMarketing and GlobalSales.
To edit the names of any of the eight available groups:
LAN Configuration


When you specify a reserved IP address for a computer or device on the LAN (based on the MAC address of the device), that computer or device always receives the same IP address each time it accesses the wireless VPN firewall’s DHCP server. Reserved IP addresses should be assigned to servers or access points that require permanent IP address settings. The reserved IP address that you select needs to be outside of the DHCP server pool.
To reserve and bind an IP address to a MAC address, select Reserved (DHCP Client) from the IP Address Type drop-down list on the LAN Groups screen and save the binding by clicking the Save Binding button on the same screen. For detailed steps, see Add Computers or Devices to the Network Database on page 69.
computer or device contacts the wireless VPN firewall’s DHCP server. Reboot the computer or device, or access its IP configuration and force a DHCP release and renew.
LAN Configuration

(see Figure 99 on page 186).
An IPv6 LAN typically functions with site-local and link-local unicast addresses. Each physical interface requires an IPv6 link-local address that is automatically derived from the MAC addresses of the IPv4 interface and that is used for address configuration and neighbor discovery. (Normally, you would not manually configure a link-local address.)
Traffic with site-local or link-local addresses is never forwarded by the wireless VPN firewall (or by any other router), that is, the traffic remains in the LAN subnet and is processed over the default VLAN only. A site-local address always starts with FEC0 (hexadecimal); a link-local unicast address always starts with FE80 (hexadecimal). To forward traffic from sources with a site local or link-local unicast address in the LAN, a DHCP server is required. For more information about link-local unicast addresses, see Configure ISATAP Automatic Tunneling on page 47.
Because each interface is automatically assigned a link-local IP address, it is not useful to assign another link-local IP address as the default IPv6 LAN address. The default IPv6 LAN address is a site-local address. You can change this address to any other IPv6 address for LAN use.
been depreciated. However, NETGEAR has implemented a site-local address as a temporary default IPv6 LAN address that you can replace with another LAN address. The firewall restricts external communication of this default site-local address.
The IPv6 clients in the LAN can autoconfigure their own IPv6 address or obtain an IPv6 address through a DHCPv6 server. For the LAN, there are three DHCPv6 options:
The IPv6 clients in the LAN generate their own IP address by using a combination of locally available information and router advertisements, but receive DNS server information from the
Stateless DHCPv6 Server · LAN Configuration

DHCPv6 server. For stateless DHCPv6, you need to configure the RADVD and advertisement prefixes (see Configure the IPv6 Router Advertisement Daemon and Advertisement Prefixes for the LAN on page 80).
Stateless DHCPv6 Server With Prefix Delegation
As an option for a stateless DHCPv6 server, you can enable prefix delegation. The ISP’s stateful DHCPv6 server assigns a prefix that is used by the wireless VPN firewall’s stateless DHCPv6 server to assign to its IPv6 LAN clients.
Prefix delegation functions in the following way:
You need to select the Prefix Delegation check box on the ISP Broadband Settings screen for IPv6 (see Use a DHCPv6 Server to Configure an IPv6 Internet Connection on page 39).
This prefix is automatically added to the List of Prefixes to Advertise table on the LAN RADVD screen for IPv6 (see Configure the IPv6 Router Advertisement Daemon and Advertisement Prefixes for the LAN on page 80).
You need to perform the following tasks:
The IPv6 clients in the LAN obtain an interface IP address, configuration information such as DNS server information, and other parameters from the DHCPv6 server. The IP address is a dynamic address. For stateful DHCPv6, you need to configure IPv6 address pools (see IPv6 LAN Address Pools on page 77).
Stateful DHCPv6 Server · LAN Configuration

To configure the IPv6 LAN settings:

LAN Configuration

Table 13. LAN Setup screen settings for IPv6
IPv6 Address Enter the LAN IPv6 address. The default address is FEC0::1.(For more information, see the introduction to this section, Manage the IPv6 LAN.)
IPv6 Prefix Length Enter the IPv6 prefix length, for example, 10 or 64. The default prefix length is 64.
Domain Name Enter the domain name of the DHCP server.

Table 13. LAN Setup screen settings for IPv6 (continued)
Server Preference Enter the DHCP server preference value. The possible values are 0–255, with 255 as the default setting. This is an optional setting that specifies the server’s preference value in a server advertise message. The client selects the server with the highest preference value as the preferred server.
Primary DNS Server Enter the IP address of the primary DNS server for the LAN.
Secondary DNS Server Enter the IP address of the secondary DNS server for the LAN.
Lease/Rebind Time Enter the period after which the DHCP lease is renewed with the original DHCP server or rebound with another DHCP server to extend the existing DHCP lease. The default period is 86400 seconds (24 hours).
IPv6 LAN Address Pools
If you configure a stateful DHCPv6 server for the LAN, you need to add local DHCP IPv6 address pools so the DHCPv6 server can control the allocation of IPv6 addresses in the LAN.
To add an IPv6 LAN address pool:
Setting Description · DHCP Status (continued) · LAN Configuration


Table 14. LAN IPv6 Config screen settings
Start IPv6 Address Enter the start IP address. This address specifies the first of the contiguous addresses in the IP address pool. Any new DHCPv6 client joining the LAN is assigned an IP address between this address and the end IP address.
End IPv6 Address Enter the end IP address. This address specifies the last of the contiguous addresses in the IP address pool. Any new DHCPv6 client joining the LAN is assigned an IP address between the start IP address and this IP address.
Prefix Length Enter the IPv6 prefix length, for example, 10 or 64.
To edit an IPv6 LAN address pool:
To delete one or more IPv6 LAN address pools:
Setting Description · LAN Configuration

IPv6 LAN Prefixes for Prefix Delegation
If you configure a stateless DHCPv6 server for the LAN and select the Prefix Delegation check box (both on the ISP Broadband Settings screen for IPv6 and on the LAN Setup screen for IPv6, a prefix delegation pool is automatically added to the List of Prefixes for Prefix Delegation table. You can also manually add prefixes to the List of Prefixes for Prefix Delegation table to enable the DHCPv6 server to assign these prefixes to its IPv6 LAN clients.
To add an IPv6 prefix:

To edit a prefix:
To delete one or more prefixes:
LAN Configuration

stateless DHCPv6, you need to configure the Router Advertisement Deamon (RADVD) and advertisement prefixes.
The RADVD is an application that uses the Neighbor Discovery Protocol (NDP) to collect link-local advertisements of IPv6 addresses and IPv6 prefixes in the LAN. The RADVD then distributes this information in the LAN, which allows IPv6 clients to configure their own IPv6 address.
Hosts and routers in the LAN use NDP to determine the link-layer addresses and related information of neighbors in the LAN that can forward packets on their behalf. The wireless VPN firewall periodically distributes router advertisements (RAs) throughout the LAN to provide such information to the hosts and routers in the LAN. RAs include IPv6 addresses, types of prefixes, prefix addresses, prefix lifetimes, the maximum transmission unit (MTU), and so on. In addition to configuring the RADVD, you also need to configure the prefixes that are advertised in the LAN RAs.
The following table provides an overview of how information is obtained in the LAN when you have configured a stateless DHCPv6 server and the RADVD:
Table 15. DHCPv6 and RADVD interaction in the LAN
Flags in the RADVD DHCPv6 Server Provides RADVD Provides
When the Managed flag is set in the RADVD, the DHCPv6 server can assign IP addresses, and the RADVD also assigns IP addresses in the sense that it provides information that allows IPv6 clients to configure their own IPv6 address.
When the Other flag is set, the DHCPv6 server does not assign IP addresses but provides DNS server and other configuration information only.
LAN Configuration

To configure the Router Advertisement Daemon for the LAN:

Table 16. RADVD screen settings for the LAN
Setting Description · LAN Configuration

Table 16. RADVD screen settings for the LAN (continued)
Advertise Interval Enter the advertisement interval of unsolicited multicast packets in seconds. The minimum value is 10 seconds; the maximum value is 1800 seconds.
MTU The maximum transmission unit (MTU) size for a packet in one transmission over a link. The default setting is 1500.
Router Lifetime The router lifetime specifies how long the default route that was created as a result of the router advertisement should remain valid. Enter the router lifetime in seconds. This is the period that the advertised prefixes are valid for route determination. The default period is 3600 seconds (one hour). The minimum value is 30 seconds; the maximum value is 9000 seconds.
Advertisement Prefixes for the LAN
You need to configure the prefixes that are advertised in the LAN RAs. For a 6to4 address, you need to specify only the site level aggregation identifier (SLA ID) and the prefix lifetime. For a global, local, or ISATAP address, you need to specify the prefix, prefix length, and prefix lifetime.
To add an advertisement prefix for the LAN:
Setting Description · LAN Configuration


Table 17. Add Advertisement Prefix screen settings for the LAN
SLA ID Enter the site level aggregation identifier (SLA ID) for the 6to4 address prefix that should be included in the advertisement.
IPv6 Prefix Enter the IPv6 prefix for the wireless VPN firewall’s LAN that should be included in the advertisement.
IPv6 Prefix Length Enter the IPv6 prefix length (typically 64) that should be included in the advertisement.
Prefix Lifetime The prefix lifetime specifies how long the IP address that was created as a result of the router advertisement should remain valid. Enter the prefix lifetime in seconds that should be included in the advertisement. The minimum period is 0 seconds; the maximum period is 65536 seconds.
To edit an advertisement prefix:
Setting Description · LAN Configuration

To delete one or more advertisement prefixes:
If you have computers using different IPv6 networks in the LAN (for example, FEC0::2 or FEC0::1000:10), you can add aliases to the LAN ports and give computers on those networks access to the Internet, but you can do so only for the default VLAN.
The IP address that is assigned as a secondary IP address needs to be unique and cannot be assigned to a VLAN.
Make sure that any secondary LAN addresses are different from the primary LAN, WAN, and DMZ IP addresses and subnet addresses that are already configured on the wireless VPN firewall. The following is an example of correctly configured IPv6 addresses:
To add a secondary LAN IPv6 address:

LAN Configuration

The Available Secondary LAN IPs table displays the secondary LAN IP addresses added to the wireless VPN firewall.
Repeat Step 2 and Step 3 for each secondary IP address that you want to add to the Available Secondary LAN IPs table.
The hosts on the secondary subnets need to be manually configured with the IP addresses, gateway IP address, and DNS server IP addresses.
To edit a secondary LAN IP address:
To delete one or more secondary LAN IP addresses:
The demilitarized zone (DMZ) is a network that, by default, has fewer firewall restrictions than the LAN. The DMZ can be used to host servers (such as a web server, FTP server, or email server) and provide public access to them. The rightmost LAN port on the wireless VPN
LAN Configuration

firewall can be dedicated as a hardware DMZ port to safely provide services to the Internet without compromising security on your LAN.
By default, the DMZ port and both inbound and outbound DMZ traffic are disabled. Enabling the DMZ port and allowing traffic to and from the DMZ increases the traffic through the WAN ports.
Using a DMZ port is also helpful with online games and videoconferencing applications that are incompatible with NAT. The wireless VPN firewall is programmed to recognize some of these applications and to work correctly with them, but there are other applications that might not function well. In some cases, local computers can run the application correctly if those computers are used on the DMZ port.
is also physically independent of the standard firewall security component that is used for the LAN.
DMZ rules, see Configure DMZ WAN Rules on page 145 and Configure LAN DMZ Rules on page 153, respectively.
the DMZ LED next to LAN port 8 (see Front Panel on page 15) lights green to indicate that the DMZ port is enabled.
The DMZ Setup (IPv4) screen lets you set up the DMZ port for IPv4 traffic. You can enable or disable the hardware DMZ port (LAN port 8; see Front Panel on page 15) and configure an IPv4 address and subnet mask for the DMZ port.
To enable and configure the DMZ port for IPv4 traffic:
LAN Configuration


Table 18. DMZ Setup screen settings for IPv4
Do you want to enable DMZ Port?
IP Address Enter the IP address of the DMZ port. Make sure that the DMZ port IP address and LAN port IP address are in different subnets (for example, an address outside the LAN DHCP address pool, such as 192.168.1.101 when the LAN DHCP pool is 192.168.1.2–192.168.1.100). The default IP address for the DMZ port 176.16.2.1.
Setting Description · DMZ Port Setup · LAN Configuration

Table 18. DMZ Setup screen settings for IPv4 (continued)
Do you want to enable DMZ Port? (continued)
Subnet Mask Enter the IP subnet mask of the DMZ port. The subnet mask specifies the network number portion of an IP address. The subnet mask for the DMZ port is 255.255.255.0.
DHCP for DMZ Connected Computers
Disable DHCP Server If another device on your network is the DHCP server for the VLAN, or if you will
manually configure the network settings of all of your computers, select the Disable DHCP Server radio button to disable the DHCP server. This is the default setting.
Enable DHCP Server Select the Enable DHCP Server radio button to enable the wireless VPN firewall to function as a Dynamic Host Configuration Protocol (DHCP) server, providing TCP/IP configuration for all computers connected to the VLAN. Enter the following settings:
Domain Name This setting is optional. Enter the domain name of the wireless VPN firewall.
Start IP Address Enter the start IP address. This address specifies the first of the contiguous addresses in the IP address pool. Any new DHCP client joining the LAN is assigned an IP address between this address and the end IP address. The default IP address 176.16.2.100.
End IP Address Enter the end IP address. This address specifies the last of the contiguous addresses in the IP address pool. Any new DHCP client joining the LAN is assigned an IP address between the start IP address and this IP address. The default IP address 176.16.2.254.
This setting is optional. If an IP address is specified, the wireless VPN firewall provides this address as the primary DNS server IP address. If no address is specified, the wireless VPN firewall provides its own LAN IP address as the primary DNS server IP address.
This setting is optional. If an IP address is specified, the wireless VPN firewall provides this address as the secondary DNS server IP address.
WINS Server This setting is optional. Enter a WINS server IP address to specify the Windows NetBIOS server, if one is present in your network.
Lease Time Enter a lease time. This specifies the duration for which IP addresses are leased to clients.

Table 18. DMZ Setup screen settings for IPv4 (continued)
DHCP Relay To use the wireless VPN firewall as a DHCP relay agent for a DHCP server somewhere else in your network, select the DHCP Relay radio button. Enter the following setting:
Relay Gateway The IP address of the DHCP server for which the wireless VPN firewall serves as a relay.
To enable the DHCP server to provide Lightweight Directory Access Protocol (LDAP) server information, select the Enable LDAP information check box. Enter the following settings.
LDAP Server The IP address or name of the LDAP server.
Port The port number for the LDAP server. The default setting is 0 (zero).
Enable DNS Proxy This setting is optional. To enable the wireless VPN firewall to provide a LAN IP address for DNS address name resolution, select the Enable DNS Proxy check box. This check box is selected by default.
The DMZ Setup (IPv6) screen lets you set up the DMZ port for IPv6 traffic. You can enable or disable the hardware DMZ port (LAN port 8; see Front Panel on page 15) for IPv6 traffic and configure an IPv6 address and prefix length for the DMZ port.
The IPv6 clients in the DMZ can autoconfigure their own IPv6 address or obtain an IPv6 address through a DHCPv6 server.

For the DMZ, there are two DHCPv6 server options:
To enable and configure the DMZ port for IPv6 traffic:

LAN Configuration

Table 19. DMZ Setup screen settings for IPv6
Do you want to enable DMZ Port?
IPv6 Address Enter the IP address of the DMZ port. Make sure that the DMZ port IP address, LAN port IP address, and WAN port IP address are in different subnets. The default IP address for the DMZ port is 176::1.
Prefix Length Enter the IPv6 prefix length, for example, 10 or 64. The default prefix length for the DMZ port is 64.
DHCPv6 for DMZ Connected Computers
Domain Name Enter the domain name of the DHCP server.
Server Preference Enter the DHCP server preference value. The possible values are 0–255, with 255 as the default setting. This is an optional setting that specifies the server’s preference value in a server advertise message. The client selects the server with the highest preference value as the preferred server.
Setting Description · DMZ Port Setup · LAN Configuration

Table 19. DMZ Setup screen settings for IPv6 (continued)
Primary DNS Server Enter the IP address of the primary DNS server for the DMZ.
Secondary DNS Server Enter the IP address of the secondary DNS server for the DMZ.
Enter the period after which the DHCP lease is renewed with the original DHCP server or rebound with another DHCP server to extend the existing DHCP lease. The default period is 86400 seconds (24 hours).
IPv6 DMZ Address Pools
If you configure a stateful DHCPv6 server for the DMZ, you need to add local DHCP IPv6 address pools so the DHCPv6 server can control the allocation of IPv6 addresses in the DMZ.
To add an IPv6 DMZ address pool:


Table 20. DMZ IPv6 Config screen settings
Start IPv6 Address Enter the start IP address. This address specifies the first of the contiguous addresses in the IP address pool. Any new DHCPv6 client joining the DMZ is assigned an IP address between this address and the end IP address.
End IPv6 Address Enter the end IP address. This address specifies the last of the contiguous addresses in the IP address pool. Any new DHCPv6 client joining the DMZ is assigned an IP address between the start IP address and this IP address.
Prefix Length Enter the IPv6 prefix length, for example, 10 or 64.
To edit an IPv6 DMZ address pool:
To delete one or more IPv6 DMZ address pools:
stateless DHCPv6, you need to configure the Router Advertisement Deamon (RADVD) and advertisement prefixes.
The RADVD is an application that uses the Neighbor Discovery Protocol (NDP) to collect link-local advertisements of IPv6 addresses and IPv6 prefixes in the DMZ. The RADVD then distributes this information in the DMZ, which allows IPv6 clients to configure their own IPv6 address.
Setting Description · LAN Configuration

Hosts and routers in the LAN use NDP to determine the link-layer addresses and related information of neighbors in the LAN that can forward packets on their behalf. The wireless VPN firewall periodically distributes router advertisements (RAs) throughout the DMZ to provide such information to the hosts and routers in the DMZ. RAs include IPv6 addresses, types of prefixes, prefix addresses, prefix lifetimes, the maximum transmission unit (MTU), and so on. In addition to configuring the RADVD, you also need to configure the prefixes that are advertised in the DMZ RAs.
The following table provides an overview of how information is obtained in the DMZ when you have configured a stateless DHCPv6 server and the RADVD:
Table 21. DHCPv6 and RADVD interaction in the DMZ
Flags in the RADVD DHCPv6 Server Provides RADVD Provides
When the Managed flag is set in the RADVD, the DHCPv6 server can assign IP addresses, and the RADVD also assigns IP addresses in the sense that it provides information that allows IPv6 clients to configure their own IPv6 address.
When the Other flag is set, the DHCPv6 server does not assign IP addresses but provides DNS server and other configuration information only.
To configure the Router Advertisement Daemon for the DMZ:
LAN Configuration


Table 22. RADVD screen settings for the DMZ
Advertise Interval Enter the advertisement interval of unsolicited multicast packets in seconds. The minimum value is 10 seconds; the maximum value is 1800 seconds.
Setting Description · LAN Configuration

Table 22. RADVD screen settings for the DMZ (continued)
MTU The maximum transmission unit (MTU) size for a packet in one transmission over a link. The default setting is 1500.
Router Lifetime The router lifetime specifies how long the default route that was created as a result of the router advertisement should remain valid. Enter the router lifetime in seconds. This is the period that the advertised prefixes are valid for route determination. The default period is 3600 seconds (one hour). The minimum value is 30 seconds; the maximum value is 9000 seconds.
Advertisement Prefixes for the DMZ
You need to configure the prefixes that are advertised in the DMZ RAs. For a 6to4 address, you need to specify only the site level aggregation identifier (SLA ID) and the prefix lifetime. For a global, local, or ISATAP address, you need to specify the prefix, prefix length, and prefix lifetime.
To add an advertisement prefix for the DMZ:
Setting Description · LAN Configuration


Table 23. Add Advertisement Prefix screen settings for the DMZ
SLA ID Enter the site level aggregation identifier (SLA ID) for the 6to4 address prefix that should be included in the advertisement.
IPv6 Prefix Enter the IPv6 prefix for the wireless VPN firewall’s DMZ that should be included in the advertisement.
IPv6 Prefix Length Enter the IPv6 prefix length (typically 64) that should be included in the advertisement.
Prefix Lifetime The prefix lifetime specifies how long the IP address that was created as a result of the router advertisement should remain valid. Enter the prefix lifetime in seconds that should be included in the advertisement. The minimum period is 0 seconds; the maximum period is 65536 seconds.
To edit an advertisement prefix:
Setting Description · LAN Configuration

To delete one or more advertisement prefixes:
Static routes provide additional routing information to your wireless VPN firewall. Under normal circumstances, the wireless VPN firewall has adequate routing information after it has been configured for Internet access, and you do not need to configure additional static routes. You should configure static routes only for unusual cases such as multiple firewalls or multiple IP subnets located on your network.
VLANs and secondary IPv4 addresses that you have configured on the LAN Multi-homing (IPv4) screen (see Configure IPv4 Multihome LAN IP Addresses on the Default VLAN on page 65). Therefore, you do not need to manually add an IPv4 static route between a VLAN and a secondary IPv4 address.
To add an IPv4 static route to the Static Route table:

LAN Configuration


Table 24. Add Static Route screen settings for IPv4
Route Name The route name for the static route (for purposes of identification and management).
Active To make the static route effective, select the Active check box.
Private If you want to limit access to the LAN only, select the Private check box. Doing so prevents the static route from being advertised in RIP.
Destination IP Address The destination IP address of the host or network to which the route leads.
Subnet Mask The IP subnet mask of the host or network to which the route leads. If the destination is a single host, enter 255.255.255.255.
Interface From the drop-down list, select the physical or virtual network interface (WAN, VLAN, or DMZ interface) through which the route is accessible.
Gateway IP Address The gateway IP address through which the destination host or network can be reached.
Metric The priority of the route. Select a value between 2 and 15. If multiple routes to the same destination exist, the route with the lowest metric is used.
Setting Description · LAN Configuration

To edit an IPv4 static route:
To delete one or more routes:
Routing Information Protocol (RIP), RFC 2453, is an Interior Gateway Protocol (IGP) that is commonly used in internal IPv4 networks (LANs). RIP enables a router to exchange its routing information automatically with other routers, to dynamically adjust its routing tables, and to adapt to changes in the network. RIP is disabled by default. RIP does not apply to IPv6.
To enable and configure RIP:
LAN Configuration


Table 25. RIP Configuration screen settings
Setting Description · LAN Configuration

Table 25. RIP Configuration screen settings (continued)
- RIP-2B. Sends the routing data in RIP-2 format and uses subnet
broadcasting. - RIP-2M. Sends the routing data in RIP-2 format and uses multicasting.
Authentication for RIP-2B/2M required?
Authentication for RP-2B or RIP-2M is disabled by default, that is, the No radio button is selected. To enable authentication for RP-2B or RIP-2M, select the Yes radio button, and enter the settings for the following fields.
MD5 Key Id The identifier for the key that is used for authentication.
MD5 Auth Key The password that is used for MD5 authentication.
Not Valid Before The beginning of the lifetime of the MD5 key. Enter the month, date, year, hour, minute, and second. Before this date and time, the MD5 key is not valid.
Not Valid After The end of the lifetime of the MD5 key. Enter the month, date, year, hour, minute, and second. After this date and time, the MD5 key is no longer valid.
MD5 Key Id The identifier for the key that is used for authentication.
MD5 Auth Key The password that is used for MD5 authentication.
Not Valid Before The beginning of the lifetime of the MD5 key. Enter the month, date, year, hour, minute, and second. Before this date and time, the MD5 key is not valid.
Not Valid After The end of the lifetime of the MD5 key. Enter the month, date, year, hour, minute, and second. After this date and time, the MD5 key is no longer valid.

In this example, we assume the following:
When you first configured the wireless VPN firewall, two implicit static routes were created:
With this configuration, if you attempt to access a device on the 134.177.0.0 remote network, the wireless VPN firewall forwards your request to the ISP. In turn, the ISP forwards your request to the remote network, where the request is likely to be denied by the remote network’s firewall.
In this case, you need to define a static route, informing the wireless VPN firewall that the 134.177.0.0 IP address should be accessed through the local LAN IP address (192.168.1.100).
The static route on the wireless VPN firewall needs to be defined as follows:
At this time, NETGEAR’s implementation of IPv6 does not support RIP next generation (RIPng) to exchange routing information, and dynamic changes to IPv6 routes are not possible. To enable routers to exchange information over a static IPv6 route, you need to manually configure the static route information on each router.
To add an IPv6 static route to the Static Route table:
LAN Configuration



Table 26. Add IPv6 Static Routing screen settings
Route Name The route name for the static route (for purposes of identification and management).
Active To make the static route effective, select the Active check box.
IPv6 Destination The destination IPv6 address of the host or network to which the route leads.
IPv6 Prefix Length The destination IPv6 prefix length of the host or network to which the route leads.
Setting Description · LAN Configuration

Table 26. Add IPv6 Static Routing screen settings (continued)
Interface From the drop-down list, select the physical or virtual network interface (WAN1, sit0 Tunnel, LAN, or DMZ interface) through which the route is accessible.
IPv6 Gateway The gateway IPv6 address through which the destination host or network can be reached.
Metric The priority of the route. Select a value between 2 and 15. If multiple routes to the same destination exist, the route with the lowest metric is used.
To edit an IPv6 static route:
To delete one or more routes:
Setting Description · LAN Configuration

This chapter describes how to configure the wireless features of your ProSafe Wireless-N 8-Port Gigabit VPN Firewall FVS318N. This chapter includes the following sections:
Before you set up the wireless features that are described in this chapter, connect the wireless VPN firewall and get the Internet connection working. The wireless VPN firewall should work with an Ethernet WAN connection. In planning your wireless network, consider the level of security required.
If you are configuring the wireless settings from a wireless computer and you change the wireless VPN firewall’s SSID, channel, or wireless security settings, you will lose your wireless connection when you click Apply. You then need to change the wireless settings of your computer to match the wireless VPN firewall’s new settings.
The wireless VPN firewall integrates a single 2.4 GHz radio and physical access point that provides 2.4 GHz 802.11b/g/n connectivity between wired Ethernet networks and radio-equipped wireless notebook systems, desktop systems, print servers, and other devices. You can configure up to four wireless security profiles and SSIDs, allowing you to tailor access and security to a variety of wireless clients.
The wireless VPN firewall provides wireless connectivity to multiple wireless network devices within a fixed range or area of coverage—interacting with a wireless network interface card

(NIC) through an antenna. Typically, an individual in-building wireless access point provides a maximum connectivity area of about a 300-foot radius. The wireless VPN firewall can support a small group of wireless users—typically 10 to 32 users.
Configure the wireless features according to the order of the following sections:
The range of your wireless connection can vary significantly based on the location of the wireless VPN firewall. The latency, data throughput performance, and notebook power consumption of wireless adapters also vary depending on your configuration choices.
degradation or inability to wirelessly connect to the wireless VPN firewall. For complete performance specifications, see the Data Sheet at http://www.netgear.com/images/FVS318N_DS_23Aug1118-36060.pdf.
For best results, place your wireless VPN firewall according to the following general guidelines:
Wireless Configuration and Security

The radio settings apply to all wireless profiles on the wireless VPN firewall. The default wireless mode is 802.11ng. You can change the wireless mode, country, and many other radio settings on the Radio Settings screen (described in this section) and on the Advanced Wireless screen (see Configure Advanced Radio Settings on page 125). The default radio settings should work well for most configurations.
To configure the basic radio settings:

Table 27. Radio Settings screen settings
Region This is a preconfigured field that you cannot change.
Country Specify the country by making a selection from the drop-down list.
Operating Frequency This is a nonconfigurable field. The radio’s operating frequency is fixed at 2.4 GHz.
Wireless Configuration and Security
Setting Descriptions

Table 27. Radio Settings screen settings (continued)
Current Channel This is a nonconfigurable field that shows the current channel if you have selected Auto from the Channel drop-down list.
Channel Specify the channel you wish to use on your wireless LAN by making a selection from the drop-down list. The wireless channels and frequencies depend on the country and wireless mode. The default setting is Auto.
Wireless Configuration and Security
Setting Descriptions

Table 27. Radio Settings screen settings (continued)
Transmit Power This is a nonconfigurable field that shows the actual transmit power in dBm.
Transmission rate Specify the transmission data rate by making a selection from the drop-down list. The default setting is Best (Automatic).
When you have changed the country settings, the wireless VPN firewall will reboot when you click Apply.
You should not need to change the operating frequency (channel) unless you notice interference problems, or are setting up the wireless VPN firewall near another wireless access point. Observe the following guidelines:
Wireless Configuration and Security
Setting Descriptions

Indoors, computers can connect over 802.11n wireless networks at a maximum range of 300 feet. Typically, a wireless VPN firewall inside a building works best with devices within a 100 foot radius. Such distances can allow for others outside your immediate area to access your network.
Unlike wired network data, your wireless data transmissions can extend beyond your walls and can be received by anyone with a compatible adapter. For this reason, use the security features of your wireless equipment. The wireless VPN firewall provides highly effective security features that are covered in detail in this chapter. Deploy the security features appropriate to your needs.

There are several ways you can enhance the security of your wireless network:
For information about how to configure WEP, see Configure and Enable Wireless Profiles on page 115.
Wireless Configuration and Security

Cipher Block Chaining Message Authentication Code Protocol (CCMP) encryption. The very strong authentication along with dynamic per frame rekeying of WPA make it virtually impossible to compromise. The wireless VPN firewall supports WPA with a pre-shared key (PSK), RADIUS, or a combination of PSK and RADIUS.
For more information about how to configure WPA, see Configure and Enable Wireless Profiles on page 115.
For more information about how to configure WPA2, see Configure and Enable Wireless Profiles on page 115.
For more information about how to configure WPA+WPA2 mixed mode, see Configure and Enable Wireless Profiles on page 115.
recommends WPA2 with CCMP to make use of 802.11n rates and speed.
Wireless security profiles, hereafter referred to as wireless profiles, let you configure unique security settings for each SSID on the wireless VPN firewall. The wireless VPN firewall supports up to four wireless profiles (BSSIDs) that you can configure from the Wireless Profiles screen (see Configure and Enable Wireless Profiles on page 115).
Wireless Configuration and Security

Each wireless profile provides the following features:
To set up a wireless profile, specify a name for the profile and the SSID, specify the type of security with authentication and data encryption, and specify whether the SSID is broadcast.
For information about the types of network authentication that the wireless VPN firewall supports, see Configure and Enable Wireless Profiles on page 115.
Some concepts and guidelines regarding the SSID are:
Wireless Configuration and Security

For a new wireless network, print or copy the following form and fill in the settings. For an existing wireless network, the network administrator can provide this information. Be sure to set the Country/Region correctly as the first step
Store this information in a safe place:
The SSID in the wireless access point is the SSID you configure on the wireless adapter card. All wireless nodes in the same network need to be configured with the same SSID.
Record the WPA2-PSK passphrase:
Wireless Configuration and Security

To add a wireless profile:

The following table explains the fields of the Wireless Profiles screen:
Table 28. Wireless Profiles screen settings
Status The status of the profile: Enabled or Disabled.
Profile The unique name of the wireless profile that makes it easy to recognize the profile.
SSID The wireless network name (SSID) for the wireless profile.
Broadcast Indicates whether the SSID is broadcast. A green circle indicates that the SSID is broadcast; a gray circle indicates that it is not.
Security The configured security method for the wireless profile.
Encryption The configured encryption method for the wireless profile.
Authentication The configured authentication method for the wireless profile.
Active Time Indicates whether the timer for the wireless profile is activated (Yes or No).
Start Time The start time for the timer.
Stop Time The stop time for the timer.
Wireless Configuration and Security
Setting Description


Table 29. Add Wireless Profiles screen settings
Profile Name The name for the default wireless profile is default1. You cannot change this name. For additional profiles, enter a unique name to make it easy to recognize the profile. You can enter a name of up to 32 alphanumeric characters.
Wireless Configuration and Security
Setting Description · Wireless Profile Configuration

Table 29. Add Wireless Profiles screen settings (continued)
SSID The wireless network name (SSID) for the wireless profile. The default SSID name is FVS318N_1. You can change this name by entering up to 32 alphanumeric characters. Make sure that additional SSIDs have unique names.
Broadcast SSID Select the check box to enable the wireless VPN firewall to broadcast its SSID, allowing wireless stations that have a null (blank) SSID to adopt the wireless VPN firewall’s SSID. To prevent the SSID from being broadcast, clear the check box.
Security Note: Before you configure security, you might want to read Wireless Data Security Options on page 111.
Specify the wireless security by making a selection from the drop-down list: • OPEN. This is the default setting. An open system has no authentication and no encryption, and therefore no security configuration. However, you can use an open system with encryption. To do so, select WEP from the Security drop-down list. In the WEP Index and Keys section of the screen, take the following steps:
- Select Open System authentication. - Select the encryption. - Enter a passphrase and generate a key, or enter a key manually. • WEP. To configure WEP, take the following steps in the WEP Index and Keys section of the screen:
- Select Shared Key authentication. - Select the encryption. - Enter a passphrase and generate a key, or enter a key manually. • WPA. To configure WPA, select the encryption and authentication. The remaining configuration depends on the selected authentication:
- For WPA-PSK, select a password. - For WPA with RADIUS, configure the RADIUS server settings. - For WPA with PSK+RADIUS, select a password and configure the
RADIUS server settings. • WPA2. To configure WPA2, select the encryption and authentication. The remaining configuration depends on the selected authentication:
- For WPA2-PSK, select a password. - For WPA2 with RADIUS, configure the RADIUS server settings. As an
option, you can enable RADIUS preauthentication. - For WPA2 with PSK+RADIUS, select a password and configure the
RADIUS server settings. As an option, you can enable RADIUS preauthentication. • WPA+WPA2. To configure WPA, select the encryption and authentication. The remaining configuration depends on the selected authentication:
- For WPA+WPA2 with PSK, select a password. - For WPA+WPA2 with RADIUS, configure the RADIUS server settings. - For WPA+WPA2 with PSK+RADIUS, select a password and configure the
RADIUS server settings.
Wireless Configuration and Security
Setting Description

Table 29. Add Wireless Profiles screen settings (continued)
For WPA, WPA2, and WPA+WPA2 only, if you have selected PSK or PSK+RADIUS authentication, enter a pre-shared key or password.
For WPA2 only, if you have selected RADIUS authentication, configure preauthentication by selecting the check box. Preauthentication allows a client to roam from one access point to another access point without having to be reauthenticated.
For WPA, WPA2, and WPA+WPA2 only, if you have selected RADIUS or PSK+RADIUS authentication, click the Radius Server Settings link to configure the RADIUS settings (see RADIUS Client and Server Configuration on page 240).
VLAN From the drop-down list, select the VLAN to which the wireless profile should be allocated.
VLAN Profiles Click the VLAN Profiles link to configure a VLAN profile (see Configure a VLAN Profile on page 59).
Active Time To enable the timer, select the Active Time check box. When the timer is enabled, the wireless profile is turned off from the start time until the stop time. To disable the timer, clear the check box.
Start Time Specify the start hour in the Hours field and the start minute in the Minutes field, and then select AM or PM from the drop-down list.
Stop Time Specify the stop hour in the Hours field and the stop minute in the Minutes field, and then select AM or PM from the drop-down list.
WLAN Partition To enable wireless client separation and prevent wireless clients that are connected to this wireless profile from communicating with each other, select the WLAN Partition check box. To disable wireless client separation, clear the check box. By default, WLAN partition is disabled.
Wireless Configuration and Security

Table 29. Add Wireless Profiles screen settings (continued)
WEP Index and Keys
Passphrase Enter a passphrase. The passphrase length needs to be between 8 and 63 characters (inclusive). The secret passphrase allows you to automatically generate the keys by clicking Generate.
If you use a wireless computer to configure wireless security settings, you will be disconnected when you click Apply. Reconfigure your wireless computer to match the new settings, or access the wireless VPN firewall from a wired computer to make further changes.
Protected Setup on page 123.
Wireless Configuration and Security
Setting Description · Encryption Key (Key1–Key4)

To edit a wireless profile:
you edit the wireless profile.
To delete one or more wireless profiles:
you delete the wireless profile.
To enable or disable one or more wireless profiles:
For increased security, you can restrict access to an SSID by allowing access to only specific computers or wireless stations based on their MAC addresses. You can restrict access to only trusted computers so that unknown computers cannot wirelessly connect to the wireless VPN firewall. MAC address filtering adds an obstacle against unwanted access to your network, but the data broadcast over the wireless link is fully exposed.
on the wireless adapter.
Wireless Configuration and Security

To allow or restrict access based on MAC addresses:

Wireless Configuration and Security

When you configure the wireless VPN firewall from a wireless computer whose MAC address is not in the access control list and when the ACL policy status is set to deny access, you will lose your wireless connection when you click Apply. You then need to access the wireless VPN firewall from a wired computer or from a wireless computer that is on the access control list to make any further changes.
To remove one or more MAC addresses from the table:
To view the status of a specific wireless profile:
On the Wireless Profiles screen (see Figure 56 on page 115), click the Status button in the Status column for the wireless profile for which you want to display the status information. The Wireless Profile Status screen displays:

To change the poll interval period, enter a new value in the Poll Interval field, and then click Set interval. To stop polling, click Stop.
The following table explains the fields of the Wireless Profile Status screen.
Wireless Configuration and Security

Table 30. Wireless Profile Status screen fields
Profile Name The name of the wireless profile.
Radio The radio to which the client is connected. By default, the radio is always 1, indicating the 2.4 GHz radio.
Packet The number of received (rx) and transmitted (tx) packets on the access point in bytes.
Bytes The number of received (rx) and transmitted (tx) bytes on the access point.
Errors The number of received (rx) and transmitted (tx) errors on the access point.
Dropped The number of received (rx) and transmitted (tx) dropped packets on the access point.
Multicast The number of received (rx) and transmitted (tx) multicast packets on the access point.
Collisions The number of signal collisions that have occurred on the access point. A collision occurs when the access point attempts to send data at the same time as a wireless station that is connected to the access point.
MAC Address The MAC address of the client.
Radio The radio to which the client is connected. By default, the radio is always 1, indicating the 2.4 GHz radio.
Security The type of security that the client is using (Open, WEP, WPA, WPA2, or WPA+WPA2).
Encryption The type of encryption that the client is using (CCMP, TKIP, or TKIP + CCMP).
Authentication The type of authentication that the client is using (Open, PSK, RADIUS, or PSK+RADIUS).
The period in minutes since the connection was established between the access point and the client.
Push 'N' Connect using Wi-Fi Protected Setup™ (WPS) allows you to connect computers to a secure wireless network with WPA or WPA2 wireless security. The wireless VPN firewall automatically sets security for each computer or device that uses WPS to join the wireless network. To use WPS, make sure that your wireless devices are Wi-Fi certified and support WPS. NETGEAR products that use WPS call it Push 'N' Connect.
You can use a WPS button or the wireless router interface method to add wireless computers and devices to your wireless network.
go to http://www.wi-fi.org.
Wireless Configuration and Security

To enable WPS and initiate the WPS process on the wireless VPN firewall:

a. Collect the pin of the wireless device.
b. In the Station PIN field, enter the pin.
c. Click the PIN button.
Wireless Configuration and Security

a. Click the PBC button.
b. Within 2 minutes, press the WPS button on your wireless device to enable the
device to connect to the wireless VPN firewall, or follow the WPS instructions that came with the device.
With either method, the wireless VPN firewall tries to communicate with the wireless device, set the wireless security for the wireless device, and allow it to join the wireless network.
To configure advanced radio settings:

Wireless Configuration and Security

Table 31. Advanced Wireless screen settings
Beacon Interval Enter an interval between 40 ms and 3500 ms for each beacon transmission, which allows the wireless VPN firewall to synchronize the wireless network. The default setting is 100.
DTIM Interval Enter the Delivery Traffic Indication Message (DTIM) interval, also referred to as the data beacon rate, which indicates the period for the beacon DTIM in multiples of beacon intervals. This value needs to be between 1 and 255. The default setting is 2.
RTS Threshold Enter the Request to Send (RTS) threshold. The default setting is 2346 bytes. If the packet size is equal to or less than the RTS threshold, the wireless VPN firewall uses the Carrier Sense Multiple Access with Collision Detection (CSMA/CD) mechanism, and the data frame is transmitted immediately after the silence period. If the packet size is larger than the RTS threshold, the wireless VPN firewall uses the CSMA with Collision Avoidance (CSMA/CA) mechanism. In this situation, the transmitting station sends an RTS packet to the receiving station and waits for the receiving station to return a Clear to Send (CTS) packet before sending the actual packet data. This method improves the performance but reduces the throughput.
Fragmentation Threshold Enter the maximum packet size that is used for the fragmentation of data packets. Packets that are larger than the specified fragmentation length are broken up into smaller packets before being transmitted. The fragmentation threshold needs to be an even number. The default setting is 2346 bytes.
Power Save Enable To enable the Wi-Fi Multimedia (WMM) Powersave feature, select the Power Save Enable check box. This feature saves power for battery-powered equipment by increasing the efficiency and flexibility of data transmission. Clear the check box to disable the feature, which is the default setting.
Wireless Configuration and Security
Setting Description

After you have configured the wireless VPN firewall as explained in the previous sections, test your wireless clients for wireless connectivity before you place the wireless VPN firewall at its permanent position.
To test for wireless connectivity:
If you have trouble connecting to the wireless VPN firewall, try to connect without security by selecting OPEN from the Security drop-down list on the Edit Wireless Profiles screen for the profile that you are using. If that does not help you to solve the connection problem, see Chapter 11, Troubleshooting.
Wireless Configuration and Security

This chapter describes how to use the firewall features of the wireless VPN firewall to protect your network. The chapter contains the following sections:
A firewall 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. You can further segment keyword blocking to certain known groups. For information about how to set up LAN groups, see Manage IPv4 Groups and Hosts (IPv4 LAN Groups) on page 67.
For IPv4, a firewall incorporates the functions of a Network Address Translation (NAT) router, protects the trusted network from hacker intrusions or attacks, and controls the types of traffic that can flow between the Internet, DMZ, and LAN. Unlike simple NAT routers, a firewall uses a process called stateful packet inspection to protect your network from attacks and intrusions. NAT performs a 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.
For IPv6, which in itself provides stronger security than IPv4, a firewall in particular controls the exchange of traffic between the Internet, DMZ, and LAN.
Consider the following operational items:
- Services (see Outbound Rules (Service Blocking) on page 130 and Inbound Rules (Port Forwarding) on page 133)
- Schedules (see Set a Schedule to Block or Allow Specific Traffic on page 182)
- Allowing or blocking sites (see Configure Content Filtering on page 178)
- Source MAC filtering (see Enable Source MAC Filtering on page 183)
- Port triggering (see Configure Port Triggering on page 190)
Firewall rules are used to block or allow specific traffic passing through from one side to the other. You can configure up to 800 firewall rules on the wireless VPN firewall (see the following table). 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.
Firewall Protection

A firewall has two default rules, one for inbound traffic and one for outbound. The default rules of the wireless VPN firewall are:
The firewall rules for blocking and allowing traffic on the wireless VPN firewall can be applied to LAN WAN traffic, DMZ WAN traffic, and LAN DMZ traffic.
Table 32. Number of supported firewall rule configurations
Traffic Rule Maximum Number of Outbound Rules
Maximum Number of Inbound Rules
Maximum Number of Supported Rules
DMZ WAN 50 50 100
LAN DMZ 50 50 100
Total Rules 400 400 800
The rules to block or allow traffic are based on the traffic’s category of service:
The wireless VPN firewall allows you to block the use of certain Internet services by computers on your network. This is called service blocking or port filtering.
to block outbound traffic from selected computers that would otherwise be allowed by the firewall.
Firewall Protection

The following table describes the fields that define the rules for outbound traffic and that are common to most Outbound Service screens (see Figure 65 on page 141, Figure 71 on page 148, and Figure 77 on page 155).
The steps to configure outbound rules are described in the following sections:
Table 33. Outbound rules overview
Setting Description Outbound Rules
Service The service or application to be covered by this rule. If the service or application does not display in the list, you need to define it using the Services screen (see Add Customized Services on page 172).
All rules when BLOCK by schedule, otherwise allow or ALLOW by schedule, otherwise block is selected as the action.
LAN WAN rules LAN DMZ rules
All rules · All rules · Firewall Protection

Table 33. Outbound rules overview (continued)
Setting Description Outbound Rules
LAN WAN rules DMZ WAN rules
DMZ WAN rules LAN DMZ rules
QoS Priority The priority assigned to IP packets of this service. The priorities are defined by Type of Service in the Internet Protocol Suite standards, RFC 1349. The QoS profile determines the priority of a service, which, in turn, determines the quality of that service for the traffic passing through the firewall. The wireless VPN firewall marks the Type of Service (ToS) field as defined in the QoS profiles that you create. For more information, see Preconfigured Quality of Service Profiles on page 177.
LAN WAN rules DMZ WAN rules
Bandwidth Profile Bandwidth limiting determines how the data is sent to and from your host. The purpose of bandwidth limiting is to provide a solution for limiting the outgoing and incoming traffic, thus preventing the LAN users from consuming all the bandwidth of the Internet link. For more information, see Create Bandwidth Profiles on page 175. For outbound traffic, you can configure bandwidth limiting only on the WAN interface for a LAN WAN rule.
IPv4 LAN WAN rules
Firewall Protection

Table 33. Outbound rules overview (continued)
Setting Description Outbound Rules
IPv4 LAN WAN rules IPv4 DMZ WAN rules
If you have enabled Network Address Translation (NAT), your network presents one IP address only to the Internet, and outside users cannot directly access any of your local computers (LAN users). (For information about configuring NAT, see Network Address Translation on page 27.) 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 informs the firewall to direct inbound traffic for a particular service to one local server based on the destination port number. This process is also known as port forwarding.
Allowing inbound services opens security holes in your network. Enable only those ports that are necessary for your network.
Whether or not DHCP is enabled, how the computer accesses the server’s LAN address impacts the inbound rules. For example:
All rules · Firewall Protection

LAN Groups screen to keep the computer’s IP address constant (see Set Up DHCP Address Reservation on page 72).
allow certain types of inbound traffic that would otherwise be blocked by the firewall.
attacks. A DoS attack does not attempt to steal data or damage your computers, but overloads your Internet connection so you cannot use it (that is, the service becomes unavailable).
selected on the Attack Checks screen (which they are by default; see Attack Checks on page 166), multiple concurrent connections of the same application from one host or IP address (such as multiple DNS queries from one computer) trigger the wireless VPN firewall’s DoS protection.
The following table describes the fields that define the rules for inbound traffic and that are common to most Inbound Service screens (see Figure 67 on page 144, Figure 73 on page 151, and Figure 79 on page 157).
The steps to configure inbound rules are described in the following sections:
Firewall Protection

Table 34. Inbound rules overview
Setting Description Inbound Rules
Service The service or application to be covered by this rule. If the service or application does not display in the list, you need to define it using the Services screen (see Add Customized Services on page 172).
All rules when BLOCK by schedule, otherwise allow or ALLOW by schedule, otherwise block is selected as the action.
IPv4 LAN WAN rules
Send to DMZ Server The DMZ server address determines which computer on your network is hosting this service rule. (You can also translate this address to a port number.)
IPv4 DMZ WAN rules
Translate to Port Number
If the LAN server or DMZ server that is hosting the service is using a port other than the default port for the service, you can enable this setting and specify a port number. If the service is using the default port, you do not need to enable this setting.
IPv4 LAN WAN rules IPv4 DMZ WAN rules
WAN Destination IP Address
The setting that determines the destination IP address applicable to incoming traffic. This is the public IP address that maps to the internal LAN server. This can be either the address of the WAN interface or another public IP address. You also have the option to enter an address range. Enter the required addresses in the Start and Finish fields to apply the rule to a range of devices.
IPv4 LAN WAN rules IPv4 DMZ WAN rules
All rules · All rules · Firewall Protection

Table 34. Inbound rules overview (continued)
Setting Description Inbound Rules
LAN WAN rules LAN DMZ rules
LAN WAN rules DMZ WAN rules
DMZ WAN rules LAN DMZ rules
Bandwidth Profile Bandwidth limiting determines how the data is sent to and from your host. The purpose of bandwidth limiting is to provide a solution for limiting the outgoing and incoming traffic, thus preventing the LAN users from consuming all the bandwidth of the Internet link. For more information, see Create Bandwidth Profiles on page 175. For inbound traffic, you can configure bandwidth limiting only on the LAN interface for a LAN WAN rule.
IPv4 LAN WAN rules
All rules · Firewall Protection

any server processes (such as a web or FTP server) from your location. Your ISP might periodically check for servers and might suspend your account if it discovers any active servers at your location. If you are unsure, see the acceptable use policy of your ISP.
As you define a new rule, it is added to a table in a Rules screen as the last item in the list, as shown in the following figure, which shows the LAN WAN Rules screen for IPv4 as an example:

For any traffic attempting to pass through the firewall, the packet information is subjected to the rules in the order shown in the Outbound Services and Inbound Services tables, beginning at the top and proceeding to the bottom. In some cases, the order of precedence of two or more rules might 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 table buttons in the Action column allow you to relocate a defined rule to a new position in the table.
Firewall Protection

The default outbound policy is to allow all traffic to the Internet to pass through. Firewall rules can then be applied to block specific types of traffic from going out from the LAN to the Internet (outbound). This feature is also referred to as service blocking. You can change the default policy of Allow Always to Block Always to block all outbound traffic, which then allows you to enable only specific services to pass through the wireless VPN firewall.
To change the default outbound policy for IPv4 traffic or to change existing IPv4 rules:

To change an existing outbound or inbound service rule, in the Action column to the right of the rule, click one of the following table buttons:
Firewall Protection

- Edit LAN WAN Outbound Service screen for IPv4 (identical to Figure 65 on page 141)
- Edit LAN WAN Inbound Service screen for IPv4 (identical to Figure 67 on page 144)
To change the default outbound policy for IPv6 traffic or to change existing IPv6 rules:

To change an existing outbound or inbound service rule, in the Action column to the right of the rule, click one of the following table buttons:
- Edit LAN WAN Outbound Service screen for IPv6 (identical to Figure 66 on page 142)
- Edit LAN WAN Inbound Service screen for IPv6 (identical to Figure 68 on page 145)
Firewall Protection

To enable, disable, or delete one or more IPv4 or IPv6 rules:
You can define rules that 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. An outbound rule can block or allow traffic between an internal IP LAN address and any external WAN IP address according to the schedule created on the Schedule screen.
Make sure that you understand the consequences of a LAN WAN outbound rule before you apply the rule. Incorrect configuration might cause serious connection problems.
You can also tailor these rules to your specific needs (see Administrator Tips on page 129).
IPv4 LAN WAN Outbound Rules
To create a new IPv4 LAN WAN outbound rule:
Click the Add table button under the Outbound Services table. The Add LAN WAN Outbound Service screen for IPv4 displays:
Firewall Protection


Unless your selection from the Action drop-down list is BLOCK always, you also need to make selections from the following drop-down lists:
Firewall Protection

IPv6 LAN WAN Outbound Rules
To create a new IPv6 LAN WAN outbound rule:

Unless your selection from the Action drop-down list is BLOCK always, you also need to make a selection from the following drop-down lists:
Firewall Protection

The Inbound Services table lists all existing rules for inbound traffic. If you have not defined any rules, no rules are listed. By default, all inbound traffic (from the Internet to the LAN) is blocked. Remember that allowing inbound services opens potential security holes in your firewall. Enable only those ports that are necessary for your network.
Make sure that you understand the consequences of a LAN WAN inbound rule before you apply the rule. Incorrect configuration might cause serious connection problems. If you are configuring the wireless VPN firewall from a remote connection, you might be locked out.
IPv4 LAN WAN Inbound Service Rules
To create a new IPv4 LAN WAN inbound rule:
Click the Add table button under the Inbound Services table. The Add LAN WAN Inbound Service screen for IPv4 displays (see the next figure).
Unless your selection from the Action drop-down list is BLOCK always, you also need to make selections from the following drop-down lists:
The following configuration is optional:
Firewall Protection


IPv6 LAN WAN Inbound Rules
To create a new IPv6 LAN WAN inbound rule:
Firewall Protection


Unless your selection from the Action drop-down list is BLOCK always, you also need to make a selection from the following drop-down list:
The firewall rules for traffic between the DMZ and the Internet are configured on the DMZ WAN Rules screen. The default outbound policy is to block all traffic from and to the Internet. You can then apply firewall rules to allow specific types of traffic either going out from the DMZ to the Internet (outbound) or coming in from the Internet to the DMZ (inbound).
There is no drop-down list that lets you set the default outbound policy as there is on the LAN WAN Rules screen. You can change the default outbound policy by enabling all outbound traffic and then blocking only specific services from passing through the wireless VPN firewall. You do so by adding outbound services rules (see Create DMZ WAN Outbound Service Rules on page 148).
Firewall Protection

inbound rules on the DMZ WAN Rules screen. When an inbound packet matches an inbound rule on the LAN WAN Rules screen, the packet is not matched against the inbound rules on the DMZ WAN Rules screen.
To access the DMZ WAN Rules screen for IPv4 or to change existing IPv4 rules:
Select Security > Firewall > DMZ WAN Rules. In the upper right of the screen, the IPv4 radio button is selected by default. The DMZ WAN Rules screen displays the IPv4 settings. (The following figure contains examples.)

To change an existing outbound or inbound service rule, in the Action column to the right of the rule, click one of the following table buttons:
- Edit DMZ WAN Outbound Service screen for IPv4 (identical to Figure 71 on page 148)
- Edit DMZ WAN Inbound Service screen for IPv4 (identical to Figure 73 on page 151)
Firewall Protection

To access the DMZ WAN Rules screen for IPv6 or to change existing IPv6 rules:

To change an existing outbound or inbound service rule, in the Action column to the right of the rule, click one of the following table buttons:
- Edit DMZ WAN Outbound Service screen for IPv6 (identical to Figure 72 on page 149)
- Edit DMZ WAN Inbound Service screen for IPv6 (identical to Figure 74 on page 152)
To enable, disable, or delete one or more IPv4 or IPv6 rules:
Firewall Protection

You can change the default outbound policy or define rules that specify exceptions to the default outbound policy. 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. An outbound rule can block or allow traffic between the DMZ and any external WAN IP address according to the schedule created on the Schedule screen.
IPv4 DMZ WAN Outbound Service Rules
To create a new IPv4 DMZ WAN outbound rule:
Click the Add table button under the Outbound Services table. The Add DMZ WAN Outbound Service screen for IPv4 displays:

Firewall Protection

Unless your selection from the Action drop-down list is BLOCK always, you also need to make selections from the following drop-down lists:
IPv6 DMZ WAN Outbound Service Rules
To create a new IPv6 DMZ WAN outbound rule:

Firewall Protection

Unless your selection from the Action drop-down list is BLOCK always, you also need to make selections from the following drop-down lists:
The Inbound Services table lists all existing rules for inbound traffic. If you have not defined any rules, no rules are listed. By default, all inbound traffic (from the Internet to the DMZ) is blocked.
Inbound rules that are configured on the LAN WAN Rules screen take precedence over inbound rules that are configured on the DMZ WAN Rules screen. As a result, if an inbound packet matches an inbound rule on the LAN WAN Rules screen, it is not matched against the inbound rules on the DMZ WAN Rules screen.
IPv4 DMZ WAN Inbound Service Rules
To create a new IPv4 DMZ WAN inbound rule:
Click the Add table button under the Inbound Services table. The Add DMZ WAN Inbound Service screen for IPv4 displays:
Firewall Protection


Unless your selection from the Action drop-down list is BLOCK always, you also need to make selections from the following drop-down lists:
The following configuration is optional:
Firewall Protection

IPv6 DMZ WAN Inbound Service Rules
To create a new IPv6 DMZ WAN inbound rule:

Unless your selection from the Action drop-down list is BLOCK always, you also need to make selections from the following drop-down list:
Firewall Protection

The LAN DMZ Rules screen allows you to create rules that define the movement of traffic between the LAN and the DMZ. The default outbound and inbound policies are to block all traffic between the local LAN and DMZ network. You can then apply firewall rules to allow specific types of traffic either going out from the LAN to the DMZ (outbound) or coming in from the DMZ to the LAN (inbound).
There is no drop-down list that lets you set the default outbound policy as there is on the LAN WAN Rules screen. You can change the default outbound policy by allowing all outbound traffic and then blocking specific services from passing through the wireless VPN firewall. You do so by adding outbound service rules (see Create LAN DMZ Outbound Service Rules on page 155).
To access the LAN DMZ Rules screen for IPv4 or to change existing IPv4 rules:
Select Security > Firewall > LAN DMZ Rules. In the upper right of the screen, the IPv4 radio button is selected by default. The LAN DMZ Rules screen displays the IPv4 settings. (The following figure contains examples.)

To change an existing outbound or inbound service rule, in the Action column to the right of the rule, click one of the following table buttons:
Firewall Protection

- Edit LAN DMZ Outbound Service screen for IPv4 (identical to Figure 77 on page 155)
- Edit LAN DMZ Inbound Service screen for IPv4 (identical to Figure 79 on page 157)
To access the LAN DMZ Rules screen for IPv6 or to change existing IPv6 rules:

To change an existing outbound or inbound service rule, in the Action column to the right of the rule, click one of the following table buttons:
- Edit LAN DMZ Outbound Service screen for IPv6 (identical to Figure 78 on page 156)
- Edit LAN DMZ Inbound Service screen for IPv6 (identical to Figure 80 on page 158)
To enable, disable, or delete one or more IPv4 or IPv6 rules:
Firewall Protection

You can change the default outbound policy or define rules that specify exceptions to the default outbound policy. 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. An outbound rule can block or allow traffic between the DMZ and any internal LAN IP address according to the schedule created on the Schedule screen.
IPv4 LAN DMZ Outbound Service Rules
To create a new IPv4 LAN DMZ outbound rule:
Click the Add table button under the Outbound Services table. The Add LAN DMZ Outbound Service screen for IPv4 displays:

Firewall Protection

Unless your selection from the Action drop-down list is BLOCK always, you also need to make a selection from the following drop-down list:
IPv6 LAN DMZ Outbound Service Rules
To create a new IPv6 LAN DMZ outbound rule:

Firewall Protection

Unless your selection from the Action drop-down list is BLOCK always, you also need to make a selection from the following drop-down list:
The Inbound Services table lists all existing rules for inbound traffic. If you have not defined any rules, no rules are listed. By default, all inbound traffic (from the LAN to the DMZ) is blocked.
IPv4 LAN DMZ Inbound Service Rules
To create a new IPv4 LAN DMZ inbound rule:
Click the Add table button under the Inbound Services table. The Add LAN DMZ Inbound Service screen for IPv4 displays:

Firewall Protection

Unless your selection from the Action drop-down list is BLOCK always, you also need to make a selection from the following drop-down list:
IPv6 LAN DMZ Inbound Service Rules
To create a new IPv6 LAN DMZ inbound rule:

Unless your selection from the Action drop-down list is BLOCK always, you also need to make a selection from the following drop-down list:
Firewall Protection

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 the day.

Firewall Protection

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 (see the following figure). In the example, CU-SeeMe connections are allowed only from a specified range of external IP addresses.

Firewall Protection

IPv4 LAN WAN or IPv4 DMZ WAN Inbound Rule: Set Up One-to-One NAT Mapping
In this example, multi-NAT is configured to support multiple public IP addresses on one WAN interface. An inbound rule configures the wireless VPN firewall to host an additional public IP address and associate this address with a web server on the LAN.
The following addressing scheme is used to illustrate this procedure:
- WAN IP address. 10.1.0.118
- LAN IP address subnet. 192.168.1.1 with subnet 255.255.255.0
- DMZ IP address subnet. 192.168.10.1 with subnet 255.255.255.0
- LAN IP address. 192.168.1.2
- DMZ IP address. 192.168.10.2
- Access to the web server is the (simulated) public IP address. 10.1.0.52
your use, you can use the additional public IP addresses to map to servers on your LAN or DMZ. One of these public IP addresses is used as the primary IP address of the router that provides Internet access to your LAN computers through NAT. The other addresses are available to map to your servers.
To configure the wireless VPN firewall for additional IP addresses:
Click the Add table button under the Inbound Services table. The Add LAN WAN Inbound Service screen displays:
Firewall Protection


To test the connection from a computer on the Internet, type http://<IP_address>, in which <IP_address> is the public IP address that you have mapped to your web server in Step 7. You should see the home page of your web server.
Firewall Protection

IPv4 LAN WAN or IPv4 DMZ WAN Inbound Rule: 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.
Do not set up an exposed host from a remote connection because you will likely lock yourself out from the wireless VPN firewall.
To expose one of the computers on your LAN or DMZ as this host:
See an example in the following figure.

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.
Firewall Protection

If you want to restrict incoming RTelnet sessions from a single IPv6 WAN user to a single IPv6 LAN user, specify the initiating IPv6 WAN address and the receiving IPv6 LAN address. See an example in the following figure.

Outbound rules let you prevent users from using applications such as Instant Messenger, Real Audio, or other nonessential sites.
If you want to block Instant Messenger usage by employees during working hours, you can create an outbound rule to block such an application from any internal IP address to any external address according to the schedule that you have created on the Schedule screen. The schedule should specify working hours.
You can also enable the wireless VPN firewall to log any attempt to use Instant Messenger during the blocked period. See an example in the following figure.
Firewall Protection


If you want to allow a group of DMZ users to access a particular FTP site on the Internet during working hours, you can create an outbound rule to allow such traffic by specifying the IPv6 DMZ start and finish addresses and the IPv6 WAN address. On the Schedule screen, create a schedule that specifies working hours, and assign it to the rule.
You can also configure the QoS profile to maximize the throughput. See an example in the following figure.
Firewall Protection


You can configure attack checks, set session limits, and manage the application level gateway (ALG) for SIP sessions.
The Attack Checks screen allows you to specify whether the wireless VPN firewall should be protected against common attacks in the DMZ, LAN, and WAN networks. The various types of IPv4 attack checks are listed on the Attack Checks screen and defined in Table 35 on page 167. For IPv6, the only options are to specify whether to allow a ping on the WAN port and whether to allow VPN pass-through for IPSec.
Firewall Protection

To enable IPv4 attack checks for your network environment:

Table 35. Attack Checks screen settings for IPv4
Respond to Ping on Internet Ports
Select the Respond to Ping on Internet Ports check box to enable the wireless VPN firewall to respond to a ping from the Internet to its IPv4 address. A ping can be used as a diagnostic tool. Keep this check box cleared unless you have a specific reason to enable the wireless VPN firewall to respond to a ping from the Internet.
Enable Stealth Mode Select the Enable Stealth Mode check box (which is the default setting) to prevent
the wireless VPN firewall from responding to port scans from the WAN, thus making it less susceptible to discovery and attacks.
Block TCP flood Select the Block TCP flood check box (which is the default setting) to enable the wireless VPN firewall to drop all invalid TCP packets and to protect the wireless VPN firewall from a SYN flood attack. A SYN flood is a form of denial of service attack in which an attacker sends a succession of SYN (synchronize) requests to a target system. When the system responds, the attacker does not complete the connections, thus leaving the connection half open and flooding the server with SYN messages. No legitimate connections can then be made.

Table 35. Attack Checks screen settings for IPv4 (continued)
Block UDP flood Select the Block UDP flood check box (which is the default setting) to prevent the wireless VPN firewall from accepting more than 20 simultaneous, active User Datagram Protocol (UDP) connections from a single device on the LAN. A UDP flood is a form of denial of service attack that can be initiated when one device sends a large number of UDP packets to random ports on a remote host. As a result, the distant host does the following:
When the victimized system is flooded, it is forced to send many ICMP packets, eventually making it unreachable by other clients. The attacker might also spoof the IP address of the UDP packets, ensuring that the excessive ICMP return packets do not reach the attacker, thus making the attacker’s network location anonymous.
Disable Ping Reply on LAN Ports
Select the Disable Ping Reply on LAN Ports check box to prevent the wireless VPN firewall from responding to a ping on a LAN port. A ping can be used as a diagnostic tool. Keep this check box cleared unless you have a specific reason to prevent the wireless VPN firewall from responding to a ping on a LAN port.
Enable IGMP IP multicast pass-through allows multicast packets that originate in the WAN, such as packets from a media streaming or gaming application, to be forwarded to the LAN subnet. Internet Group Management Protocol (IGMP) is used to support multicast between IP hosts and their adjacent neighbors. Select the Enable IGMP check box to enable IP multicast pass-through. By default, IP multicast pass-through is disabled.

Table 35. Attack Checks screen settings for IPv4 (continued)
Jumbo frames allow multiple smaller packets to be combined into a single larger packet, reducing network overhead and increasing data transfer performance. Jumbo frames are supported on ports 1, 2, 3, and 4 only. Select the Jumbo Frame check box to enable jumbo frames. By default, jumbo frames are disabled.
To enable IPv6 attack checks for your network environment:


The session limits feature allows you to specify the total number of sessions that are allowed, per user, over an IPv4 connection across the wireless VPN firewall. The session limits feature is disabled by default.
To enable and configure session limits:

Table 36. Session Limit screen settings
Setting Description · Session Limit · Firewall Protection

Table 36. Session Limit screen settings (continued)
Total Number of Packets Dropped due to Session Limit
This is a nonconfigurable counter that displays the total number of dropped packets when the session limit is reached.
TCP Timeout For each protocol, specify a time-out in seconds. A session expires if no data for the session is received for the duration of the time-out period. The default time-out periods are 1800 seconds for TCP sessions, 120 seconds for UDP sessions, and 60 seconds for ICMP sessions. UDP Timeout
The application level gateway (ALG) facilitates multimedia sessions such as voice over IP (VoIP) sessions that use the Session Initiation Protocol (SIP) across the firewall and provides support for multiple SIP clients. SIP support for the ALG, which is an IPv4 feature, is disabled by default.
To enable ALG for SIP:


When you create inbound and outbound firewall rules, you use firewall objects such as services, QoS profiles, bandwidth profiles, and schedules to narrow down the firewall rules:
applied. For information about specifying schedules, see Set a Schedule to Block or Allow Specific Traffic on page 182.
Services are functions performed by server computers at the request of client computers. You can configure up to 124 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 RFC 1700, Assigned Numbers. Service numbers for other applications are typically chosen from the range 1024 to 65535 by the authors of the application. However, on the wireless VPN firewall you can select service numbers in the range from 1 to 65535.
Although the wireless VPN firewall already holds a list of many service port numbers, you are not limited to these choices. Use the Services screen to add additional services and applications to the list for use in defining firewall rules. The Services screen shows a list of services that you have defined, as shown in the following figure.
Firewall Protection

To define a new service, you need to determine first which port number or range of numbers is used by the application. You can usually determine this information by contacting the publisher of the application, user groups, or newsgroups. When you have the port number information, you can enter it on the Services screen.
To add a customized service:

Table 37. Services screen settings
Name A descriptive name of the service for identification and management purposes.
ICMP Type A numeric value that can range between 0 and 40. For a list of ICMP types, see http://www.iana.org/assignments/icmp-parameters.
Setting Description · Firewall Protection

Table 37. Services screen settings (continued)
Start Port The first TCP or UDP port of a range that the service uses.
Finish Port The last TCP or UDP port of a range that the service uses. If the service uses only a single port number, enter the same number in the Start Port and Finish Port fields.
From the Default QoS Priority drop-down list, select the QoS profile that you want to assign to the service. For more information about QoS profiles, see Preconfigured Quality of Service Profiles on page 177.
To edit a service:

To delete one or more services:
Setting Description · Default QoS Priority · Firewall Protection

Bandwidth profiles determine the way in which data is communicated with the hosts. The purpose of bandwidth profiles is to provide a method for allocating and limiting traffic, thus allocating LAN users sufficient bandwidth while preventing them from consuming all the bandwidth on your WAN link. A single bandwidth profile can be for both outbound and inbound traffic.
For outbound IPv4 traffic, you can apply bandwidth profiles on the WAN interface; for inbound IPv4 traffic, you can apply bandwidth profiles to a LAN interface. Bandwidth profiles do not apply to the DMZ interface, nor to IPv6 traffic.
When a new connection is established by a device, the device locates the firewall rule corresponding to the connection:
An exception occurs for an individual bandwidth profile if the classes are per-source IP address classes. The source IP address is the IP address of the first packet that is transmitted for the connection. So for outbound firewall rules, the source IP address is the LAN-side IP address; for inbound firewall rules, the source IP address is the WAN-side IP address. The class is deleted when all the connections that are using the class expire.
After you have created a bandwidth profile, you can assign the bandwidth profile to firewall rules on the following screens:
To add and enable a bandwidth profile:

Firewall Protection


Table 38. Add Bandwidth Profile screen settings
Profile Name A descriptive name of the bandwidth profile for identification and management purposes.
The inbound minimum allocated bandwidth in Kbps. There is no default setting.
The inbound maximum allowed bandwidth in Kbps. The maximum allowable bandwidth is 100,000 Kbps, and you cannot configure less than 100 Kbps. There is no default setting.
The outbound minimum allocated bandwidth in Kbps. There is no default setting.
The outbound maximum allowed bandwidth in Kbps. The maximum allowable bandwidth is 100,000 Kbps, and you cannot configure less than 100 Kbps. There is no default setting.

Table 38. Add Bandwidth Profile screen settings (continued)
To edit a bandwidth profile:
To delete one or more bandwidth profiles:
A Quality of Service (QoS) profile defines the relative priority of an IP packet when multiple connections are scheduled for simultaneous transmission on the wireless VPN firewall. A QoS profile becomes active only when it is associated with a nonblocking inbound or outbound firewall rule or service, and traffic matching the firewall rule or service is processed by the wireless VPN firewall. Priorities are defined by the Type of Service in the Internet Protocol Suite standards, RFC 1349.
You can assign a QoS profile to a firewall rule or service on the following screens:
Setting Description · Firewall Protection

These are the default QoS profiles that are preconfigured and that cannot be edited:
To restrict internal LAN users from access to certain sites on the Internet, you can use the content filtering and web component blocking features of the wireless VPN firewall. By default, these features are disabled; all requested traffic from any website 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.
Several types of blocking are available:
- Proxy. A proxy server (or simply, proxy) allows computers to route connections to other computers through the proxy, thus circumventing certain firewall rules. For example, if connections to a specific IP address are blocked by a firewall rule, the requests can be routed through a proxy that is not blocked by the rule, rendering the restriction ineffective. Enabling this feature blocks proxy servers.
- Java. Blocks Java applets from being downloaded from pages that contain them. Java applets are small programs embedded in web pages that enable dynamic functionality of the page. A malicious applet can be used to compromise or infect computers. Enabling this setting blocks Java applets from being downloaded.
Firewall Protection

- ActiveX. Similar to Java applets, ActiveX controls are installed on a Windows computer running Internet Explorer. A malicious ActiveX control can be used to compromise or infect computers. Enabling this setting blocks ActiveX applets from being downloaded.
- Cookies. Cookies are used to store session information by websites that usually require login. However, several websites use cookies to store tracking information and browsing habits. Enabling this option blocks cookies from being created by a website.
accessed correctly. Blocking cookies might interfere with useful functions provided by these websites.
You can apply the keywords to one or more LAN groups. Requests from the computers in the groups are blocked where keyword blocking has been enabled. Blocking does not occur for the computers in the groups where keyword blocking has been disabled.
You can bypass keyword blocking for trusted domains by adding the exact matching domain to the Trusted Domains table. Access to the domains or keywords on this list by computers in the groups for which keyword blocking has been enabled is allowed without any blocking.
Keyword application examples:
To enable and configure content filtering:
Firewall Protection


Firewall Protection

These components are explained in the introduction of this section on page 178.
To apply keyword blocking to LAN groups:
screen (see Change Group Names in the Network Database on page 71), the new names are displayed on the Block Sites screen.
To build your list of blocked keywords or blocked domain names:
To edit an entry, click the Edit table button in the Action column to the right of the entry.
To build your list of trusted domains:
To edit an entry, click the Edit table button in the Action column to the right of the entry.
Firewall Protection

Schedules define the time frames under which firewall rules can be applied. Three schedules, Schedule 1, Schedule 2, and Schedule 3, can be defined, and you can select any one of these when defining firewall rules.
To set a schedule:

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

The Source MAC Filter screen enables you to permit or block traffic coming from certain known computers or devices.
By default, the source MAC address filter is disabled. All the traffic received from computers with any MAC address is allowed. When the source MAC address filter is enabled, depending on the selected policy, traffic is either permitted or blocked if it comes from any computers or devices whose MAC addresses are listed in MAC Addresses table.
Rules (Service Blocking) on page 130.
To enable MAC filtering and add MAC addresses to be permitted or blocked:

Firewall Protection

If you select Permit and Block the rest from the drop-down list but do not add the MAC address of the computer from which you are accessing the web management interface, you are locked out of the web management interface.
To remove one or more MAC addresses from the table:
IP/MAC binding allows you to bind an IPv4 or IPv6 address to a MAC address and the other way around. Some computers or devices are configured with static addresses. To prevent users from changing their static IP addresses, the IP/MAC binding feature needs to be enabled on the wireless VPN firewall. If the wireless VPN firewall detects packets with an IP address that matches the IP address in the IP/MAC Bindings table but does not match the related MAC address in the IP/MAC Bindings table (or the other way around), the packets are dropped. If you have enabled the logging option for the IP/MAC binding feature, these packets are logged before they are dropped. The wireless VPN firewall displays the total number of dropped packets that violate either the IP-to-MAC binding or the MAC-to-IP binding.
Firewall Protection

assignment on the LAN Groups submenu. See Manage the Network Database on page 68.
As an example, assume that three computers on the LAN are set up as follows, and that their IPv4 and MAC addresses are added to the IP/MAC Bindings table:
There are three possible scenarios in relation to the addresses in the IP/MAC Bindings table:
In this example, the wireless VPN firewall blocks the traffic coming from Host 2 and Host 3, but allows the traffic coming from Host 1 to any external network. The total count of dropped packets is displayed.
To set up a binding between a MAC address and an IPv4 address:
IPv4/MAC Bindings · Firewall Protection


Table 39. IP/MAC Binding screen settings for IPv4
Name A descriptive name of the binding for identification and management purposes.
MAC Address The MAC address of the computer or device that is bound to the IP address.
IP Address The IPv4 address of the computer or device that is bound to the MAC address.
To log the dropped packets, select Enable from the drop-down list. The default setting is Disable.
Setting Description · Log Dropped Packets · Firewall Protection

To edit an IP/MAC binding:
To remove one or more IP/MAC bindings from the table:
To change the IPv4 MAC polling interval from its default setting of 10 seconds:

To set up a binding between a MAC address and an IPv6 address:
IPv6/MAC Bindings · Firewall Protection


Table 40. IP/MAC Binding screen settings for IPv6
Name A descriptive name of the binding for identification and management purposes.
MAC Address The MAC address of the computer or device that is bound to the IP address.
IP Address The IPv6 address of the computer or device that is bound to the MAC address.
To log the dropped packets, select Enable from the drop-down list. The default setting is Disable.
Setting Description · Log Dropped Packets · Firewall Protection

To edit an IP/MAC binding:
To remove one or more IP/MAC bindings from the table:
To change the IPv6 MAC polling interval from its default setting of 10 seconds:

Firewall Protection

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 the port triggering feature requires that you know the port numbers used by the application.
Once configured, port triggering operates as follows:
Without port triggering, the response from the external application would be treated as a new connection request rather than a response to a request from the LAN network. As such, it would be handled in accordance with the inbound port forwarding rules, and most likely would be blocked.
(Port Forwarding) on page 133.
To add a port triggering rule:
Firewall Protection


Table 41. Port Triggering screen settings
Name A descriptive name of the rule for identification and management purposes.
Enable From the drop-down list, select Yes to enable the rule. (You can define a rule but not enable it.) The default setting is No.
Outgoing Ports Start Port The start port (1–65535) of the range for triggering.
End Port The end port (1–65535) of the range for triggering.
Incoming Ports Start Port The start port (1–65535) of the range for responding.
End Port The end port (1–65535) of the range for responding.
To edit a port triggering rule:
Setting Description · Firewall Protection

To remove one or more port triggering rules from the table:
To display the status of the port triggering rules:
Click the Status option arrow in the upper right of the Port Triggering screen. A pop-up screen displays, showing the status of the port triggering rules.

The Universal Plug and Play (UPnP) feature enables the wireless VPN firewall to automatically discover and configure devices when it searches the LAN and WAN. UPnP is supported for IPv4 devices only.
To configure UPnP:

Firewall Protection

The UPnP Portmap Table in the lower part of the screen shows the IP addresses and other settings of UPnP devices that have accessed the wireless VPN firewall and that have been automatically detected by the wireless VPN firewall:
To refresh the contents of the UPnP Portmap Table, click Refresh.
Firewall Protection

This chapter describes how to use the IP security (IPSec) virtual private networking (VPN) features of the wireless VPN firewall to provide secure, encrypted communications between your local network and a remote network or computer. The chapter contains the following sections:
You can use the IPSec VPN Wizard to configure multiple gateway or client VPN tunnel policies.
The following sections provide wizard and NETGEAR ProSafe VPN Client software configuration procedures:
ProSafe VPN Client supports IPv4 only; an upcoming release of the VPN Client will support IPv6.

Configuring a VPN tunnel connection requires that you specify all settings on both sides of the VPN tunnel to 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 determine the IPSec keys and VPN policies it sets up. The VPN Wizard also configures the settings for the network connection: security association (SA), traffic selectors, authentication algorithm, and encryption. The settings that are used by the VPN Wizard are based on the recommendations of the VPN Consortium (VPNC), an organization that promotes multivendor VPN interoperability.

To set up an IPv4 gateway-to-gateway VPN tunnel using the VPN Wizard:
Virtual Private Networking Using IPSec and L2TP Connections


To view the wizard default settings, click the VPN Wizard default values option arrow in the upper right of the screen. A pop-up screen displays (see the following figure), showing the wizard default values. The default values are the same for IPv4 and IPv6.
Virtual Private Networking Using IPSec and L2TP Connections


Table 42. IPSec VPN Wizard settings for an IPv4 gateway-to-gateway tunnel
This VPN tunnel will connect to the following peers
Select the Gateway radio button. The local WAN port’s IP address or Internet name displays in the End Point Information section of the screen.
Connection Name and Remote IP Type
What is the new Connection Name?
Enter a descriptive name for the connection. This name is used to help you to manage the VPN settings; the name is not supplied to the remote VPN endpoint.
What is the pre-shared key? Enter a pre-shared key. The key needs to be entered both here and on the remote VPN gateway. This key needs to have a minimum length of 8 characters and should not exceed 49 characters.
End Point Informationa
What is the Remote WAN’s IP Address or Internet Name?
Enter the IPv4 address or Internet name (FQDN) of the WAN interface on the remote VPN tunnel endpoint.
What is the Local WAN’s IP Address or Internet Name?
When you select the Gateway radio button in the About VPN Wizard section of the screen, the IPv4 address of the wireless VPN firewall’s active WAN interface is automatically entered.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · About VPN Wizard

Table 42. IPSec VPN Wizard settings for an IPv4 gateway-to-gateway tunnel (continued)
Secure Connection Remote Accessibility
What is the remote LAN IP Address?
Enter the LAN IPv4 address of the remote gateway.
What is the remote LAN Subnet Mask?
Enter the LAN subnet mask for the remote gateway.
a. Both local and remote endpoints should be defined as either FQDNs or IP addresses. A combination of an IP address and an FQDN is not supported.
edit the VPN policy to enable keep-alives, which periodically sends ping packets to the host on the peer side of the network to keep the tunnel alive. For more information, see Configure Keep-Alives on page 260.
After you have validated the connection, you can use the wizard to create new policies using the FQDN for the WAN addresses.

a. Select VPN > Connection Status. The Connection Status submenu tabs display with the IPSec VPN Connection Status screen in view:
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description


b. Locate the policy in the table, and click the Connect table button. The IPSec VPN
connection becomes active.
its servers when your DHCP WAN address changes, the VPN tunnel will fail because the FQDNs do not resolve to your new address. If you have the option to configure the update interval, set it to an appropriately short time.
To set up an IPv6 gateway-to-gateway VPN tunnel using the VPN Wizard:
Virtual Private Networking Using IPSec and L2TP Connections


To view the wizard default settings, click the VPN Wizard default values option arrow in the upper right of the screen. A pop-up screen displays (see the following figure), showing the wizard default values. The default values are the same for IPv4 and IPv6.
Virtual Private Networking Using IPSec and L2TP Connections

Table 43. IPSec VPN Wizard settings for an IPv6 gateway-to-gateway tunnel
This VPN tunnel will connect to the following peers
Select the Gateway radio button. The local WAN port’s IP address or Internet name displays in the End Point Information section of the screen.
Connection Name and Remote IP Type
What is the new Connection Name?
Enter a descriptive name for the connection. This name is used to help you to manage the VPN settings; the name is not supplied to the remote VPN endpoint.
What is the pre-shared key? Enter a pre-shared key. The key needs to be entered both here and on the remote VPN gateway. This key needs to have a minimum length of 8 characters and should not exceed 49 characters.
End Point Informationa
What is the Remote WAN’s IP Address or Internet Name?
Enter the IPv6 address or Internet name (FQDN) of the WAN interface on the remote VPN tunnel endpoint.
What is the Local WAN’s IP Address or Internet Name?
When you select the Gateway radio button in the About VPN Wizard section of the screen, the IPv6 address of the wireless VPN firewall’s active WAN interface is automatically entered.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · About VPN Wizard

Table 43. IPSec VPN Wizard settings for an IPv6 gateway-to-gateway tunnel (continued)
Secure Connection Remote Accessibility
What is the remote LAN IP Address?
Enter the LAN IPv6 address of the remote gateway.
IPv6 Prefix Length Enter the prefix length for the remote gateway.
a. Both local and remote endpoints should be defined as either FQDNs or IP addresses. A combination of an IP address and an FQDN is not supported.
edit the VPN policy to enable keep-alives, which periodically sends ping packets to the host on the peer side of the network to keep the tunnel alive. For more information, see Configure Keep-Alives on page 260.
After you have validated the connection, you can use the wizard to create new policies using the FQDN for the WAN addresses.

a. Select VPN > Connection Status. The Connection Status submenu tabs display with the IPSec VPN Connection Status screen in view:
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description


b. Locate the policy in the table, and click the Connect table button. The IPSec VPN
connection becomes active.
its servers when your DHCP WAN address changes, the VPN tunnel will fail because the FQDNs do not resolve to your new address. If you have the option to configure the update interval, set it to an appropriately short time.

To configure a VPN client tunnel, follow the steps in the following sections:
Virtual Private Networking Using IPSec and L2TP Connections

Use the VPN Wizard to Configure the Gateway for a Client Tunnel
To set up a client-to-gateway VPN tunnel using the VPN Wizard:

To display the wizard default settings, click the VPN Wizard default values option arrow in the upper right of the screen. A pop-up screen displays (see Figure 108 on page 197), showing the wizard default values. After you have completed the wizard, you can modify these settings for the tunnel policy that you have set up.
Virtual Private Networking Using IPSec and L2TP Connections

Table 44. IPSec VPN Wizard settings for a client-to-gateway tunnel
This VPN tunnel will connect to the following peers
Select the VPN Client radio button. The default remote FQDN (remote.com) and the default local FQDN (local.com) display in the End Point Information section of the screen.
Connection Name and Remote IP Type
What is the new Connection Name?
Enter a descriptive name for the connection. This name is used to help you to manage the VPN settings; the name is not supplied to the VPN client.
What is the pre-shared key? Enter a pre-shared key. The key needs to be entered both here and on the
remote VPN gateway, or the remote VPN client. This key needs to have a minimum length of 8 characters and cannot exceed 49 characters.
End Point Informationa
What is the Remote Identifier Information?
When you select the Client radio button in the About VPN Wizard section of the screen, the default remote FQDN (remote.com) is automatically entered. Use the default remote FQDN, or enter another FQDN.
What is the Local Identifier Information?
When you select the Client radio button in the About VPN Wizard section of the screen, the default local FQDN (local.com) is automatically entered. Use the default local FQDN, or enter another FQDN.
Secure Connection Remote Accessibility
What is the remote LAN IP Address?
These fields are masked out for VPN client connections. What is the remote LAN Subnet Mask?
a. Both local and remote endpoints should be defined as either FQDNs or IP addresses. A combination of an IP address and an FQDN is not supported.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · About VPN Wizard


update its servers when your DHCP WAN address changes, the VPN tunnel will fail because the FQDNs do not resolve to your new address. If you have the option to configure the update interval, set it to an appropriately short time.
Table 45. Information required to configure the VPN client
Component Enter the information that you collected Example
Remote identifier information remote.com
Local identifier information local.com
Router’s LAN network IPv4 address 192.168.1.0
Router’s WAN IPv4 address 192.168.15.175
Use the NETGEAR VPN Client Wizard to Create a Secure Connection
The VPN client lets you set up the VPN connection manually (see Manually Create a Secure Connection Using the NETGEAR VPN Client on page 211) or with the integrated Configuration Wizard, which is the easier and preferred method. The Configuration Wizard configures the default settings and provides basic interoperability so that the VPN client can easily communicate with the wireless VPN firewall (or third-party VPN devices). The Configuration Wizard does not let you enter the local and remote IDs, so you need to manually enter this information.
Virtual Private Networking Using IPSec and L2TP Connections
Pre-shared key I7!KL39dFG_8

ProSafe VPN Client installed. The VPN Client supports IPv4 only; an upcoming release of the VPN Client will support IPv6.
To use the Configuration Wizard to set up a VPN connection between the VPN client and the wireless VPN firewall:

Virtual Private Networking Using IPSec and L2TP Connections



Virtual Private Networking Using IPSec and L2TP Connections


a. In the tree list pane of the Configuration Panel screen, click Gateway (the default name given to the authentication phase). The Authentication pane displays in the Configuration Panel screen, with the Authentication tab selected by default.
b. Click the Advanced tab in the Authentication pane. The Advanced pane displays:

Virtual Private Networking Using IPSec and L2TP Connections

c. Specify the settings that are explained in the following table.
Table 46. VPN client advanced authentication settings
Aggressive Mode Select this check box to enable aggressive mode as the mode of negotiation with the wireless VPN firewall.
NAT-T Select Automatic from the drop-down list to enable the VPN client and wireless VPN firewall to negotiate NAT-T.
Local and Remote ID
Local ID As the type of ID, select DNS from the Local ID drop-down list because you specified FQDN in the wireless VPN firewall configuration. As the value of the ID, enter remote.com as the local ID for the VPN client.
Remote ID As the type of ID, select DNS from the Remote ID drop-down list because you specified an FQDN in the wireless VPN firewall configuration. As the value of the ID, enter local.com as the remote ID for the wireless VPN firewall.
a. Click Global Parameters in the left column of the Configuration Panel screen. The Global Parameters pane displays in the Configuration Panel screen:
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · Advanced features


b. Specify the default lifetimes in seconds:
The VPN client configuration is now complete.
Instead of using the wizard on the VPN client, you can also manually configure the VPN client, which is explained in the following section.
Manually Create a Secure Connection Using the NETGEAR VPN Client
ProSafe VPN Client installed.
To manually configure a VPN connection between the VPN client and the wireless VPN firewall, create authentication settings (phase 1 settings), create an associated IPSec configuration (phase 2 settings), and then specify the global parameters.
Virtual Private Networking Using IPSec and L2TP Connections

Configure the Authentication Settings (Phase 1 Settings)
To create new authentication settings:

a. Right-click the authentication phase name.
b. Select Rename.
c. Type vpn_client.
d. Click anywhere in the tree list pane.
Virtual Private Networking Using IPSec and L2TP Connections

The Authentication pane displays in the Configuration Panel screen, with the Authentication tab selected by default.

Table 47. VPN client authentication settings
Interface Select Any from the drop-down list.
Remote Gateway Enter the remote IP address or DNS name of the wireless VPN firewall. For example, enter 192.168.15.175.
Preshared Key Select the Preshared Key radio button. Enter the pre-shared key that you already specified on the wireless VPN firewall. For example, enter I7!KL39dFG_8. Confirm the key in the Confirm field.
IKE Encryption Select the 3DES encryption algorithm from the drop-down list.
Authentication Select the SHA1 authentication algorithm from the drop-down list.
Key Group Select the DH2 (1024) key group from the drop-down list.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description


Table 48. VPN client advanced authentication settings
Aggressive Mode Select this check box to enable aggressive mode as the mode of negotiation with the wireless VPN firewall.
NAT-T Select Automatic from the drop-down list to enable the VPN client and wireless VPN firewall to negotiate NAT-T.
Local and Remote ID
Local ID As the type of ID, select DNS from the Local ID drop-down list because you specified FQDN in the wireless VPN firewall configuration. As the value of the ID, enter remote.com as the local ID for the VPN client.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · Advanced features

Table 48. VPN client advanced authentication settings (continued)
Remote ID As the type of ID, select DNS from the Remote ID drop-down list because you specified an FQDN in the wireless VPN firewall configuration. As the value of the ID, enter local.com as the remote ID for the wireless VPN firewall.
Create the IPSec Configuration (Phase 2 Settings)
settings) is referred to as the IKE settings.
To create an IPSec configuration:
a. Right-click the IPSec configuration name.
b. Select Rename.
c. Type netgear_platform.
d. Click anywhere in the tree list pane.
The IPSec pane displays in the Configuration Panel screen, with the IPSec tab selected by default:
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description


Table 49. VPN client IPSec configuration settings
VPN Client address Either enter 0.0.0.0 as the IP address, or enter a virtual IP address that is used by the VPN client in the wireless VPN firewall’s LAN; the computer (for which the VPN client opened a tunnel) appears in the LAN with this IP address.
Address Type Select Subnet address from the drop-down list. This selection defines which addresses the VPN client can communicate with after the VPN tunnel is established.
Remote LAN address Enter 192.168.1.0 as the remote IP address (that is, LAN network address) of the gateway that opens the VPN tunnel.
Subnet mask Enter 255.255.255.0 as the remote subnet mask of the gateway that opens the VPN tunnel.
ESP Encryption Select 3DES as the encryption algorithm from the drop-down list.
Authentication Select SHA-1 as the authentication algorithm from the drop-down list.
Mode Select Tunnel as the encapsulation mode from the drop-down list.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description

Table 49. VPN client IPSec configuration settings (continued)
PFS and Group Select the PFS check box, and then select the DH2 (1024) key group from the drop-down list.
Configure the Global Parameters
To specify the global parameters:
The wireless VPN firewall configuration is now complete.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description

Both the NETGEAR ProSafe VPN Client and the wireless VPN firewall provide VPN connection and status information. This information is useful for verifying the status of a connection and troubleshooting problems with a connection.
There are many ways to establish a connection. The following procedures assume that you use the default authentication phase name Gateway and the default IPSec configuration name Tunnel. If you manually set up the connection and changed the names, use vpn_client (or any other name that you have configured) as the authentication phase name and netgear_platform (or any other name that you have configured) as the IPSec configuration name.
To establish a connection, use one of the following three methods:
- Click the Tunnel IPSec configuration name, and press Ctrl+O.
- Right-click the Tunnel IPSec configuration name, and select Open tunnel.

Virtual Private Networking Using IPSec and L2TP Connections

- Double-click Gateway-Tunnel.
- Right-click Gateway-Tunnel, and select Open tunnel.
- Click Gateway-Tunnel, and press Ctrl+O.


Whichever way you choose to open the tunnel, when the tunnel opens successfully, the Tunnel opened message displays above the system tray:

Once launched, the VPN client displays an icon in the system tray that indicates whether a tunnel is opened, using a color code:

at least one VPN tunnel opened
Virtual Private Networking Using IPSec and L2TP Connections

To view detailed negotiation and error information on the NETGEAR VPN client:
Right-click the VPN client icon in the system tray, and select Console. The VPN Client Console Active screen displays:

To view the status of current IPSec VPN tunnels, select VPN > Connection Status. The Connection Status submenu tabs display with the IPSec VPN Connection Status screen in view. (The following figure shows an IPSec SA as an example.)
Virtual Private Networking Using IPSec and L2TP Connections

The Active IPSec SA(s) table lists each active connection with the information that is described in the following table. The default poll interval is 10 seconds. To change the poll interval period, enter a new value in the Poll Interval field, and then click the Set Interval button. To stop polling, click the Stop button.
Table 50. IPSec VPN Connection Status screen information
Policy Name The name of the VPN policy that is associated with this SA.
Endpoint The IP address on the remote VPN endpoint.
Tx (KB) The amount of data that is transmitted over this SA.
Tx (Packets) The number of IP packets that are transmitted over this SA.
State The status of the SA. Phase 1 is the authentication phase, and Phase 2 is key exchange phase. If there is no connection, the status is IPSec SA Not Established.
Action Click the Connect table button to build the connection, or click the Disconnect table button to terminate the connection.
To display the IPSec VPN log:
Select Monitoring > VPN Logs > IPSec VPN Logs. The IPSec VPN Logs screen displays:

Virtual Private Networking Using IPSec and L2TP Connections
Item Description

After you have used the VPN Wizard to set up a VPN tunnel, a VPN policy and an IKE policy are stored in separate policy tables. The name that you selected as the VPN tunnel connection name during the VPN Wizard setup identifies both the VPN policy and IKE policy. You can edit existing policies, or manually add new VPN and IKE policies directly in the policy tables.
The Internet Key Exchange (IKE) protocol performs negotiations between the two VPN gateways and provides automatic management of the keys that are used for IPSec connections. It is important to remember that:
IKE policies are activated when the following situations occur:
The VPN tunnel is then available for data transfer.
When you use the VPN Wizard to set up a VPN tunnel, an IKE policy is established and populated in the List of IKE Policies, and is given the same name as the new VPN connection name. You can also edit exiting policies or add new IKE policies from the IKE Policies screen.
Virtual Private Networking Using IPSec and L2TP Connections

To access the IKE Policies screen:
Select VPN > IPSec VPN. The IPSec VPN submenu tabs display with the IKE Policies screen in view. In the upper right of the screen, the IPv4 radio button is selected by default. The IKE Policies screen displays the IPv4 settings. (The following figure shows some examples.) To display the IPv6 settings on the IKE Policies screen, select the IPv6 radio button.

Each policy contains the data that are explained in the following table. These fields are explained in more detail in Table 52 on page 226.
Table 51. IKE Policies screen information for IPv4 and IPv6
Name The name that identifies the IKE policy. When you use the VPN Wizard to set up a VPN policy, an accompanying IKE policy is automatically created with the same name that you select for the VPN policy.
Mode The exchange mode: Main or Aggressive.
Local ID The IKE/ISAKMP identifier of the wireless VPN firewall. The remote endpoint needs to have this value as its remote ID.
Remote ID The IKE/ISAKMP identifier of the remote endpoint, which needs to have this value as its local ID.
Encr The encryption algorithm that is used for the IKE security association (SA). This setting needs to match the setting on the remote endpoint.
Auth The authentication algorithm that is used for the IKE SA. This setting needs to match the setting on the remote endpoint.
DH The Diffie-Hellman (DH) group that is used when keys are exchanged. This setting needs to match the setting on the remote endpoint.
Virtual Private Networking Using IPSec and L2TP Connections
IKE Policies Screen · Item Description

To delete one or more IKE polices:
For information about how to add or edit an IKE policy, see Manually Add or Edit an IKE Policy on page 224.
active without first disabling or deleting the VPN policy.
Manually Add or Edit an IKE Policy
To manually add an IKE policy for IPv4 or IPv6:
Virtual Private Networking Using IPSec and L2TP Connections


Virtual Private Networking Using IPSec and L2TP Connections

Table 52. Add IKE Policy screen settings
Do you want to use Mode Config Record?
Select Mode Config Record
From the drop-down list, select one of the Mode Config records that you defined on the Add Mode Config Record screen (see Configure Mode Config Operation on the Wireless VPN Firewall on page 244).
Policy Name A descriptive name of the IKE policy for identification and management purposes.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · Mode Config Record · General

Table 52. Add IKE Policy screen settings (continued)
Identifier Depending on the selection of the Identifier drop-down list, enter the IP address, email address, FQDN, or distinguished name.
Identifier Depending on the selection of the Identifier drop-down list, enter the IP address, email address, FQDN, or distinguished name.
Virtual Private Networking Using IPSec and L2TP Connections

Table 52. Add IKE Policy screen settings (continued)
Pre-shared key A key with a minimum length of 8 characters and no more than 49 characters. Do not use a double quote (''), single quote('), or space in the key.
SA-Lifetime (sec) The period in seconds for which the IKE SA is valid. When the period times out, the next rekeying occurs. The default is 28800 seconds (8 hours).
Enable Dead Peer Detection
Detection Period The period in seconds between consecutive DPD R-U-THERE messages, which are sent only when the IPSec traffic is idle.
Reconnect after failure count
The maximum number of DPD failures before the wireless VPN firewall tears down the connection and then attempts to reconnect to the peer. The default is 3 failures.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · Diffie-Hellman (DH) Group

Table 52. Add IKE Policy screen settings (continued)
Username The user name for XAUTH.
Password The password for XAUTH.
To edit an IKE policy:
Virtual Private Networking Using IPSec and L2TP Connections

You can create two types of VPN policies. When you use the VPN Wizard to create a VPN policy, only the Auto method is available.
In addition, a certification authority (CA) can also be used to perform authentication (see Manage Digital Certificates for VPN Connections on page 313). For gateways to use a CA to perform authentication, each VPN gateway needs to 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 by any sender to encrypt data intended for the receiver (the key owner). The receiver then uses its private key to decrypt the data (without the private key, decryption is impossible). The use of certificates for authentication reduces the amount of data entry that is required on each VPN endpoint.
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 policies, or delete them entirely. These are the rules for VPN policy use:
To access the VPN Policies screen, select VPN > IPSec VPN > VPN Policies. In the upper right of the screen, the IPv4 radio button is selected by default. The VPN Policies screen displays the IPv4 settings. (The following figure shows some examples.) To display the IPv6 settings on the IKE Policies screen, select the IPv6 radio button.
Virtual Private Networking Using IPSec and L2TP Connections
VPN Policies Screen

Each policy contains the data that are explained in the following table. These fields are explained in more detail in Table 54 on page 235.
Table 53. VPN Policies screen information for IPv4 and IPv6
! (Status) Indicates whether the policy is enabled (green circle) or disabled (gray circle). To enable or disable a policy, select the check box to the left of the circle, and click the Enable or Disable table button, as appropriate.
Name The name that identifies the VPN policy. When you use the VPN Wizard to create a VPN policy, the name of the VPN policy (and of the automatically created accompanying IKE policy) is the connection name.
Type Auto or Manual as described previously (Auto is used during VPN Wizard configuration).
Local IP address (either a single address, range of address, or subnet address) on your LAN. Traffic needs to be from (or to) these addresses to be covered by this policy. (The subnet address is supplied as the default IP address when you are using the VPN Wizard.)
Remote IP address or address range of the remote network. Traffic needs to 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.)
Auth The authentication algorithm that is used for the VPN tunnel. This setting needs to match the setting on the remote endpoint.
Encr The encryption algorithm that is used for the VPN tunnel. This setting needs to match the setting on the remote endpoint.
Virtual Private Networking Using IPSec and L2TP Connections
Item Description

To delete one or more VPN polices:
To enable or disable one or more VPN policies:
For information about how to add or edit a VPN policy, see Manually Add or Edit a VPN Policy on this page.
Manually Add or Edit a VPN Policy
To manually add a VPN policy:
Virtual Private Networking Using IPSec and L2TP Connections


Figure 142. Add New VPN Policy screen for IPv4
Virtual Private Networking Using IPSec and L2TP Connections


Figure 143. Add New VPN Policy screen for IPv6
Virtual Private Networking Using IPSec and L2TP Connections

Table 54. Add New VPN Policy screen settings for IPv4 and IPv6
Policy Name A descriptive name of the VPN policy for identification and management purposes.
Enable NetBIOS? Select this check box to enable NetBIOS broadcasts to travel over the VPN tunnel. For more information about NetBIOS, see Configure NetBIOS Bridging with IPSec VPN on page 262. This feature is disabled by default.
Enable Auto Initiate Select this check box to enable the VPN tunnel to autoestablish itself without the presence of any traffic.
Ping IP Address The IP address that the wireless VPN firewall pings. The address needs to be of a host that can respond to ICMP ping requests.
Detection Period The period in seconds between the keep-alive requests. The default setting is 10 seconds.
Reconnect after failure count
The maximum number of keep-alive requests before the wireless VPN firewall tears down the connection and then attempts to reconnect to the remote endpoint. The default setting is 3 keep-alive requests.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · General · Enable Keepalive

Table 54. Add New VPN Policy screen settings for IPv4 and IPv6 (continued)
- Subnet Mask. For IPv4 addresses on the IPv4 screen only, enter the
subnet mask. - IPv6 Prefix Length. For IPv6 addresses on the IPv6 screen only, enter the
prefix length.
Remote IP From the drop-down list, select the address or addresses that are part of the VPN tunnel on the remote endpoint. The selections are the same as for the Local IP drop-down list.
SPI-Incoming The Security Parameters Index (SPI) for the inbound policy. Enter a hexadecimal value between 3 and 8 characters (for example, 0x1234).
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · Traffic Selection · Manual Policy Parameters

Table 54. Add New VPN Policy screen settings for IPv4 and IPv6 (continued)
SPI-Outgoing The Security Parameters Index (SPI) for the outbound policy. Enter a hexadecimal value between 3 and 8 characters (for example, 0x1234).
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · Auto Policy Parameters

Table 54. Add New VPN Policy screen settings for IPv4 and IPv6 (continued)
Select IKE Policy Select an existing IKE policy that defines the characteristics of the Phase-1 negotiation. To display the selected IKE policy, click the View Selected button.
To edit a VPN policy:
When many VPN clients connect to a wireless VPN firewall, you might want to use a unique user authentication method beyond relying on a single common pre-shared key for all clients. Although you could configure a unique VPN policy for each user, it is more efficient to
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description

authenticate users from a stored list of user accounts. XAUTH provides the mechanism for requesting individual authentication information from the user. 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.
You can enable XAUTH when you manually add or edit an IKE policy. Two types of XAUTH are available:
checks the local user database for the user credentials. If the user account is not present, the wireless VPN firewall then connects to a RADIUS server.
Once the XAUTH has been enabled, you need to establish user accounts in the user database to be authenticated against XAUTH, or you need to enable a RADIUS-CHAP or RADIUS-PAP server.
IKE policy is in use by a VPN policy. The VPN policy needs to be disabled before you can modify the IKE policy.
To enable and configure XAUTH:
Virtual Private Networking Using IPSec and L2TP Connections

Table 55. Extended authentication settings for IPv4 and IPv6
Username The user name for XAUTH.
Password The password for XAUTH.
When XAUTH is enabled in an Edge Device configuration, users need to be authenticated either by a local user database account or by an external RADIUS server. Whether or not you use a RADIUS server, you might want some users to be authenticated locally. These users need to be added to the List of Users table on the Users screen, as described in Configure User Accounts on page 303.
Remote Authentication Dial In User Service (RADIUS, RFC 2865) is a protocol for managing authentication, authorization, and accounting (AAA) of multiple users in a network. A RADIUS server stores 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 request. At that point, the remote user needs to provide authentication
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · Authentication Type

information such as a user name and password or some encrypted response using his or her user name and password information. The gateway then attempts to 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.
addresses only, the servers can be used for authentication, authorization, and accounting of both IPv4 and IPv6 users.
To configure primary and backup RADIUS servers:

Table 56. RADIUS Client screen settings
To enable and configure the primary RADIUS server, select the Yes radio button, and then enter the settings for the three fields to the right. The default setting is that the No radio button is selected.
Primary Server IP Address The IPv4 address of the primary RADIUS server.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · Primary RADIUS Server

Table 56. RADIUS Client screen settings (continued)
Secret Phrase A shared secret phrase to authenticate the transactions between the client and the primary RADIUS server. The same secret phrase needs to be configured on both the client and the server.
Primary Server NAS Identifier
The primary Network Access Server (NAS) identifier that needs to be present in a RADIUS request.
Note: The wireless VPN firewall functions as an NAS, allowing network access to external users after verification of their authentication information. In a RADIUS transaction, the NAS needs to provide some NAS identifier information to the RADIUS server. Depending on the configuration of the RADIUS server, the wireless VPN firewall’s IP address might be sufficient as an identifier, or the server might require a name, which you need to enter in this field.
To enable and configure the backup RADIUS server, select the Yes radio button, and then enter the settings for the three fields to the right. The default setting is that the No radio button is selected.
Backup Server IP Address The IPv4 address of the backup RADIUS server.
Secret Phrase A shared secret phrase to authenticate the transactions between the client and the backup RADIUS server. The same secret phrase needs to be configured on both the client and the server.
Backup Server NAS Identifier
The backup Network Access Server (NAS) identifier that needs to be present in a RADIUS request.
Time out period The period in seconds that the wireless VPN firewall waits for a response from a RADIUS server. The default setting is 30 seconds.
Maximum Retry Counts The maximum number of times that the wireless VPN firewall attempts to connect to a RADIUS server. The default setting is 4 retry counts.
on the Edit IKE Policy screen or Add IKE Policy screen (see Configure XAUTH for VPN Clients on page 239).
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · Backup RADIUS Server · Connection Configuration

To simplify the process of connecting remote VPN clients to the wireless VPN firewall, use the Mode Config feature to automatically assign IPv4 addresses to remote users, including a network access IP address, subnet mask, WINS server, and DNS address. Remote users are given IP addresses available in a secured network space so that remote users appear as seamless extensions of the network.
You can use the Mode Config feature in combination with an IPv6 IKE policy to assign IPv4 addresses to clients, but you cannot assign IPv6 addresses to clients.
After the IKE Phase 1 negotiation is complete, the VPN connection initiator (which is the remote user with a VPN client) requests the IP configuration settings such as the IP address, subnet mask, WINS server, and DNS address from the wireless VPN firewall. The Mode Config feature allocates an IP address from the configured IP address pool and activates a temporary IPSec policy, using the information that is specified in the Traffic Tunnel Security Level section of the Mode Config record (on the Add Mode Config Record screen that is shown in Figure 146 on page 245).
configure an IKE policy and select the newly created Mode Config record from the Select Mode Config Record drop-down list (see Configure Mode Config Operation on the Wireless VPN Firewall on page 244). You do not need to change any VPN policy.
the VPN client has gracefully disconnected or after the SA liftetime for the connection has timed out.
Virtual Private Networking Using IPSec and L2TP Connections

To configure Mode Config on the wireless VPN firewall, first create a Mode Config record, and then select the Mode Config record for an IKE policy.
To configure Mode Config on the wireless VPN firewall:

As an example, the screen shows two Mode Config records with the names EMEA Sales and NA Sales:
Virtual Private Networking Using IPSec and L2TP Connections


Table 57. Add Mode Config Record screen settings
Record Name A descriptive name of the Mode Config record for identification and management purposes.
First Pool Assign at least one range of IP pool addresses in the First Pool fields to enable the wireless VPN firewall to allocate these to remote VPN clients. The Second Pool and Third Pool fields are optional. To specify any client pool, enter the starting IP address for the pool in the Starting IP field, and enter the ending IP address for the pool in the Ending IP field.
Virtual Private Networking Using IPSec and L2TP Connections

Table 57. Add Mode Config Record screen settings (continued)
WINS Server If there is a WINS server on the local network, enter its IP address in the Primary field. You can enter the IP address of a second WINS server in the Secondary field.
DNS Server Enter the IP address of the DNS server that is used by remote VPN clients in the Primary field. You can enter the IP address of a second DNS server in the Secondary field.
Traffic Tunnel Security Level
Local IP Address The local IP address to which remote VPN clients have access. If you do not specify a local IP address, the wireless VPN firewall’s default LAN IP address is used (by default, 192.168.1.1).
Local Subnet Mask The local subnet mask. Typically, this is 255.255.255.0.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description

Continue the Mode Config configuration procedure by configuring an IKE policy.
clients, but you cannot assign IPv6 addresses to clients.
Virtual Private Networking Using IPSec and L2TP Connections


Virtual Private Networking Using IPSec and L2TP Connections

specifically for a Mode Config configuration. Table 52 on page 226 explains the general IKE policy settings.
Table 58. Add IKE Policy screen settings for a Mode Config configuration
Do you want to use Mode Config Record?
Select the Yes radio button.
Select Mode Config Record
From the drop-down list, select the Mode Config record that you created in Step 4 on page 247. This example uses NA Sales.
Policy Name A descriptive name of the IKE policy for identification and management purposes. This example uses ModeConfigNA_Sales.
Direction / Type Responder is automatically selected when you select the Mode Config record in the Mode Config Record section of the screen. This ensures that the wireless VPN firewall responds to an IKE request from the remote endpoint but does not initiate one.
Exchange Mode Aggressive mode is automatically selected when you select the Mode Config record in the Mode Config Record section of the screen.
Identifier Type From the drop-down list, select FQDN.
Identifier Enter an FQDN for the wireless VPN firewall. This example uses router.com.
Identifier Type From the drop-down list, select FQDN.
Identifier Enter the FQDN for the remote endpoint. This needs to be an FQDN that is not used in any other IKE policy. This example uses client.com.
Virtual Private Networking Using IPSec and L2TP Connections

Table 58. Add IKE Policy screen settings for a Mode Config configuration (continued)
Encryption Algorithm To negotiate the security association (SA), from the drop-down list, select the 3DES algorithm.
From the drop-down list, select the SHA-1 algorithm to be used in the VPN header for the authentication process.
Authentication Method Select Pre-shared key as the authentication method, and enter a key in the Pre-shared key field.
Pre-shared key A key with a minimum length of 8 characters and no more than 49 characters. Do not use a double quote (''), single quote('), or space in the key. This example uses H8!spsf3#JYK2!.
The DH Group sets the strength of the algorithm in bits. From the drop-down list, select Group 2 (1024 bit).
SA-Lifetime (sec) The period in seconds for which the IKE SA is valid. When the period times out, the next rekeying occurs. The default setting is 28800 seconds (8 hours). However, for a Mode Config configuration, NETGEAR recommends 3600 seconds (1 hour).
Enable Dead Peer Detection
Detection Period The period in seconds between consecutive DPD R-U-THERE messages, which are sent only when the IPSec traffic is idle. The default setting is 10 seconds. This example uses 30 seconds.
Reconnect after failure count
The maximum number of DPD failures before the wireless VPN firewall tears down the connection and then attempts to reconnect to the peer. The default setting is 3 failures.
Virtual Private Networking Using IPSec and L2TP Connections

Table 58. Add IKE Policy screen settings for a Mode Config configuration (continued)
Username The user name for XAUTH.
Password The password for XAUTH.
When the Mode Config feature is enabled, the following information is negotiated between the VPN client and the wireless VPN firewall during the authentication phase:
The virtual IP address that is issued by the wireless VPN firewall is displayed in the VPN Client Address field on the VPN client’s IPSec pane.
Virtual Private Networking Using IPSec and L2TP Connections

ProSafe VPN Client installed.
To configure the VPN client for Mode Config operation, create authentication settings (phase 1 settings), create an associated IPSec configuration (phase 2 settings), and then specify the global parameters.
Configure the Mode Config Authentication Settings (Phase 1 Settings)
To create new authentication settings:
Virtual Private Networking Using IPSec and L2TP Connections


a. Right-click the authentication phase name.
b. Select Rename.
c. Type GW_ModeConfig.
d. Click anywhere in the tree list pane.
The Authentication pane displays in the Configuration Panel screen, with the Authentication tab selected by default:

Virtual Private Networking Using IPSec and L2TP Connections

Table 59. VPN client authentication settings (Mode Config)
Interface Select Any from the drop-down list.
Remote Gateway Enter the remote IP address or DNS name of the wireless VPN firewall. For example, enter 192.168.15.175.
Preshared Key Select the Preshared Key radio button. Enter the pre-shared key that you already specified on the wireless VPN firewall. For example, enter H8!spsf3#JYK2!. Confirm the key in the Confirm field.
IKE Encryption Select the 3DES encryption algorithm from the drop-down list.
Authentication Select the SHA1 authentication algorithm from the drop-down list.
Key Group Select the DH2 (1024) key group from the drop-down list.

Virtual Private Networking Using IPSec and L2TP Connections
Setting Description

Table 60. VPN client advanced authentication settings (Mode Config)
Mode Config Select this check box to enable Mode Config.
Aggressive Mode Select this check box to enable aggressive mode as the mode of negotiation with the wireless VPN firewall.
NAT-T Select Automatic from the drop-down list to enable the VPN client and wireless VPN firewall to negotiate NAT-T.
Local and Remote ID
Local ID As the type of ID, select DNS from the Local ID drop-down list because you specified FQDN in the wireless VPN firewall configuration. As the value of the ID, enter client.com as the local ID for the VPN client.
Remote ID As the type of ID, select DNS from the Remote ID drop-down list because you specified an FQDN in the wireless VPN firewall configuration. As the value of the ID, enter router.com as the remote ID for the wireless VPN firewall.
Create the Mode Config IPSec Configuration (Phase 2 Settings)
settings) is referred to as the IKE settings.
To create an IPSec configuration:
a. Right-click the IPSec configuration name.
b. Select Rename.
c. Type Tunnel_ModeConfig.
d. Click anywhere in the tree list pane.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · Advanced features

The IPSec pane displays in the Configuration Panel screen, with the IPSec tab selected by default:

Table 61. VPN client IPSec configuration settings (Mode Config)
This field is masked out because Mode Config is selected. After an IPSec connection is established, the IP address that is issued by the wireless VPN firewall displays in this field (see Figure 157 on page 260).
Address Type Select Subnet address from the drop-down list.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · VPN Client address · Remote host address

Table 61. VPN client IPSec configuration settings (Mode Config) (continued)
Subnet mask Enter 255.255.255.0 as the remote subnet mask of the wireless VPN firewall that opens the VPN tunnel. This is the LAN IP subnet mask that you specified in the Local Subnet Mask field on the Add Mode Config Record screen of the wireless VPN firewall. If you left the Local Subnet Mask field blank, enter the wireless VPN firewall’s default IP subnet mask.
ESP Encryption Select 3DES as the encryption algorithm from the drop-down list.
Authentication Select SHA-1 as the authentication algorithm from the drop-down list.
Mode Select Tunnel as the encapsulation mode from the drop-down list.
PFS and Group Select the PFS check box, and then select the DH2 (1024) key group from the drop-down list.
Configure the Mode Config Global Parameters
To specify the global parameters:

Virtual Private Networking Using IPSec and L2TP Connections
Setting Description

The Mode Config configuration of the VPN client is now complete.
To test the Mode Config connection from the VPN client to the wireless VPN firewall:

When the tunnel opens successfully, the Tunnel opened message displays above the system tray, and the VPN client displays a green icon in the system tray.

Virtual Private Networking Using IPSec and L2TP Connections


is not used in an IKE policy.
To edit a Mode Config record:
To delete one or more Mode Config records:
In some cases, you might not want a VPN tunnel to be disconnected when traffic is idle, for example, when client-server applications over the tunnel cannot tolerate the tunnel
Virtual Private Networking Using IPSec and L2TP Connections

establishment time. If you require a VPN tunnel to remain connected, you can use the keep-alive and Dead Peer Detection (DPD) features to prevent the tunnel from being disconnected and to force a reconnection if the tunnel disconnects for any reason.
For DPD to function, the peer VPN device on the other end of the tunnel also needs to support DPD. Keep-alive, though less reliable than DPD, does not require any support from the peer device.
The keep-alive feature maintains the IPSec SA by sending periodic ping requests to a host across the tunnel and monitoring the replies.
To configure the keep-alive feature on a configured VPN policy:

Virtual Private Networking Using IPSec and L2TP Connections

Table 62. Keep-alive settings
Enable Keepalive Select the Yes radio button to enable the keep-alive feature. Periodically, the wireless VPN firewall sends keep-alive requests (ping packets) to the remote endpoint to keep the tunnel alive. You need to specify the ping IP address in the Ping IP Address field, the detection period in the Detection Period field, and the maximum number of keep-alive requests that the wireless VPN firewall sends in the Reconnect after failure count field.
Ping IP Address The IP address that the wireless VPN firewall pings. The address should be of a host that can respond to ICMP ping requests.
Detection Period The period in seconds between the keep-alive requests. The default setting is 10 seconds.
Reconnect after failure count
The maximum number of keep-alive requests before the wireless VPN firewall tears down the connection and then attempts to reconnect to the remote endpoint. The default setting is 3 keep-alive requests.
The Dead Peer Detection (DPD) feature lets the wireless VPN firewall maintain the IKE SA by exchanging periodic messages with the remote VPN peer.
To configure DPD on a configured IKE policy:
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · General


Table 63. Dead Peer Detection settings
Enable Dead Peer Detection
Select the Yes radio button to enable DPD. When the wireless VPN firewall detects an IKE connection failure, it deletes the IPSec and IKE SA and forces a reestablishment of the connection. You need to specify the detection period in the Detection Period field and the maximum number of times that the wireless VPN firewall attempts to reconnect in the Reconnect after failure count field.
Detection Period The period in seconds between consecutive DPD R-U-THERE messages, which are sent only when the IPSec traffic is idle. The default setting is 10 seconds.
Reconnect after failure count
The maximum number of DPD failures before the wireless VPN firewall tears down the connection and then attempts to reconnect to the peer. The default setting is 3 failures.
Windows networks use the Network Basic Input/Output System (NetBIOS) for several basic network services such as naming and neighborhood device discovery. Because VPN routers do not usually pass NetBIOS traffic, these network services do not function for hosts on opposite ends of a VPN connection. To solve this problem, you can configure the wireless VPN firewall to bridge NetBIOS traffic over the VPN tunnel.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description · IKE SA Parameters

To enable NetBIOS bridging on a configured VPN tunnel:
As an alternate solution to IPSec VPN tunnels, you can configure a Layer 2 Tunneling Protocol (L2TP) server on the wireless VPN firewall to allow users to access L2TP clients over L2TP tunnels. A maximum of 25 simultaneous L2TP user sessions are supported. (The very first IP address of the L2TP address pool is used for distribution to the wireless VPN firewall.)
An L2TP Access Concentrator (LAC) typically initiates a tunnel to fulfill a connection request from an L2TP user; the L2TP server accommodates the tunnel request. After an L2TP tunnel
Virtual Private Networking Using IPSec and L2TP Connections

is established, the L2TP user can connect to an L2TP client that is located behind the wireless VPN firewall.
L2TP. (Packets that traverse the L2TP tunnel are not encapsulated by IPSec.)
You need to enable the L2TP server on the wireless VPN firewall, specify an L2TP server address pool, and create L2TP user accounts. For information about how to create L2TP user accounts, see Configure User Accounts on page 303.
To enable the L2TP server and configure the L2TP server pool:

Table 64. L2TP Server screen settings
Starting IP Address The first IP address of the pool. This address is used for distribution to the wireless VPN firewall.
Ending IP Address The last IP address of the pool. A maximum of 26 contiguous addresses is supported. (The first address of the pool cannot be assigned to a user.)
Idle Timeout The period after which an idle user is automatically logged out of the L2TP server. The default idle time-out period is 10 minutes.
Virtual Private Networking Using IPSec and L2TP Connections
Setting Description

To view the active L2TP tunnel users, select VPN > Connection Status > L2TP Active Users. The L2TP Active Users screen displays:

The List of L2TP Active Users table lists each active connection with the information that is described in the following table.
Table 65. L2TP Active Users screen information
Username The name of the L2TP user that you have defined (see Configure User Accounts on page 303).
Remote IP The client’s IP address on the remote LAC.
L2TP IP The IP address that is assigned by the L2TP server on the wireless VPN firewall.
Action Click the Disconnect table button to terminate the L2TP connection.
Virtual Private Networking Using IPSec and L2TP Connections
Item Description

The wireless VPN firewall provides a hardware-based SSL VPN solution designed specifically to provide remote access for mobile users to their corporate resources, bypassing the need for a preinstalled VPN client on their computers. Using the familiar Secure Sockets Layer (SSL) protocol, commonly used for e-commerce transactions, the wireless VPN firewall can authenticate itself to an SSL-enabled client, such as a standard web browser. Once the authentication and negotiation of encryption information are completed, the server and client can establish an encrypted connection. With support for up to 5 dedicated SSL VPN tunnels, the wireless VPN firewall allows users to easily access the remote network for a customizable, secure, user portal experience from virtually any available platform.
This chapter contains the following sections:
The wireless VPN firewall’s SSL VPN portal can provide two levels of SSL service to the remote user:

The SSL VPN client provides a point-to-point (PPP) connection between the client and the wireless VPN firewall, and a virtual network interface is created on the user’s computer. The wireless VPN firewall assigns the computer an IP address and DNS server IP addresses, allowing the remote computer to access network resources in the same manner as if it were connected directly to the corporate network, subject to any policy restrictions that you configure.
- Port forwarding supports only TCP connections, not UDP connections, or connections using other IP protocols.
- Port forwarding detects and reroutes individual data streams on the user’s computer to the port forwarding connection rather than opening up a full tunnel to the corporate network.
- Port forwarding offers more fine-grained management than an SSL VPN tunnel. You define individual applications and resources that are available to remote users.
The SSL VPN portal can present the remote user with one or both of these SSL service levels, depending on how you set up the configuration.
To configure and activate SSL connections, perform the following six basic steps in the order that they are presented:
When remote users log in to the wireless VPN firewall, they see a portal page that you can customize to present the resources and functions that you choose to make available.
a. Create one or more authentication domains for authentication of SSL VPN users.
When remote users log in to the wireless VPN firewall, they need to specify a domain to which their login account belongs. The domain determines the authentication method that is used and the portal layout that is presented, which in turn determines the network resources to which the users are granted access. Because you need to assign a portal layout when creating a domain, the domain is created after you have created the portal layout.
b. Create one or more groups for your SSL VPN users.
When you define the SSL VPN policies that determine network resource access for your SSL VPN users, you can define global policies, group policies, or individual policies. Because you need to assign an authentication domain when creating a group, the group is created after you have created the domain.
c. Create one or more SSL VPN user accounts.
Virtual Private Networking Using SSL Connections

Because you need to assign a group when creating an SSL VPN user account, the user account is created after you have created the group.
Create a list of servers and services that can be made available through user, group, or global policies. You can also associate fully qualified domain names (FQDNs) with these servers. The wireless VPN firewall resolves the names to the servers using the list you have created.
For the SSL VPN tunnel option, the wireless VPN firewall creates a virtual network adapter on the remote computer that then functions as if it were on the local network. Configure the portal’s SSL VPN client to define a pool of local IP addresses to be issued to remote clients, as well as DNS addresses. Declare static routes or grant full access to the local network, subject to additional policies.
Network resource objects are groups of IP addresses, IP address ranges, and services. By defining resource objects, you can more quickly create and configure network policies.
Policies determine access to network resources and addresses for individual users, groups, or everyone.
The Portal Layouts screen that you can access from the SSL VPN configuration menu allows you to create a custom screen that remote users see when they log in to the portal. Because the log-in screen is customizable, it provides an ideal way to communicate remote access instructions, support information, technical contact information, or VPN-related news updates to remote users. The log-in screen is also well suited as a starting screen for restricted users; if mobile users or business partners are permitted to access only a few resources, the log-in screen that you create presents only the resources that are relevant to these users.
You apply portal layouts by selecting one from the available portal layouts in the configuration of a domain. When you have completed your portal layout, you can apply the portal layout to one or more authentication domains (see Configure Domains on page 296). You can also make the new portal the default portal for the SSL VPN gateway by selecting the default radio button next to the portal layout name.
The wireless VPN firewall’s default portal address is https://<IP_address>/portal/SSL-VPN in which the IP address can be either an IPv4 or an IPv6 address. Both types of addresses are supported simultaneously. The default domain geardomain is assigned to the default SSL-VPN portal.
Virtual Private Networking Using SSL Connections

You can define individual layouts for the SSL VPN portal. The layout configuration includes the menu layout, theme, portal pages to display, and web cache control options. The default portal layout is the SSL-VPN portal. You can add additional portal layouts. You can also make any portal the default portal for the wireless VPN firewall by clicking the Default button in the Action column of the List of Layouts table, to the right of the desired portal layout.
To create a new SSL VPN portal layout:

Figure 162. Portal Layouts screen for IPv4

Figure 163. Portal Layouts screen for IPv6
Virtual Private Networking Using SSL Connections

The List of Layouts table displays the following fields:
- Portal URL (IPv4). The IPv4 URL at which the portal can be accessed. The IPv4 address in the URL is the public WAN address of the wireless VPN firewall (see Configure the IPv4 Internet Connection and WAN Settings on page 26). Both the IPv4 URL and the IPv6 URL can be active simultaneously.
- Portal URL (IPv6). The IPv6 URL at which the portal can be accessed. The IPv6 address in the URL is the public WAN address of the wireless VPN firewall (see Configure the IPv6 Internet Connection and WAN Settings on page 37). Both the IPv6 URL and the IPv4 URL can be active simultaneously.

Virtual Private Networking Using SSL Connections

Table 66. Add Portal Layout screen settings
Portal Layout and Theme Name
Portal Layout Name A descriptive name for the portal layout. This name is part of the path of the SSL VPN portal URL.
Portal Site Title The title that displays at the top of the user’s web browser window, for example, Company Customer Support.
Banner Title The banner title of a banner message that users see before they log in to the portal, for example, Welcome to Customer Support.
Banner Message The text of a banner message that users see before they log in to the portal, for example, In case of login difficulty, call 123-456-7890. Enter a plain text message, or include HTML and JavaScript tags. The maximum length of the login screen message is 4096 characters.
Display banner message on login page
Select this check box to show the banner title and banner message text on the login screen as shown in Figure 175 on page 290.
HTTP meta tags for cache control (recommended)
Select this check box to apply cache control directives for the HTTP meta tags to this portal layout. Cache control directives include:
Virtual Private Networking Using SSL Connections
Setting Description

Table 66. Add Portal Layout screen settings (continued)
ActiveX web cache cleaner
Select this check box to enable ActiveX cache control to be loaded when users log in to the SSL VPN portal. The web cache cleaner prompts the user to delete all temporary Internet files, cookies, and browser history when the user logs out or closes the web browser window. The ActiveX web cache control is ignored by web browsers that do not support ActiveX.
SSL VPN Portal Pages to Display
VPN Tunnel page To provide full network connectivity, select this check box.
Port Forwarding To specific defined network services, select this check box to provide access.
To edit a portal layout:
To delete one or more portal layouts:
Remote users connecting to the wireless VPN firewall through an SSL VPN portal need to be authenticated before they are granted access to the network. The login screen that is presented to the user requires three items: a user name, a password, and a domain selection. The domain determines both the authentication method and the portal layout that are used.
You need to create name and password accounts for the SSL VPN users. When you create a user account, you need to specify a group. Groups are used to simplify the application of
Virtual Private Networking Using SSL Connections
Setting Description

access policies. When you create a group, you need to specify a domain. Therefore, you should create any domains first, then groups, and then user accounts.
For information about how to configure domains, groups, and users, see Configure Authentication Domains, Groups, and Users on page 296.
Port forwarding provides access to specific defined network services. To define these services, you need to specify the internal server addresses and port numbers for TCP applications that are intercepted by the port forwarding client on the user’s computer. This client reroutes the traffic to the wireless VPN firewall.
To configure port forwarding, you need to define the IP addresses of the internal servers and the port number for TCP applications that are available to remote users.
To add a server and a port number:

Virtual Private Networking Using SSL Connections

Table 67. Port forwarding applications/TCP port numbers
TCP Application Port Number
FTP data (usually not needed) 20
FTP Control Protocol 21
SMTP (send mail) 25
POP3 (receive mail) 110
NTP (Network Time Protocol) 123
VNC (virtual network computing) 5900 or 5800
a. Users can specify the port number together with the host name or IP address.
To delete an application from the List of Configured Applications for Port Forwarding table:
After you have configured port forwarding by defining the IP addresses of the internal servers and the port number for TCP applications that are available to remote users, you then can also specify host-name-to-IP-address resolution for the network servers as a convenience for users. Host name resolution allows users to access TCP applications at familiar addresses such as mail.example.com or ftp.customer.com rather than by IP addresses.
Virtual Private Networking Using SSL Connections

To add servers and host names for client name resolution:
display in the List of Configured Applications for Port Forwarding table, you need to add it before you can rename it.
To delete a name from the List of Configured Host Names for Port Forwarding table:
The SSL VPN client on the wireless VPN firewall assigns IP addresses to remote VPN tunnel clients. Because the VPN tunnel connection is a point-to-point connection, you can assign IP addresses from the local subnet to the remote VPN tunnel clients.
The following are some additional considerations:
- A full tunnel sends all of the client’s traffic across the VPN tunnel.
Virtual Private Networking Using SSL Connections

- A split tunnel sends only traffic that is destined for the local network based on the specified client routes. All other traffic is sent to the Internet. A split tunnel allows you to manage bandwidth by reserving the VPN tunnel for local traffic only.
First determine the address range to be assigned to VPN tunnel clients, and then define the address range.
To define the client IP address range:

Figure 166. SSL VPN Client screen for IPv4
Virtual Private Networking Using SSL Connections


Figure 167. SSL VPN Client screen for IPv6
Table 68. SSL VPN Client screen settings for IPv4 and IPv6
Client IP Address Range
Enable Full Tunnel Support Select this check box to enable full-tunnel support. If you leave this check box cleared (which is the default setting), full-tunnel support is disabled but split-tunnel support is enabled, and you need to add client routes (see Add Routes for VPN Tunnel Clients on page 278).
DNS Suffix A DNS suffix to be appended to incomplete DNS search strings. This setting is optional.
Primary DNS Server The IP address of the primary DNS server that is assigned to the VPN tunnel clients. This setting is optional.
Virtual Private Networking Using SSL Connections
Setting Description

Table 68. SSL VPN Client screen settings for IPv4 and IPv6 (continued)
Secondary DNS Server The IP address of the secondary DNS server that is assigned to the VPN tunnel clients. This setting is optional.
Client Address Range Begin
The first IP address of the IPv4 address range that you want to assign to the VPN tunnel clients. By default, the first IPv4 address is 192.168.251.1.
Client Address Range End
The last IP address of the IPv4 address range that you want to assign to the VPN tunnel clients. By default, the last IPv4 address is 192.168.251.254.
Client IPv6 Address Range Begin
The first IP address of the IPv6 address range that you want to assign to the VPN tunnel clients. By default, the first IPv6 address is 4000::1.
Client IPv6 Address Range End
The last IP address of the IPv6 address range that you want to assign to the VPN tunnel clients. By default, the last IPv6 address is 4000::200.
The VPN tunnel clients assume that the following networks are located across the VPN-over-SSL tunnel:
If the assigned client IP address range is in a different subnet from the local network, or if the local network has multiple subnets, or if you select split-tunnel operation, you need to define client routes.
To add an SSL VPN tunnel client route:
Virtual Private Networking Using SSL Connections
Setting Description · IPv4 screen only · IPv6 screen only

If VPN tunnel clients are already connected, disconnect and then reconnect the clients on the SSL VPN Connection Status screen (see View the SSL VPN Connection Status and SSL VPN Log on page 292). Doing so allows the clients to receive new addresses and routes.
To change the specifications of an existing route and to delete an old route:
If an existing route is no longer needed, you can delete it.
Network resources are groups of IP addresses, IP address ranges, and services. By defining resource objects, you can more quickly create and configure network policies. You do not need to redefine the same set of IP addresses or address ranges when you configure the same access policies for multiple users.
Defining network resources is optional; smaller organizations can choose to create access policies using individual IP addresses or IP networks rather than predefined network resources. But for most organizations, NETGEAR recommends that you use network resources. If your server or network configuration changes, you can perform an update quickly by using network resources instead of individually updating all of the user and group policies.
The resource name and service are independent of the IP version. However, the resource definition (see Edit Network Resources to Specify Addresses on page 280) is dependent on the IP version because you can assign either an IPv4 or an IPv6 address or network.
To define a network resource:
Virtual Private Networking Using SSL Connections


- VPN Tunnel. The resource applies only to a VPN tunnel.
- Port Forwarding. The resource applies only to port forwarding.
- All. The resource applies both to a VPN tunnel and to port forwarding.
To delete one or more network resources:
To edit network resources:
Virtual Private Networking Using SSL Connections


Table 69. Resources screen settings to edit a resource
Resource Name The unique identifier for the resource. You cannot modify the resource name after you have created it on the first Resources screen.
Service The SSL service that is assigned to the resource. You cannot modify the service after you have assigned it to the resource on the first Resources screen.
Virtual Private Networking Using SSL Connections
Setting Description · Add Resource Addresses

Table 69. Resources screen settings to edit a resource (continued)
IP Address / Name Applicable only when you select IP Address as the object type. Enter the IP address or FQDN for the location that is permitted to use this resource.
Network Address Applicable only when you select IP Network as the object type. Enter the network IP address for the locations that are permitted to use this resource. You also need to enter the mask length (IPv4 only) or prefix length (IPv6 only):
Enter the network mask (0–31) for the locations that are permitted to use this resource.
Enter the prefix length for the locations that are permitted to use this resource.
Port Range / Port Number A port or a range of ports (0–65535) to apply the policy to. The policy is applied to all TCP and UDP traffic that passes on those ports. Leave the fields blank to apply the policy to all traffic.
To delete a configuration from the Defined Resource Addresses table, click the Delete table button to the right of the configuration that you want to delete.
You can define and apply user, group, and global policies to predefined network resource objects, IP addresses, address ranges, or all IP addresses, and to different SSL VPN services. A specific hierarchy is invoked over which policies take precedence. The wireless VPN firewall policy hierarchy is defined as follows:
Virtual Private Networking Using SSL Connections
Setting Description

For example, a policy that is configured for a single IP address takes precedence over a policy that is configured for a range of addresses. And a policy that applies to a range of IP addresses takes precedence over a policy that is applied to all IP addresses. If two or more IP address ranges are configured, then the smallest address range takes precedence. Host names are treated the same as individual IP addresses.
Network resources are prioritized just like other address ranges. However, the prioritization is based on the individual address or address range, not the entire network resource.
For example, assume the following global policy configuration:
Assuming that no conflicting user or group policies have been configured, if a user attempted to access FTP servers at the following addresses, the actions listed would occur:
address 10.0.1.3. The wireless VPN firewall’s policy engine does not perform reverse DNS lookups.
To view the existing SSL VPN policies:
Virtual Private Networking Using SSL Connections


To add an SSL VPN policy:
Virtual Private Networking Using SSL Connections


Figure 171. Add SSL VPN Policy screen for IPv4

Figure 172. Add SSL VPN Policy screen for IPv6
Virtual Private Networking Using SSL Connections

Table 70. Add SSL VPN Policy screen settings
Add SSL VPN Policies
Policy Name A descriptive name of the SSL VPN policy for identification and management purposes.
From the drop-down list, select a network resource that you have defined on the Resources screen (see Use Network Resource Objects to Simplify Policies on page 279).
Permission From the drop-down list, select Permit or Deny to specify whether the policy permits or denies access.
IP Address Policy Name A descriptive name of the SSL VPN policy for identification and management purposes.
IP Address The IPv4 or IPv6 address to which the SSL VPN policy is applied.
Port Range / Port Number
A port (fill in the Begin field) or a range of ports (fill in the Begin and End fields) to which the SSL VPN policy is applied. Ports can be 0 through 65535. The policy is applied to all TCP and UDP traffic that passes on those ports. Leave the fields blank to apply the policy to all traffic.
Virtual Private Networking Using SSL Connections

Table 70. Add SSL VPN Policy screen settings (continued)
Apply Policy to? (continued)
Permission From the drop-down list, select Permit or Deny to specify whether the policy permits or denies access.
IP Network Policy Name A descriptive name of the SSL VPN policy for identification and management purposes.
IP Address The network IPv4 or IPv6 network address to which the SSL VPN policy is applied.
The IPv4 network subnet mask to which the SSL VPN policy is applied.
The IPv6 prefix length that apples to the network to which the SSL VPN policy is applied.
Port Range / Port Number
A port (fill in the Begin field) or a range of ports (fill in the Begin and End fields) to which the SSL VPN policy is applied. Ports can be 0 through 65535. The policy is applied to all TCP and UDP traffic that passes on those ports. Leave the fields blank to apply the policy to all traffic.
Permission From the drop-down list, select Permit or Deny to specify whether the policy permits or denies access.
Policy Name A descriptive name of the SSL VPN policy for identification and management purposes.
Port Range / Port Number
A port (fill in the Begin field) or a range of ports (fill in the Begin and End fields) to which the SSL VPN policy is applied. Ports can be 0 through 65535. The policy is applied to all TCP and UDP traffic that passes on those ports. Leave the fields blank to apply the policy to all traffic.
Permission From the drop-down list, select Permit or Deny to specify whether the policy permits or denies access.
Virtual Private Networking Using SSL Connections

secure HTTP remote management is enabled (see Configure Remote Management Access on page 331). If secure HTTP remote management is not enabled, all SSL VPN user connections are disabled.
To edit an SSL VPN policy:
To delete one or more SSL VPN policies:
All screens that you can access from the SSL VPN menu of the web management interface display a user portal link in the upper right of the screen, above the menu bars ( ).
When you click the User Portal link, the SSL VPN default portal opens (see Figure 176 on page 291). This user portal is not the same as the new SSL portal login screen that you defined in Create the Portal Layout on page 268.
To open the new SSL portal login screen:
Virtual Private Networking Using SSL Connections

Figure 173. Portal Layouts screen for IPv4
Figure 174. Portal Layouts screen for IPv6
Virtual Private Networking Using SSL Connections


Virtual Private Networking Using SSL Connections



The User Portal screen displays a simple menu that, depending on the resources allocated, provides the SSL user with the following menu selections:
Virtual Private Networking Using SSL Connections

tunnel, the NETGEAR SSL VPN tunnel adapter is installed; the first time that a user attempts to connect through the port forwarding tunnel, the NETGEAR port forwarding engine is installed.
To view the status of current SSL VPN tunnels:
Select VPN > Connection Status > SSL VPN Connection Status. The SSL VPN Connection Status screen displays:

The active user’s name, group, and IP address are listed in the table with a time stamp indicating the time and date that the user connected.
To disconnect an active user, click the Disconnect table button to the right of the user’s table entry.
To display the SSL VPN log:
Select Monitoring > VPN Logs > SSL VPN Logs. The SSL VPN Logs screen displays:
Virtual Private Networking Using SSL Connections


Virtual Private Networking Using SSL Connections

This chapter describes how to manage users, authentication, and security certificates for IPSec VPN and SSL VPN. The chapter contains the following sections:
Users are assigned to a group, and a group is assigned to a domain. Therefore, you should first create any domains, then groups, then user accounts.
are discussed in Manage IPv4 Groups and Hosts (IPv4 LAN Groups) on page 67.
You need to create name and password accounts for all users who need to be able to connect to the wireless VPN firewall. This includes administrators, guests, and SSL VPN clients. Accounts for IPSec VPN clients are required only if you have enabled extended authentication (XAUTH) in your IPSec VPN configuration.
Users connecting to the wireless VPN firewall need to be authenticated before being allowed to access the wireless VPN firewall or the VPN-protected network. The login screen that is presented to the user requires three items: a user name, a password, and a domain selection. The domain determines the authentication method that is used and, for SSL connections, the portal layout that is presented.
assigned to a group.

Except in the case of IPSec VPN users, when you create a user account, you need to specify a group. When you create a group, you need to specify a domain.
The following table summarizes the external authentication protocols and methods that the wireless VPN firewall supports.
Table 71. External authentication protocols and methods
Authentication Protocol or Method
PAP Password Authentication Protocol (PAP) is a simple protocol in which the client sends a password in clear text.
CHAP 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.
RADIUS A network-validated PAP or CHAP password-based authentication method that functions with Remote Authentication Dial In User Service (RADIUS).
MIAS A network-validated PAP or CHAP password-based authentication method that functions with Microsoft Internet Authentication Service (MIAS), which is a component of Microsoft Windows 2003 Server.
WiKID WiKID Systems is a PAP or CHAP key-based two-factor authentication method that functions with public key cryptography. The client sends an encrypted PIN to the WiKID server and receives a one-time passcode with a short expiration period. The client logs in with the passcode. See Appendix B, Two-Factor Authentication, for more on WiKID authentication.
NT Domain A network-validated domain-based authentication method that functions with a Microsoft Windows NT Domain authentication server. This authentication method has been superseded by Microsoft Active Directory authentication but is supported to authenticate legacy Windows clients.
Active Directory A network-validated domain-based authentication method that functions with a Microsoft Active Directory authentication server. Microsoft Active Directory authentication servers support a group and user structure. Because the Active Directory supports a multilevel hierarchy (for example, groups or organizational units), this information can be queried to provide specific group policies or bookmarks based on Active Directory attributes.
LDAP A network-validated domain-based authentication method that functions with a Lightweight Directory Access Protocol (LDAP) authentication server. LDAP is a standard for querying and updating a directory. Because LDAP supports a multilevel hierarchy (for example, groups or organizational units), this information can be queried to provide specific group policies or bookmarks based on LDAP attributes.
Manage Users, Authentication, and VPN Certificates
Description

The domain determines the authentication method to be used for associated users. For SSL connections, the domain also determines the portal layout that is presented, which in turn determines the network resources to which the associated users have access. The default domain of the wireless VPN firewall is named geardomain. You cannot delete the default domain.
To create a domain:

Manage Users, Authentication, and VPN Certificates
Create Domains

The List of Domains table displays the domains with the following fields:

Table 72. Add Domain screen settings
Domain Name A descriptive (alphanumeric) name of the domain for identification and management purposes.
- Authentication Server - Authentication Secret
Manage Users, Authentication, and VPN Certificates
Setting Description

Table 72. Add Domain screen settings (continued)
- Authentication Server - Authentication Secret • MIAS-CHAP. Microsoft Internet Authentication Service (MIAS) CHAP. Complete the following fields:
- Authentication Server - Active Directory Domain • LDAP. Lightweight Directory Access Protocol (LDAP). Complete the following fields, and make a selection from the LDAP Encryption drop-down list:
- Authentication Server - LDAP Base DN
Select Portal The portal that is assigned to this domain and that is presented to the user to enter credentials. The default portal is SSL-VPN.
Authentication Server The server IP address or server name of the authentication server for any type of authentication other than authentication through the local user database.
Authentication Secret The authentication secret or password that is required to access the authentication server for RADIUS, WiKID, or MIAS authentication.
Workgroup The workgroup that is required for Microsoft NT Domain authentication.
Manage Users, Authentication, and VPN Certificates
Setting Description · Authentication Type (continued)

Table 72. Add Domain screen settings (continued)
The Active Directory domain name that is required for Microsoft Active Directory authentication.
If you disable local authentication, make sure that there is at least one external administrative user; otherwise, access to the wireless VPN firewall is blocked.
To delete one or more domains:
Manage Users, Authentication, and VPN Certificates
Setting Description · Active Directory Domain

To edit a domain:
The use of groups simplifies the configuration of VPN policies when different sets of users have different restrictions and access controls. It also simplifies the configuration of web access exception rules. Like the default domain of the wireless VPN firewall, the default group is also named geardomain. The default group geardomain is assigned to the default domain geardomain. You cannot delete the default domain geardomain, nor its associated default group geardomain.
When you create a new domain on the Domains screen (see the previous section), a group with the same name as the new domain is created automatically. You cannot delete such a group. However, when you delete the domain with which it is associated, the group is deleted automatically.
assigned to a group.
SSL VPN policies. These groups should not be confused with LAN groups that are defined on the IPv4 LAN Groups screen and that are used to simplify firewall policies. For information about LAN groups, see Manage IPv4 Groups and Hosts (IPv4 LAN Groups) on page 67.
Manage Users, Authentication, and VPN Certificates
Edit Domains

To create a VPN group:

The List of Groups table displays the VPN groups with the following fields:
Manage Users, Authentication, and VPN Certificates
Create Groups


Table 73. Add Group screen settings
Name A descriptive (alphanumeric) name of the group for identification and management purposes.
Domain The drop-down list shows the domains that are listed on the Domain screen. From the drop-down list, select the domain with which the group is associated. For information about how to configure domains, see Configure Domains on page 296.
Idle Timeout The period after which an idle user is automatically logged out of the wireless VPN firewall’s web management interface. The default idle time-out period is 10 minutes.
To delete one or more groups:
Groups that were automatically created when you created a domain cannot be deleted on the Groups screen. See the Important note at the beginning of this section.
Manage Users, Authentication, and VPN Certificates
Setting Description

For groups that were automatically created when you created a domain, you can modify only the idle time-out settings but not the group name or associated domain.
For groups that you created on the Add Groups screen, you can modify the domain and the idle time-out settings but not the group name.
To edit a VPN group:
When you create a user account, you need to assign the user to a user group. When you create a group, you need to assign the group to a domain that specifies the authentication method. Therefore, you should first create any domains, then groups, and then user accounts.
assigned to a group.
There are two default user accounts:
You can create five different types of user accounts by applying one of the predefined user types:
Manage Users, Authentication, and VPN Certificates
Edit Groups

To create a user account:

The List of Users table displays the users and has the following fields:
Manage Users, Authentication, and VPN Certificates


Table 74. Add Users screen settings
User Name A descriptive (alphanumeric) name of the user for identification and management purposes.
Select Group The drop-down list shows the groups that are listed on the Group screen. From the drop-down list, select the group to which the user is assigned. For information about how to configure groups, see Configure Groups on page 300.
Password The password that the user needs to enter to gain access to the wireless VPN firewall.
Confirm Password This field needs to be identical to the password that you entered in the Password field.
Idle Timeout The period after which an idle user is automatically logged out of the web management interface. The default idle time-out period is 5 minutes.
Manage Users, Authentication, and VPN Certificates
Setting Description

To delete one or more user accounts:
You can restrict the ability of defined users to log in to the wireless VPN firewall’s web management interface. You can also require or prohibit logging in from certain IP addresses or from particular browsers. This section consists of the following subsections:
To configure user login policies:

Manage Users, Authentication, and VPN Certificates
Configure Login Policies

is selected by default for guests and administrators. The Disable Login check box is disabled (masked out) for administrators.
Configure Login Restrictions Based on IPv4 Addresses
To restrict logging in based on IPv4 addresses:

Manage Users, Authentication, and VPN Certificates

Table 75. Defined addresses settings for IPv4
Network Address / IP Address
Depending on your selection from the Source Address Type drop-down list, enter the IP address or the network address.
Mask Length For a network address, enter the netmask length (0–32).
To delete one or more IPv4 addresses:
Configure Login Restrictions Based on IPv6 Addresses
To restrict logging in based on IPv6 addresses:
Manage Users, Authentication, and VPN Certificates
Setting Description


Table 76. Defined addresses settings for IPv6
Network Address / IP Address
Depending on your selection from the Source Address Type drop-down list, enter the IP address or the network address.
Prefix Length For a network address, enter the prefix length (0–64).
Manage Users, Authentication, and VPN Certificates
Setting Description

To delete one or more IPv6 addresses:
Configure Login Restrictions Based on Web Browser
To restrict logging in based on the user’s browser:

Manage Users, Authentication, and VPN Certificates

To delete one or more browsers:
For any user, you can change the password, user type, and idle time-out settings. Only administrators have read/write access. All other users have read-only access.
management interface are both password. NETGEAR recommends that you change the password for the administrator account to a more secure password, and that you configure a separate secure password for the guest account.
language, and should be a mixture of letters (both uppercase and lowercase), numbers, and symbols. Your password can be up to 32 characters.
changed back to password and 5 minutes, respectively.
Manage Users, Authentication, and VPN Certificates

To modify user settings, including passwords:

you need to change the user name or the group, delete the user account and recreate it with the correct name or group.
Table 77. Edit User screen settings
Manage Users, Authentication, and VPN Certificates
Setting Description · Select User Type

Table 77. Edit User screen settings (continued)
Check to Edit Password
Select this check box to make the password fields accessible to modify the password.
Enter Your Password Enter the password with which you have logged in.
New Password Enter the new password.
Confirm New Password Reenter the new password for confirmation.
Idle Timeout The period after which an idle user is automatically logged out of the web management interface. The default idle time-out period is 5 minutes.
The wireless VPN firewall uses digital certificates (also known as X509 certificates) during the Internet Key Exchange (IKE) authentication phase to authenticate connecting IPSec VPN gateways or clients, or to be authenticated by remote entities:
Digital certificates are extended for secure web access connections over HTTPS (that is, SSL connections).
Digital certificates either can be self-signed or can be issued by certification authorities (CAs) such as an internal Windows server or an external organization such as Verisign or Thawte.
However, if the digital certificate contains the extKeyUsage extension, the certificate needs to be used for one of the purposes defined by the extension. For example, if the digital certificate contains the extKeyUsage extension that is defined for SNMPv2, the same certificate cannot be used for secure web management. The extKeyUsage would govern the certificate acceptance criteria on the wireless VPN firewall when the same digital certificate is being used for secure web management.
On the wireless VPN firewall, the uploaded digital certificate is checked for validity and purpose. The digital certificate is accepted when it passes the validity test and the purpose matches its use. The check for the purpose needs to correspond to its use for IPSec VPN, SSL VPN, or both. If the defined purpose is for IPSec VPN and SSL VPN, the digital certificate is uploaded to both the IPSec VPN certificate repository and the SSL VPN
Manage Users, Authentication, and VPN Certificates
Setting Description

certificate repository. However, if the defined purpose is for IPSec VPN only, the certificate is uploaded only to the IPSec VPN certificate repository.
The wireless VPN firewall uses digital certificates to authenticate connecting VPN gateways or clients, and to be authenticated by remote entities. A digital certificate that authenticates a server, for example, is a file that contains the following elements:
You can obtain a digital certificate from a well-known commercial certification authority (CA) such as Verisign or Thawte, or you can generate and sign your own digital certificate. Because a commercial CA takes steps to verify the identity of an applicant, a digital certificate from a commercial CA provides a strong assurance of the server’s identity. A self-signed digital certificate triggers a warning from most browsers because it provides no protection against identity theft of the server.
The wireless VPN firewall contains a self-signed digital certificate from NETGEAR. This certificate can be downloaded from the wireless VPN firewall login screen for browser import. However, NETGEAR recommends that you replace this digital certificate with a digital certificate from a well-known commercial CA prior to deploying the wireless VPN firewall in your network.
To display the Certificates screen, select VPN > Certificates. Because of the large size of this screen, and because of the way the information is presented, the Certificates screen is divided and presented in this manual in three figures (Figure 191 on page 315, Figure 193 on page 317, and Figure 195 on page 321).
The Certificates screen lets you view the currently loaded digital certificates, upload a new digital certificate, and generate a certificate signing request (CSR). The wireless VPN firewall typically holds two types of digital certificates:
The Certificates screen contains four tables that are explained in detail in the following sections:
Manage Users, Authentication, and VPN Certificates

To view and upload trusted certificates:
Select VPN > Certificates. The Certificates screen displays. (The following figure shows the top section of the screen with the trusted certificate information and an example certificate in the Trusted Certificates [CA Certificate] table.)

Figure 191. Certificates, screen 1 of 3
The Trusted Certificates (CA Certificate) table lists the digital certificates of CAs and contains the following fields:
To upload a digital certificate of a trusted CA on the wireless VPN firewall:
Manage Users, Authentication, and VPN Certificates

To delete one or more digital certificates:
Instead of obtaining a digital certificate from a CA, you can generate and sign your own digital certificate. However, a self-signed digital certificate triggers a warning from most browsers because it provides no protection against identity theft of the server. (The following figure shows an image of a browser security alert.)
There can be three reasons why a security alert is generated for a security certificate:
When a security alert is generated, the user can decide whether to trust the host.

Manage Users, Authentication, and VPN Certificates

Generate a CSR and Obtain a Self-Signed Certificate from a CA
To use a self-signed certificate, you first need to request the digital certificate from a CA, and then download and activate the digital certificate on the wireless VPN firewall. To request a self-signed certificate from a CA, you need to generate a certificate signing request (CSR) for and on the wireless VPN firewall. The CSR is a file that contains information about your company and about the device that holds the certificate. Refer to the CA for guidelines about the information that you need to include in your CSR.
To generate a new CSR file, obtain a digital certificate from a CA, and upload it to the wireless VPN firewall:

Figure 193. Certificates, screen 2 of 3
Manage Users, Authentication, and VPN Certificates

Table 78. Generate self-signed certificate request settings
Name A descriptive name of the domain for identification and management purposes.
Subject The name that other organizations see as the holder (owner) of the certificate. In general, use your registered business name or official company name for this purpose.
Signature Algorithm Although this seems to be a drop-down list, the only possible selection is RSA. In other words, RSA is the default to generate a CSR.
Optional Fields IP Address Enter your fixed (static) IP address. If your IP address is dynamic, leave this field blank.
Domain Name Enter your Internet domain name, or leave this field blank.
E-mail Address Enter the email address of a technical contact in your company.
Manage Users, Authentication, and VPN Certificates
Setting Description


a. Connect to the website of the CA.
b. Start the SCR procedure.
c. When prompted for the requested data, copy the data from your saved text file
(including “ BEGIN CERTIFICATE REQUEST ” and “ END CERTIFICATE REQUEST ”).
d. Submit the CA form. If no problems ensue, the digital certificate is issued by the CA.
Manage Users, Authentication, and VPN Certificates

To delete one or more SCRs:
View and Manage Self-Signed Certificates
The Active Self Certificates table on the Certificates screen (see Figure 193 on page 317) shows the digital certificates issued to you by a CA and available for use. For each self-signed certificate, the table lists the following information:
To delete one or more self-signed certificates:
A Certificate Revocation List (CRL) file shows digital certificates that have been revoked and are no longer valid. Each CA issues its own CRLs. It is important that you keep your CRLs up-to-date. You should obtain the CRL for each CA regularly.
To view the currently loaded CRLs and upload a new CRL:
Manage Users, Authentication, and VPN Certificates


Figure 195. Certificates, screen 3 of 3
The Certificate Revocation Lists (CRL) table lists the active CAs and their critical release dates:
is deleted when you upload the new CRL.
To delete one or more CRLs:
Manage Users, Authentication, and VPN Certificates

This chapter describes the tools for managing the network traffic to optimize its performance and the system management features of the wireless VPN firewall. The chapter contains the following sections:
Performance management consists of controlling the traffic through the wireless VPN firewall so that the necessary traffic gets through when there is a bottleneck. You can either reduce unnecessary traffic or reschedule some traffic to low-peak times to prevent bottlenecks from occurring in the first place. The wireless VPN firewall has the necessary features and tools to help the network manager accomplish these goals.
The maximum bandwidth capacity of the wireless VPN firewall in each direction is as follows:
In practice, the WAN-side bandwidth capacity is much lower when DSL or cable modems are used to connect to the Internet: The typical traffic rate is 1.5 Mbps. As a result, and depending on the traffic that is being carried, the WAN side of the wireless VPN firewall is the limiting factor for the data rate for most installations.

You can adjust the following features of the wireless VPN firewall in such a way that the traffic load on the WAN side decreases:
LAN WAN Outbound Rules and DMZ WAN Outbound Rules (Service Blocking)
You can control specific outbound traffic (from LAN to WAN and from the DMZ to WAN). The LAN WAN Rules screen and the DMZ WAN Rules screen list all existing rules for outbound traffic. Any outbound rule that you create restricts outgoing traffic and therefore decreases the traffic load on the WAN side.
On the LAN WAN screen, if you have not defined any rules, only the default rule is listed. The default LAN WAN outbound rule allows all outgoing traffic.
Incorrect configuration of outbound firewall rules can cause serious connection problems.
Each rule lets you specify the desired action for the connections that are covered by the rule:
The following section summarizes the various criteria that you can apply to outbound rules in order to reduce traffic. For more information about outbound rules, see Outbound Rules (Service Blocking) on page 130. For detailed procedures about how to configure outbound rules, see Configure LAN WAN Rules on page 138 and Configure DMZ WAN Rules on page 145.
When you define outbound firewall rules, you can further refine their application according to the following criteria:
- Any. The rule applies to all computers and devices on your LAN.
Network and System Management

- Single address. The rule applies to the address of a particular computer.
- Address range. The rule applies to a range of addresses.
- Groups. The rule applies to a group of computers. (You can configure groups for LAN WAN outbound rules but not for DMZ WAN outbound rules.) The Known PCs and Devices table is an automatically maintained list of all known computers and network devices and is generally referred to as the network database, which is described in Manage the Network Database on page 68. Computers and network devices are entered into the network database by various methods, which are described in Manage IPv4 Groups and Hosts (IPv4 LAN Groups) on page 67.
- Any. The rule applies to all Internet IP address.
- Single address. The rule applies to a single Internet IP address.
- Address range. The rule applies to a range of Internet IP addresses.
If you want to reduce traffic by preventing access to certain sites on the Internet, you can use the wireless VPN firewall’s content-filtering feature. By default, this feature is disabled; all requested traffic from any website is allowed.
The wireless VPN firewall provides the following methods to filter web content in order to reduce traffic:
To further narrow down the content filtering, you can configure groups to which the content-filtering rules apply and trusted domains for which the content-filtering rules do not apply.
Network and System Management
Content Filtering

If you want to reduce outgoing traffic by preventing Internet access by certain computers on the LAN, you can use the source MAC filtering feature to drop the traffic received from the computers with the specified MAC addresses. By default, this feature is disabled; all traffic received from computers with any MAC address is allowed. See Enable Source MAC Filtering on page 183 for the procedure about how to use this feature.
The following features of the wireless VPN firewall tend to increase the traffic load on the WAN side:
LAN WAN Inbound Rules and DMZ WAN Inbound Rules (Port Forwarding)
The LAN WAN Rules screen and the DMZ WAN Rules screen list all existing rules for inbound traffic (from WAN to LAN and from WAN to the DMZ). Any inbound rule that you create allows additional incoming traffic and therefore increases the traffic load on the WAN side.
ON the LAN WAN screen, if you have not defined any rules, only the default rule is listed. The default LAN WAN inbound rule blocks all access from outside except responses to requests from the LAN side.
Incorrect configuration of inbound firewall rules can cause serious connection problems.
Each rule lets you specify the desired action for the connections covered by the rule:
The following section summarizes the various criteria that you can apply to inbound rules and that might increase traffic. For more information about inbound rules, see Inbound Rules (Port Forwarding) on page 133. For detailed procedures about how to configure inbound
Network and System Management
Source MAC Filtering

rules, see Configure LAN WAN Rules on page 138 and Configure DMZ WAN Rules on page 145.
When you define inbound firewall rules, you can further refine their application according to the following criteria:
- Any. The rule applies to all computers and devices on your LAN.
- Single address. The rule applies to the address of a particular computer.
- Address range. The rule applies to a range of addresses.
- Groups. The rule is applied to a group of computers. (You can configure groups for LAN WAN outbound rules but not for DMZ WAN outbound rules.) The Known PCs and Devices table is an automatically maintained list of all known computers and network devices and is generally referred to as the network database, which is described in Manage the Network Database on page 68. Computers and network devices are entered into the network database by various methods, which are described in Manage IPv4 Groups and Hosts (IPv4 LAN Groups) on page 67.
- Any. The rule applies to all Internet IP address.
- Single address. The rule applies to a single Internet IP address.
- Address range. The rule applies to a range of Internet IP addresses.
Network and System Management

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 the port triggering feature requires that you know the port numbers used by the application. Without port triggering, the response from the external application would be treated as a new connection request rather than a response to a request from the LAN network. As such, it would be handled in accordance with the inbound port forwarding rules, and most likely would be blocked. For the procedure about how to configure port triggering, see Configure Port Triggering on page 190.
The demilitarized zone (DMZ) is a network that, by default, has fewer firewall restrictions when compared to the LAN. The DMZ can be used to host servers (such as a web server, FTP server, or email server) and provide public access to them. The eighth LAN port on the wireless VPN firewall (the rightmost LAN port) can be dedicated as a hardware DMZ port to safely provide services to the Internet without compromising security on your LAN. By default, the DMZ port and both inbound and outbound DMZ traffic are disabled. Enabling the DMZ port and allowing traffic to and from the DMZ increases the traffic through the WAN ports.
For information about how to enable the DMZ port, see Enable and Configure the DMZ Port for IPv4 and IPv6 Traffic on page 85. For the procedures about how to configure DMZ traffic rules, see Configure DMZ WAN Rules on page 145.
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. For an example of how to set up an exposed host, see IPv4 LAN WAN or IPv4 DMZ WAN Inbound Rule: Specifying an Exposed Host on page 163.
VPN and L2TP Tunnels
The wireless VPN firewall supports site-to-site IPSec VPN tunnels, dedicated SSL VPN tunnels, and L2TP tunnels. Each tunnel requires extensive processing for encryption and authentication, thereby increasing traffic through the WAN ports.
For information about IPSec VPN and L2TP tunnels, see Chapter 6, Virtual Private Networking Using IPSec and L2TP Connections. For information about SSL VPN tunnels, see Chapter 7, Virtual Private Networking Using SSL Connections.
Network and System Management
Port Triggering · DMZ Port · Exposed Hosts

By setting the QoS priority and assigning bandwidth profiles to firewall rules, you can shift the traffic mix to aim for optimum performance of the wireless VPN firewall.
The QoS priority settings determine the Quality of Service for the traffic passing through the wireless VPN firewall. You can assign a QoS priority to LAN WAN and DMZ WAN outbound firewall rules. The QoS is set individually for each firewall rule. You can change the mix of traffic through the WAN ports by granting some services a higher priority than others:
For more information about QoS profiles, see Preconfigured Quality of Service Profiles on page 177.
When you set the QoS priority, the WAN bandwidth does not change. You change the WAN bandwidth that is assigned to a service or application by applying a bandwidth profile to a LAN WAN inbound or outbound rule. The purpose of bandwidth profiles is to provide a method for allocating and limiting traffic, thus allocating LAN users sufficient bandwidth while preventing them from consuming all the bandwidth on your WAN links.
For more information about bandwidth profiles, see Create Bandwidth Profiles on page 175.
The wireless VPN firewall includes several tools that can be used to monitor the traffic conditions of the firewall and content-filtering engine and to monitor the users’ access to the Internet and the types of traffic that they are allowed to have. See Chapter 10, Monitor System Access and Performance, for a description of these tools.
Network and System Management
Set QoS Priorities · Assign Bandwidth Profiles

The default administrator and default guest passwords for the web management interface are both password. NETGEAR recommends that you change the password for the administrator account to a more secure password, and that you configure a separate secure password for the guest account.
settings, see Configure User Accounts on page 303 and Set User Login Policies on page 306.
To modify the administrator and guest passwords and idle time-out settings:
Network and System Management


You cannot modify the administrator user name, user type, or group assignment.
language, and should be a mixture of letters (both uppercase and lowercase), numbers, and symbols. Your password can be up to 32 characters.
changed back to password and 5 minutes, respectively.
Network and System Management

You can also change the administrator login policies:
logged in as an administrator.
addresses as practical.
In general, these policy settings work well for an administrator. However, you can change the administrator login policies as explained in Set User Login Policies on page 306.
An administrator can configure, upgrade, and check the status of the wireless VPN firewall over the Internet through a Secure Sockets Layer (SSL) VPN connection.
through a WAN interface is granted (see Configure Login Policies on page 306), the wireless VPN firewall’s web management interface is accessible to anyone who knows its IP address and default password. Because a malicious WAN user can reconfigure the wireless VPN firewall and misuse it in many ways, NETGEAR highly recommends that you change the admin and guest default passwords before continuing (see Change Passwords and Administrator and Guest Settings on page 329).
Network and System Management

To configure the wireless VPN firewall for remote management:

Figure 198. Remote Management screen for IPv4
Network and System Management


Figure 199. Remote Management screen for IPv6
Table 79. Remote Management screen settings for IPv4 and IPv6
Allow Secure HTTP Management?
To enable secure HTTP management, select the Yes radio button, which is the default setting. To disable secure HTTP management, select the No radio button.
Network and System Management
Setting Description · Secure HTTP Management

Table 79. Remote Management screen settings for IPv4 and IPv6 (continued)
Allow Secure HTTP Management? (continued)
Port Number Enter the port number through which access is allowed. The default port number is 443.
To enable Telnet management, select the Yes radio button. To disable Telnet management, select the No radio button, which is the default setting.
If you are remotely connected to the wireless VPN firewall and you select the No radio button to disable secure HTTP management, you and all other SSL VPN users are disconnected when you click Apply.
When remote management is enabled, you need to use an SSL connection to access the wireless VPN firewall from the Internet. You need to enter https:// (not http://) and type the wireless VPN firewall’s WAN IP address and port number in your browser. For example, if the wireless VPN firewall’s WAN IP address is 192.168.15.175 and the port number is 443, type the following in your browser: https://192.168.15.175:443.
The wireless VPN firewall’s remote login URL is:
https://<IP_address>: or https://<FullyQualifiedDomainName>:
The IP address can be an IPv4 or IPv6 address.
With respect to security, note the following:
Network and System Management

the WAN IP address of your wireless VPN firewall by running tracert from the Windows Run menu option. Trace the route to your registered FQDN. For example, enter tracert wireless VPN firewall.mynetgear.net, and the WAN IP address that your ISP assigned to the wireless VPN firewall is displayed.
You can access the command-line interface (CLI) using the console port on the rear panel of the wireless VPN firewall (see Rear Panel on page 18).
You can access the CLI from a communications terminal when the wireless VPN firewall is still set to its factory defaults (or use your own settings if you have changed them).
To access the CLI:
in which ip address is the IP address of the wireless VPN firewall.
Any configuration changes made through the CLI are not preserved after a reboot or power cycle unless you issue the CLI save command after making the changes.
Simple Network Management Protocol (SNMP) forms part of the Internet Protocol Suite as defined by the Internet Engineering Task Force (IETF). SNMP is used in network management systems such as the NETGEAR ProSafe Network Management Software (NMS200) to monitor network-attached devices for conditions that warrant administrative attention.
SNMP exposes management data in the form of variables on the managed systems, which describe the system configuration. These variables can then be queried (and sometimes set) by managing applications.
Network and System Management
telnet <ip address>

SNMP lets you monitor and manage your wireless VPN firewall 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 wireless VPN firewall supports SNMPv1, SNMPv2c, and SNMPv3.
To configure the SNMP settings:

The SNMPv3 Users table includes the default SNMPv3 users that are preconfigured on the wireless VPN firewall. The SNMPv3 Users table shows the following columns:
- NoAuthNoPriv. Both authentication and privacy are disabled.
- AuthNoPriv. Authentication is enabled but privacy is disabled.
- AuthPriv. Both authentication and privacy are enabled.
The SNMP Configuration table shows the following columns:
Network and System Management

Table 80. SNMP screen settings
IP Address Enter the IP address of the new SNMP manager.
Port Enter the port number of the new SNMP manager. The default port number is 162.
Community Enter the community string that allows the SNMP manager access to the MIB objects of the wireless VPN firewall for the purpose of reading only.
To edit an SNMP configuration:

Network and System Management
Setting Description

To delete one or more SNMP configurations:
To edit the SNMPv3 default users:

Table 81. Edit User screen settings for SNMPv3 users
Username The default user name (admin or guest) for information only.
Access Type The default access type (RWUSER or ROUSER) for information only.
Network and System Management
Setting Description

Table 81. Edit User screen settings for SNMPv3 users (continued)
Authentication Password The authentication password that an SNMPv3 user needs to enter to be granted access to the SNMP agent that collects the MIB objects from the wireless VPN firewall.
Privacy Password The privacy password that an SNMPv3 user needs to enter to allow decryption of the MIB objects that the SNMP agent collects from the wireless VPN firewall.
To configure the SNMP system information:

Table 82. SNMP SysConfiguration screen settings
SysContact Enter the SNMP system contact information that is available to the SNMP manager. This setting is optional.
SysLocation Enter the physical location of the wireless VPN firewall. This setting is optional.
Network and System Management
Setting Description · Setting Description

Table 82. SNMP SysConfiguration screen settings (continued)
SysName Enter the name of the wireless VPN firewall for SNMP identification purposes. The default name is FVS318N.
The configuration settings of the wireless VPN firewall are stored in a configuration file on the wireless VPN firewall. This file can be saved (backed up) to a computer, retrieved (restored) from the computer, cleared to factory default settings, or upgraded to a new version.
Once the wireless VPN firewall is installed and works correctly, make a backup of the configuration file to a computer. If necessary, you can later restore the wireless VPN firewall settings from this file.
The Backup & Restore Settings screen lets you:
To display the Settings Backup and Firmware Upgrade screen, select Administration > Settings Backup & Upgrade.

Network and System Management
Setting Description

The backup feature saves all wireless VPN firewall settings to a file. Back up your settings periodically, and store the backup file in a safe place.
firewall that has the same language and management software versions. Remember to change the IP address of the second wireless VPN firewall before deploying it to eliminate IP address conflicts on the network.
To back up settings:
Restore only settings that were backed up from the same software version. Restoring settings from a different software version can corrupt your backup file or the wireless VPN firewall system software.
To restore settings from a backup file:
The wireless VPN firewall reboots. During the reboot process, the Settings Backup and Firmware Upgrade screen might remain visible, or a status message with a counter might show the number of seconds left until the reboot process is complete. The reboot process takes about 165 seconds. (If you can see the unit: The reboot process is complete when the Test LED on the front panel goes off.)
Network and System Management
Back Up Settings · Restore Settings

Once you start restoring settings, do not interrupt the process. Do not try to go online, turn off the wireless VPN firewall, shut down the computer, or do anything else to the wireless VPN firewall until the settings have been fully restored.
Revert to Factory Default Settings
To reset the wireless VPN firewall to the original factory defaults settings:
Use one of the following two methods:
The wireless VPN firewall reboots. If you use the software Default button, the Settings Backup and Firmware Upgrade screen might remain visible during the reboot process, or a status message with a counter might show the number of seconds left until the reboot process is complete. The reboot process takes about 165 seconds. (If you can see the unit: The reboot process is complete when the Test LED on the front panel goes off.)
When you press the hardware factory default Reset button or click the software Default button, the wireless VPN firewall settings are erased. All firewall rules, VPN policies, LAN and WAN settings, and other settings are lost. Back up your settings if you intend on using them.
firewall’s password is password, and the LAN IP address is 192.168.1.1.
Network and System Management

You can install a different version of the wireless VPN firewall firmware from the Settings Backup and Firmware Upgrade screen. To view the current version of the firmware that the wireless VPN firewall is running, from the main menu, select Monitoring. The Router Status screen displays, showing the firmware version in the System Info section of the screen. After you have updated the firmware, the new firmware version is displayed.
To download a firmware version and upgrade the firmware:
During the upgrade process, the Settings Backup and Firmware Upgrade screen remains visible and a status bar shows the progress of the upgrade process. The upgrade process can take up to 10 minutes. When the status bar shows that the upgrade process is complete, it can take another 10 minutes before the wireless VPN firewall reboots.
After you have started the firmware installation process, do not interrupt the process. Do not try to go online, turn off the wireless VPN firewall, or do anything else to the wireless VPN firewall until the wireless VPN firewall has fully rebooted.
erase the configuration and manually reconfigure your wireless VPN firewall after upgrading it. See the firmware release notes that NETGEAR makes available.
Network and System Management
Update the Firmware

Configure date, time, and NTP server designations on the System Date & Time screen. Network Time Protocol (NTP) is a protocol that is used to synchronize computer clock times in a network of computers. Setting the correct system time and time zone ensures that the date and time recorded in the wireless VPN firewall logs and reports are accurate.
To set time, date, and NTP servers:

The bottom of the screen display the current weekday, date, time, time zone, and year (in the example in the previous figure: Current Time: Tue Mar 6 22:48:17 GMT-0800 2012).
Table 83. Time Zone screen settings
Date/Time From the drop-down list, select the local time zone in which the wireless VPN firewall operates. The correct time zone is required in order for scheduling to work correctly.
Automatically Adjust for Daylight Savings Time
If daylight saving time is supported in your region, select the Automatically Adjust for Daylight Savings Time check box. By default, the check box is disabled.
Force IPv6 address resolution for servers
Select this check box to force the use of IPv6 addresses and FQDN (domain name) resolution in the Server 1 Name / IP Address and Server 2 Name / IP Address fields when you have selected the Use Custom NTP Servers radio button.
Network and System Management
Setting Description

Table 83. Time Zone screen settings (continued)
NTP Servers (default or custom)
NTP Servers (custom) Server 1 Name / IP Address Enter the IP address or host name of the primary NTP server.
Server 2 Name / IP Address Enter the IP address or host name of the backup NTP server.
FQDN, the wireless VPN firewall determines the IP address of the NTP server by performing a DNS lookup. Before the wireless VPN firewall can perform this lookup, you need to configure a DNS server address on the Broadband ISP Settings screen (see Manually Configure an IPv4 Internet Connection on page 31.)
Network and System Management
Setting Description

This chapter describes the system-monitoring features of the wireless VPN firewall. You can be alerted to important events such WAN traffic limits reached, login failures, and attacks. You can also view status information about the firewall, WAN ports, LAN ports, active VPN users and tunnels, and more. In addition, the diagnostics utilities are described. The chapter contains the following sections:
E-mail screen and some of the functions that are part of the Diagnostics screen require that you configure the email notification server—see Configure Logging, Alerts, and Event Notifications on page 349.
If your ISP charges by traffic volume over a given period, or if you want to study traffic types over a period, you can activate the traffic meter for IPv4 traffic on the WAN port.
To configure and monitor traffic limits on the WAN port:
The Internet Traffic Statistics section in the lower part of the screen displays statistics on Internet traffic through the WAN port. If you have not enabled the traffic meter, these statistics are not available.


Monitor System Access and Performance

Table 84. Broadband Traffic Meter screen settings
Do you want to enable Traffic Metering on Broadband?
Monthly Limit Enter the monthly traffic volume limit in MB. The default setting is 0 MB.
Increase this month limit by
Select this check box to temporarily increase a previously specified monthly traffic volume limit, and enter the additional allowed volume in MB. The default setting is 0 MB.
This month limit This is a nonconfigurable field that displays the total monthly traffic volume limit that applies to this month. This total is the sum of the monthly traffic volume and the increased traffic volume.
Send e-mail report before restarting counter
An email report is sent immediately before the counter restarts. Ensure that emailing of logs is enabled on the Firewall Logs & E-mail screen (see Configure Logging, Alerts, and Event Notifications on page 349).
Monitor System Access and Performance

Table 84. Broadband Traffic Meter screen settings (continued)
When Limit is reached
Send e-mail alert An email alert is sent when traffic is blocked. Ensure that emailing of logs is enabled on the Firewall Logs & E-mail screen (see Configure Logging, Alerts, and Event Notifications on page 349).
To display a report of the Internet traffic by type, click the Traffic by Protocol option arrow in the upper right of the Broadband Traffic Meter screen. The Traffic by Protocol pop-up screen displays. The incoming and outgoing volume of traffic for each protocol and the total volume of traffic are displayed. Traffic counters are updated in MBs; the counter starts only when traffic passed is at least 1 MB. In addition, the pop-up screen displays the traffic meter’s start and end dates. If you did not configure the traffic meter, the start date is blank.

You can configure the wireless VPN firewall to log routing events such as dropped and accepted packets, to log system events such as a change of time by an NTP server, secure login attempts, and reboots, and to log other events. You can also schedule logs to be sent to the administrator and enable logs to be sent to a syslog server on the network.
To configure and activate logs:
Monitor System Access and Performance
Setting Description


Monitor System Access and Performance

Table 85. Firewall Logs & E-mail screen settings
Log Identifier Enter the name of the log identifier. The identifier is appended to log messages to identify the device that sent the log messages. The default identifier is FVS318N.
Select this check box to log packets from MAC addresses that match the source MAC address filter settings.
Session Limit Select this check box to log packets that are dropped because the session limit has been exceeded.
Select this check box to log packets that are dropped because the bandwidth limit has been exceeded.
Monitor System Access and Performance

Table 85. Firewall Logs & E-mail screen settings (continued)
Do you want logs to be emailed to you?
Select the Yes radio button to enable the wireless VPN firewall to email logs to a specified email address. Complete the fields that are shown on the right side of the screen. Select the No radio button to prevent the logs from being emailed, which is the default setting.
E-Mail Server Address The IP address or Internet name of your ISP’s outgoing email
SMTP server.
Return E-Mail Address The email address of the sender for email identification purposes.
For example, enter fvs_alerts@company.com.
Send to E-Mail Address
The email address to which the logs are sent. Typically, this is the email address of the administrator.
Custom SMTP Port Enter the port number of the SMTP server for the outgoing email.
Username The user name for SMTP server authentication.
Password The password for SMTP server authentication.
Respond to Identd from SMTP Server
To respond to Ident protocol messages, select the Respond to Identd from SMTP Server check box. The Ident protocol is a relatively weak scheme to verify the sender of an email. (A common daemon program for providing the Ident service is Identd.)
Send e-mail logs by Schedule
Day From the Day drop-down list, select the day on which the logs are sent.
Time From the Time drop-down list select the hour on which the logs are sent, and then select either the a.m. or p.m. radio button.
Monitor System Access and Performance
Setting Description · Enable E-mail Logs

Table 85. Firewall Logs & E-mail screen settings (continued)
Do you want to enable syslog?
To enable the wireless VPN firewall to send logs to a specified syslog server, select the Yes radio button. Complete the fields that are shown on the right side of the screen. To prevent the logs from being sent, select the No radio button, which is the default setting.
SysLog Server The IP address or FQDN of the syslog server.
volume of log messages. NETGEAR recommends that you enable firewall logs for debugging purposes only.
To send syslogs from one site to another over a gateway-to-gateway VPN tunnel:
Monitor System Access and Performance
Setting Description · Enable SysLogs

The following sections describe steps 2 through 4, using the topology that is described in the following table:
Type of Address Gateway 1 at Site 1 Gateway 2 at Site 2
WAN IP address 10.0.0.1 10.0.0.2
LAN IP address 192.168.10.0 192.168.20.0
LAN subnet mask 255.255.255.0 255.255.255.0
LAN IP address syslog server 192.168.10.2 Not applicable
Configure Gateway 1 at Site 1
To create a gateway-to-gateway VPN tunnel to Gateway 2, using the IPSec VPN wizard:
To change the remote IP address in the VPN policy:
Monitor System Access and Performance

Configure Gateway 2 at Site 2
To create a gateway-to-gateway VPN tunnel to Gateway 1, using the IPSec VPN wizard:
To change the local IP address in the VPN policy:
To specify the syslog server that is connected to Gateway 1:
syslogs should be sent to the syslog server at Site 1. You can use the IPSec VPN Connection Status screen to verify the connection.
Monitor System Access and Performance

When you start up the wireless VPN firewall, the default screen that displays is the Router Status screen.
The Router Status screen and Detailed Status screen provide real-time information about the following important components of the wireless VPN firewall:
The Tunnel Status screen provides real-time information about the IPv6 tunnels.
These status screens are described in the following sections:
To view the Router Status screen:
Select Monitoring > Router Status. The Router Status screen displays:
Monitor System Access and Performance
Router Status Screen


The following table explains the fields of the Router Status screen:
Table 86. Router Status screen information
System Name The NETGEAR system name.
Firmware Version The installed firmware version.
For each of the LAN ports, the screen shows the IP address and subnet mask. For more detailed information, see Table 88 on page 361.
Monitor System Access and Performance
Item Description · System Info · LAN (VLAN) Information

Table 86. Router Status screen information (continued)
MAC Address The MAC address of the wireless VPN firewall.
IPv6 Address The IPv6 address that is assigned to the wireless VPN firewall. For information about configuring the IPv6 address, see Configure the IPv6 Internet Connection and WAN Settings on page 37.
DHCP Server The status of the IPv4 DHCP server (Enabled or Disabled). For information about configuring the IPv4 DHCP server, see Configure a VLAN Profile on page 59.
DHCP Relay The status of the IPv4 DHCP relay (Enabled or Disabled). For information about configuring the IPv4 DHCP relay, see Configure a VLAN Profile on page 59.
DHCPv6 Server The status of the DHCPv6 server (Enabled or Disabled) for the LAN. For information about configuring the DHCPv6 server for the LAN, see Manage the IPv6 LAN on page 73.
IPv6 Address The IPv6 address that is assigned to the DMZ port. For information about configuring the IPv6 address for the DMZ, see Enable and Configure the DMZ Port for IPv4 and IPv6 Traffic on page 85.
DHCPv6 Server The status of the DHCPv6 server (Enabled or Disabled) for the DMZ. For information about configuring the DHCPv6 server for the DMZ, see Enable and Configure the DMZ Port for IPv4 and IPv6 Traffic on page 85.
WAN (IPv4) The screen shows the IPv4 address, subnet mask, gateway, and status of the port (UP or Down). For more detailed information, see Table 88 on page 361.
WAN (IPv6) The screen shows the IPv6 address, gateway, and status of the port (UP or Down). For more detailed information, see Table 88 on page 361.
SSID The status of the SSID (Enabled or Disabled). For more detailed information, see Table 88 on page 361.
To view the Router Statistics screen:
Monitor System Access and Performance


The following table explains the fields of the Router Statistics screen.
To change the poll interval period, enter a new value (in seconds) in the Poll Interval field, and then click Set interval. To stop polling, click Stop.
Table 87. Router Statistics screen information
System up Time. The period since the last time that the wireless VPN firewall was started up.
For the broadband (WAN) interface and for all LAN interfaces combined, the following statistics are displayed:
Tx Pkts The number of packets transmitted on the port in bytes.
Rx Pxts The number of packets received on the port in bytes.
Collisions The number of signal collisions that have occurred on the port. A collision occurs when the port attempts to send data at the same time as a port on the other router or computer that is connected to this port.
Tx B/s The number of bytes transmitted per second on the port.
Rx B/s The number of bytes received per second on the port.
Up Time The period that the port has been active since it was restarted.
To view the Detailed Status screen, select Monitoring > Router Status > Detailed Status. The Detailed Status screen displays:
Monitor System Access and Performance
Item Description · Router Statistics · Detailed Status Screen


Monitor System Access and Performance

The following table explains the fields of the Detailed Status screen:
Table 88. Detailed Status screen information
LAN Port Configuration The following fields are shown for each of the LAN ports.
VLAN Profile The name of the VLAN profile that you assigned to this port on the LAN Setup screen (see Assign and Manage VLAN Profiles on page 56). If the VLAN is not enabled on this port, the default profile (with VLAN ID 1) is assigned automatically.
VLAN ID The VLAN ID that you assigned to this port on the Add VLAN Profile screen (see Configure a VLAN Profile on page 59). If the default VLAN profile is used, the VLAN ID is 1, which means that all tagged and untagged traffic can pass on this port.
IP Address The IP address for this port. If the port is part of the default VLAN, the IP address is the default LAN IP address (192.168.1.1). For information about configuring VLAN profiles, see Configure a VLAN Profile on page 59.
Subnet Mask The subnet mask for this port. If the port is part of the default VLAN, the subnet mask is the default LAN IP subnet mask (255.255.255.0). For information about configuring VLAN profiles, see Configure a VLAN Profile on page 59.
DHCP Status The status of the IPv4 DHCP server for the VLAN (Enabled or Disabled). For information about enabling DHCP for VLANs, see Configure a VLAN Profile on page 59.
MAC Address The default MAC address for the port or the MAC address that you have specified on the Broadband Advanced Options screen for the port. For information about configuring the MAC address, see Configure Advanced WAN Options and Other Tasks on page 50.
IP Address The IPv4 address and subnet mask of the WAN port. For information about configuring the IPv4 address of the WAN port, see Configure the IPv4 Internet Connection and WAN Settings on page 26.
IPv6 Address The IPv6 address of the WAN port. For information about configuring the IPv4 address of the WAN port, see Configure the IPv6 Internet Connection and WAN Settings on page 37.
WAN State The WAN state can be either UP or DOWN, depending on whether the port is connected to the Internet.
Monitor System Access and Performance
Item Description · WAN Configuration

Table 88. Detailed Status screen information (continued)
NAT (IPv4 only) The NAT state can be either Enabled or Disabled, depending on whether NAT is enabled (see Network Address Translation on page 27) or classical routing is enabled (see Classical Routing on page 27).
IPv4 Connection Type The connection type can be Static IP, DHCP, PPPoE, or PPTP, depending on whether the WAN address is obtained dynamically through a DHCP server or assigned statically by you. For information about connection types, see Configure the IPv4 Internet Connection and WAN Settings on page 26.
IPv6 Connection Type The connection type can be Static IPv6, PPPoE, or Dynamic IP (DHCPv6), depending on whether the WAN address is obtained dynamically through a DHCP server or ISP, or assigned statically by you. For information about connection types, see Configure the IPv6 Internet Connection and WAN Settings on page 37.
IPv4 Connection State The IPv4 connection state can be either Connected or Not Connected, depending on whether the WAN interface is connected to the Internet over an IPv4 address. For information about configuring the IPv4 address of the WAN port, see Configure the IPv4 Internet Connection and WAN Settings on page 26.
IPv6 Connection State The IPv6 connection state can be either Connected or Not Connected, depending on whether the WAN interface is connected to the Internet over an IPv6 address. For information about configuring the IPv6 address of the WAN port, see Configure the IPv6 Internet Connection and WAN Settings on page 37.
Link State The link state can be either LINK UP or LINK DOWN, depending on whether the WAN port is physically connected to a modem, dish, or router. For information about connecting a WAN port, see the ProSafe Wireless-N 8-Port Gigabit VPN Firewall FVS318N Installation Guide.
Gateway The IP address of the gateway. These IPv4 settings are either obtained dynamically from your ISP or specified by you on the Broadband ISP Settings (IPv4) screen (see Manually Configure an IPv4 Internet Connection on page 31).
Primary DNS Server The IP address of the primary DNS server.
Secondary DNS Server The IP address of the secondary DNS
server.
Gateway (IPv6) The IP address of the gateway. These IPv6 settings are either obtained dynamically from your ISP or specified by you on the Broadband ISP Settings (IPv6) screen (see Configure a Static IPv6 Internet Connection on page 41).
Primary DNS Server (IPv6)
The IP address of the primary DNS server.
Secondary DNS Server (IPv6)
The IP address of the secondary DNS server.
Mode The wireless mode of the radio.
Region The region that is assigned to the radio.
For information about how to configure the wireless radio, see Configure the Basic Radio Settings on page 108.
Country The country that is assigned to the radio.
Channel The active channel on the radio.
Operating Frequency The operating frequency of the radio.
Monitor System Access and Performance
Item Description · Wireless Configuration

Table 88. Detailed Status screen information (continued)
SSID The SSID of the wireless profile.
Security Settings The security settings of the wireless profile.
Encryption The encryption that is configured on the wireless profile,
For information about configuring wireless profiles, see Configure and Enable Wireless Profiles on page 115.
Authentication The authentication that is configured on the wireless profile,
IP Address The IP address of the wireless profile.
AP MAC Address The MAC address of the wireless profile.
Status The status can be Enabled or Disabled, depending on whether the wireless profile is enabled.
The IPv6 Tunnel Status screen displays the status of all active 6to4 and ISATAP tunnels and their IPv6 addresses.
To view the status of the tunnels and IPv6 addresses:
Select Monitoring > Router Status > Tunnel Status. The Tunnel Status screen displays:
The IPv6 Tunnel Status table shows the following fields:
Monitor System Access and Performance
Item Description · Wireless Profile Information · Tunnel Status Screen

The Connection Status screens display a list of IPSec VPN connections, SSL VPN connections, and L2TP users who are currently logged in to the wireless VPN firewall.
To view the active IPSec VPN connections:
Select VPN > Connection Status. The Connection Status submenu tabs display with the IPSec VPN Connection Status screen in view:
The policy name, the endpoint’s IP address, the amount of data and number of packets transmitted, and the state of the connection are listed in the table.
To activate a tunnel, click the Connect table button to the right of the policy’s table entry; to disconnect an active connection, click the Disconnect table button to the right of the policy’s table entry.
To view the active SSL VPN connections:
Select VPN > Connection Status > SSL VPN Connection Status. The SSL VPN Connection Status screen displays:
The active user’s user name, group, and IP address are listed in the table with a time stamp indicating the time and date that the user connected.
Monitor System Access and Performance

To disconnect an active user, click the Disconnect table button to the right of the user’s table entry.
To view the active L2TP tunnel users:
Select VPN > Connection Status > L2TP Active Users. The L2TP Active Users screen displays:
The active user name, client’s IP address on the remote LAC, and IP address that is assigned by the L2TP server on the wireless VPN firewall are listed in the table.
To disconnect an active user, click the Disconnect table button to the right of the user’s table entry.
To display the IPSec VPN log:
Select Monitoring > VPN Logs. The Logs tabs display with the IPSec VPN Logs screen in view.
Monitor System Access and Performance

To display the SSL VPN log:
Select Monitoring > VPN Logs > SSL VPN Logs. The SSL VPN Logs screen displays:
To view the status of the port triggering feature:
Monitor System Access and Performance

The Port Triggering Status screen displays the information that is described in the following table:
Table 89. Port Triggering Status screen information
# The sequence number of the rule onscreen.
Rule The name of the port triggering rule that is associated with this entry.
LAN IP Address The IP address of the computer or device that is currently using this rule.
Open Ports The incoming ports that are associated with this rule. Incoming traffic using one of these ports is sent to the IP address that is listed in the LAN IP Address field.
Time Remaining The time remaining before this rule is released and made available for other computers or devices. This timer is restarted when incoming or outgoing traffic is received.
You can view the status of the IPv4 and IPv6 WAN connections, the DNS servers, and the DHCP servers.
IPv4 WAN Port Status
To view the IPv4 status of the WAN port:
Monitor System Access and Performance
Item Description

The type of connection determines the information that is displayed on the Connection Status screen. The screen can display the information that is described in the following table:
Table 90. Connection Status screen information for an IPv4 connection
Connection Time The period that the wireless VPN firewall has been connected through the WAN port.
Connection Type The connection type can be either DHCP or Static IP.
Connection Status The connection status can be either Connected or Disconnected.
IP Address The addresses that were automatically detected or that you configured on the Broadband ISP Settings (IPv4) screen.
DHCP Server DHCP only. The DHCP server that was automatically detected. This field displays only if your ISP does not require a login and the IP address is acquired dynamically from your ISP. You have configured these ISP settings on the Broadband ISP Settings screen.
Lease Obtained DHCP only. The time when the DHCP lease was obtained.
Lease Duration DHCP only. The period that the DHCP lease remains in effect.
Click Disconnect to disconnect the connection; click Connect to establish the connection.
Monitor System Access and Performance

IPv6 WAN Port Status
To view the IPv6 status of the WAN port:
The type of connection determines the information that is displayed on the Connection Status screen. The screen can display the information that is described in the following table:
Table 91. Connection Status screen information for an IPv6 connection
Connection Time The period that the wireless VPN firewall has been connected through the WAN port.
IPv6 Connection Type The connection type can be either Dynamic IP (DHCP), Static, or PPPoE.
IPv6 Connection Status The connection status can be either Connected or Disconnected.
IP Address The IPv6 addresses that were automatically detected or that you configured on the Broadband ISP Settings (IPv6) screen.
Primary DNS Server (IPv6)
Secondary DNS Server (IPv6)
Click Disconnect to disconnect the connection; click Connect to establish the connection.
Monitor System Access and Performance
Item Description · Gateway

The LAN Groups screen shows the network database, which is the Known PCs and Devices table, which contains all IP devices that wireless VPN firewall has discovered on the local network. The LAN Setup screen lets you access the DHCP log.
View the Attached Devices
To view the attached devices on the LAN Groups screen:
Select Network Configuration > LAN Setup > LAN Groups. The LAN Groups screen displays. (The following figure shows some examples in the Known PCs and Devices table.)
The Known PCs and Devices table contains a list of all known computers and network devices that are assigned dynamic IP addresses by the wireless VPN firewall, have been discovered by other means, or were manually added. Collectively, these entries make up the network database. For information about how to edit the Known PCs and Devices table or manually add entries to the table, see Manage the Network Database on page 68.
For each attached computer or device, the Known PCs and Devices table displays the following fields:
Monitor System Access and Performance

assigned a static IP address, you need to update this entry manually after the IP address on the computer or device has changed.
and Devices table is lost until the wireless VPN firewall rediscovers the devices.
View the DHCP Log
To review the most recent entries in the DHCP log:

To view the most recent entries, click Refresh Log. To delete all the existing log entries, click Clear Log. Click the LAN Setup option arrow in the upper right to display the LAN Setup (IPv4) screen, from which you can modify the DHCP settings (see Configure a VLAN Profile on page 59).
Monitor System Access and Performance

To view the status of a specific wireless profile:
To change the poll interval period, enter a new value in the Poll Interval field, and then click Set interval. To stop polling, click Stop.
The following table explains the fields of the Wireless Profile Status screen.
Table 92. Wireless Profile Status screen fields
Profile Name The name of the wireless profile.
Radio The radio to which the client is connected. By default, the radio is always 1, indicating the 2.4 GHz radio.
Packet The number of received (rx) and transmitted (tx) packets on the access point in bytes.
Bytes The number of received (rx) and transmitted (tx) bytes on the access point.
Errors The number of received (rx) and transmitted (tx) errors on the access point.
Dropped The number of received (rx) and transmitted (tx) dropped packets on the access point.
Multicast The number of received (rx) and transmitted (tx) multicast packets on the access point.
Collisions The number of signal collisions that have occurred on the access point. A collision occurs when the access point attempts to send data at the same time as a wireless station that is connected to the access point.
Monitor System Access and Performance
Item Description · Wireless Profile Statistics

Table 92. Wireless Profile Status screen fields (continued)
MAC Address The MAC address of the client.
Radio The radio to which the client is connected. By default, the radio is always 1, indicating the 2.4 GHz radio.
Security The type of security that the client is using (Open, WEP, WPA, WPA2, or WPA+WPA2).
Encryption The type of encryption that the client is using (CCMP, TKIP, or TKIP + CCMP).
Authentication The type of authentication that the client is using (Open, PSK, RADIUS, or PSK+RADIUS).
The period in minutes since the connection was established between the access point and the client.
The wireless VPN firewall provides diagnostic tools that help you analyze the status of the network and traffic conditions. Two types of tools are available:
To display the Diagnostics screen:
Monitor System Access and Performance
Item Description · Connected Clients · Time Connected



The various tasks that you can perform on the Diagnostics screen are explained in the following sections.
Monitor System Access and Performance

Use the ping utility to send a ping packet request in order to check the connection between the wireless VPN firewall and a specific IP address or FQDN. 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 are displayed on a new screen.
To send a ping:
A traceroute lists all routers between the source (the wireless VPN firewall) and the destination IP address.
To send a traceroute:
A Domain Name Server (DNS) converts the Internet name (for example, www.netgear.com) to an IP address. If you need the IP address of a web, FTP, mail, or other server on the Internet, request a DNS lookup to find the IP address.
To look up a DNS address:
Monitor System Access and Performance

Displaying the internal routing table can assist NETGEAR technical support in diagnosing routing problems.
To display the routing table:
On the Diagnostics screen for IPv4, in the Router Options section of the screen, click the Display button next to Display the IPv4 Routing Table. The routing table is shown in the Route Display pop-up screen.
On the Diagnostics screen for IPv6, in the Router Options section of the screen, click the Display button next to Display the IPv6 Routing Table. The routing table is shown in the Route Display pop-up screen.
Capturing packets can assist NETGEAR technical support in diagnosing packet transfer problems. You can also use a traffic analyzer to do your own problem diagnoses.
To capture packets in real time:

Monitor System Access and Performance

You can perform a remote reboot, for example, when the wireless VPN firewall seems to have become unstable or is not operating normally.
Rebooting breaks any existing connections either to the wireless VPN firewall (such as your management session) or through the wireless VPN firewall (for example, LAN users accessing the Internet). However, connections to the Internet are automatically reestablished when possible.
To reboot the wireless VPN firewall:
In Router Options section of the screen, next to Reboot the Router, click the Reboot button. The wireless VPN firewall reboots. The Diagnostics screen might remain visible during the reboot process, or a status message with a counter might show the number of seconds left until the reboot process is complete. The reboot process takes about 165 seconds.
Monitor System Access and Performance

This chapter provides troubleshooting tips and information for the wireless VPN firewall. After each problem description, instructions are provided to help you diagnose and solve the problem. For the common problems listed, go to the section indicated.
Go to Basic Functioning on page 379.
Go to Basic Functioning on page 379.
Go to Troubleshoot the Web Management Interface on page 380.
Go to When You Enter a URL or IP Address, a Time-Out Error Occurs on page 381.
Go to Troubleshoot the ISP Connection on page 382.
Go to Troubleshooting the IPv6 Connection on page 383
Go to Troubleshoot a TCP/IP Network Using a Ping Utility on page 386.
Go to Restore the Default Configuration and Password on page 388.
Go to Address Problems with Date and Time on page 389.
Go to Access the Knowledge Base and Documentation on page 389.

Diagnostics Utilities on page 373.
After you turn on power to the wireless VPN firewall, verify that the following sequence of events occurs:
a. The Test LED is no longer lit.
b. The left LAN port LEDs are lit for any local ports that are connected.
c. The left WAN port LEDs are lit for any WAN ports that are connected.
If a port’s left LED is lit, a link has been established to the connected device. If a port is connected to a 1000 Mbps device, verify that the port’s right LED is green. If the port functions at 100 Mbps, the right LED is amber. If the port functions at 10 Mbps, the right LED is off.
If any of these conditions do not occur, see the appropriate following section.
If the Power and other LEDs are off when your wireless VPN firewall is turned on, make sure that the power cord is correctly connected to your wireless VPN firewall and that the power supply adapter is correctly connected to a functioning power outlet.
If the error persists, you have a hardware problem and should contact NETGEAR technical support.
When the wireless VPN firewall is powered on, the Test LED turns on for approximately 2 minutes and then turns off when the wireless VPN firewall has completed its initialization. If the Test LED remains on, there is a fault within the wireless VPN firewall.
Troubleshooting

If all LEDs are still on more than several minutes minute after power-up, do the following:
If the error persists, you might have a hardware problem and should contact NETGEAR technical support.
If either the LAN LEDs or WAN LEDs do not light when the Ethernet connection is made, check the following:
When connecting the wireless VPN firewall’s WAN ports to one or two devices that provide the Internet connections, use the cables that are supplied with the devices. These cables could be standard straight-through Ethernet cables or Ethernet crossover cables.
If you cannot access the wireless VPN firewall’s web management interface from a computer on your local network, check the following:
configuration settings, you can reboot the wireless VPN firewall and use a sniffer to capture packets sent during the reboot. Look at the ARP packets to locate the wireless VPN firewall’s LAN interface address.
Troubleshooting

IP address does not need to be on the same subnet as the wireless VPN firewall.
If the wireless VPN firewall does not save changes you have made in the web management interface, check the following:
A number of things could be causing this situation. Try the following troubleshooting steps:
Troubleshooting

If your wireless VPN firewall is unable to access the Internet, you should first determine whether the wireless VPN firewall is able to obtain a WAN IP address from the ISP. Unless you have been assigned a static IP address, your wireless VPN firewall requests an IP address from the ISP. You can determine whether the request was successful using the web management interface.
To check the WAN IP address:
- For IPv6. In the upper right of the screen, select the IPv6 radio button. The ISP Broadband Settings screen displays the IPv6 settings. Then click the Status option arrow. The Connection Status pop-up screen for IPv6 displays (see Figure 20 on page 41).
If your wireless VPN firewall is unable to obtain an IP address from the ISP, you might need to force your modem, dish, or router to recognize your new wireless VPN firewall by performing the following procedure:
If your wireless VPN firewall is still unable to obtain an IP address from the ISP, the problem might be one of the following:
Troubleshooting

system name, or account name that was assigned to you by your ISP. You might also have to enter the assigned domain name or workgroup name in the Domain Name field, and you might have to enter additional information. For more information, see Manually Configure an IPv4 Internet Connection on page 31.
- Inform your ISP that you have bought a new network device, and ask them to use the wireless VPN firewall’s MAC address.
- Configure your wireless VPN firewall to spoof your computer’s MAC address. You can do this in the Router’s MAC Address section on the Broadband Advanced Options screen. For more information, see Configure Advanced WAN Options and Other Tasks on page 50.
If your wireless VPN firewall can obtain an IP address, but an attached computer is unable to load any web pages from the Internet:
A DNS server is a host on the Internet that translates Internet names (such as www.netgear.com) to numeric IP addresses. Typically your ISP provides the addresses of one or two DNS servers for your use. You can configure your computer manually with DNS addresses, as explained in your operating system documentation.
If you have difficulty connecting over an IPv6 connection, there might be an incorrect configuration on the wireless VPN firewall or the computer from which you are trying to connect to the wireless VPN firewall:
Check the wireless VPN firewall:
Troubleshooting

Check the computer:
- Windows 7, all 32- and 64-bit versions
- Windows Vista, all 32- and 64-bit versions
- Windows XP Professional SP3 (32- and 64-bit)
- Windows Server 2008, all versions
- Windows Server 2008 R2, all versions
- Windows Server 2003, all versions
- Windows Server 2003 R2, all versions
- Linux and other UNIX-based systems with a correctly configured kernel
a. Open the Network Connections screen or the Network and Sharing Center screen. For example, on the Windows taskbar, click Start, then select Control Panel, and then Network Connections.
b. Click or double-click Local Area Connection for the connection to the wireless VPN
firewall. The Local Area Connection Properties screen displays:

Troubleshooting

c. Make sure that Internet Protocol Version 6 (TCP/IPv6) displays, as is shown in the
previous figure. • Make sure that the computer has an IPv6 address. If the computer has a link-local address only, it cannot reach the wireless VPN firewall or the Internet. On a computer that runs a Windows-based operating system, do the following (note that the steps might differ on the various Windows operating systems):
a. Open the Network Connections screen or the Network and Sharing Center screen. For example, on the Windows taskbar, click Start, then select Control Panel, and then Network Connections.
b. Click or double-click Local Area Connection for the connection to the wireless VPN
firewall.
c. Click or double-click View status of this connection. The Local Area Connection
Status screen displays:

d. Make sure that Internet access shows for the IPv6 connection. (The previous figure
shows that there is no Internet access.)
e. Click Details. The Network Connection Details screen displays:
Troubleshooting


f. Make sure that an IPv6 address shows. The previous figure does not show an IPv6
address for the computer but only a link-local IPv6 address and an IPv6 default gateway address, both of which start, in this case, with FE80.
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. You can easily troubleshoot a TCP/IP network by using the ping utility in your computer or workstation.
You can ping the wireless VPN firewall from your computer to verify that the LAN path to the wireless VPN firewall is set up correctly.
To ping the wireless VPN firewall from a computer running Windows 95 or later:
ping 192.168.1.1
Troubleshooting

Pinging with 32 bytes of data
If the path is working, you see this message:
If the path is not working, you see this message:
If the path is not functioning correctly, you could have one of the following problems:
- Make sure that the LAN port LED is on. If the LED is off, follow the instructions in LAN or WAN Port LEDs Not On on page 380.
- 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 wireless VPN firewall.
- Verify that the Ethernet card driver software and TCP/IP software are both installed and configured on your computer or workstation.
- Verify that the IP address for your wireless VPN firewall and your workstation are correct and that the addresses are on the same subnet.
After verifying that the LAN path works correctly, test the path from your computer to a remote device. From the Windows Run dialog box, type:
ping -n 10 <IP address>
in which 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:
Request timed out · Troubleshooting

information. For more information, see Manually Configure an IPv4 Internet Connection on page 31.
To reset the wireless VPN firewall to the original factory default settings, you can use one of the following two methods:
a. Select Administration > Settings Backup & Upgrade:
b. Click the Default button.
The wireless VPN firewall reboots. During the reboot process, the Settings Backup and Firmware Upgrade screen might remain visible, or a status message with a counter might show the number of seconds left until the reboot process is complete.
Troubleshooting

The reboot process takes about 165 seconds. (If you can see the unit: The reboot process is complete when the Test LED on the front panel goes off.)
When you press the hardware factory default Reset button or click the software Default button, the wireless VPN firewall settings are erased. All firewall rules, VPN policies, LAN and WAN settings, and other settings are lost. Back up your settings if you intend on using them.
firewall’s password is password, and the LAN IPv4 address is 192.168.1.1.
The System Date & Time screen displays the current date and time of day (see Configure Date and Time Service on page 344). The wireless 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:
To access NETGEAR’s knowledge base for the wireless VPN firewall:
Select Web Support > Knowledgebase.
To access NETGEAR’s documentation library for your wireless VPN firewall model:
Select Web Support > Documentation.
Troubleshooting

A. Default Settings and Technical
Specifications
This appendix provides the default settings and the physical and technical specifications of the wireless VPN firewall in the following sections:
You can use the factory default Reset button located on the rear panel to reset all settings to their factory defaults. This is called a hard reset (for more information, see Revert to Factory Default Settings on page 342):
The following table shows the default configuration settings for the wireless VPN firewall:
Table 93. Wireless VPN firewall factory default configuration settings
User login URL https://192.168.1.1
Administrator user name (case-sensitive) admin
Administrator login password (case-sensitive) password
Guest user name (case-sensitive) guest
Guest login password (case-sensitive) password
WAN IPv4 mode NAT
WAN IPv6 mode IPv4 only mode
Feature Default Behavior · Login settings · WAN settings

Table 93. Wireless VPN firewall factory default configuration settings (continued)
Stateless IP/ICMP Translation (SIIT) Disabled
WAN MAC address Use default MAC address of the wireless VPN firewall
WAN MTU size 1500 bytes 1492 bytes for PPPoE connections
Dynamic DNS for IPv4 Disabled
IPv4 LAN, DMZ, and routing settings
LAN IPv4 address for the default VLAN 192.168.1.1
LAN IPv4 subnet mask for the default VLAN 255.255.255.0
VLAN 1 membership All ports
LAN DHCP server for the default VLAN Enabled
LAN DHCP IPv4 starting address for the default VLAN 192.168.1.100
LAN DHCP IPv4 ending address for the default VLAN 192.168.1.254
VLAN MAC addresses All LAN ports share the same MAC address
Broadcast of ARP packets Enabled for the default VLAN
DMZ port for IPv4 Disabled
DMZ IPv4 address (Port 8) 172.16.2.1
DMZ IPv4 subnet mask (Port 8) 255.255.255.0
DMZ DHCP server Disabled
DMZ DHCP IPv4 starting address 176.16.2.100
DMZ DHCP IPv4 ending address 176.16.2.254
IPv6 LAN and DMZ settings
LAN IPv6 address FEC0::1
LAN IPv6 prefix length 64
LAN DHCPv6 server Disabled
Default Settings and Technical Specifications

Table 93. Wireless VPN firewall factory default configuration settings (continued)
DMZ port for IPv6 Disabled
DMZ IPv6 address (Port 8) 176::1
DMZ IPv6 prefix length (Port 8) 64
DMZ DHCPv6 server Disabled
Firewall and security settings
Inbound LAN WAN rules (communications coming in from the Internet)
All traffic is blocked, except for traffic in response to requests from the LAN.
Outbound LAN WAN rules (communications from the LAN to the Internet)
All traffic is allowed.
Inbound and outbound DMZ WAN rules None
Inbound and outbound LAN DMZ rules None
Respond to ping on WAN (Internet) ports Disabled
Respond to ping on LAN ports Disabled
IPv4 VPN pass-through for IPSec in NAT mode Enabled
IPv4 VPN pass-through for PPTP in NAT mode Enabled
IPv4 VPN pass-through for L2TP in NAT mode Enabled
IPv6 VPN pass-through for IPSec Enabled
Multicast pass-through for IGMP Disabled
TCP time-out 1800 seconds
UDP time-out 120 seconds
ICMP time-out 60 seconds
Source MAC filtering Disabled
Port triggering rules None
Default Settings and Technical Specifications

Table 93. Wireless VPN firewall factory default configuration settings (continued)
QoS profiles Normal-Service Minimize-Cost Maximize-Reliability Maximize-Throughput Minimize-Delay
Proxy server blocking Disabled
Java applets blocking Disabled
ActiveX controls blocking Disabled
Wireless radio and access point settings
Region Nonconfigurable: set for the region in which you purchased the wireless VPN firewall.
Default security profile default1
Default network name (SSID) FVS318N_1
Default Settings and Technical Specifications

Table 93. Wireless VPN firewall factory default configuration settings (continued)
Transmission rate Best1
Default transmit power Full
802.11 wireless mode 802.11ng (for most countries)
802.11b/g/n radio frequency channel Auto
802.11n channel spacing 20 MHz
Beacon interval 100 ms
RTS threshold 2346 bytes
Fragmentation threshold 2346 bytes
ID type Local WAN IP address
Local WAN ID Local WAN IP address
Remote WAN ID Not applicable
Authentication method Pre-shared Key
Key group DH-Group 2 (1024 bit)
Life time 8 hours
Life time 1 hour
Default Settings and Technical Specifications

Table 93. Wireless VPN firewall factory default configuration settings (continued)
Key group DH-Group 2 (1024 bit)
Local WAN ID remote.com
Remote WAN ID local.com
Authentication method Pre-shared Key
Key group DH-Group 2 (1024 bit)
Life time 8 hours
Life time 1 hour
Key group DH-Group 2 (1024 bit)
Primary RADIUS server Disabled and none configured
Secondary RADIUS server Disabled and none configured
RADIUS time-out period 30 seconds
RADIUS maximum retry count 4
SSL VPN IPv4 client address range 192.168.251.1–192.168.251.254
SSL VPN IPv6 client address range 4000::1–4000::200
User, group, and domain settings
Default Settings and Technical Specifications

Table 93. Wireless VPN firewall factory default configuration settings (continued)
default users, default passwords
Administrative and monitoring settings
Secure HTTP management Enabled
Time zone adjusted for daylight saving time Disabled
Other event logs Disabled
IPSec VPN logs Enabled
SSL VPN logs Enabled
The following table shows the physical and technical specifications for the wireless VPN firewall:
Table 94. Wireless VPN firewall physical and technical specifications
Network protocol and standards compatibility
Data and Routing Protocols TCP/IP, RIP-1, RIP-2, PPP over Ethernet (PPPoE), DHCP, DHCPv6
Default Settings and Technical Specifications

Table 94. Wireless VPN firewall physical and technical specifications (continued)
Power plug (localized to the country of sale)
North America 120V, 60 Hz, input
United Kingdom, Australia 240V, 50 Hz, input
Europe 230V, 50 Hz, input
Input, for all regions 12VDC @ 1A output
Dimensions (W x H x D) 19 x 12.5 x 3.5 cm (7.5 X 4.9 X 1.4 in)
Weight 0.59 kg (1.3 lb)
Operating temperatures 0º to 40ºC
Storage temperatures –20º to 70ºC
Operating humidity 90% maximum relative humidity, noncondensing
Storage humidity 95% maximum relative humidity, noncondensing
Meets requirements of FCC Part 15 Class B
EN 55 022 (CISPR 22), Class B
See Appendix C, Notification of Compliance (Wired).
See Appendix D, Notification of Compliance (Wireless).
LAN 8 LAN autosensing 10/100/1000BASE-T, RJ-45, one of which is a configurable DMZ interface
WAN 1 WAN autosensing 10/100/1000BASE-T, RJ-45
1 administrative console port RS-232
Default Settings and Technical Specifications

The following table shows the IPSec VPN specifications for the wireless VPN firewall:
Table 95. Wireless VPN firewall IPSec VPN specifications
Network Management Web-based configuration and status monitoring
Number of concurrent users supported 12
IPSec authentication algorithm SHA-1, MD5
IPSec encryption algorithm DES, 3DES, AES-128, AES-192, AES-256
IPSec key exchange IKE, manual key, pre-shared key, X.509 certificate
IPSec authentication types Local user database, RADIUS PAP, RADIUS CHAP
IPSec certificates supported CA certificates, self-signed certificate
The following table shows the SSL VPN specifications for the wireless VPN firewall:
Table 96. Wireless VPN firewall SSL VPN specifications
Network Management Web-based configuration and status monitoring
Number of concurrent users supported 5
SSL versions SSLv3, TLS1.0
SSL encryption algorithm DES, 3DES, ARC4, AES-128, AES-192, AES-256
SSL message integrity MD5, SHA-1, MAC-MD5/SHA-1, HMAC-MD5/SHA-1
SSL authentication types Local user database, RADIUS-PAP, RADIUS-CHAP, RADIUS-MSCHAP, RADIUS-MSCHAPv2, WiKID-PAP, WiKID-CHAP, MIAS-PAP, MIAS-CHAP, NT domain, Active Directory, LDAP
SSL certificates supported CA certificates, self-signed certificate
Default Settings and Technical Specifications
Setting Specification · Setting Specification

The following table shows the wireless specifications for the wireless VPN firewall:
Table 97. Wireless VPN firewall wireless specifications
802.11bg data rates 1, 2, 5.5, 6, 9, 11, 12, 18, 24, 36, 48, 54 Mbps, and auto-rate capable
802.11ng/n data rates Data rates for a channel width of 20 MHz and a (short) guard interval of 400 ms: Best (automatic), 7.2 Mbps, 14.4 Mbps, 21.7 Mbps, 28.9 Mbps, 43.3 Mbps, 57.8 Mbps, 65 Mbps, 72.2 Mbps, 14.44 Mbps, 28.88 Mbps, 43.33 Mbps, 57.77 Mbps, 86.66 Mbps, 115.56 Mbps, 130 Mbps, 144.44 Mbps
Data rates for a channel width of 40 MHz and a (short) guard interval of 400 ms: Best (automatic), 15 Mbps, 30 Mbps, 45 Mbps, 60 Mbps, 90 Mbps, 120 Mbps, 135 Mbps, 150 Mbps, 30 Mbps, 60 Mbps, 90 Mbps, 120 Mbps, 180 Mbps, 240 Mbps, 270 Mbps, 300 Mbps
802.11b/bg/ng/n operating frequencies
802.11 b/bg/ng/n encryption
64-bits and 128-bits WEP, TKIP, CCMP data encryption
Network management Web-based configuration and status monitoring
Default Settings and Technical Specifications
Setting Specification

B. 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:
In today’s market, online identity theft and online fraud continue to be one of the fast-growing cybercrime activities used by many unethical hackers and cybercriminals 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 a result of these cybercrime activities. Security threats and hackers have become more sophisticated, and 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 in the authentication process. NETGEAR has also recognized the need to provide more than just a firewall to protect the networks. NETGEAR has implemented a more robust authentication system known as two-factor authentication (2FA or T-FA) to help address the fast-growing network security issues.

Two-factor authentication is a security solution that enhances and strengthens security by implementing multiple factors of 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 sure that you are who you say you are. These factors are:
This appendix focuses on and discusses only the first two factors, something you know and something you have. This 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:
You need to have both of these factors to gain access to your bank account. Similar to the way ATM cards work, access to the corporate networks and data can also be strengthened using a combination of 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 has implemented 2 two-factor authentication solutions from WiKID. WiKID is the software-based token solution. So instead of using only Windows Active Directory or LDAP as the authentication server, administrators now have the option to use WiKID to perform two-factor authentication on NETGEAR SSL and VPN firewall products.
The WiKID solution is based on a request-response architecture where a one-time passcode (OTP), which is time-synchronized with the authentication server, is generated and sent to the user after 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 an example of how WiKID works:
To use WiKID (for end users):
Two-Factor Authentication



server so that the OTP can be used only once and needs to be used before the expiration time. If a user does not use this passcode before it expires, the user needs to go through the request process again to generate a new OTP.
Two-Factor Authentication


Two-Factor Authentication

This section includes user requirements for operating this product in accordance with National laws for usage of radio spectrum and operation of radio devices. Failure of the end-user to comply with the applicable requirements may result in unlawful operation and adverse action against the end-user by the applicable National regulatory authority.
This product's firmware limits operation to only the channels allowed in a particular Region or Country. Therefore, all options described in this user's guide may not be available in your version of the product.
FCC Requirements for Operation in the United States
FCC Information to User
This product does not contain any user serviceable components and is to be used with approved antennas only. Any product changes or modifications will invalidate all applicable regulatory certifications and approvals
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
FCC Guidelines for Human Exposure
This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance of 20 cm between the radiator and your body. This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter.
FCC Declaration Of Conformity
We, NETGEAR, Inc., 350 East Plumeria Drive, San Jose, CA 95134, declare under our sole responsibility that the ProSafe Wireless-N 8-Port Gigabit VPN Firewall FVS318N complies with Part 15 of FCC Rules.
Operation is subject to the following two conditions:
Regulatory Compliance Information

FCC Radio Frequency Interference Warnings & Instructions
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 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 methods:
Modifications made to the product, unless expressly approved by NETGEAR, Inc., could void the user's right to operate the equipment.
Canadian Department of Communications Radio Interference Regulations
This digital apparatus, ProSafe Wireless-N 8-Port Gigabit VPN Firewall FVS318N, does not exceed the Class B limits for radio-noise emissions from digital apparatus as set out in the Radio Interference Regulations of the Canadian Department of Communications.
This Class [B] digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe [B] est conforme à la norme NMB-003 du Canada.
The ProSafe Wireless-N 8-Port Gigabit VPN Firewall FVS318N complies with essential requirements of EU EMC Directive 2004/108/EC and Low Voltage Directive 2006/95/EC as supported by applying the following test methods and standards:
Notification of Compliance (Wired)
European Union

AES Copyright (c) 2001, Dr. Brian Gladman, brg@gladman.uk.net, Worcester, UK. All rights reserved. TERMS Redistribution and use in source and binary forms, with or without modification, are permitted subject to the following conditions:
This software is provided “as is” with no express or implied warranties of correctness or fitness for purpose.
Open SSL Copyright (c) 1998–2000 The OpenSSL Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
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 (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Notification of Compliance (Wired)
Additional Copyrights

MD5 Copyright (C) 1990, RSA Data Security, Inc. All rights reserved. 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.
PPP Copyright (c) 1989 Carnegie Mellon University. All rights reserved. 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 zlib.h. Interface of the zlib general purpose compression library version 1.1.4, March 11th, 2002. Copyright (C) 1995–2002 Jean-loup Gailly and Mark Adler. 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:
Jean-loup Gailly: jloup@gzip.org; 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 rfc1950.txt (zlib format), rfc1951.txt (deflate format), and rfc1952.txt (gzip format). For more information, see http://www.ietf.org/rfc/.
Notification of Compliance (Wired)

D. Notification of Compliance (Wireless)
Europe – EU Declaration of Conformity
Marking by the above symbol indicates compliance with the Essential Requirements of the R&TTE Directive of the European Union (1999/5/EC). This equipment meets the following conformance standards:
EN300 328 (2.4Ghz), EN301 489-17 EN60950-1
For complete DoC, visit the NETGEAR EU Declarations of Conformity website at: http://support.netgear.com/app/answers/detail/a_id/11621/.
EDOC in Languages of the European Community
Cesky [Czech] NETGEAR Inc. tímto prohlašuje, že tento Radiolan je ve shode se základními požadavky a dalšími príslušnými ustanoveními smernice 1999/5/ES.
Dansk [Danish] Undertegnede NETGEAR Inc. erklærer herved, at følgende udstyr Radiolan overholder de væsentlige krav og øvrige relevante krav i direktiv 1999/5/EF.
Hiermit erklärt NETGEAR Inc., dass sich das Gerät Radiolan in Übereinstimmung mit den grundlegenden Anforderungen und den übrigen einschlägigen Bestimmungen der Richtlinie 1999/5/EG befindet.
Eesti [Estonian] Käesolevaga kinnitab NETGEAR Inc. seadme Radiolan vastavust direktiivi 1999/5/EÜ põhinõuetele ja nimetatud direktiivist tulenevatele teistele asjakohastele sätetele.
English Hereby, NETGEAR Inc., declares that this Radiolan is in compliance with the essential requirements and other relevant provisions of Directive 1999/5/EC.
Regulatory Compliance Information · Language Statement · Deutsch [German]

Español [Spanish] Por medio de la presente NETGEAR Inc. declara que el Radiolan cumple con los requisitos
esenciales y cualesquiera otras disposiciones aplicables o exigibles de la Directiva 1999/5/CE.
Ελληνική [Greek] ΜΕ ΤΗΝ ΠΑΡΟΥΣΑ NETGEAR Inc. ΔΗΛΩΝΕΙ ΟΤΙ Radiolan ΣΥΜΜΟΡΦΩΝΕΤΑΙ ΠΡΟΣ ΤΙΣ ΟΥΣΙΩΔΕΙΣ ΑΠΑΙΤΗΣΕΙΣ ΚΑΙ ΤΙΣ ΛΟΙΠΕΣ ΣΧΕΤΙΚΕΣ ΔΙΑΤΑΞΕΙΣ ΤΗΣ ΟΔΗΓΙΑΣ 1999/5/ΕΚ.
Français [French] Par la présente NETGEAR Inc. déclare que l'appareil Radiolan est conforme aux exigences essentielles et aux autres dispositions pertinentes de la directive 1999/5/CE.
Italiano [Italian] Con la presente NETGEAR Inc. dichiara che questo Radiolan è conforme ai requisiti essenziali ed alle altre disposizioni pertinenti stabilite dalla direttiva 1999/5/CE.
Latviski [Latvian] Ar šo NETGEAR Inc. deklarē, ka Radiolan atbilst Direktīvas 1999/5/EK būtiskajām prasībām un citiem ar to saistītajiem noteikumiem.
Šiuo NETGEAR Inc. deklaruoja, kad šis Radiolan atitinka esminius reikalavimus ir kitas 1999/5/EB Direktyvos nuostatas.
Hierbij verklaart NETGEAR Inc. dat het toestel Radiolan in overeenstemming is met de essentiële eisen en de andere relevante bepalingen van richtlijn 1999/5/EG.
Malti [Maltese] Hawnhekk, NETGEAR Inc., jiddikjara li dan Radiolan jikkonforma mal-htigijiet essenzjali u ma provvedimenti ohrajn relevanti li hemm fid-Dirrettiva 1999/5/EC.
Alulírott, NETGEAR Inc. nyilatkozom, hogy a Radiolan megfelel a vonatkozó alapvetõ követelményeknek és az 1999/5/EC irányelv egyéb elõírásainak.
Polski [Polish] Niniejszym NETGEAR Inc. oświadcza, że Radiolan jest zgodny z zasadniczymi wymogami oraz pozostałymi stosownymi postanowieniami Dyrektywy 1999/5/EC.
NETGEAR Inc. declara que este Radiolan está conforme com os requisitos essenciais e outras disposições da Directiva 1999/5/CE.
NETGEAR Inc. izjavlja, da je ta Radiolan v skladu z bistvenimi zahtevami in ostalimi relevantnimi določili direktive 1999/5/ES.
NETGEAR Inc. týmto vyhlasuje, že Radiolan spĺňa základné požiadavky a všetky príslušné ustanovenia Smernice 1999/5/ES.
Suomi [Finnish] NETGEAR Inc. vakuuttaa täten että Radiolan tyyppinen laite on direktiivin 1999/5/EY oleellisten vaatimusten ja sitä koskevien direktiivin muiden ehtojen mukainen.
Härmed intygar NETGEAR Inc. att denna Radiolan står I överensstämmelse med de väsentliga egenskapskrav och övriga relevanta bestämmelser som framgår av direktiv 1999/5/EG.
Notification of Compliance (Wireless)

Hér með lýsir NETGEAR Inc. yfir því að Radiolan er í samræmi við grunnkröfur og aðrar kröfur, sem gerðar eru í tilskipun 1999/5/EC.
NETGEAR Inc. erklærer herved at utstyret Radiolan er i samsvar med de grunnleggende krav og øvrige relevante krav i direktiv 1999/5/EF.
This device is a 2.4 GHz wideband transmission system (transceiver), intended for use in all EU member states and EFTA countries, except in France and Italy where restrictive use applies.
In Italy the end-user should apply for a license at the national spectrum authorities in order to obtain authorization to use the device for setting up outdoor radio links and/or for supplying public access to telecommunications and/or network services.
This device may not be used for setting up outdoor radio links in France and in some areas the RF output power may be limited to 10 mW EIRP in the frequency range of 2454 - 2483.5 MHz. For detailed information the end-user should contact the national spectrum authority in France.
FCC Requirements for Operation in the United States
FCC Information to User
This product does not contain any user serviceable components and is to be used with approved antennas only. Any product changes or modifications will invalidate all applicable regulatory certifications and approvals.
FCC Guidelines for Human Exposure
This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance of 20 cm between the radiator and your body.
This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter.
FCC Declaration of Conformity
We, NETGEAR, Inc., 350 East Plumeria Drive, San Jose, CA 95134, declare under our sole responsibility that the ProSafe Wireless-N 8-Port Gigabit VPN Firewall FVS318N complies with Part 15 Subpart B of FCC CFR47 Rules. Operation is subject to the following two conditions:
FCC Radio Frequency Interference Warnings & Instructions
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 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 methods:
Notification of Compliance (Wireless)
Íslenska [Icelandic] · Norsk [Norwegian] · FCC Caution

Canadian Department of Communications Radio Interference Regulations
This digital apparatus (ProSafe Wireless-N 8-Port Gigabit VPN Firewall FVS318N) does not exceed the Class B limits for radio-noise emissions from digital apparatus as set out in the Radio Interference Regulations of the Canadian Department of Communications.
This Class [B] digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe [B] est conforme à la norme NMB-003 du Canada
This device complies with RSS-210 of the Industry Canada Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
This equipment complies with IC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance 20cm between the radiator & your body.
Ce dispositif est conforme à la norme CNR-210 d'Industrie Canada applicable aux appareils radio exempts de licence. Son fonctionnement est sujet aux deux conditions suivantes: (1) le dispositif ne doit pas produire de brouillage préjudiciable, et (2) ce dispositif doit accepter tout brouillage reçu, y compris un brouillage susceptible de provoquer un fonctionnement indésirable.
Cet équipement est conforme aux limites d'exposition aux rayonnements IC établies pour un environnement non contrôlé. Cet équipement doit être installé et utilisé avec un minimum de 20 cm de distance entre la source de rayonnement et votre corps.
The following table shows the Recommended Minimum Distance between NETGEAR equipment and household appliances to reduce interference (in feet and meters).
Household Appliance Recommended Minimum Distance (in feet and meters)
Microwave ovens 30 feet / 9 meters
Baby Monitor - Analog 20 feet / 6 meters
Baby Monitor - Digital 40 feet / 12 meters
Cordless phone - Analog 20 feet / 6 meters
Cordless phone - Digital 30 feet / 9 meters
Bluetooth devices 20 feet / 6 meters
ZigBee 20 feet / 6 meters
Notification of Compliance (Wireless)
Industry Canada · Interference Reduction Table













Pages referenced in this manual — manufacturer, support and downloads.
Owners and our team usually reply within a day — and your question helps the next person too.
Be the first to ask — other owners or our team will answer.