Netopia 2200 series, 3300 Series User Guide

Download

Netopia® Software User Guide

Version 7.6.1

Netopia

June 2006

2200 and 3300 Series Gateways

Copyright

Netopia, the Netopia logo, Broadband Without Boundaries, and 3-D Reach are registered trademarks belonging to Netopia, Inc., registered U.S. Patent and Trademark Ofﬁce. All other trademarks are the proper ty of their respective owners. All rights reser ved.

Netopia, Inc. Part Number: 6161231-00-01

Table of Contents

CHAPTER 1

CHAPTER 2

Introduction

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

What’s New in 7.6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

About Netopia Documentation . . . . . . . . . . . . . . . . . . . . . . . . . 14

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 15

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Internal Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

A Word About Example Screens . . . . . . . . . . . . . . . . . . . . . . . 17

Basic Mode Setup

Important Safety Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . 20

POWER SUPPLY INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

TELECOMMUNICATION INSTALLATION. . . . . . . . . . . . . . . . . . . . . . 20

PRODUCT VENTILATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Wichtige Sicherheitshinweise . . . . . . . . . . . . . . . . . . . . . . . . . . 21

NETZTEIL INSTALLIEREN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

INSTALLATION DER TELEKOMMUNIKATION . . . . . . . . . . . . . . . . . 21

Setting up the Netopia Gateway . . . . . . . . . . . . . . . . . . . . . . . . 22

Microsoft Windows: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Macintosh MacOS 8 or higher or Mac OS X: . . . . . . . . . . . . . . . 23

Configuring the Netopia Gateway . . . . . . . . . . . . . . . . . . . . . . 25

MiAVo VDSL and Ethernet WAN models Quickstart . . . . . . . . . . . . . . 26

PPPoE Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Set up the Netopia Pocket Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Netopia Gateway Status Indicator Lights . . . . . . . . . . . . . . . . . 31

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Table of Contents

Home Page - Basic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Manage My Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Status Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Enable Remote Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Expert Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Update Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Factory Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

CHAPTER 3

Expert Mode

Accessing the Expert Web Interface . . . . . . . . . . . . . . . . . . . . . 41

Open the Web Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Home Page - Expert Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Home Page - Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Navigating the Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Breadcrumb Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Alert Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

LAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Wireless . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Multiple SSIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Wireless MAC Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

PPP over Ethernet interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Ethernet WAN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

IP Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

IP Static ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Pinholes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

How to Use the Quickstart Page . . . . . . . . . . . . . . . . . . . . . . . . . 49

Setup Your Gateway using a PPP Connection . . . . . . . . . . . . . . 49

About Closed System Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

WPA Version Allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Use RADIUS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Configure Specific Pinholes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Table of Contents

Planning for Your Pinholes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Example: A LAN Requiring Three Pinholes . . . . . . . . . . . . . . . . 82

Pinhole Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . 84

IPMaps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Configure the IPMaps Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

FAQs for the IPMaps Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

What are IPMaps and how are they used? . . . . . . . . . . . . . . . . . 88

What types of servers are supported by IPMaps? . . . . . . . . . . . 88

Can I use IPMaps with my PPPoE or PPPoA connection? . . . . . 88

Will IPMaps allow IP addresses from different subnets to be assigned to my

Gateway? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

IPMaps Block Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Default Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Configure a Default Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Typical Network Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

NAT Combination Application . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

IP-Passthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

A restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Differentiated Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

DNS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

DHCP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

RADIUS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

IGMP (Internet Group Management Protocol) . . . . . . . . . . . . . . . . . 102

UPnP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

LAN Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Ethernet Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Configuring for Bridge Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Example #1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Example #2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Syslog Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Log Event Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Internal Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Software Hosting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

List of Supported Games and Software . . . . . . . . . . . . . . . . . . . 131

Rename a User(PC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Clear Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Create and Change Passwords . . . . . . . . . . . . . . . . . . . . . . . . 136

Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Table of Contents

Use a Netopia Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

BreakWater Basic Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Configuring for a BreakWater Setting . . . . . . . . . . . . . . . . . . . . 138

TIPS for making your BreakWater Basic Firewall Selection . . . 140

Basic Firewall Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

IPSec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

SafeHarbour IPSec VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Configuring a SafeHarbour VPN . . . . . . . . . . . . . . . . . . . . . . . . 145

Parameter Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Stateful Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Stateful Inspection Firewall installation procedure . . . . . . . . . . . . . . . 153

Exposed Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Stateful Inspection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Open Ports in Default Stateful Inspection Installation . . . . . . . . . . . . 158

Firewall Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

General firewall terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Basic IP packet components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Basic protocol types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Firewall design rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Firewall Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Implied rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Example filter set page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Filter basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Example network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Example filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Example 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Packet Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

What’s a filter and what’s a filter set? . . . . . . . . . . . . . . . . . . . . . . . . . 168

How filter sets work. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Filter priority. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

How individual filters work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

A filtering rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Parts of a filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Port numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Port number comparisons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Other filter attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Putting the parts together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Filtering example #1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Filtering example #2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Table of Contents

Design guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

An approach to using filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Working with IP Filters and Filter Sets . . . . . . . . . . . . . . . . . . 177

Adding a filter set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Adding filters to a filter set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Viewing filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Modifying filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Deleting filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Moving filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Deleting a filter set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Associating a Filter Set with an Interface . . . . . . . . . . . . . . . . 183

Policy-based Routing using Filtersets . . . . . . . . . . . . . . . . . . 186

TOS field matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Security Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Using the Security Monitoring Log . . . . . . . . . . . . . . . . . . . . . . . 189

Timestamp Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Install Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Updating Your Gateway’s Netopia Firmware Version . . . . . . . . 193

Step 1: Required Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Step 2: Netopia firmware Image File . . . . . . . . . . . . . . . . . . . . . . . . . 194

Install Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Use Netopia Software Feature Keys . . . . . . . . . . . . . . . . . . . . . . . . . 197

Obtaining Software Feature Keys . . . . . . . . . . . . . . . . . . . . . . . 197

Procedure - Install a New Feature Key File . . . . . . . . . . . . . . . . 197

To check your installed features: . . . . . . . . . . . . . . . . . . . . . . . . 199

Install Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

CHAPTER 4

CHAPTER 5

Basic Troubleshooting

. . . . . . . . . . . . . . . . . . . . . . . . 203

Status Indicator Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

LED Function Summary Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Factory Reset Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Advanced Troubleshooting

Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Expert Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Ports: Ethernet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

. . . . . . . . . . . . . . . . . . . . . 219

Table of Contents

Ports: DSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

IP: Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

DSL: Circuit Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

System Log: Entire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Network Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

CHAPTER 6

Command Line Interface

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Starting and Ending a CLI Session . . . . . . . . . . . . . . . . . . . . . 238

Logging In. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Ending a CLI Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Saving Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Using the CLI Help Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

About SHELL Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

SHELL Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

SHELL Command Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

SHELL Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Common Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

WAN Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

About CONFIG Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 251

CONFIG Mode Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Navigating the CONFIG Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Entering Commands in CONFIG Mode . . . . . . . . . . . . . . . . . . . . . . . 253

Guidelines: CONFIG Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

Displaying Current Gateway Settings. . . . . . . . . . . . . . . . . . . . . . . . . 254

Step Mode: A CLI Configuration Technique . . . . . . . . . . . . . . . . . . . .254

Validating Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

CONFIG Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

DSL Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

ATM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Bridging Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Common Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

DHCP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Common Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

DMT Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

DSL Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Domain Name System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Common Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

. . . . . . . . . . . . . . . . . . . . . . . 235

Table of Contents

Dynamic DNS Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

IGMP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

IP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Common Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

ARP Timeout Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

DSL Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Ethernet LAN Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Default IP Gateway Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

IP-over-PPP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Static ARP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

IGMP Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

IPsec Passthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

IP Prioritization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Differentiated Services (DiffServ). . . . . . . . . . . . . . . . . . . . . . . . 274

SIP Passthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Static Route Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

IPMaps Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Network Address Translation (NAT) Default Settings . . . . . . . . . . . . 278

Network Address Translation (NAT) Pinhole Settings . . . . . . . . . . . . 279

PPPoE /PPPoA Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Configuring Basic PPP Settings . . . . . . . . . . . . . . . . . . . . . . . . 280

Configuring Port Authentication . . . . . . . . . . . . . . . . . . . . . . . . 282

Ethernet Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Command Line Interface Preference Settings . . . . . . . . . . . . . . . . . 283

Port Renumbering Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Firewall Settings (for BreakWater Firewall) . . . . . . . . . . . . . . . . 286

SafeHarbour IPSec Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Internet Key Exchange (IKE) Settings . . . . . . . . . . . . . . . . . . . . 291

Stateful Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Packet Filtering Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

SNMP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

SNMP Notify Type Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

System Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Default syslog installation procedure . . . . . . . . . . . . . . . . . . . . . 304

Wireless Settings (supported models). . . . . . . . . . . . . . . . . . . . . . . . 306

Wireless Privacy Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Wireless MAC Address Authorization Settings . . . . . . . . . . . . . 312

RADIUS Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

VLAN Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Table of Contents

Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

UPnP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

DSL Forum settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

TR-064 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

TR-069 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

VDSL Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

VDSL Parameter Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

VDSL Parameters Accepted Values . . . . . . . . . . . . . . . . . . . . . 320

CHAPTER 7

CHAPTER 8

Glossary

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

-----A----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

-----B----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

-----C----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

-----D----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

-----E----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

-----F----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

-----H----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

-----I----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

-----K----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

-----L-----. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

-----M----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

-----N----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

-----P----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

-----Q----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

-----R----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

-----S----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

-----T----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

-----U----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

-----V----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

-----W----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

-----X----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

Technical Specifications and Safety Information

. . . . . 343

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Dimensions: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Communications interfaces: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Operating temperature: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Storage temperature: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Table of Contents

Relative storage humidity: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

Software and protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

Software media: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

Routing: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

WAN support: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

Security: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

Management/configuration methods: . . . . . . . . . . . . . . . . . . . . 344

Diagnostics: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

Agency approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

North America . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

International . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

Regulatory notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

European Community. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

Manufacturer’s Declaration of Conformance . . . . . . . . . . . . . 346

United States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Service requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Declaration for Canadian users . . . . . . . . . . . . . . . . . . . . . . . . . 347

Caution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Important Safety Instructions . . . . . . . . . . . . . . . . . . . . . . . . . 348

Australian Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

Caution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

Telecommunication installation cautions . . . . . . . . . . . . . . . . . . 348

47 CFR Part 68 Information . . . . . . . . . . . . . . . . . . . . . . . . . . 349

FCC Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

FCC Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

Electrical Safety Advisory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

CHAPTER 9

Overview of Major Capabilities

Wide Area Network Termination . . . . . . . . . . . . . . . . . . . . . . . 352

PPPoE/PPPoA (Point-to-Point Protocol over Ethernet/ATM) . . . . . . 352

Instant-On PPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

Simplified Local Area Network Setup . . . . . . . . . . . . . . . . . . . 353

DHCP (Dynamic Host Configuration Protocol) Server . . . . . . . . . . . 353

DNS Proxy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

Embedded Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

. . . . . . . . . . . . . . . . . . 351

Table of Contents

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

Remote Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

Password Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . . . 355

Netopia Advanced Features for NAT . . . . . . . . . . . . . . . . . . . . 357

Internal Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

Pinholes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

Default Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

Combination NAT Bypass Configuration. . . . . . . . . . . . . . . . . . 358

IP-Passthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

VPN IPSec Pass Through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

VPN IPSec Tunnel Termination. . . . . . . . . . . . . . . . . . . . . . . . . 360

Stateful Inspection Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

SSL Certificate Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363

What’s New in 7.6.1

CHAPTER 1 Introduction

What’s New in 7.6.1

New in Netopia Firmware Version 7.6.1 are the following features:

VLAN Enhancements - 802.1P and 802.1Q, QoS (Quality of Service) protocols on the

•

MAC (Medium Access Control) level. See “VLAN” on page 111.

•

Command line reserved address support for DHCP. See page 260 for more information.

About Netopia Documentation

☛

Netopia, Inc. provides a suite of technical information for its 2200- and 3300-series family of intelligent enterprise and consumer Gateways. It consists of:

Software User Guide

•

Dedicated Quickstart guides

Speciﬁc White Papers

•

The documents are available in electronic form as Por table Document Format (PDF) ﬁles. They are viewed (and printed) from Adobe Acrobat Reader, Exchange, or any other application that supports PDF ﬁles.

They are downloadable from Netopia’s website:

http://www.netopia.com/

NOTE:

This guide describes the wide variety of features and functionality of the Netopia Gateway, when used in Router mode. The Netopia Gateway may also be delivered in Bridge mode. In Bridge mode, the Gateway acts as a pass-through device and allows the workstations on your LAN to have public addresses directly on the Internet.

Intended Audience

This guide is targeted primarily to residential ser vice subscribers.

Expert Mode sections may also be of use to the support staf fs of broadband service providers and advanced residential service subscribers.

See “Expert Mode” on page 41.

Documentation Conventions

General

This manual uses the following conventions to present information:

Convention (Typeface) Description

bold italic monospaced

bold italic sans serif

terminal

bold terminal

Italic

Italic type indicates the complete titles of

Internal Web Interface

Menu commands

Web GUI page links and button names

Computer display text

User-entered text

manuals.

Convention (Graphics) Description

blue rectangle or line

Denotes an “excerpt” from a Web page or the visual truncation of a Web page

Denotes an area of emphasis on a Web page

solid rounded rectangle with an arrow

Command Line Interface

Syntax conventions for the Netopia Gateway command line interface are as follows:

Convention

straight ([ ]) brackets in cmd line Optional command arguments

Description

curly ({ }) brackets, with values separated with vertical bars (|).

bold terminal type face

italic terminal type face

Alternative values for an argument are presented in curly ({ }) brackets, with values separated with vertical bars (|).

User-entered text

Variables for which you supply your own values

Organization

This guide consists of nine chapters, including a glossary, and an index. It is organized as follows:

• Chapter 1, “Introduction” — Describes the Netopia document suite, the purpose of,

the audience for, and structure of this guide. It gives a table of conventions.

• Chapter 2, “Basic Mode Setup” — Describes how to get up and running with your

Netopia Gateway.

• Chapter 3, “Expert Mode” — Focuses on the “Expert Mode” Web-based user inter-

face for advanced users. It is organized in the same way as the Web UI is organized. As you go through each section, functions and procedures are discussed in detail.

• Chapter 4, “Basic Troubleshooting” — Gives some simple suggestions for trouble-

shooting problems with your Gateway’s initial conﬁguration.

• Chapter 5, “Advanced Troubleshooting” — Gives suggestions and descriptions of

expert tools to use to troubleshoot your Gateway’s conﬁguration.

• Chapter 6, “Command Line Interface” — Describes all the current text-based com-

mands for both the SHELL and CONFIG modes. A summary table and individual command examples for each mode is provided.

• Chapter 7, “Glossary”

• Chapter 8, “Technical Speciﬁcations and Safety Information”

• Chapter 9, “Overview of Major Capabilities” — Presents a product description sum-

mary.

• Index

A Word About Example Screens

This manual contains many example screen illustrations. Since Netopia 2200- and 3300 Series Gateways offer a wide variety of features and functionality, the example screens shown may not appear exactly the same for your particular Gateway or setup as they appear in this manual. The example screens are for illustrative and explanator y purposes, and should not be construed to represent your own unique environment.

CHAPTER 2 Basic Mode Setup

Most users will ﬁnd that the basic Quickstart conﬁguration is all that they ever need to use. This section may be all that you ever need to conﬁgure and use your Netopia Gateway. The following instructions cover installation in Router Mode.

This section covers:

• “Impor tant Safety Instructions” on page 20

• “Wichtige Sicherheitshinweise” on page 21 (German)

• “Setting up the Netopia Gateway” on page 22

• “Conﬁguring the Netopia Gateway” on page 25

• “Netopia Gateway Status Indicator Lights” on page 31

• “Home Page - Basic Mode” on page 32

Important Safety Instructions

POWER SUPPLY INSTALLATION

Connect the power supply cord to the power jack on the Netopia Gateway. Plug the power supply into an appropriate electrical outlet.

☛ CAUTION:

Depending on the power supply provided with the product, either the direct plug-in power supply blades, power supply cord plug or the appliance coupler serves as the mains power disconnect. It is important that the direct plug-in power supply, socket-outlet or appliance coupler be located so it is readily accessible. (Sweden) Apparaten skall anslutas till jordat uttag när den ansluts till ett nätverk

(Norway) Apparatet må kun tilkoples jordet stikkontakt. USB-powered models: For Use with Listed I.T.E. Only

TELECOMMUNICATION INSTALLATION

When using your telephone equipment, basic safety precautions should always be followed to reduce the risk of ﬁre, electric shock and injur y to persons, including the following:

• Do not use this product near water, for example, near a bathtub, wash bowl, kitchen

sink or laundry tub, in a wet basement or near a swimming pool.

• Avoid using a telephone (other than a cordless type) during an electrical storm. There

may be a remote risk of electrical shock from lightning.

• Do not use the telephone to report a gas leak in the vicinity of the leak.

PRODUCT VENTILATION

The Netopia Gateway is intended for use in a consumer's home. Ambient temperatures around this product should not exceed 104°F (40°C). It should not be used in locations exposed to outside heat radiation or trapping of its own heat. The product should have at least one inch of clearance on all sides except the bottom when properly installed and should not be placed inside tightly enclosed spaces unless proper ventilation is provided.

SAVE THESE INSTRUCTIONS

Wichtige Sicherheitshinweise

NETZTEIL INSTALLIEREN

Verbinden Sie das Kabel vom Netzteil mit dem Power-Anschluss an dem Netopia Gateway. Stecken Sie dann das Netzteil in eine Netzsteckdose.

☛ Achtung:

Abhängig von dem mit dem Produkt gelieferten Netzteil, entweder die direkten Steckernetzgeräte, Stecker vom Netzkabel oder der Gerätekoppler dienen als Hauptspannungsunterbrechung. Es ist wichtig, dass das Steckernetzgerät, Steckdose oder Gerätekoppler frei zugänglich sind. (Sweden) Apparaten skall anslutas till jordat uttag när den ansluts till ett nätverk

(Norway) Apparatet må kun tilkoples jordet stikkontakt. USB-powered models: For Use with Listed I.T.E. Only

INSTALLATION DER TELEKOMMUNIKATION

Wenn Ihre Telefonausrüstung verwendet wird, sollten grundlegende Sicherheitsanweisungen immer befolgt werden, um die Gefahr eines Feuers, eines elektrischen Schlages und die Verletzung von Personen, zu verringern. Beachten Sie diese weiteren Hinweise:

• Benutzen Sie dieses Produkt nicht in Wassernähe wie z.B. nahe einer Badewanne,

Waschschüssel, Küchenspüle, in einem nassen Keller oder an einem Swimmingpool.

• Vermeiden Sie das Telefonieren (gilt nicht für schnurlose Telefone) während eines Gewit-

ters. Es besteht die Gefahr eines elektrischen Schlages durch einen Blitz.

• Nicht das Telefon benutzen um eine Gasleckstelle zu Melden, wenn Sie sich in der Nähe

der Leckstelle beﬁnden.

Bewahren Sie diese Anweisungen auf

Setting up the Netopia Gateway

Refer to your Quickstart Guide for instructions on how to connect your Netopia gateway to your power source, PC or local area network, and your Internet access point, whether it is a dedicated DSL outlet or a DSL or cable modem. Different Netopia Gateway models are supplied for any of these connections. Be sure to enable Dynamic Addressing on your PC. Perform the following:

Microsoft Windows:

Step 1. Navigate to the TCP/IP Properties Control Panel.

a. Some Windows versions follow a path like this:

Start menu -> Settings -> Control Panel -> Network (or Network and Dial-up Connections -> Local Area Connection -> Properties) > TCP/IP [your_network_card] or Internet Protocol [TCP/IP]

-> Properties

Setting up the Netopia Gateway

b. Some Windows versions follow a path like this:

Start menu -> Control Panel -> Network and Internet Connections -> Network Connections -> Local Area Connection -> Properties -> Internet Protocol [TCP/IP] -> Properties

Macintosh MacOS 8 or higher or Mac OS X:

Step 1. Access the TCP/IP or Network control panel.

a. MacOS follows a path like this:

Apple Menu -> Control Panels -> TCP/IP

Control Panel

b. Mac OS X follows a path like this:

Apple Menu -> System Preferences -> Network

Then go to Step 2.

Step 2. Select Built-in Ethernet

Step 3. Select Conﬁgure Using DHCP

Step 4. Close and Save, if prompted.

Proceed to “Conﬁguring the Netopia Gateway” on page 25.

Configuring the Netopia Gateway

Conﬁguring the Netopia Gateway

1. Run your Web browser application, such as Firefox or Microsoft Internet

Explorer, from the computer connected to the Netopia Gateway.

Enter http://192.168.1.254 in the Location text box. The Admin Password page appears.

Access to your Netopia device can be controlled through two access control accounts, Admin or User.

• The Admin, or administrative user, performs all conﬁguration, management or mainte-

nance operations on the Gateway.

• The User account provides monitor capability only.

A user may NOT change the conﬁguration, perform upgrades or invoke maintenance functions.

For the security of your connection, an Admin password must be set on the Netopia unit.

MiAVo VDSL and Ethernet WAN models Quickstart

The browser then displays the Quickstart page.

2. Click the

Once a connection is established, your browser is redirected to your ser vice provider’s home page or a registration page on the Internet.

Connect to the Internet

button.

☛ NOTE:

For MiAVo Series (3397GP) models, skip the rest of this section.

Congratulations! Your conﬁguration is complete.

You can skip to “Home Page - Basic Mode” on page 32.

Configuring the Netopia Gateway

PPPoE Quickstart

For a PPPoE connection, your browser will display a different series of web pages:

The browser then displays the Quickstart web page.

3. Enter the username and password supplied by your Internet Service Pro-

vider. Click the

Once you enter your username and password here, you will no longer need to enter them whenever you access the Internet. The Netopia Gateway stores this information and automatically connects you to the Internet.

The Gateway displays a message while it conﬁgures itself.

Connect to the Internet

button.

4. When the connection succeeds, your browser will display a success

message.

Once a connection is established, your browser is redirected to your ser vice provider’s home page or a registration page on the Internet.

5. Congratulations! Your installation is complete. You can now surf to your

favorite Web sites by typing an URL in your browser’s location box or by selecting one of your favorite Internet bookmarks.

Configuring the Netopia Gateway

Set up the Netopia Pocket Gateway

Your Netopia 3342N/3352N Pocket Gateway comes with its own installation wizard.

• If you are using Windows 98, insert the CD.

• If you are using Windows XP, Windows 2000, or Windows NT, you don’t even need the

CD.

Follow these easy setup steps:

1. Plug the Netopia Pocket Gateway into a USB port on your PC.

2. Whether you use the CD (Windows 98) or not (all other Windows versions), on

Windows-based PCs, the Netopia Installation Wizard will launch automatically.

The Netopia Installation Wizard will assist you to conﬁgure your PC to work with the Netopia pocket Gateway. Follow the on-screen instructions.

To proceed, click the

button.

The Netopia Installation Wizard performs a series of checks on your system and then will install USB drivers for your connection.

3. Place the Netopia Pocket Gateway near your PC so you can see it easily.

Make sure any cables are kept away from power cords, ﬂuorescent lighting ﬁxtures, and other sources of electrical interference.

4. When the wizard prompts you, connect the RJ-11 Telephone Cable from the DSL

port on the Netopia Pocket Gateway to the ADSL phone jack.

The DSL indicator light should blink for up to two minutes and then come on solid green once the device is connected to your computer.

phone jack

RJ-11 phone cable

USB port

Netopia Pocket Gateway/

The Wizard displays a success message when the settings are conﬁgured.

5. The Netopia Installation Wizard will then launch your web browser and display

the

Welcome

page where you conﬁgure your Netopia Pocket Gateway.

Netopia Gateway Status Indicator Lights

Colored LEDs on your Netopia Gateway indicate the status of various port activity. Different Gateway models have different ports for your connections and dif ferent indicator LEDs. The Quickstart Guide accompanying your Netopia Gateway describes the behavior of the various indicator LEDs.

Example status indicator lights

Status Indicator Lights (LEDs)

netopia

Home Page - Basic Mode

After you have performed the basic Quickstart conﬁguration, any time you log in to your Netopia Gateway you will access the Netopia Gateway Home Page.

You access the Home Page by typing tion box.

The Basic Mode Home Page appears.

http://192.168.1.254

in your Web browser’s loca-

Home Page - Basic Mode

The Home Page displays the following information in the center section:

Item Description

Serial Number

Software

Release

Warranty Date

Status of DSL

Status of

Connection

Local WAN IP

Address

Remote Gateway Address

Primary DNS

Secondary

DNS

ISP Username

This is the unique serial number of your Gateway.

This is the version number of the current embedded software in your Gateway.

This is the date that your Gateway was installed and enabled.

DSL connection (Internet) is either Up or Down

‘Waiting for DSL’ is displayed while the Gateway is training. This should change to ‘Up’ within two minutes. ‘Up’ is displayed when the ADSL line is synched and the PPPoE session is established. ‘Down’ indicates inability to establish a connection; possible line failure.

This is the negotiated address of the Gateway’s WAN interface. This address is usually dynamically assigned.

This is the negotiated address of the remote router to which this Gateway is connected.

These are the negotiated DNS addresses.

This is your PPPoE username as assigned by your service provider.

Ethernet

Status

USB Status

Date & Time

(if so equipped) Local Area Network (Ethernet) is either Up or Down

If your Gateway is so equipped, Local Area Network (USB) is either Up or Down

This is the current UTC time; blank if this is not available due to lack of a network connection.

The links in the left-hand column on this page allow you to manage or conﬁgure several features of your Gateway. Each link is described in its own section.

Link: Manage My Account

You can change your ISP account information for the Netopia Gateway. You can also manage other aspects of your account on your service provider’s account management Web site.

Click on the

If you have a PPPoE account, enter your username, and then your new password. Conﬁrm your new password. For security, your actual passwords are not displayed on the screen as you type. You must enter the new password twice to be sure you have typed it correctly.

Click the

Manage My Account

Submit

button.

link. The Manage My Account page appears.

If you have a non-PPPoE account, click the OK button.

You will be taken to your service provider’s Web site account management page.

Home Page - Basic Mode

Link: Status Details

If you need to diagnose any problems with your Netopia Gateway or its connection to the Internet, you can run a sophisticated diagnostic tool. It checks several aspects of your physical and electronic connection and repor ts its results on-screen. This can be useful for troubleshooting, or when speaking with a technical support technician.

Click on the

Click the of these tests, see “Diagnostics” on page 229.

Status Details

Run Diagnostics

link. The Diagnostics page appears.

button to run your diagnostic tests. For a detailed description

Link: Enable Remote Management

This link allows you to authorize a remotely-located person, such as a support technician, to directly access your Netopia Gateway. This is useful for ﬁxing conﬁguration problems when you need expert help. You can limit the amount of time such a person will have access to your Gateway. This will prevent unauthorized individuals from gaining access after the time limit has expired.

Click the

Since you’ve already has entered an Admin password, you can use that Admin password or enter a new password. If you enter a new password, it becomes the temporar y Admin password. After the time-out period has expired, the Admin password rever ts to the original Admin password you entered.

Enter a temporary password for the person you want to authorize, and conﬁrm it by typing it again. You can select a time-out period for this password, from 5 to 30 minutes, from the pull-down menu. Be sure to tell the authorized person what the password is, and for how long the time-out is set. Click the OK button.

Enable Rmt Mgmt

link. The Enable Remote Management page appears.

Home Page - Basic Mode

Link: Expert Mode

Most users will ﬁnd that the basic Quickstart conﬁguration is all that they ever need to use. Some users, however, may want to do more advanced conﬁguration. The Netopia Gateway has many advanced features that can be accessed and conﬁgured through the Exper t Mode pages.

Click the

You should carefully consider any conﬁguration changes you want to make, and be sure that your service provider supports them.

Once you click the OK button you will be taken to the Expert Mode Home Page.

The Expert Mode Home Page is the main access point for conﬁguring and managing the advanced features of your Gateway. See “Expert Mode” on page 41 for information.

Expert Mode

link to display the Expert Mode Conﬁrmation page.

Link: Update Firmware

☛ NOTE:

(This link is not available on the 3342/3352 models, since ﬁrmware updates must be upgraded via the USB host driver. 3342N/3352N models do support this feature.)

Periodically, the embedded ﬁrmware in your Gateway may be updated to improve the operation or add new features. Your gateway includes its own onboard installation capability. Your service provider may inform you when new ﬁrmware is available, or you can check for yourself.

Click the

If you click the latest ﬁrmware revision. If a newer version is found, your ﬁrmware will be automatically updated once you conﬁrm the installation.

Update Firmware

Continue

button, the Gateway will check a remote Firmware Ser ver for the

link. The Firmware Update Conﬁrmation page appears.

Home Page - Basic Mode

Link: Factory Reset

In some cases, you may need to clear all the conﬁguration settings and start over again to program the Netopia Gateway. You can perform a factor y reset to do this.

Click on

Factory Reset

☛ NOTE:

Exercise caution before per forming a Factor y Reset. This will erase any conﬁguration changes that you may have made and allow you to reprogram your Gateway.

to reset the Gateway back to its original factory default settings.

Accessing the Expert Web Interface

CHAPTER 3 Expert Mode

Using the Expert Mode Web-based user interface for the Netopia 2200- and 3300-series Gateway you can conﬁgure, troubleshoot, and monitor the status of your Gateway.

Accessing the Expert Web Interface

Open the Web Connection

Once your Gateway is powered up, you can use any recent version of the best-known web browsers such as Netscape Navigator or Microsoft Internet Explorer from any LAN-attached PC or workstation. The procedure is:

1. Enter the name or IP address of your Netopia Gateway in the Web

browser's window and press Return.

For example, you would enter

2. If an administrator or user password has been assigned to the Netopia

Gateway, enter word and click

The Basic Mode Home Page opens.

Admin

http://192.168.1.254

User

as the username and the appropriate pass-

3. Click on the

You are challenged to conﬁrm your choice.

Click OK. The Home Page opens in Expert Mode.

Expert Mode

link in the left-hand column of links.

Accessing the Expert Web Interface

Home Page - Expert Mode

The Home Page is the summary page for your Netopia Gateway. The toolbar at the top provides links to controlling, conﬁguring, and monitoring pages. Critical conﬁguration and operational status is displayed in the center section.

Home Page - Information

The Home page’s center section contains a summary of the Gateway’s conﬁguration settings and operational status.

Summary Information

Field Status and/or Description

General Information

Hardware Model number and summary speciﬁcation Serial Number Unique serial number, located on label attached to bottom of unit Software Version Release and build number of running Netopia Operating System. Product ID Refers to internal circuit board series; useful in determining which software

upgrade applies to your hardware type.

Date & Time This is the current UTC time; blank if this is not available due to lack of a

network connection.

Breakwater Firewall If the optional feature key is installed: Status of the Breakwater Firewall:

ClearSailing, SilentRunning, or LANdLocked.

Safe Harbour If the optional feature key is installed: SafeHarbour VPN IPsec Tunnel option

(if installed): either On or Off.

WAN

Status Wide Area Network may be Waiting for DSL (or other waiting status), Up or

Down

Data Rate (Kbps) Once connected, displays DSL speed rate, Downstream and Upstream Local Address IP address assigned to the WAN port. Peer Address The IP address of the gateway to which the connection defaults. If doing

DHCP, this info will be acquired. If doing PPP, this info will be negotiated. Connection Type May be either Instant On or Always On. NAT On or Off. ON if using Network Address Translation to share the IP address

across many LAN users. WAN Users Displays the number of users allotted and the total number available for

use.

LAN

IP Address Internal IP address of the Netopia Gateway. Netmask Deﬁnes the IP subnet for the LAN

Default is 255.255.255.0 for a Class C device DHCP Server On or Off. ON if using DHCP to get IP addresses for your LAN client

machines. DHCP Leases A “lease” is held by each LAN client that has obtained an IP address through

DHCP. Ethernet (or USB)

Status

Status of your Ethernet network connection (if supported). Up or Down.

Toolbar

The toolbar is the dark blue bar at the top of the page containing the major navigation buttons. These buttons are available from almost ever y page, allowing you to move freely about the site.

Home Conﬁgure Troubleshoot Security Install Restart Help

Quickstart System Status Passwords Install Certiﬁcate LAN Network Tools Firewall Install Key WAN Diagnostics IPSec Install Software Advanced Stateful Inspection

Packet Filter

Security Log

Navigating the Web Interface

Link: Breadcrumb Trail

The breadcrumb trail is built in the light brown area beneath the toolbar. As you navigate down a path within the site, the trail is built from left to right. To return anywhere along the path from which you came, click on one of the links.

Restart

Button: Restart

The Restart button on the toolbar allows you to restart the Gateway at any time. You will be prompted to conﬁrm the restar t before any action is taken. The Restar t Conﬁrmation message explains the consequences of and reasons for restarting the Gateway.

Restart

Link: Alert Symbol

The Alert symbol appears in the upper right corner if you make a database change; one in which a change is made to the Gateway’s conﬁguration. The Alert serves as a reminder that you must Save the changes and Restart the Gateway before the change will take effect. You can make many changes on various pages, and even leave the browser for up to 5 minutes, but if the Gateway is restarted before the changes are applied, they will be lost. When you click on the Alert symbol, the Save Changes page appears. Here you can select various options to save or discard these changes.

If more than one Alert is triggered, you will need to take action to clear the ﬁrst Alert before you can see the second Alert.

Help

Button: Help

Context-sensitive Help is provided in your Gateway. The page shown here is displayed when you are on the Home page or other transitional pages. To see a context help page example, go to

Security -> Passwords

, then click

Help

Configure

Conﬁgure

Button: Conﬁgure

The Conﬁguration options are presented in the order of likelihood you will need to use them. Quickstart is typically accessed during the hardware installation and initial conﬁguration phase. Often, these settings should be changed only in accordance with infor- mation from your Service Provider. LAN and WAN settings are available to ﬁne-tune your system. Advanced provides some special capabilities typically used for gaming or small ofﬁce environments, or where LAN-side servers are involved.

☛ This button will not be available if you log on as User.

Link: Quickstart

How to Use the Quickstart Page. Quickstart is normally used immediately after

the new hardware is installed. When you are ﬁrst conﬁguring your Gateway, Quickstart appears ﬁrst.

(Once you have conﬁgured your Gateway, logging on displays the Home page. Thereafter, if you need to use Quickstart, choose it from the Expert Mode Conﬁgure menu.)

Setup Your Gateway using a PPP Connection.

This example screen is the for a PPP Quickstart conﬁguration. Your gateway authenticates with the Service Provider equipment using the ISP Username and Password. These values are given to you by your Service Provider.

1. Enter your ISP Username and ISP Password.

2. Click

A brief message is displayed while the Gateway attempts to establish a connection.

3. When the connection succeeds, your browser will display your Service

Connect to the Internet

Provider’s home page.

If you encounter any problems connecting, refer to the chapters “Basic Troubleshooting”

on page 203 or “Advanced Troubleshooting” on page 219.

Link: LAN

Configure

* Enable Interface: Enables all LAN-connected computers to share resources and to connect to the WAN. The Interface should always be enabled unless you are instructed to disable it by your Service Provider during troubleshooting.

* IP Address: The LAN IP Address of the Gateway. The IP Address you assign to your LAN interface must not be used by another device on your LAN network.

* IP Netmask: Speciﬁes the subnet mask for the TCP/IP network connected to the virtual circuit. The subnet mask speciﬁes which bits of the 32-bit binary IP address represent network information. The default subnet mask for most networks is 255.255.255.0 (Class C subnet mask.)

* Restrictions: Speciﬁes whether an administrator can open a Web Administrator or Telnet connection to the Gateway over the LAN interface in order to monitor and conﬁgure the Gateway. On the LAN Interface, you can enable or disable administrator access. By default, administrative restrictions are turned of f, meaning an administrator can open a Web Administrator or Telnet connection through the LAN Inter face.

• Advanced: Clicking on the Advanced link displays the Advanced LAN IP Interface page.

• IGMP Forwarding: The default setting is Disabled. If you check this option, it will

enable Internet Group Management Protocol (IGMP) multicast for warding. IGMP allows a router to determine which host groups have members on a given network segment.

• RIP Send Mode: Speciﬁes whether the gateway should use Routing Information Proto-

col (RIP) broadcasts to advertise its routing tables to other routers on your network. You may choose from the following protocols:

• RIP-1: Routing Information Protocol version 1

• RIP-2: RIP Version 2 is an extension of the original Routing Information Protocol (RIP-

1) that expands the amount of useful information in the RIP packets. While RIP-1 and RIP-2 share the same basic algorithms, RIP-2 supports several new features, including inclusion of subnet masks in RIP packets and implementation of multicasting instead of broadcasting (which reduces the load on hosts which do not suppor t routing protocols.

• RIP-1 compatibility: Compatible with RIP version 1

• RIP-2 with MD5: MD5 authentication is an extension of RIP-2 that increases security by requiring an authentication key when routes are adver tised.

• RIP MD5 Key: Secret password when using RIP-2 with MD5.

• RIP Receive Mode: Speciﬁes whether the Gateway should use Routing Information

Protocol (RIP) broadcasts to update its routing tables with information received from other routers on your network. The protocol choices are the same as for the RIP send mode.

• Proxy ARP: Speciﬁes whether you want the Gateway to respond when it receives an

address resolution protocol for devices behind it. This is a way to make a computer that is physically located on one network appear to be part of a different physical network connected to the same Gateway. It allows you to hide a computer with a public IP

Configure

address on a private network behind your Gateway, and still have the computer appear to be on the public network “in front of” the Gateway.

• Static Client Address Translation: If you check this checkbox, this feature allows a

statically addressed computer whose IP address falls outside of the LAN subnet(s) to simply plug in and get online without any manual conﬁguration on either the host or the Netopia Gateway. If enabled, statically addressed LAN hosts that have an address outside of LAN subnets will be able to communicate via the Router’s WAN interface to the Internet. Supported static IP address values must fall outside of the Router's LAN subnet(s).

• DHCP Server: Your Gateway can provide network conﬁguration information to computers on your LAN, using the Dynamic Host Conﬁguration Protocol (DHCP).

If you already have a DHCP server on your LAN, you should turn this service off.

If you want the Gateway to provide this service, click the menu, choose Server, then conﬁgure the range of IP addresses that you would like the Gateway to hand out to your computers.

Server Mode

pull-down

You can also specify the length of time the computers can use the conﬁguration information; DHCP calls this period the lease time.

Your Service Provider may, for certain services, want to provide conﬁguration from its DHCP servers to the computers on your LANs. In this case, the Gateway will relay the DHCP requests from your computers to a DHCP ser ver in the Service Provider's network. Click the relay-agent and enter the IP address of the Ser vice Provider's DHCP server in the Server Address ﬁeld. This address is furnished by the Service Provider.

☛ NOTE:

The Relay-agent option only works when NAT is off and the Gateway is in router mode.

Wireless (supported models)

If your Gateway is a wireless model (such as a 3347W) you can enable or disable the wireless LAN (WLAN) by clicking the

Wireless functionality is enabled by default.

If you uncheck the Enable Wireless checkbox, the Wireless Options are disabled, and the Gateway will not provide or broadcast any wireless LAN ser vices.

Wireless

link.

SSID (Network ID): The SSID is preset to a number that is unique to your unit. You can either leave it as is, or change it by entering a freeform name of up to 32 characters, for example “Ed’s Wireless LAN”. On client PCs’ software, this might also be called the Net- work Name. The SSID is used to identify this particular wireless LAN. Depending on their operating system or client wireless card, users must either:

• select from a list of available wireless LANs that appear in a scanned list on their client

• or, if you are in Closed System Mode (see Enable Closed System Mode below), enter

this name on their clients in order to join this wireless LAN.

The pull-down menu for enabling Privacy offers four settings: WPA-802.1x, WPA-PSK, WEP - Automatic, and Off - No Privacy. WEP-Manual is also available on the Advanced Conﬁguration Options page. See “Privacy” on page 55.

Configure

☛ NOTE:

On the 2200-Series Gateways, WEP-Manual privacy is enabled by default. Use the Netopia Installation Wizard on the accompanying Netopia CD to generate WEP keys for connecting wireless client computers.

Privacy

• Off - No Privacy provides no encr yption on your wireless LAN data.

• WPA-802.1x provides RADIUS server authentication suppor t.

• WPA-PSK provides Wireless Protected Access, the most secure option for your wire-

less network. This mechanism provides the best data protection and access control.

The Pre Shared Key is a passphrase shared between the Router and the clients and is used to generate dynamically changing keys. The passphrase can be 8-63 characters or up to 64 hex characters. It is recommended to use at least 20 characters for best security.

• WEP - Automatic is a passphrase generator. You enter a passphrase that you choose

in the Passphrase ﬁeld. The passphrase can be any string of words or numbers. You can provide a level of data security by enabling WEP (Wired Equivalent Privacy) for

encryption of network data. You can enable 40-, 128-, or 256-bit WEP Encryption (depending on the capability of your client wireless card) for IP trafﬁc on your LAN.

You select a single key for encryption of outbound trafﬁc. The WEP-enabled client must have an identical key of the same length, in the identical slot (1 – 4) as the Gateway, in order to successfully receive and decr ypt the trafﬁc. Similarly, the client also has a ‘default’ key that it uses to encrypt its transmissions. In order for the Gateway to receive the client’s data, it must likewise have the identical key of the same length, in the same slot. For simplicity, a Gateway and its clients need only enter, share, and use the ﬁrst key.

Configure

Click the

Click the Alert icon, and then the

Submit

button. The Alert icon appears.

Save and Restart

link.

Advanced

If you click the

Advanced

link, the advanced 802.11 Wireless Settings page appears.

Note: This page displays different options depending on which form of Privacy or other

Configure

options you have enabled.

You can then conﬁgure:

Operating Mode: The pull-down menu allows you to select and lock the Gateway into the wireless transmission mode you want. For compatibility with clients using 802.11b (up to 11 Mbps transmission) and 802.11g (up to 20+ Mbps), select Normal (802.11b + g). To limit your wireless LAN to one mode or the other, select 802.11b Only, or 802.11g Only.

☛ NOTE:

If you choose to limit the operating mode to 802.11b or 802.11g only, clients using the mode you excluded will not be able to connect.

Default Channel: on which the network will broadcast. This is a frequency range within the

2.4Ghz band. Channel selection depends on government regulated radio frequencies that vary from region to region. The widest range available is from 1 to 14. However, in North America only 1 to 11 may be selected. Europe, France, Spain and Japan will differ. Channel selection can have a signiﬁcant impact on performance, depending on other wireless activity close to this Gateway. Channel selection is not necessary at the client computers; the clients will scan the available channels seeking access points using the same SSID as the client.

AutoChannel Setting: For 802.11G models, AutoChannel is a feature that allows the Netopia Gateway to determine the best channel to broadcast automatically.

Three settings are available from the pull-down menu: Off-Use default, At Startup, and Continuous.

• Off-Use default is the default setting; the Netopia Gateway will use the conﬁgured

default channel selected from the previous pull-down menu.

• At Startup causes the Netopia Gateway at startup to brieﬂy initialize on the default

channel, then perform a full two- to three-second scan, and switch to the best channel it can ﬁnd, remaining on that channel until the next reboot.

• Continuous per forms the at-star tup scan, and will continuously monitor the current

channel for any other Access Point beacons. If an Access Point beacon is detected on the same channel, the Netopia Gateway will initiate a three- to four-minute scan of the channels, locate a better one, and switch. Once it has switched, it will remain on this channel for at least 30 minutes before switching again if another Access Point is detected.

Enable Closed System Mode: If enabled, Closed System Mode hides the wireless network from the scanning features of wireless client computers. Unless both the wireless clients and the Gateway share the same SSID in Closed System mode, the Gateway’s wireless LAN will not appear as an available network when scanned for by wireless-enabled computers. Members of the Closed System WLAN must log onto the Gateway’s wireless network with the identical SSID as that conﬁgured in the router.

Closed System mode is an ideal way to increase wireless security and to prevent casual detection by unwanted neighbors, ofﬁce users, or malicious users such as hackers.

If you do not enable Closed System Mode, it is more convenient, but potentially less secure, for clients to access your WLAN by scanning available access points. You must decide based on your own network requirements.

About Closed System Mode

Enabling Closed System Mode on your wireless Gateway provides another level of security, since your wireless LAN will no longer appear as an available access point to client PCs that are casually scanning for one.

Your own wireless network clients, however, must log into the wireless LAN by using the exact SSID of the Netopia Gateway.

In addition, if you have enabled WEP encryption on the Netopia Gateway, your network clients must also have WEP encryption enabled, and must have the same WEP encryption key as the Netopia Gateway.

Once the Netopia Gateway is located by a client computer, by setting the client to a matching SSID, the client can connect immediately if WEP is not enabled. If WEP is enabled then the client must also have WEP enabled and a matching WEP key.

Wireless client cards from dif ferent manufacturers and different operating systems accomplish connecting to a wireless LAN and enabling WEP in a variety of ways. Consult the documentation for your particular wireless card and/or operating system.

☛ NOTE:

While clients may also have a passphrase feature, these are vendor-speciﬁc and may not necessarily create the same keys. You can passphrase generate a set of keys on one, and manually enter them on the other to get around this.

Configure

Block Wireless Bridging: Check the checkbox to block wireless clients from communicating with other wireless clients on the LAN side of the Gateway.

• WEP - Manual allows you to enter your own encr yption keys manually. This is a difﬁcult

process, but only needs to be done once. Avoid the temptation to enter all the same characters.

Encryption Key Size #1 – #4: Selects the length of each encryption key. The longer the key, the stronger the encryption and the more dif ﬁcult it is to break the encryption.

Encryption Key #1 – #4: The encryption keys. You enter keys using hexadecimal digits. For 40/64bit encryption, you need ten digits; 26 digits for 128bit, and 58 digits for 256bit WEP. Hexadecimal characters are 0 – 9, and a – f.

Examples:

• 40bit: 02468ACE02

• 128bit: 0123456789ABCDEF0123456789

• 256bit: 592CA140F0A238B0C61AE162F592CA140F0A238B0C61AE162F21A09C

Use WEP encryption key (1 – 4) #: Speciﬁes which key the Gateway will use to encrypt transmitted trafﬁc. The default is key #1.

You disable the wireless LAN by unchecking the Enable Wireless checkbox, clicking the

Submit

WPA Version Allowed

If you select either WPA-802.1x or WPA-PSK as your privacy setting, the WPA Version Allowed pull-down menu appears to allow you to select the WPA version(s) that will be

required for client connections. Choices are:

button, followed by the

Save and Restart

link.

• WPA Version 1 and 2, for maximum interoperability,

• WPA Version 1 Only, for backward compatibility,

• WPA Version 2 Only, for maximum security.

All clients must support the version(s) selected in order to successfully connect.

Configure

Multiple SSIDs

The Multiple Wireless SSIDs feature allows you to add additional network identiﬁers (SSIDs or Network Names) for your wireless network.

To enable Multiple Wireless SSIDs, click the

When the Multiple Wireless SSIDs screen appears, check the Enable SSID checkbox for each SSID you want to enable.

The screen expands to allow you to name each additional Wireless ID, and specify a Privacy mode for each one.

Multiple SSIDs

link.

Privacy modes available from the pull-down menu for the multiple SSIDs are: WPA-PSK, WPA-802.1x, or Off-No Privacy. WEP can also be selected on the additional SSIDs as

long as it is not used on the primary SSID. WEP can only be used on one SSID, so any others will not have WEP available.

These additional Wireless IDs are “Closed System Mode” Wireless IDs that will not be shown by a client scan, and therefore must be manually conﬁgured at the client. In addition, wireless bridging between clients is disabled for all members of these additional network IDs.

Click the

After your ﬁrst entry, the Alert icon will appear in the upper right corner of your screen. When you are ﬁnished adding SSIDs, click the Alert icon, and Save your changes and restart the Gateway.

Submit

button.

Wireless MAC Authorization

Wireless MAC Authorization allows you to specify which client PCs are allowed to join

the wireless LAN by speciﬁc hardware address. Once it is enabled, only entered MAC addresses that have been set to Allow will be accepted onto the wireless LAN. All unlisted addresses will be blocked, in addition to the listed addresses with Allow disabled.

Configure

To enable Wireless MAC Authentication, click the

When the Wireless MAC Authentication screen appears, check the Enable Wireless MAC Authorization checkbox:

The screen expands as follows:

MAC Authorization

link.

Click the

Add

button. The Authorized Wireless MAC Address Entry screen appears.

Enter the MAC (hardware) address of the client PC you want to authorize for access to your wireless LAN. The Allow Access? checkbox is enabled by default. Unchecking this checkbox speciﬁcally denies access from this MAC address. Click the

Submit

button.

☛ Note:

When MAC Authorization is enabled, all wireless clients are blocked until their MAC addresses are added to the Authorized list.

Your entry will be added to a list of up to 32 authorized addresses as shown:

You can continue to buttons.

After your ﬁrst entry, the Alert icon will appear in the upper right corner of your screen. When you are ﬁnished adding addresses to the list, click the Aler t icon, and Save your changes and restart the Gateway.

Add, Edit

, or

Delete

addresses to the list by clicking the respective

Configure

Use RADIUS Server

RADIUS servers allow external authentication of users by means of a remote authentication database. The remote authentication database is maintained by a Remote Authentication Dial-In User Service (RADIUS) server. In conjunction with Wireless User Authentication, you can use a RADIUS server database to authenticate users seeking access to the wireless services, as well as the authorized user list maintained locally within the Gateway.

If you click the information.

RADIUS

link, the screen expands to allow you to enter your RADIUS server

• RADIUS Server Addr/Name: The default RADIUS ser ver name or IP address that you

want to use.

• RADIUS Server Secret: The RADIUS secret key used by this server. The shared secret

should have the same characteristics as a normal password.

• RADIUS Server Port: The por t on which the RADIUS server is listening, typically, the

default 1812.

Click the

You can also conﬁgure alternate RADIUS servers from the Advanced Network Conﬁguration page, by clicking the

Submit

button.

Advanced

link.

The Advanced Network Conﬁguration page appears.

You access the RADIUS Server conﬁguration screen from the Advanced Network Conﬁguration web page, by clicking the

RADIUS Server

link.

Link: WAN

Configure

When you click the depending on the WAN interface of your Netopia Gateway.

WAN IP Interfaces: Your IP inter faces are listed.

WAN

link, the WAN IP conﬁguration page appears. This page varies

PPP over Ethernet interface

Click the

PPP over Ethernet

link to conﬁgure it.

The WAN IP Interface page appears.

Enable Interface: You can disable the interface by unchecking the checkbox. However,

doing so will disable all ability for your LAN users to connect to the WAN using the Gateway.

Address Mapping (NAT): Speciﬁes whether you want the Gateway to use network address translation (NAT) when communicating with remote routers. NAT lets you conceal details of your network from remote routers. By default, address mapping is enabled.

Restrictions: This setting determines the types of trafﬁc the Gateway accepts from the WAN. Admin Disabled means that Gateway trafﬁc is accepted but administrative commands are ignored. None means that all trafﬁc is accepted. When PPP is enabled, Admin

Disabled is the default.

ISP Username: This is the username used to authenticate your Gateway with the Service

Provider's network. This value is given to you by your Service Provider.

ISP Password: This is the password used to authenticate your Gateway with the Service Provider's network. This value is given to you by your Service Provider.

Connection Type: The pulldown menu allows you to choose to have either an uninterrupted connection or an as-needed connection.

Configure

• Always On: This setting provides convenience, but it leaves your network permanently connected to the Internet.

• Instant On furnishes almost all the beneﬁts of an Always On connection, but has additional security beneﬁts:

- Your network cannot be attacked when it is not connected.

- Your network may change address with each connection, making it more difﬁcult to attack.

Timeout: (only appears if Instant-On Connection Type is selected) Speciﬁes the time in seconds before disconnect if there is no trafﬁc over the Internet link.

Advanced:

If you click the appears.

Advanced

link, the Advanced WAN IP Interface conﬁguration page

Local Address: If this value is 0.0.0.0,

the Gateway will acquire its IP address from your ISP. Otherwise this address is assigned to the virtual PPP interface.

Peer Address: Address of the server on the Service Provider side of the ppp link. This peer will attempt to negotiate the local IP address if IP Address = 0.0.0.0. If the remote peer does not accept the IP address, the link will not come up.

RIP Receive Mode: Routing Information Protocol (RIP) is needed if there are IP routers on other segments of your Ethernet network that the Netopia Gateway needs to recognize. Set to Off, Netopia Firmware Version 7.6.1 will accept information from either RIP-1 or RIP-2 routers. With Receive RIP Mode set to RIP-1, the Netopia Gateway will accept routing information provided by RIP packets from other routers that use the same subnet mask.

Set to RIP-2, Netopia Firmware Version 7.6.1 will accept routing information provided by RIP packets from other routers that use different subnet masks.

From the pull-down menu, choose Off, RIP-1, RIP-2, RIP-1 compatibility, or RIP-2 with

MD5.

RIP Receive MD5 Key: (Only appears if RIP-2 with MD5 RIP Receive Mode is selected)

The purpose of MD5 authentication is to provide an additional level of conﬁdence that a RIP packet received was generated by a reliable source. In other words, MD5 authentication provides an enhanced level of security that information that your PC receives does not originate from a malicious source posing as par t of your network. This ﬁeld llows you to enter an MD5 encryption key of from 1 – 16 ASCII characters for authenticating RIP receipts.

LCP Settings:

Authentication: Select Off, PAP and/or CHAP, PAP only, or CHAP only from the pull-

down menu. The settings for port authentication on the Gateway must match the authentication expected by the remote system. The username and passwords are available on the WAN IP Interfaces page.

MRU: Speciﬁes the Maximum Receive Unit for the PPP Interface.

Magic Number: Enables or disables LCP magic number negotiation.

Protocol Compression: Speciﬁes whether you want the Gateway to compress the PPP Protocol ﬁeld when it transmits datagrams over the PPP link.

LCP Echo Requests: Speciﬁes whether you want your Gateway to send LCP echo requests. You should turn off LCP echoing if you do not want the Gateway to drop a PPP link to a nonresponsive peer.

Max Failures: Speciﬁes the maximum number of Conﬁgure-NAK messages the PPP module can send without having sent a Conﬁgure-ACK message.

Max Conﬁgures: Speciﬁes the maximum number of unacknowledged conﬁguration requests that your Gateway will send.

Max Terminates: Speciﬁes the maximum number of unacknowledged termination requests that your Gateway will send before terminating the PPP link.

Configure

Restart Timer: The number of seconds the Gateway should wait before retransmitting a conﬁguration or termination request.

Click the

Submit

button when you are ﬁnished.

Ethernet WAN interface

Click the The WAN IP Interface page appears.

Ethernet WAN

link to conﬁgure it.

Enable Interface: You can disable the interface by unchecking the checkbox. However, doing so will disable all ability for your LAN users to connect to the WAN using the Gateway.

Obtain IP Address Automatically: Your ser vice provider may tell you that the WAN IP Address for your Gateway is static. In this case, disable this checkbox and enter the IP Address and IP Netmask from your Ser vice Provider in the appropriate ﬁelds.

IP Address: This is the IP Address from your Service Provider when using static IP addressing.

IP Netmask: This is the Netmask from your Service Provider when using static IP addressing.

Disabled is the default.

Advanced:

If you click the appears.

routers. With Receive RIP Mode set to RIP-1, the Netopia Gateway will accept routing information provided by RIP packets from other routers that use the same subnet mask. Set to RIP-2, Netopia Firmware Version 7.6.1 will accept routing information provided by RIP packets from other routers that use different subnet masks.

From the pull-down menu, choose Off, RIP-1, RIP-2, RIP-1 compatibility, or RIP-2 with

MD5.

Enable Proxy ARP: Checking the checkbox will enable the Gateway to respond when it

receives an Address Resolution Protocol message for devices behind it.

Advanced

link the Advanced WAN IP Interface conﬁguration page

RIP Receive Mode: Routing Information Pro-

tocol (RIP) is needed if there are IP routers on other segments of your Ethernet network that the Netopia Gateway needs to recognize. Set to Off, Netopia Firmware Version 7.6.1 will accept information from either RIP-1 or RIP-2

Configure

IP Gateway

Enable Gateway Option: You can conﬁgure the Gateway to send packets to a default

gateway if it does not know how to reach the destination host. Interface Type: If you have PPPoE enabled, you can specify that packets destined for

unknown hosts will be sent to the gateway being used by the remote PPP peer. If you select ip-address, you must enter the IP address of a host on a local or remote network to receive the trafﬁc.

Default Gateway: The IP Address of the default gateway.

Other WAN Options

PPPoE: You can enable or disable PPPoE. This link also allows conﬁguration of NAT,

admin restrictions, PPPoE username/password, and connection type. ATM Circuits: You can conﬁgure the ATM circuits and the number of Sessions. The IP

Interface(s) should be reconﬁgured after making changes here.

Available Encapsulation types: Available Multiplexing types:

PPP over Ethernet (PPPoE) LLC/SNAP

PPP over ATM (PPPoA) VC muxed

RFC-1483 Bridged Ethernet

RFC-1483 Routed IP

None

Netopia Firmware Version 7 supports VPI/VCI autodetection by default. If VPI/VCI autodetection is enabled, the ATM Circuits page displays VPI/VCI = 0. If you conﬁgure a new

ATM VPI/VCI pair, upon saving and restarting, autodetection is disabled and only the new VPI/VCI pair conﬁguration will be enabled.

VPI/VCI Autodetection consists of eight static VPI/VCI pair conﬁgurations. These are 0/ 35, 8/35, 0/32, 8/32, 1/35, 1/1, 1/32, 2/32. These eight VPI/VCI pairs will be created if the Gateway is conﬁgured for autodetection. the Gateway does not establish a circuit using any of these preconﬁgured VPI/VCI pairs, then you can manually enter a VPI/VCI pair in the ATM Circuits page.

ATM Trafﬁc Shaping: You can prioritize delay-sensitive data by conﬁguring the Quality of Service (QoS) characteristics of the virtual circuit. Click the link.

You can choose UBR (Unspeciﬁed Bit Rate), CBR (Constant Bit Rate), or VBR (Variable Bit Rate) from the pull-down menu and set the Peak Cell Rate (PCR) in the editable ﬁeld.

UBR (Unspeciﬁed Bit Rate) guarantees no minimum transmission rate. Cells are transmitted on a “best effort” basis. However, there is a cap on the maximum transmission rate for UBR VCs. In a practical situation:

• UBR VCs should be transmitted at a priority lower than CBR.

• Bandwidth should be shared equally among UBR VCs. UBR applications are non-real-time trafﬁc such as IP data trafﬁc. CBR (Constant Bit Rate) guarantees a certain transmission rate (although the appli-

cation may underutilize this bandwidth). A Peak Cell Rate (PCR) characterizes CBR. CBR is most suited for real time applications such as real time voice / video, although it can be used for other applications.

VBR (Variable Bit Rate) This class is characterized by:

• a Peak Cell Rate (PCR), which is a temporary burst, not a sustained rate, and

• a Sustained Cell Rate (SCR),

• a Burst Tolerance (BT), speciﬁed in terms of Maximum Burst Size (MBS). The MBS is the maximum number of cells that can be transmitted at the peak cell rate and should be less than, or equal to the Peak Cell Rate, which should be less than, or equal to the line rate.

ATM Trafﬁc Shaping

Configure

VBR has two sub-classes: a. VBR non-real-time (VBR-nrt): Typical applications are non-real-time trafﬁc, such as IP

data trafﬁc. This class yields a fair amount of Cell Delay Variation (CDV). b. VBR real time (VBR-rt): Typical applications are real-time trafﬁc, such as compressed

voice over IP and video conferencing. This class transmits cells with a more tightly bounded Cell Delay Variation. The applications follow CBR.

☛ Note:

The difference between VBR-rt and VBR-nr t is the tolerated Cell Delay Variation range and the provisioned Maximum Burst Size.

Class PCR SCR MBS Transmit Priority Comments

UBR X N/A N/A Low PCR is a cap

CBR X N/A N/A High PCR is a guaranteed rate

VBR X X X High PCR > SCR.

SCR is a guaranteed rate. PCR is a cap.

Link: Advanced

Selected Advanced options are discussed in the pages that follow. Many are self-explanatory or are dictated by your service provider.

The following are links under Conﬁgure -> Advanced:

Configure

Link: IP Static Routes

A static route identiﬁes a manually conﬁgured pathway to a remote network. Unlike dynamic routes, which are acquired and conﬁrmed periodically from other routers, static routes do not time out. Consequently, static routes are useful when working with PPP, since an intermittent PPP link may make maintenance of dynamic routes problematic.

When you click the

You can conﬁgure as many as 32 static IP routes for the Gateway. To add a static route, click the

The IP Static Route Entry page appears.

Add

Static Routes

button.

link, the IP Static Routes page appears.

• Destination Network: Enter the IP address of the static route. It may not be 0.0.0.0.

• Netmask: Enter the subnet mask for the IP network at the other end of the static route.

The subnet mask associated with the destination network must represent the same network class (A, B, or C) or a lower class (such as a class C subnet mask or class B network number) to be valid.

• Interface Type: Choose PPP (vcc1) – depending on the interface; typically vcc1 for

DSL – or IP Address from the pull-down menu to specify whether the static route is accessible through PPP or IP address.

• Gateway: Enter the IP address of the gateway for the static route. The default gateway

must be located on a network connected to your Netopia Gateway conﬁgured interface.

• Metric: Speciﬁes the hop count for the static route. Enter a number from 1 to 15 to indi-

cate the number of routes (actual or best guess) a packet must traverse to reach the remote network. Some metric or a value of 1 will be used to indicate:

• The remote network is one router away and the static route is the best way to reach it.

• The remote network is more than one router away but the static route should not be replaced by a dynamic route, even if the dynamic route is more ef ﬁcient.

• RIP Advertise: From the pull-down menu, choose how the static route should be adver-

tised via RIP:

• Split Horizon: Do not advertise route if the gateway is on the same subnet.

• Always: Advertise route in all RIP messages.

• Never: Do not advertise route.

Click the Save Changes page, when you are ﬁnished.

Once you save your changes, you will be returned to the IP Static Routes entr y screen.

Submit

button. The Alert icon will appear, so that you can switch to the

• You can continue to Add, Edit, or Delete Static Routes from this screen.

When you are ﬁnished, click the Alert icon , switch to the Save Changes page, and

click the

Save Changes

link.

Configure

Link: IP Static ARP

Your Gateway maintains a dynamic Address Resolution Protocol (ARP) table to map IP addresses to Ethernet (MAC) addresses. It populates this ARP table dynamically, by retrieving IP address/MAC address pairs only when it needs them. Optionally, you can deﬁne static ARP entries to map IP addresses to their corresponding Ethernet MAC addresses. Unlike dynamic ARP table entries, static ARP table entries do not time out. The IP address cannot be 0.0.0.0. The Ethernet MAC address entr y is in nn-nn-nn-nn-nn-nn (hexadecimal) format.

Link: Pinholes

Pinholes allow you to transparently route selected types of network trafﬁc, such as FTP requests or HTTP (Web) connections, to a speciﬁc host behind the Gateway. Creating a pinhole allows access trafﬁc originating from a remote connection (WAN) to be sent to the internal computer (LAN) that is speciﬁed in the Pinhole page.

Pinholes are common for applications like multiplayer online games. Refer to software manufacturer application documentation for speciﬁc trafﬁc types and port numbers.

Conﬁgure Speciﬁc Pinholes. Planning for Your Pinholes. Determine if any

of the service applications that you want to provide on your LAN stations use TCP or UDP protocols. If an application does, then you must conﬁgure a pinhole to implement por t forwarding. This is accessed from the Advanced -> Pinholes page.

Example: A LAN Requiring Three Pinholes . The procedure on the following

pages describes how you set up your NAT-enabled Netopia Gateway to support three separate applications. This requires passing three kinds of speciﬁc IP trafﬁc through to your LAN.

Application 1

and would like users on the Internet to have access to it. With NAT “On”, the only externally visible IP address on your network is the Gateway’s WAN IP (supplied by your Service Provider). All trafﬁc intended for that LAN Web server must be directed to that IP address.

Application 2

email for all of the LAN users.

Application 3

want this speciﬁc LAN station to be dedicated to games.

A sample table to plan the desired pinholes is:

For this example, Internet protocols TCP and UDP must be passed through the NAT security feature and the Gateway’s embedded Web (HTTP) port must be re-assigned by conﬁguring new settings on the Internal Servers page.

: You have a Web server located on your LAN behind your Netopia Gateway

: You want one of your LAN stations to act as the “central repository” for all

: One of your LAN stations is specially conﬁgured for game applications. You

WAN Trafﬁc Type Protocol Pinhole Name

Web TCP my-webserver 192.168.1.1 Email TCP my-mailserver 192.168.1.2 Games UDP my-games 192.168.1.3

LAN Internal IP

Address

☛ TIPS for making Pinhole Entries:

1. If the port forwarding feature is required for Web services, ensure that the embedded Web server’s port number is re-assigned PRIOR to any Pinhole data entry.

2. Enter data for one Pinhole at a time.

3. Use a unique name for each Pinhole. If you choose a duplicate name, it will overwrite the previous information without warning.

Configure

A diagram of this LAN example is:

Internet

WAN

Ethernet

Interface

210.219.41.20

Gateway

LAN Ethernet Interface

my-webserver

192.168.1.1

NAT

Embedded

NAT Pinholes

Web Server

210.219.41.20:8100

You can also use the LAN-side address of the Gateway, 192.168.1.x:8100 to access the web and 192.168.1.x:23 to access the telnet server.

my-mailserver

192.168.1.2

my-games

192.168.1.3

Pinhole Conﬁguration Procedure. Use the following steps:

1. From the

Servers

Since Port Forwarding is required for this example, the Netopia embedded Web server is conﬁgured ﬁrst.

Conﬁgure

link.

toolbar button ->

Advanced

link, select the

Internal

☛ NOTE:

The two text boxes, Web (HTTP) Server Port and Telnet Server Port, on this page refer to the port numbers of the Netopia Gateway’s embedded admin- istration ports.

To pass Web trafﬁc through to your LAN station(s), select a Web (HTTP) Port number that is greater than 1024. In this example, you choose 8100.

2. Type

8100

in the Web (HTTP) Server Port text box.

3. Click the

4. Click

Advanced

Submit

button.

. Select the

Pinholes

link to go to the Pinhole page.

Configure

5. Click

6. Click on the

Add

. Type your speciﬁc data into the Pinhole Entries table of this

page. Click

Submit

Add or Edit more Pinholes

link. Click the

next Pinhole. Type the speciﬁc data for the second Pinhole.

Add

button. Add the

7. Click on the

next Pinhole. Type the speciﬁc data for the third Pinhole.

Add or Edit more Pinholes

link. Click the

☛ NOTE:

Note the following parameters for the “my-games” Pinhole:

1. The Protocol ID is UDP.

2. The external port is speciﬁed as a range.

3. The Internal port is speciﬁed as the lower range entry.

Add

button. Add the

8. Click on the

sure they are correct.

9. Click the

Add or Edit more Pinholes

Alert

icon.

link. Review your entries to be

Configure

10. Click the

task and ensure that the parameters are properly saved.

Save and Restart

link to complete the entire Pinhole creation

☛ NOTE:

REMEMBER: When you have re-assigned the port address for the embedded Web server, you can still access this facility. Use the Gateway’s WAN address plus the new port number. In this example it would be <WAN Gateway address>:<new port number> or, in this case,

210.219.41.20:8100

You can also use the LAN-side address of the Gateway, 192.168.1.x:8100 to access the web and 192.168.1.x:23 to access the telnet server.

Link: IPMaps

IPMaps supports one-to-one Network Address Translation (NAT) for IP addresses assigned to servers, hosts, or speciﬁc computers on the LAN side of the Netopia Gateway.

A single static or dynamic (DHCP) WAN IP address must be assigned to support other devices on the LAN. These devices utilize Netopia’s default NAT/PAT capabilities.

Conﬁgure the IPMaps Feature

FAQs for the IPMaps Feature

Before conﬁguring an example of an IPMaps-enabled network, review these frequently asked questions.

What are IPMaps and how are they used? The IPMaps feature allows multi-

ple static WAN IP addresses to be assigned to the Netopia Gateway.

Static WAN IP addresses are used to support speciﬁc services, like a web ser ver, mail server, or DNS server. This is accomplished by mapping a separate static WAN IP address to a speciﬁc internal LAN IP address. All trafﬁc arriving at the Gateway intended for the static IP address is transferred to the internal device. All outbound trafﬁc from the internal device appears to originate from the static IP address.

Locally hosted servers are supported by a public IP address while LAN users behind the NAT-enabled IP address are protected.

IPMaps is compatible with the use of NAT, with either a statically assigned IP address or DHCP/PPP served IP address for the NAT table.

What types of servers are supported by IPMaps? IPMaps allows a Netopia

Gateway to support servers behind the Gateway, for example, web, mail, FTP, or DNS servers. VPN servers are not supported at this time.

Can I use IPMaps with my PPPoE or PPPoA connection? Yes. IPMaps

can be assigned to the WAN interface provided they are on the same subnet. Service providers will need to ensure proper routing to all IP addresses assigned to your WAN interface.

Will IPMaps allow IP addresses from different subnets to be assigned to my Gateway?

same subnet.

WAN IP addresses from different subnets are not supported.

IPMap will support statically assigned WAN IP addresses from the

Configure

IPMaps Block Diagram

The following diagram shows the IPMaps principle in conjunction with existing Netopia NAT operations:

Netopia Gateway

Static IP Addresses for IPMaps Applications

143.137.50.37

143.137.50.36

143.137.50.35 Static IP Addresses or DHCP/PPP Served IP Address for Netopia’s default NAT/PAT Capabilities

WAN Interface LAN Interface

IPMaps: One-to-One Multiple Address Mapping

NAT/PAT Table

143.137.50.37

143.137.50.36

143.137.50.35

LAN stations with WAN IP trafﬁc forwarded by Netopia’s IPMaps

LAN stations with WAN IP trafﬁc forwarded by Netopia’s NAT function.

...

192.168.1.1

192.168.1.2

192.168.1.3

...

192.168.1.n

192.168.1.1

192.168.1.2

192.168.1.3

. . .

192.168.1.n

Link: Default Server

This feature allows you to:

• Direct your Gateway to forward all externally initiated IP trafﬁc (TCP and UDP protocols

only) to a default host on the LAN.

• Enable it for cer tain situations:

– Where you cannot anticipate what port number or packet protocol an in-bound application might use. For example, some network games select arbitrary port numbers when a connection is opened.

– When you want all unsolicited trafﬁc to go to a speciﬁc LAN host.

• Conﬁgure for IP Passthrough.

Conﬁgure a Default Server. This feature allows you to direct unsolicited or non-

speciﬁc trafﬁc to a designated LAN station. With NAT “On” in the Gateway, these packets normally would be discarded.

For instance, this could be application trafﬁc where you don’t know (in advance) the port or protocol that will be used. Some game applications ﬁt this proﬁle.

Use the following steps to setup a NAT default server to receive this information:

1. Select the

Server

2. From the pull-down menu, select

The NAT Server IP Address ﬁeld appears.

3. Determine the IP address of the LAN computer you have chosen to

Conﬁgure

link.

toolbar button, then

Default-Server

Advanced

, then the

Default

receive the unexpected or unknown trafﬁc.

Configure

Enter this address in the NAT Server IP Address ﬁeld.

4. Click the

5. Click the

6. Click the

Submit Alert

button.

Save and Restart

link to conﬁrm.

Typical Network Diagram. A typical network using the NAT Default Server looks like

this:

Internet

Gateway

LAN STN #3

192.168.1.3

WAN Ethernet

Interface

210.219.41.20

LAN

Ethernet

Interface

Embedded Web Server

210.219.41.20 (Port 80 default)

NAT

NAT Default Server

LAN STN #2

192.168.1.2

NAT protected

NAT Default Server

192.168.1.1

You can also use the LAN-side address of the Gateway, 192.168.1.x to access the web and telnet server.

NAT Combination Application. Netopia’s NAT security feature allows you to con-

ﬁgure a sophisticated LAN layout that uses both the Pinhole and Default Server capabilities.

With this topology, you conﬁgure the embedded administration ports as a ﬁrst task, followed by the Pinholes and, ﬁnally, the NAT Default Server.

When using both NAT pinholes and NAT Default Server the Gateway works with the following rules (in sequence) to for ward trafﬁc from the Internet to the LAN:

1. If the packet is a response to an existing connection created by outbound

trafﬁc from a LAN PC, forward to that station.

2. If not, check for a match with a pinhole conﬁguration and, if one is found,

forward the packet according to the pinhole rule.

3. If there’s no pinhole, the packet is forwarded to the Default Server.

IP-Passthrough. Your Gateway offers an IP passthrough feature. The IP passthrough

feature allows a single PC on the LAN to have the Gateway’s public address assigned to it. It also provides PAT (NAPT) via the same public IP address for all other hosts on the private LAN subnet. Using IP passthrough:

• The public WAN IP is used to provide IP address translation for private LAN computers.

• The public WAN IP is assigned and reused on a LAN computer.

• DHCP address serving can automatically ser ve the WAN IP address to a LAN computer.

When DHCP is used for addressing the designated passthrough PC, the acquired or conﬁgured WAN address is passed to DHCP, which will dynamically conﬁgure a singleservable-address subnet, and reserve the address for the conﬁgured MAC address. This dynamic subnet conﬁguration is based on the local and remote WAN address and subnet mask. If the WAN interface does not have a suitable subnet mask that is usable, for example when using PPP or PPPoE, the DHCP subnet conﬁguration will default to a class C subnet mask.

Configure

• If you want to manually assign the WAN address to a LAN PC, do not check the DHCP

Enable checkbox.

• If you check the DHCP Enable checkbox, the screen expands.

The Host Hardware Address ﬁeld displays. Here you enter the MAC address of the designated IP-Passthrough computer.

• If this MAC address is not all zeroes, then it will use DHCP to set the LAN host's

address to the (conﬁgured or acquired) WAN IP address. The MAC address must be six colon-delimited or dash-delimited sets of hex digits ('0' –

'FF').

• If you leave the MAC address as zeros then the ﬁrst DHCP client will be assigned the

WAN address.

Once conﬁgured, the passthrough host's DHCP leases will be shor tened to two minutes. This allows for timely updates of the host's IP address, which will be a private IP address before the WAN connection is established. After the WAN connection is established and has an address, the passthrough host can renew its DHCP address binding to acquire the WAN IP address.

A restriction. Since both the Gateway and the passthrough host will use the same IP

address, new sessions that conﬂict with existing sessions will be rejected by the Gateway. For example, suppose you are a teleworker using an IPSec tunnel from the Gateway and from the passthrough host. Both tunnels go to the same remote endpoint, such as the VPN access concentrator at your employer’s ofﬁce. In this case, the ﬁrst one to start the IPSec trafﬁc will be allowed; the second one – since, from the WAN, it's indistinguishable – will fail.

Link: Differentiated Services

When you click the tion screen appears.

Netopia Firmware Version 7.6.1 offers Dif ferentiated Services (Diffser v) enhancements. These enhancements allow your Gateway to make Quality of Service (QoS) decisions about what path Internet trafﬁc, such as Voice over IP (VoIP), should travel across your network. For example, you may want streaming video conferencing to use high quality, but more restrictive, connections, or, you might want e-mail to use less restrictive, but less reliable, connections.

Differentiated Services

link, the Differentiated Services conﬁgura-

• To enable Differentiated Ser vices, check the Enable checkbox.

• Enter a value from 60 to 100 (percent) in the Low-High Priority Ratio ﬁeld. The

default is 92. Differentiated Services uses the low-to-high priority queue ratio to regulate traf ﬁc ﬂow.

For example, to provide the least possible latency and highest possible throughput for high priority trafﬁc, you could set the ratio to 100(%). This would cause the gateway to forward low priority data only after the high priority queue is completely empty. In practice, you should set it to something less than 100%, since the low priority trafﬁc might have to wait too long to be passed, and consequently be subject to time-outs.

Click the

Submit

button.

Configure

You can then deﬁne Custom Flows. If your applications do not provide Quality of Service (QoS) control, Custom Flows allows you to deﬁne streams for some protocols, por t ranges, and between speciﬁc end point addresses.

• To deﬁne a custom ﬂow, click the

The Custom Flow Entry screen appears.

• Inside IP Address/Netmask – For outbound ﬂows, specify an IP address/netmask on your LAN. For inbound ﬂows, this setting is ignored. This setting marks packets from this LAN IP host/network based on the address and netmask information. For outbound ﬂows, the Inside IP Address/Netmask is the source address. If you enter a zero IP address (0.0.0.0), the IP address/netmask ﬁelds will be ignored.

• Outside IP Address/Netmask – If you want trafﬁc destined for and originating from a certain WAN IP address to be controlled, enter the IP address and subnet mask here. If you leave the default all-zeroes, the outside address check is ignored.

For outbound ﬂows, the outside address is the destination IP address for trafﬁc; for inbound packets, the outside address is the source IP address.

Note:

When setting the Inside/Outside IP Address/Netmask settings, note that a netmask value can be used to conﬁgure for a network rather than a single IP address.

Add

button.

• Name – Enter a name in this ﬁeld to label the ﬂow.

• Protocol – Select the protocol from the pull-down menu: TCP (default), UDP, ICMP, or Other. “Other” is appropriate for setting up ﬂows on protocols with non-standard port deﬁnitions. IPSEC and PPTP are common examples.

• Numerical Protocol – If you select “Other” protocol, this ﬁeld appears for you to provide its actual protocol number, with a range of 0 – 255.

• Direction – Choose Outbound (default), Inbound, or Both from the pull-down menu.

• Start Port – For TCP or UDP protocols, you can optionally specify a range of ports. Enter the starting por t here.

• End Port – Enter the ending port here.

• Quality of Service (QoS) – This is the Quality of Service setting for the ﬂow, based on the TOS bit information. Select Expedite, Assure, or Of f (default) from the pull-down menu. The following table outlines the TOS bit settings and behavior:

QoS Setting TOS Bit Value Behavior

Off TOS=000 This custom ﬂow is disabled. You can activate

it by selecting one of the two settings below. This setting allows you to pre-deﬁne ﬂows without actually activating them.

Assure TOS=001 Use normal queuing and throughput rules, but

do not drop packets if possible. Appropriate for applications with no guaranteed delivery mechanism.

Expedite TOS=101 Use minimum delay. Appropriate for VoIP and

video applications.

Configure

Link: DNS

Your Service Provider may maintain a Domain Name server. If you have the information for the DNS servers, enter it on the DNS page. If your Gateway is conﬁgured to use DHCP to obtain its WAN IP address, the DNS information is automatically obtained from that same DHCP Server.

Link: DHCP Server

Your Gateway can provide network conﬁguration information to computers on your LAN, using the Dynamic Host Conﬁguration Protocol (DHCP).

If you already have a DHCP server on your LAN, you should turn this service off.

If you want the Gateway to provide this service, select Server from the pull-down menu, then conﬁgure the range of IP addresses that you would like the Gateway to hand out to your computers.

Server Mode

You can also specify the length of time the computers can use the conﬁguration information; DHCP calls this period the lease time.

Select Relay-agent and enter the IP address of the Service Provider's DHCP server in the Server Address ﬁeld. This address is furnished by the Service Provider.

☛ NOTE:

The relay-agent option only works when NAT is off and the Gateway is in router mode.

Configure

Link: RADIUS Server

If you click the

RADIUS

link, the RADIUS Servers screen appears.

• RADIUS Server Addr/Name: The default RADIUS ser ver name or IP address that you

want to use.

• RADIUS Server Secret: The RADIUS secret key used by this server. The shared secret

should have the same characteristics as a normal password.

• RADIUS Server Port: The por t on which the RADIUS server is listening, typically, the

default 1812.

Click the

Submit

button.

You can also conﬁgure alternate RADIUS servers from the Wireless Conﬁguration pages. See “Use RADIUS Server” on page 67 for more inormation.

Link: SNMP

When you click the

SNMP

link, the SNMP conﬁguration page appears.

100

The Simple Network Management Protocol (SNMP) lets a network administrator monitor problems on a network by retrieving settings on remote network devices. The network administrator typically runs an SNMP management station program on a local host to obtain information from an SNMP agent. In this case, the Netopia Gateway is an SNMP agent. Your Gateway supports SNMP-V1, with the exception of most sets (read-only and traps), and SNMP-V2. (For certain parts of the NPAV2TRAP.MIB – parameters under resNat- Params, resDslParams, resSecParams – set is supported.)

You enter SNMP conﬁguration information on this page. Your network administrator furnishes the SNMP parameters.

Netopia 2200 series, 3300 Series User Guide

Specifications and Main Features

Frequently Asked Questions

User Manual

Copyright

Table of Contents

What’s New in 7.6.1

CHAPTER 1 Introduction

About Netopia Documentation

Intended Audience

Documentation Conventions

General

Internal Web Interface

Command Line Interface

Organization

A Word About Example Screens

CHAPTER 2 Basic Mode Setup

Important Safety Instructions

POWER SUPPLY INSTALLATION

TELECOMMUNICATION INSTALLATION

PRODUCT VENTILATION

Wichtige Sicherheitshinweise

NETZTEIL INSTALLIEREN

INSTALLATION DER TELEKOMMUNIKATION

Setting up the Netopia Gateway

Configuring the Netopia Gateway

MiAVo VDSL and Ethernet WAN models Quickstart

PPPoE Quickstart

Set up the Netopia Pocket Gateway

Netopia Gateway Status Indicator Lights

Home Page - Basic Mode

Link: Manage My Account

Link: Status Details

Link: Enable Remote Management

Link: Expert Mode

Link: Update Firmware

Link: Factory Reset

Accessing the Expert Web Interface

CHAPTER 3 Expert Mode

Open the Web Connection

Home Page - Expert Mode

Home Page - Information

Toolbar

Navigating the Web Interface

Link: Breadcrumb Trail

Restart

Button: Restart

Link: Alert Symbol

Help

Button: Help

Configure

Link: Quickstart

Link: LAN

Wireless

Privacy

Advanced

Multiple SSIDs

Wireless MAC Authorization

Link: WAN

PPP over Ethernet interface

Ethernet WAN interface

Link: Advanced

Link: IP Static Routes

Link: IP Static ARP

Link: Pinholes

Link: IPMaps

Link: Default Server

Link: Differentiated Services

Link: DNS

Link: DHCP Server

Link: RADIUS Server

Link: SNMP