ARRIS 224742 ADSL2+ 802.11b/g Ethernet Modem User Manual Administrator s Handbook V7 7 4

ARRIS Group, Inc. ADSL2+ 802.11b/g Ethernet Modem Administrator s Handbook V7 7 4

UserManual.wiki >

224742 User Manual >

User Manual Part One

Contents

1. User Manual Part One
2. User Manual Part Two

User Manual Part One

Administrator’s Handbook Embedded Software Version 7.7.4Motorola Netopia ® 2200, 3300 and 7000 Series Gateways

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: “This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)” The word 'cryptographic' can be left out if the routines from the library being used are not cryptographic related :-). 4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: “This product includes software written by Tim Hudson (tjh@cryptsoft.com)”THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.The licence and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence.] Portions of this software are based in part on the work of the following: Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. All rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Portions of this software are based in part on the work of the following: Copyright (C) 1990, RSA Data Security, Inc. All rights reserved.<<RSA Data Security, Inc. MD5 Message-Digest Algorithm>>License to copy and use this software is granted provided that it is identified as the “RSA Data Security, Inc. MD5 Message Digest Algorithm” in all material mentioning or referencing this software or this function.License is also granted to make and use derivative works provided that such works are identified as “derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm” in all material mentioning or referencing the derived work.<<RSA Data Security, Inc. MD4 Message-Digest Algorithm>>License to copy and use this software is granted provided that it is identified as the “RSA Data Security, Inc. MD4 Message Digest Algorithm” in all material mentioning or referencing this software or this function.License is also granted to make and use derivative works provided that such works are identified as “derived from the RSA Data Security, Inc. MD4 Message-Digest Algorithm” in all material mentioning or referencing the derived work.

Administrator’s Handbook RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It is provided “as is” without express or implied warranty of any kind.These notices must be retained in any copies of any part of this documentation and/or software. Portions of this software are based in part on the work of the following: Copyright (c) 1989 Carnegie Mellon University. All rights reserved.Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by Carnegie Mellon University. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission.THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. Portions of this software are based in part on the work of the following: Copyright 2000, 2001 Shane Kerr. All rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR(S) ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

5 Table of Contents CHAPTER 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 What’s New in 7.7.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 About Motorola Netopia® Documentation . . . . . . . . . . . . . . . . 15 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 15 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Internal Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 A Word About Example Screens . . . . . . . . . . . . . . . . . . . . . . . 17 CHAPTER 2 Basic Mode Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Important Safety Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . 20 POWER SUPPLY INSTALLATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . 20TELECOMMUNICATION INSTALLATION . . . . . . . . . . . . . . . . . . . . . . 20PRODUCT VENTILATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Wichtige Sicherheitshinweise . . . . . . . . . . . . . . . . . . . . . . . . . 21 NETZTEIL INSTALLIEREN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21INSTALLATION DER TELEKOMMUNIKATION . . . . . . . . . . . . . . . . . . 21 Setting up the Motorola Netopia® Gateway . . . . . . . . . . . . . . 22 Microsoft Windows: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Macintosh MacOS 8 or higher or Mac OS X: . . . . . . . . . . . . . . . . 24 Configuring the Motorola Netopia® Gateway . . . . . . . . . . . . . 25 MiAVo VDSL and Ethernet WAN models Quickstart . . . . . . . . . . . . . . 25PPPoE Quickstart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Set up the Motorola Netopia® Pocket Gateway. . . . . . . . . . . . . . . . . . 28 Motorola Netopia® Gateway Status Indicator Lights . . . . . . . . 30 Home Page - Basic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Manage My Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Status Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Enable Remote Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Expert Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Update Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Factory Reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 CHAPTER 3 Expert Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Accessing the Expert Web Interface . . . . . . . . . . . . . . . . . . . . 39 Open the Web Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Home Page - Expert Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Administrator’s Handbook6 Home Page - Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Navigating the Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . 43 Breadcrumb Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Alert Symbol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47How to Use the Quickstart Page . . . . . . . . . . . . . . . . . . . . . . . . . 47Setup Your Gateway using a PPP Connection . . . . . . . . . . . . . . 47LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Wireless . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56About Closed System Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57WPA Version Allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Multiple SSIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59WiFi Multimedia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Wireless MAC Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Use RADIUS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65WAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67PPP over Ethernet interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Advanced: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Ethernet WAN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70WAN Ethernet and VDSL Gateways. . . . . . . . . . . . . . . . . . . . . . . 73ADSL Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78IP Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79IP Static ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Pinholes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Configure Specific Pinholes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Planning for Your Pinholes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Example: A LAN Requiring Three Pinholes . . . . . . . . . . . . . . . . . 82Pinhole Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . 84IPMaps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Configure the IPMaps Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87FAQs for the IPMaps Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87What are IPMaps and how are they used? . . . . . . . . . . . . . . . . . 87What types of servers are supported by IPMaps? . . . . . . . . . . . . 87Can I use IPMaps with my PPPoE or PPPoA connection? . . . . . 87Will IPMaps allow IP addresses from different subnets to be assigned to my Gate-way? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87IPMaps Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Default Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Configure a Default Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Typical Network Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89NAT Combination Application . . . . . . . . . . . . . . . . . . . . . . . . . . . 90IP-Passthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90A restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Differentiated Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96RADIUS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

7 SNMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98IGMP (Internet Group Management Protocol) . . . . . . . . . . . . . . . . . . 100UPnP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102LAN Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Ethernet Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Configuring for Bridge Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Ethernet Switching/Policy Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Syslog Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Log Event Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Internal Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Software Hosting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130List of Supported Games and Software . . . . . . . . . . . . . . . . . . . 131Rename a User(PC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Manual options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Automatic options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Ethernet MAC Override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Clear Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Create and Change Passwords . . . . . . . . . . . . . . . . . . . . . . . . . 140Firewall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Use a Motorola Netopia® Firewall . . . . . . . . . . . . . . . . . . . . . . . 142BreakWater Basic Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Configuring for a BreakWater Setting . . . . . . . . . . . . . . . . . . . . . 142TIPS for making your BreakWater Basic Firewall Selection . . . 143Basic Firewall Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143IPSec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146SafeHarbour IPSec VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Configuring a SafeHarbour VPN. . . . . . . . . . . . . . . . . . . . . . . . . 148Parameter Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Stateful Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Stateful Inspection Firewall installation procedure . . . . . . . . . . . . . . . 154Exposed Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Stateful Inspection Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Open Ports in Default Stateful Inspection Installation . . . . . . . . . . . . 157 Firewall Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 General firewall terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Basic IP packet components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Basic protocol types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Firewall design rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Firewall Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Implied rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Example filter set page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Filter basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Example network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Example filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Administrator’s Handbook8 Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Example 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Packet Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163What’s a filter and what’s a filter set?. . . . . . . . . . . . . . . . . . . . . . . . . 163How filter sets work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Filter priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164How individual filters work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165A filtering rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Parts of a filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Port numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Port number comparisons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Other filter attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Putting the parts together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Filtering example #1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Filtering example #2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Design guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169An approach to using filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Working with IP Filters and Filter Sets . . . . . . . . . . . . . . . . . . 171 Adding a filter set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Adding filters to a filter set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Viewing filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Modifying filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Deleting filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Moving filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Deleting a filter set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Associating a Filter Set with an Interface . . . . . . . . . . . . . . . 176 Policy-based Routing using Filtersets . . . . . . . . . . . . . . . . . . 177 TOS field matching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Security Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Using the Security Monitoring Log . . . . . . . . . . . . . . . . . . . . . . . 179Timestamp Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Install Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Updating Your Gateway’s Motorola Netopia® Firmware Version 183Step 1: Required Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Step 2: Motorola Netopia® firmware Image File . . . . . . . . . . . . . . . . 184Install Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Use Motorola Netopia® Software Feature Keys . . . . . . . . . . . . . . . . 187Obtaining Software Feature Keys . . . . . . . . . . . . . . . . . . . . . . . . 187Procedure - Install a New Feature Key File . . . . . . . . . . . . . . . . 187To check your installed features: . . . . . . . . . . . . . . . . . . . . . . . . 189Install Certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 CHAPTER 4 Basic Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . 193 Status Indicator Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 LED Function Summary Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Factory Reset Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

9 CHAPTER 5 Advanced Troubleshooting . . . . . . . . . . . . . . . . . . . . . 207 Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Expert Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Ports: Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Ports: DSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213IP: Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214DSL: Circuit Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215System Log: Entire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217Network Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 CHAPTER 6 Command Line Interface . . . . . . . . . . . . . . . . . . . . . . 223 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Starting and Ending a CLI Session . . . . . . . . . . . . . . . . . . . . 226 Logging In. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Ending a CLI Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Saving Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Using the CLI Help Facility . . . . . . . . . . . . . . . . . . . . . . . . . . 226 About SHELL Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 SHELL Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227SHELL Command Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 SHELL Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Common Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228WAN Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 About CONFIG Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 240 CONFIG Mode Prompt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Navigating the CONFIG Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . 240Entering Commands in CONFIG Mode . . . . . . . . . . . . . . . . . . . . . . . 241Guidelines: CONFIG Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Displaying Current Gateway Settings. . . . . . . . . . . . . . . . . . . . . . . . . 242Step Mode: A CLI Configuration Technique . . . . . . . . . . . . . . . . . . . . 242Validating Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 CONFIG Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Remote ATA Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . 243DSL Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245ATM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245Bridging Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246Common Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247DHCP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Common Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248DHCP Generic Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249DHCP Option Filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253DMT Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254DSL Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Domain Name System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255Common Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255Dynamic DNS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256IGMP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Administrator’s Handbook10 IP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Common Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259ARP Timeout Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259DSL Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Ethernet LAN Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261Additional subnets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262Default IP Gateway Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263IP-over-PPP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263Static ARP Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266IGMP Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266IPsec Passthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266IP Prioritization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266Differentiated Services (DiffServ) . . . . . . . . . . . . . . . . . . . . . . . . 267Packet Mapping Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 269Queue Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271Basic Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272Weighted Fair Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273Priority Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274Funnel Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275Interface Queue Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . 275SIP Passthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276RTSP Passthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276Static Route Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276IPMaps Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277Network Address Translation (NAT) Default Settings. . . . . . . . . . . . . 278Network Address Translation (NAT) Pinhole Settings . . . . . . . . . . . . 278PPPoE /PPPoA Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Configuring Basic PPP Settings . . . . . . . . . . . . . . . . . . . . . . . . . 279Configuring Port Authentication . . . . . . . . . . . . . . . . . . . . . . . . . 281PPPoE with IPoE Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282Ethernet WAN platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282ADSL platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283Ethernet Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283802.3ah Ethernet OAM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284Command Line Interface Preference Settings . . . . . . . . . . . . . . . . . . 285Port Renumbering Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287Firewall Settings (for BreakWater Firewall). . . . . . . . . . . . . . . . . 287SafeHarbour IPSec Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287Internet Key Exchange (IKE) Settings . . . . . . . . . . . . . . . . . . . . 291Stateful Inspection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293Packet Filtering Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296SNMP Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297SNMP Notify Type Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298Syslog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301Default syslog installation procedure . . . . . . . . . . . . . . . . . . . . . 302Wireless Settings (supported models) . . . . . . . . . . . . . . . . . . . . . . . . 303Wireless Multi-media (WMM) Settings . . . . . . . . . . . . . . . . . . . . 306Wireless Privacy Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308Wireless MAC Address Authorization Settings . . . . . . . . . . . . . . 309RADIUS Server Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310VLAN Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Example 1: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

11 Example 2: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313VoIP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320UPnP settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321DSL Forum settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321TR-064 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321TR-069 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322Backup IP Gateway Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323VDSL Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325VDSL Parameter Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325VDSL Parameters Accepted Values . . . . . . . . . . . . . . . . . . . . . . 327 CHAPTER 7 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 -----A----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331-----B----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332-----C----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332-----D----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333-----E----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334-----F----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335-----H----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335-----I----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336-----K----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336-----L----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336-----M----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337-----N----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337-----P----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338-----Q----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338-----R----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339-----S----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339-----T----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340-----U----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341-----V----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341-----W-----. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341-----X----- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 CHAPTER 8 Technical Specifications and Safety Information . . . . 343 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 Dimensions: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Communications interfaces: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Operating temperature: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Storage temperature: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Relative storage humidity: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Software and protocols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Software media: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Routing: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343WAN support: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Security: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Management/configuration methods: . . . . . . . . . . . . . . . . . . . . . 344Diagnostics: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 Agency approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

Administrator’s Handbook12 North America . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344International . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344Regulatory notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344European Community. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 Manufacturer’s Declaration of Conformance . . . . . . . . . . . . . 344 United States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345Service requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345Declaration for Canadian users. . . . . . . . . . . . . . . . . . . . . . . . . . 345Caution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 Important Safety Instructions . . . . . . . . . . . . . . . . . . . . . . . . . 346 Australian Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 346Caution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346Caution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346Telecommunication installation cautions . . . . . . . . . . . . . . . . . . 346 47 CFR Part 68 Information . . . . . . . . . . . . . . . . . . . . . . . . . 347 FCC Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347FCC Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 Electrical Safety Advisory . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 Copyright Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 348 CHAPTER 9 Overview of Major Capabilities . . . . . . . . . . . . . . . . . . 351 Wide Area Network Termination . . . . . . . . . . . . . . . . . . . . . . 351 PPPoE/PPPoA (Point-to-Point Protocol over Ethernet/ATM) . . . . . . . 351Instant-On PPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Simplified Local Area Network Setup . . . . . . . . . . . . . . . . . . 352 DHCP (Dynamic Host Configuration Protocol) Server . . . . . . . . . . . . 352DNS Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Embedded Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Remote Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354Password Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . . . . 354Motorola Netopia® Advanced Features for NAT . . . . . . . . . . . . 355Internal Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355Pinholes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356Default Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356Combination NAT Bypass Configuration . . . . . . . . . . . . . . . . . . 356IP-Passthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356VPN IPSec Pass Through. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357VPN IPSec Tunnel Termination . . . . . . . . . . . . . . . . . . . . . . . . . 357Stateful Inspection Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358SSL Certificate Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358VLANs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

13 CHAPTER 1 Introduction What’s New in 7.7.4 New in Motorola Netopia® Embedded Software Version 7.7.4 are the following features: • Internet Group Management Protocol (IGMP) Version 3 support. See “IGMP (Internet Group Management Protocol)” on page 100. • TR-101 Support:• Concurrent support for PPPoE and IPoE connections on the WAN. See “WAN” on page 67.• Multiple LAN IP Subnet support. See “LAN” on page 49.• Additional DHCP range support. These ranges are associated with the additional LAN subnets on a 1-to-1 basis.• DHCP option ﬁltering support. Allows DHCP option data to be used to determine the desired DHCP address range. See “DHCP Option Filtering” on page 252.• Support for additional WAN settings to control multicast forwarding as well as if 0.0.0.0 is used as the source address for IGMP packets. See “Advanced:” on page 69.• Support for “unnumbered” interfaces. For IP interfaces, this allows the address to be set to 0 and the DHCP client also to be disabled. See page 71. • PPPoE/DHCP Autosensing. See “WAN” on page 67. • Wireless Multimedia Mode (WMM) support. See “WiFi Multimedia” on page 62. • Firewall: ClearSailing is automatically enabled on all 2200-Series ADSL2+ platforms. (Explicit excep-tions: bonded and VDSL2, 3341, and 3387WG.) See “Firewall” on page 142. • TR-069 Remote device management is automatically enabled by default for 2200-Series Gateways. (Explicit exceptions: bonded and VDSL2, 3341, 3387WG). See “TR-069” on page 322. • Voice-over-IP (VoIP) Support using Session Initiation Protocol (SIP) for supported models. See “VoIP” on page 120 and VoIP CLI “VoIP settings” on page 316. • Support of VLAN ID 0 on the Ethernet WAN and support for setting p-bits on a segment/port basis; inter-VLAN groups. See “VLAN” on page 107 and CLI “VLAN Settings” on page 311. • Backup IP Gateway Support. See “Backup” on page 133 and CLI “Backup IP Gateway Settings” on page 323.Corresponding commands have been added to the Command Line Interface (CLI). See “Command Line Interface” on page 223. • Reset WAN port and wireless counter and CLI command to display individual Ethernet port statistics. See “reset enet [ all ]” on page 231 and “show enet [ all ]” on page 233. •CLI for Motorola Netopia® ATA Remote Management. See “Remote ATA Conﬁguration Commands” on page 243.

Administrator’s Handbook14•Provide Bandwidth Management using Weighted Fair Queueing.See “Queue Conﬁguration” on page 271.•New CLI command for disabling Dying Gasp. See “DMT Settings” on page 254.•Ethernet in the First Mile Operations Administration and Maintenance (802.3ah EFM OAM) Support. See “802.3ah Ethernet OAM Settings” on page 284.•IP multicast to layer 2 unicast mapping. See “IGMP Settings” on page 257.•Real Time Streaming Protocol (RTSP) ALG support for Video-on-Demand (VoD) Services. See “RTSP Passthrough” on page 276.

15About Motorola Netopia® Documentation☛ NOTE:This guide describes the wide variety of features and functionality of the Motorola Netopia® Gateway, when used in Router mode. The Motorola Netopia® Gateway may also be delivered in Bridge mode. In Bridge mode, the Gateway acts as a pass-through device and allows the work-stations on your LAN to have public addresses directly on the Internet.Motorola, Inc. provides a suite of technical information for its 2200-, 3300- and 7000-series family of intel-ligent enterprise and consumer Gateways. It consists of: •Administrator’s Handbook•Dedicated Quickstart guides•Speciﬁc White PapersThe documents are available in electronic form as Portable 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 Motorola’s Netopia website: http://www.netopia.com/Intended AudienceThis guide is targeted primarily to residential service subscribers. Expert Mode sections may also be of use to the support staffs of broadband service providers and advanced residential service subscribers.See “Expert Mode” on page 39.Documentation ConventionsGeneralThis manual uses the following conventions to present information:Convention (Typeface) Descriptionbold italic monospacedMenu commandsbold italic sans serif Web GUI page links and button names

Administrator’s Handbook16Internal Web InterfaceCommand Line InterfaceSyntax conventions for the Netopia Gateway command line interface are as follows:terminal Computer display textbold terminal User-entered textItalic Italic type indicates the complete titles of manuals.Convention (Graphics) DescriptionDenotes an “excerpt” from a Web page or the visual truncation of a Web pageDenotes an area of emphasis on a Web pageConvention Descriptionstraight ([ ]) brackets in cmd line Optional command arguments curly ({ }) brackets, with values sep-arated with vertical bars (|).Alternative values for an argument are presented in curly ({ }) brackets, with values separated with vertical bars (|).bold terminal type faceUser-entered textitalic terminal type faceVariables for which you supply your own valuesblue rectangle or linesolid rounded rectangle with an arrow

17OrganizationThis guide consists of nine chapters, including a glossary, and an index. It is organized as follows:•Chapter 1, “Introduction” — Describes the Motorola 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 Motorola Netopia® Gateway.•Chapter 3, “Expert Mode” — Focuses on the “Expert Mode” Web-based user interface for advanced users. It is organized in the same way as the Web UI is organized. As you go through each section, func-tions and procedures are discussed in detail.•Chapter 4, “Basic Troubleshooting” — Gives some simple suggestions for troubleshooting 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 commands for both the SHELL and CONFIG modes. A summary table and individual command examples for each mode is pro-vided.•Chapter 7, “Glossary” •Chapter 8, “Technical Speciﬁcations and Safety Information”•Chapter 9, “Overview of Major Capabilities” — Presents a product description summary.•IndexA Word About Example ScreensThis manual contains many example screen illustrations. Since Motorola Netopia® 2200-, 3300- and 7000-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 exam-ple screens are for illustrative and explanatory purposes, and should not be construed to represent your own unique environment.

Administrator’s Handbook18

19CHAPTER 2 Basic Mode SetupMost 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 Motorola Netopia® Gateway. The following instruc-tions cover installation in Router Mode.This section covers:•“Important Safety Instructions” on page 20•“Wichtige Sicherheitshinweise” on page 21 (German)•“Setting up the Motorola Netopia® Gateway” on page 22•“Conﬁguring the Motorola Netopia® Gateway” on page 25•“Motorola Netopia® Gateway Status Indicator Lights” on page 30•“Home Page - Basic Mode” on page 31

Administrator’s Handbook20Important Safety InstructionsPOWER SUPPLY INSTALLATIONConnect the power supply cord to the power jack on the Motorola 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 sup-ply blades, power supply cord plug or the appliance coupler serves as the mains power discon-nect. 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. OnlyTELECOMMUNICATION INSTALLATIONWhen using your telephone equipment, basic safety precautions should always be followed to reduce the risk of ﬁre, electric shock and injury 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 VENTILATIONThe Motorola 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

21Wichtige SicherheitshinweiseNETZTEIL INSTALLIERENVerbinden Sie das Kabel vom Netzteil mit dem Power-Anschluss an dem Motorola Netopia® Gateway. Stecken Sie dann das Netzteil in eine Netzsteckdose.☛ Achtung:Abhängig von dem mit dem Produkt gelieferten Netzteil, entweder die direkten Stecker-netzgeräte, Stecker vom Netzkabel oder der Gerätekoppler dienen als Hauptspannungsunter-brechung. 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. OnlyINSTALLATION DER TELEKOMMUNIKATIONWenn 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 ver-ringern. 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 Gewitters. 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

Administrator’s Handbook22Setting up the Motorola Netopia® GatewayRefer to your Quickstart Guide for instructions on how to connect your Motorola 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 Motorola Netopia® Gateway models are supplied for any of these con-nections. 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 b. Some Windows versions follow a path like this:Start menu -> Con-trol Panel -> Net-work and Internet Connections -> Net-work Connections -> Local Area Connec-tion -> Properties -> Internet Protocol [TCP/IP] -> Proper-ties

23c. Windows Vista is set to obtain an IP address automatically by default. You may not need to conﬁgure it at all.To check, open the Networking Control Panel and select Internet Protocol Version 4 (TCP/IPv4). Click the Properties button.The Internet Protocol Version 4 (TCP/IPv4) Properties window should appear as shown.If not, select the radio buttons shown above, and click the OK button.

Administrator’s Handbook24Macintosh MacOS 8 or higher or Mac OS X: Step 1. Access the TCP/IP or Network control panel. Then go to Step 2.Step 2. Select Built-in Ethernet Step 3. Select Conﬁgure Using DHCPStep 4. Close and Save, if prompted.Proceed to “Conﬁguring the Motorola Netopia® Gateway” on page 25.a. MacOS follows a path like this:Apple Menu -> Control Pan-els -> TCP/IP Control Panel b. Mac OS X follows a path like this:Apple Menu -> System Preferences -> Network

25Conﬁguring the Motorola Netopia® Gateway1. Run your Web browser application, such as Firefox or Microsoft Internet Explorer, from the computer connected to the Motorola Netopia® Gateway.Enter http://192.168.1.254 in the Location text box. The Admin Password page appears.Access to your Motorola Netopia® device can be controlled through two access control accounts, Admin or User.•The Admin, or administrative user, performs all conﬁguration, management or maintenance 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 Motorola Netopia® unit.MiAVo VDSL and Ethernet WAN models QuickstartThe browser then displays the Quickstart page.2. Click the Connect to the Internet button.

Administrator’s Handbook26Once a connection is established, your browser is redirected to your service provider’s home page or a registration page on the Internet.☛ 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 31.

27PPPoE QuickstartFor 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 Provider. Click the Connect to the Internet button.Once you enter your username and password here, you will no longer need to enter them whenever you access the Internet. The Motorola Netopia® Gateway stores this information and automatically connects you to the Internet.The Gateway displays a message while it conﬁgures itself.4. When the connection succeeds, your browser will display a success message.Once a connection is established, your browser is redirected to your service 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 favor-ite Internet bookmarks.

Administrator’s Handbook28Set up the Motorola Netopia® Pocket GatewayYour Motorola 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, Windows NT or Windows Vista, you don’t even need the CD.Follow these easy setup steps:1. Plug the Motorola 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 Motorola Netopia® Installation Wizard will launch automatically.The Motorola Netopia® Installation Wizard will assist you to conﬁgure your PC to work with the Motorola Netopia® pocket Gateway. Follow the on-screen instructions.To proceed, click the Next button.The Motorola Netopia® Installation Wizard performs a series of checks on your system and then will install USB drivers for your connection. 3. Place the Motorola 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 Motorola 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 jackNetopia Pocket Gateway/RJ-11 phone cableUSB port

29The Wizard displays a success message when the settings are conﬁgured.5. The Motorola Netopia® Installation Wizard will then launch your web browser and display the Welcome page where you conﬁgure your Motorola Netopia® Pocket Gateway.

Administrator’s Handbook30Motorola Netopia® Gateway Status Indicator LightsColored LEDs on your Motorola Netopia® Gateway indicate the status of various port activity. Different Gateway models have different ports for your connections and different indicator LEDs. The Quickstart Guide accompanying your Motorola Netopia® Gateway describes the behavior of the various indicator LEDs.Example status indicator lightsnetopiaStatus Indicator Lights (LEDs)

31Home Page - Basic ModeAfter you have performed the basic Quickstart conﬁguration, any time you log in to your Motorola Netopia® Gateway you will access the Motorola Netopia® Gateway Home Page. You access the Home Page by typing http://192.168.1.254 in your Web browser’s location box.The Basic Mode Home Page appears.☛ VoIP-enabled Gateways also display VoIP phone information, as well.

Administrator’s Handbook32The Home Page displays the following information in the center section: 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.Item DescriptionSerial Number This is the unique serial number of your Gateway.Software ReleaseThis is the version number of the current embedded software in your Gate-way.Warranty Date This is the date that your Gateway was installed and enabled.Status of DSL DSL connection (Internet) is either Up or DownStatus of Connection‘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.Local WAN IP AddressThis is the negotiated address of the Gateway’s WAN interface. This address is usually dynamically assigned.Remote Gateway AddressThis is the negotiated address of the remote router to which this Gateway is connected.Primary DNSSecondary DNSThese are the negotiated DNS addresses.ISP Username This is your PPPoE username as assigned by your service provider.Ethernet Status (if so equipped) Local Area Network (Ethernet) is either Up or DownUSB Status If your Gateway is so equipped, Local Area Network (USB) is either Up or DownLine 1/2 RegistrationIf your Gateway is so equipped, voice Line 1 and/or 2 is either Idle or Con-nectedDate & Time This is the current UTC time; blank if this is not available due to lack of a network connection.

33Link: Manage My AccountYou can change your ISP account information for the Motorola Netopia® Gateway. You can also manage other aspects of your account on your service provider’s account management Web site.Click on the Manage My Account link. The Manage My Account page appears.If you have a PPPoE account, enter your username, and then your new password. Conﬁrm your new pass-word. 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 Submit button. 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.

Administrator’s Handbook34Link: Status DetailsIf you need to diagnose any problems with your Motorola Netopia® Gateway or its connection to the Inter-net, you can run a sophisticated diagnostic tool. It checks several aspects of your physical and electronic connection and reports its results on-screen. This can be useful for troubleshooting, or when speaking with a technical support technician.Click on the Status Details link. The Diagnostics page appears.Click the Run Diagnostics button to run your diagnostic tests. For a detailed description of these tests, see “Diagnostics” on page 217.

35Link: Enable Remote ManagementThis link allows you to authorize a remotely-located person, such as a support technician, to directly access your Motorola 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 Enable Rmt Mgmt link. The Enable Remote Management page appears.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 temporary Admin password. After the time-out period has expired, the Admin password reverts 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.

Administrator’s Handbook36Link: Expert ModeMost 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 Motorola Netopia® Gateway has many advanced features that can be accessed and conﬁgured through the Expert Mode pages.Click the Expert Mode link to display the Expert Mode Conﬁrmation page.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 39 for information.

37Link: 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 Update Firmware link. The Firmware Update Conﬁrmation page appears.If you click the Continue button, the Gateway will check a remote Firmware Server for the latest ﬁrmware revision. If a newer version is found, your ﬁrmware will be automatically updated once you conﬁrm the installation.

Administrator’s Handbook38Link: Factory ResetIn some cases, you may need to clear all the conﬁguration settings and start over again to program the Motorola Netopia® Gateway. You can perform a factory reset to do this.Click on Factory Reset to reset the Gateway back to its original factory default settings. ☛ NOTE:Exercise caution before performing a Factory Reset. This will erase any conﬁguration changes that you may have made and allow you to reprogram your Gateway.

39CHAPTER 3 Expert ModeUsing the Expert Mode Web-based user interface for the Motorola Netopia® 2200-, 3300- and 7000-series Gateway you can conﬁgure, troubleshoot, and monitor the status of your Gateway. Accessing the Expert Web InterfaceOpen the Web ConnectionOnce 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 Motorola Netopia® Gateway in the Web browser's window and press Return.For example, you would enter http://192.168.1.254.2. If an administrator or user password has been assigned to the Motorola Netopia® Gate-way, enter Admin or User as the username and the appropriate password and click OK.The Basic Mode Home Page opens.3. Click on the Expert Mode link in the left-hand column of links.

Administrator’s Handbook40You are challenged to conﬁrm your choice.Click OK.The Home Page opens in Expert Mode.

41Home Page - Expert ModeThe Home Page is the summary page for your Motorola Netopia® Gateway. The toolbar at the top provides links to controlling, conﬁguring, and monitoring pages. Critical conﬁguration and operational status is dis-played in the center section. Home Page - InformationThe Home page’s center section contains a summary of the Gateway’s conﬁguration settings and opera-tional status.Summary Information Field Status and/or DescriptionGeneral InformationHardware Model number and summary speciﬁcationSerial Number Unique serial number, located on label attached to bottom of unitSoftware Version Release and build number of running Motorola 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

Administrator’s Handbook42Status Wide Area Network may be Waiting for DSL (or other waiting status), Up or DownData Rate (Kbps) Once connected, displays DSL speed rate, Downstream and UpstreamLocal 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.LANIP Address Internal IP address of the Motorola Netopia® Gateway.Netmask Deﬁnes the IP subnet for the LAN Default is 255.255.255.0 for a Class C deviceDHCP 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) StatusStatus of your Ethernet network connection (if supported). Up or Down.VoIPLine 1/2 Registration If your Gateway is so equipped, voice Line 1 and/or 2 is either Idle or Reg-istered

43ToolbarThe toolbar is the dark blue bar at the top of the page containing the major navigation buttons. These but-tons are available from almost every page, allowing you to move freely about the site. Navigating the Web InterfaceLink: Breadcrumb TrailThe 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.Home Conﬁgure Troubleshoot Security Install Restart HelpQuickstart System Status Passwords Install CertiﬁcateLAN Network Tools Firewall Install KeyWAN Diagnostics IPSec Install SoftwareAdvanced Stateful InspectionPacket FilterSecurity Log

Administrator’s Handbook44RestartButton: RestartThe Restart button on the toolbar allows you to restart the Gateway at any time. You will be prompted to conﬁrm the restart before any action is taken. The Restart Conﬁrmation message explains the conse-quences of and reasons for restarting the Gateway.

45Link: Alert SymbolThe 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.

Administrator’s Handbook46HelpButton: HelpContext-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 -> Pass-words, then click Help.

47ConﬁgureButton: ConﬁgureThe 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 information 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: QuickstartHow 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 Ser-vice Provider equipment using the ISP Username and Password. These values are given to you by your Ser-vice Provider. 1. Enter your ISP Username and ISP Password.2. Click Connect to the Internet.

Administrator’s Handbook48A brief message is displayed while the Gateway attempts to establish a connection. 3. When the connection succeeds, your browser will display your Service Provider’s home page.If you encounter any problems connecting, refer to the chapters “Basic Troubleshooting” on page 193 or “Advanced Troubleshooting” on page 207.

49Link: LAN* 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 dur-ing troubleshooting.* IP Address: The LAN IP Address of the Gateway. The IP Address you assign to your LAN inter face 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 sub-net 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 off, 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.

Administrator’s Handbook50•IGMP Forwarding: The default setting is Disabled. If you check this option, it will enable Internet Group Management Protocol (IGMP) multicast forwarding. IGMP allows a router to determine which host groups have members on a given network segment. See “IGMP (Internet Group Management Protocol)” on page 100 for more information.•RIP Send Mode: Speciﬁes whether the gateway should use Routing Information Protocol (RIP) broad-casts 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 algo-rithms, 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 support 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 advertised.• 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 net-work 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 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 Motorola 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).• IP Subnets: The IP Subnets screen allows you to conﬁgure up to seven secondary subnets and their DHCP ranges, by entering IP address/subnet mask pairs:

51☛ Note: You need not use this screen if you have only a single Ethernet IP subnet.This screen displays seven rows of editable columns. All seven row labels are always visible, regardless of the number of subnets conﬁgured.•To add an IP subnet, select one of the rows, and click the Edit button. Check the Enabled checkbox and click the Submit button.The screen expands to allow you to enter subnet information. If DHCP Server (see below) is not enabled, the DHCP Start Address and DHCP End Address ﬁelds do not appear.•Enter the Router’s IP address on the subnet in the IP Address ﬁeld and the subnet mask for the subnet in the Netmask ﬁeld.•Enter the DHCP Start Address and End Address of the subnet range in their respective ﬁelds.Ranges cannot overlap and there may be only one range per subnet.•Click the Submit button. •When you are ﬁnished adding subnets, click the Alert icon at the upper right, and in the resulting page, click the Save and Restart link.To delete a conﬁgured subnet, set both the IP address and subnet mask values to 0.0.0.0, either explicitly or by clearing each ﬁeld and clicking the Submit button to commit the change.☛ NOTE: All additional DHCP ranges use the global lease period value. See page 52.

Administrator’s Handbook52• 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 Server Mode pull-down menu, choose Server, then con-ﬁgure the range of IP addresses that you would like the Gateway to hand out to your computers. 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 server in the Service Provider's network. Click the 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.

53Wireless(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 link. 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 services.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 Network Name. The SSID is used to identify this particular wire-less 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 “Pri-vacy” on page 54.☛ NOTE:On the 2200-Series Gateways, WEP-Manual privacy is enabled by default. Use the Motorola Netopia® Installation Wizard on the accompanying Motorola Netopia® CD to generate WEP keys for connecting wireless client computers.

Administrator’s Handbook54Privacy•Off - No Privacy provides no encryption on your wireless LAN data.•WPA-802.1x provides RADIUS server authentication support.•WPA-PSK provides Wireless Protected Access, the most secure option for your wireless 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 gener-ate 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 Pass-phrase ﬁ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 net-work data. You can enable 40-, 128-, or 256-bit WEP Encryption (depending on the capability of your cli-ent wireless card) for IP trafﬁc on your LAN.

55You 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 decrypt 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.Click the Submit button. The Alert icon appears. Click the Alert icon, and then the Save and Restart link.

Administrator’s Handbook56AdvancedIf 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 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 trans-mission 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,

57France, Spain and Japan will differ. Channel selection can have a signiﬁcant impact on per formance, 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 Motorola 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 Motorola Netopia® Gateway will use the conﬁgured default channel selected from the previous pull-down menu.•At Startup causes the Motorola 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 performs the at-startup 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 Motorola 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 scan-ning features of wireless client computers. Unless both the wireless clients and the Router share the same SSID in Closed System mode, the Router’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 Router’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 ModeEnabling Closed System Mode on your wireless Gateway provides another level of security, since your wire-less 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 Motorola Netopia® Gateway.In addition, if you have enabled WEP encryption on the Motorola Netopia® Gateway, your network clients must also have WEP encryption enabled, and must have the same WEP encryption key as the Motorola Netopia® Gateway.Once the Motorola 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 different 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 wire-less card and/or operating system.

Administrator’s Handbook58☛ NOTE: While clients may also have a passphrase feature, these are vendor-speciﬁc and may not nec-essarily create the same keys. You can passphrase generate a set of keys on one, and manu-ally enter them on the other to get around this.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 encryption 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.

59Encryption 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: 592CA140F0A238B0C61AE162F592CA140F0A238B0C61AE162F21A09CUse 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 button, fol-lowed by the Save and Restart link.WPA Version AllowedIf 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: •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.Multiple SSIDsThe 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 Multiple SSIDs link.When the Multiple Wireless SSIDs screen appears, check the Enable SSID checkbox for each SSID you want to enable.

Administrator’s Handbook60The screen expands to allow you to name each additional Wireless ID, and specify a Privacy mode for each one.

61Privacy 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 Submit button.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.

Administrator’s Handbook62WiFi MultimediaWiFi Multimedia is an advanced feature that allows you to prioritize various types of data travelling over the wireless network. Certain types of data that are sensitive to delays, such as voice or video, must be priori-tized ahead of other, less delay-sensitive types, such as email. WiFi Multimedia currently implements wireless Quality of Service (QoS) by transmitting data depending on Diffserv priority settings. These priorities are mapped into four Access Categories (AC), in increasing order of priority: •Background (BK), •Best Effort (BE), •Video (VI), and •Voice (VO). It requires WiFi Multimedia (WMM)-capable clients, usually a separate feature enabled at the client network settings, and client PC software that makes use of Differentiated Services (Diffserv). Refer to your operat-ing system instructions for enabling Diffserv QoS..When you click the WiFi Multimedia link the WiFi Multimedia page appears.To enable the WiFi Multimedia custom settings, select Diffserv from the pull-down menu.

63The screen expands.Router EDCA Parameters (Enhanced Distributed Channel Access) govern wireless data from your Gate-way to the client; Client EDCA Parameters govern wireless data from the client to your Gateway.☛ NOTE:It is not recommended that you modify these settings without direct knowledge or instructions to do so. Modifying these settings inappropriately could seriously degrade network perfor-mance.•AIFs: (Arbitration Interframe Spacing) the wait time in milliseconds for data frames.•cwMin: (Minimum Contention Window) upper limit in milliseconds of the range for determining initial ran-dom backoff. The value you choose must be lower than cwMax.•cwMax: (Maximum Contention Window) upper limit in milliseconds of the range of determining ﬁnal ran-dom backoff. The value you choose must be higher than cwMin.•TXOP Limit: Time interval in microseconds that clients may initiate transmissions. (When Operating Mode is B-only, default values are used and this ﬁeld is not conﬁgurable.)Wireless MAC AuthorizationWireless 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

Administrator’s Handbook64be accepted onto the wireless LAN. All unlisted addresses will be blocked, in addition to the listed addresses with Allow disabled.To enable Wireless MAC Authentication, click the MAC Authorization link.When the Wireless MAC Authentication screen appears, check the Enable Wireless MAC Authorization checkbox:The screen expands as follows: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

65are 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 Add, Edit, or Delete addresses to the list by clicking the respective 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 Alert icon, and Save your changes and restart the Gate-way.Use RADIUS ServerRADIUS 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 authen-ticate users seeking access to the wireless services, as well as the authorized user list maintained locally within the Gateway.If you click the RADIUS link, the screen expands to allow you to enter your RADIUS server information.

Administrator’s Handbook66•RADIUS Server Addr/Name: The default RADIUS server 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 port 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 Advanced Network Conﬁguration page, by clicking the 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.

67Link: WANWhen you click the WAN link, the WAN IP conﬁguration page appears. This page varies depending on the WAN interface of your Motorola Netopia® Gateway.WAN IP Interfaces: Your IP interfaces are listed.PPP over Ethernet interfaceClick 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 dis-able 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.

Administrator’s Handbook68Restrictions: This setting determines the types of trafﬁc the Gateway accepts from the WAN. Admin Dis-abled 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.DHCP/PPPoE/PPPoA Autosensing: The pull-down menu allows you to select an autosens-ing feature, or to disable it. Selecting between PPPoE/DHCP or PPPoE/PPPoA enables automatic sensing of your WAN connection type. If you select PPPoE/DHCP, the gateway attempts to connect using PPPoE ﬁrst. If the Gateway fails to connect after 60 seconds, it switches to DHCP. As soon as it can connect via DHCP, the Gateway chooses and sets DHCP as its default. Otherwise, after attempting to connect via DHCP for 60 seconds, the Gateway switches back to PPPoE. The Gateway will continue to switch back and forth in this manner until it successfully connects. Similarly, selecting PPPoE/PPPoA causes the Gateway to attempt to con-nect by trying these protocols in parallel, and using the ﬁrst one that is successful. If you choose to disable the feature, select Off.ISP Username: This is the username used to authenticate your Gateway with the Service Provider's net-work. 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 net-work. This value is given to you by your Service Provider.Connection Type: The pull-down menu allows you to choose to have either an uninterrupted connection or an as-needed connection.• 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 dis-connect if there is no trafﬁc over the Internet link.

69Advanced:If you click the Advanced link, the Advanced WAN IP Interface conﬁguration page appears.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 seg-ments of your Ethernet network that the Motorola Netopia® Gateway needs to recognize. Set to Off, Netopia Embedded Software Version 7.7.4 will not accept information from either RIP-1 nor RIP-2 rout-ers. With Receive RIP Mode set to RIP-1, the Motor-ola Netopia® Gateway will accept routing information provided by RIP packets from other routers that use the same subnet mask. Set to RIP-2, Netopia Embedded Software Version 7.7.4 will accept routing information provided by RIP packets from other rout-ers 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 authentica-tion provides an enhanced level of security that information that your PC receives does not originate from a malicious source posing as part of your network. This ﬁeld allows you to enter an MD5 encryption key of from 1 – 16 ASCII characters for authenticating RIP receipts.Multicast Forward: If you check this checkbox, this interface acts as an IGMP proxy host, and IGMP pack-ets are transmitted and received on this interface on behalf of IGMP hosts on the LAN interface.IGMP Null Source Address: If you check this checkbox, the source IP address of every IGMP packet trans-mitted from this interface is set to 0.0.0.0. This complies with the requirements of TR-101, and removes the need for a publicly advertised IP address on the WAN interface. This checkbox is only available if “Mul-ticast Forward” is checked.

Administrator’s Handbook70LCP 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 sys-tem. 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 with-out 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 Gate-way will send before terminating the PPP link.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 interfaceClick the Ethernet WAN link to conﬁgure it.

71The WAN IP Interface page appears.Enable Interface: You can disable the interface by unchecking the checkbox. However, doing so will dis-able all ability for your LAN users to connect to the WAN using the Gateway.Obtain IP Address Automatically: Your service 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 Service 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.☛ NOTE:Beginning with Firmware Version 7.7, you can now run an IPoE interface without an IP address (“unnumbered” interface), if you un-check “Obtain IP Address Automatically” and set the IP Address to 0.

Administrator’s Handbook72Address 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 Dis-abled means that Gateway trafﬁc is accepted but administrative commands are ignored. None means that all trafﬁc is accepted. Admin Disabled is the default.Advanced:If you click the Advanced link the Advanced WAN IP Interface conﬁguration page appears.RIP Receive Mode: Routing Information Protocol (RIP) is needed if there are IP routers on other segments of your Ethernet network that the Motorola Netopia® Gate-way needs to recognize. Set to Off, Netopia Embedded Software Version 7.7.4 will not accept information from either RIP-1 nor RIP-2 routers. With Receive RIP Mode set to RIP-1, the Motorola Netopia® Gateway will accept routing information provided by RIP packets from other routers that use the same subnet mask. Set to RIP-2, Netopia Embedded Software Version 7.7.4 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.Multicast Forward: If you check this checkbox, this interface acts as an IGMP proxy host, and IGMP pack-ets are transmitted and received on this interface on behalf of IGMP hosts on the LAN interface.IGMP Null Source Address: If you check this checkbox, the source IP address of every IGMP packet trans-mitted from this interface is set to 0.0.0.0. This complies with the requirements of TR-101, and removes the need for a publicly advertised IP address on the WAN interface. This checkbox is only available if “Mul-ticast Forward” is checked.IP GatewayEnable 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 OptionsPPPoE: You can enable or disable PPPoE. This link also allows conﬁguration of NAT, admin restrictions, PPPoE username/password, and connection type.

73WAN Ethernet and VDSL GatewaysTo allow for concurrent PPPoE and IPoE support on WAN Ethernet Gateways, including VDSL units, PPPoE with IPoE is available on the PPPoE conﬁguration page. Checking the checkbox will provide this concurrent support. When you enable PPPoE with IPoE, the additional WAN interface becomes available for conﬁguration.☛ NOTE:Enabling pppoe-with-ipoe disables support for multiple PPPoE sessions.ADSL GatewaysATM 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/SNAPPPP over ATM (PPPoA) VC muxedRFC-1483 Bridged EthernetRFC-1483 Routed IPNone

Administrator’s Handbook74Your Motorola Netopia® ADSL Gateway supports VPI/VCI autodetection by default. If VPI/VCI autodetec-tion 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.PPPoE with IPoE: For ADSL Gateways, you must conﬁgure two VCCs with the same VPI/VCI settings to provide concurrent PPPoE with IPoE support.You must use ﬁxed VPI/VCI values for PPPoE with IPoE. You cannot have both VPI/VCI values set to 0/0; autodetection does not work in this mode.

75Once the VCCs have been conﬁgured, the WAN IP Interfaces screen displays the additional interface which you can then conﬁgure as required.

Administrator’s Handbook76ATM Trafﬁc Shaping: You can prioritize delay-sensitive data by conﬁguring the Quality of Service (QoS) characteristics of the virtual circuit. Click the ATM Trafﬁc Shaping 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 practi-cal 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 application 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. 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-nrt is the tolerated Cell Delay Variation range and the provisioned Maximum Burst Size.

77Class PCR SCR MBS Transmit Priority CommentsUBR X N/A N/A Low PCR is a capCBR X N/A N/A High PCR is a guaranteed rateVBR X X X High PCR > SCR. SCR is a guaranteed rate.PCR is a cap.

Administrator’s Handbook78Link: AdvancedSelected Advanced options are discussed in the pages that follow. Many are self-explanatory or are dic-tated by your service provider.The following are typical links under Conﬁgure -> Advanced (some models offer other links):

79Link: IP Static RoutesA 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 Static Routes link, the IP Static Routes page appears.You can conﬁgure as many as 32 static IP routes for the Gateway. To add a static route, click the Add but-ton.The IP Static Route Entry 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 Motorola Netopia® Gateway conﬁgured interface.•Metric: Speciﬁes the hop count for the static route. Enter a number from 1 to 15 to indicate 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.

Administrator’s Handbook80•RIP Advertise: From the pull-down menu, choose how the static route should be advertised 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 Submit button. The Alert icon will appear, so that you can switch to the Save Changes page, when you are ﬁnished.Once you save your changes, you will be returned to the IP Static Routes entry screen.•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.

81Link: IP Static ARPYour Gateway maintains a dynamic Address Resolution Protocol (ARP) table to map IP addresses to Ether-net (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 corre-sponding 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 entry is in nn-nn-nn-nn-nn-nn (hexadeci-mal) format.

Administrator’s Handbook82Link: PinholesPinholes 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 originat-ing from a remote connection (WAN) to be sent to the internal computer (LAN) that is speciﬁed in the Pin-hole page.Pinholes are common for applications like multiplayer online games. Refer to software manufacturer appli-cation 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 port 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 Motorola Netopia® Gateway to support three separate applications. This requires passing three kinds of speciﬁc IP trafﬁc through to your LAN. Application 1: You have a Web server located on your LAN behind your Motorola Netopia® Gateway 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: You want one of your LAN stations to act as the “central repository” for all email for all of the LAN users.Application 3: One of your LAN stations is specially conﬁgured for game applications. You want this spe-ciﬁ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.WAN Trafﬁc Type Protocol Pinhole Name LAN Internal IP Address Web TCP my-webserver 192.168.1.1 Email TCP my-mailserver 192.168.1.2 Games UDP my-games 192.168.1.3

83☛ 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. A diagram of this LAN example is: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.WANLANEthernet Interface192.168.1.1192.168.1.2192.168.1.3my-webservermy-mailservermy-gamesGatewayNATNAT PinholesEmbeddedWeb Server210.219.41.20210.219.41.20:8100Ethernet InterfaceInternet

Administrator’s Handbook84Pinhole Conﬁguration Procedure. Use the following steps:1. From the Conﬁgure toolbar button -> Advanced link, select the Internal Servers link.Since Port Forwarding is required for this example, the Motorola Netopia® embedded Web server is con-ﬁgured ﬁrst.☛ NOTE:The two text boxes, Web (HTTP) Server Port and Telnet Server Port, on this page refer to the port numbers of the Motorola Netopia® Gateway’s embedded administration 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 Submit button.4. Click Advanced. Select the Pinholes link to go to the Pinhole page.5. Click Add. Type your speciﬁc data into the Pinhole Entries table of this page. Click Sub-mit.

856. Click on the Add or Edit more Pinholes link. Click the Add button. Add the next Pinhole. Type the speciﬁc data for the second Pinhole.7. Click on the Add or Edit more Pinholes link. Click the Add button. Add the next Pinhole. Type the speciﬁc data for the third Pinhole.☛ 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.

Administrator’s Handbook868. Click on the Add or Edit more Pinholes link. Review your entries to be sure they are cor-rect.9. Click the Alert icon.10. Click the Save and Restart link to complete the entire Pinhole creation task and ensure that the parameters are properly saved.☛ 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:8100You 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.

87Link: IPMapsIPMaps 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 Motorola Netopia® Gateway. A single static or dynamic (DHCP) WAN IP address must be assigned to support other devices on the LAN. These devices utilize Motorola Netopia®’s default NAT/PAT capabilities.Conﬁgure the IPMaps FeatureFAQs for the IPMaps FeatureBefore 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 multiple static WAN IP addresses to be assigned to the Motorola Netopia® Gateway. Static WAN IP addresses are used to support speciﬁc services, like a web server, 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 Motorola Netopia® Gate-way 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 Gate-way? IPMap will support statically assigned WAN IP addresses from the same subnet.WAN IP addresses from different subnets are not supported.

Administrator’s Handbook88IPMaps Block DiagramThe following diagram shows the IPMaps principle in conjunction with existing Motorola Netopia® NAT oper-ations:NAT/PAT Table143.137.50.37143.137.50.36143.137.50.35192.168.1.1192.168.1.n192.168.1.3192.168.1.2......Motorola Netopia® GatewayStatic IP Addressesfor IPMaps Applications143.137.50.37143.137.50.36143.137.50.35Static IP AddressesorDHCP/PPP Served IP Address for Netopia’s default NAT/PAT CapabilitiesIPMaps:One-to-OneMultiple Address MappingLAN stations with WAN IP trafﬁc forwarded by Netopia’s IPMapsLAN stations with WAN IP trafﬁc forwarded by Netopia’s NAT function.WAN Interface LAN Interface192.168.1.1192.168.1.2192.168.1.3192.168.1.n...

89Link: Default ServerThis 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 certain 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 Conﬁgure toolbar button, then Advanced, then the Default Server link.2. From the pull-down menu, select Default-Server. The NAT Server IP Address ﬁeld appears. 3. Determine the IP address of the LAN computer you have chosen to receive the unex-pected or unknown trafﬁc.Enter this address in the NAT Server IP Address ﬁeld.4. Click the Submit button. 5. Click the Alert button.6. Click the Save and Restart link to conﬁrm. Typical Network Diagram. A typical network using the NAT Default Server looks like this:

Administrator’s Handbook90You can also use the LAN-side address of the Gateway, 192.168.1.x to access the web and telnet server.NAT Combination Application. Motorola 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 Pin-holes 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 forward 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.WANLANEthernet Interface192.168.1.3192.168.1.2192.168.1.1LAN STN #3LAN STN #2NAT Default ServerGatewayNATNAT DefaultEmbeddedWeb Server210.219.41.20210.219.41.20(Port 80 default)NAT protectedEthernet InterfaceInternetServer

91•DHCP address serving can automatically serve 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 single-servable-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.•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ﬁg-ured 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 shortened 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 ses-sions 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 indistinguish-able – will fail.

Administrator’s Handbook92Link: Differentiated ServicesWhen you click the Differentiated Services link, the Differentiated Services conﬁguration screen appears.Differentiated Services (Diffserv) 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.VDSL and Bonded ADSL models display this screen:Most other models display this screen:•To enable Differentiated Services, check the Enable checkbox.•(Not displayed on VDSL and Bonded ADSL models) 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 pri-ority trafﬁc might have to wait too long to be passed, and consequently be subject to time-outs.Click the Submit button.You can then deﬁne Custom Flows. If your applications do not provide Quality of Service (QoS) control, Cus-tom Flows allows you to deﬁne streams for some protocols, port ranges, and between speciﬁc end point addresses.

93•To deﬁne a custom ﬂow, click the Add button.The Custom Flow Entry screen appears.• 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 option-ally specify a range of ports. Enter the starting port here.• End Port – Enter the ending port here.• 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.

Administrator’s Handbook94• Quality of Service (QoS) – This is the Quality of Service setting for the ﬂow, based on the TOS bit information. Select Expedite, Assure, or Off (default) from the pull-down menu. The following table out-lines the TOS bit settings and behavior:QoS Setting TOS Bit Value BehaviorOff 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 pack-ets if possible. Appropriate for applications with no guaranteed delivery mechanism.Expedite TOS=101 Use minimum delay. Appropriate for VoIP and video applications.Network Control TOS=111 Use highest possible priority.

95Link: DNSYour Service Provider may maintain a Domain Name server. If you have the information for the DNS serv-ers, 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.

Administrator’s Handbook96Link: DHCP ServerYour 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 Server Mode pull-down menu, then conﬁgure the range of IP addresses that you would like the Gateway to hand out to your computers.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 server in the Service Provider's network. 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.

97Link: RADIUS ServerRADIUS 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 authen-ticate users seeking access to the wireless services, as well as the authorized user list maintained locally within the Gateway.If you click the RADIUS link, the RADIUS Servers screen appears.•RADIUS Server Addr/Name: The default RADIUS server 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 port 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 65 for more information.

Administrator’s Handbook98Link: SNMPWhen you click the SNMP link, the SNMP conﬁguration page appears.The Simple Network Management Protocol (SNMP) lets a network administrator monitor problems on a net-work 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 Motorola 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 resNatParams, resDslParams, resSecParams – set is supported.)You enter SNMP conﬁguration information on this page. Your network administrator furnishes the SNMP parameters.☛ WARNING:SNMP presents you with a security issue. The community facility of SNMP behaves somewhat like a password. The community “public” is a well-known community name. It could be used to examine the conﬁguration of your Gateway by your service provider or an uninvited reviewer. The information can be read from the Gateway. If you are strongly concerned about security, you may leave the “public” community blank.

99The Notiﬁcation Type pull-down menu allows you to conﬁgure the type of SNMP notiﬁcations that will be generated: •v1 Trap – This selection will generate notiﬁcations containing an SNMPv1 Trap Protocol Data Unit (PDU)•v2 Trap – This selection will generate notiﬁcations containing an SNMPv2 Trap PDU•Inform – This selection will generate notiﬁcations containing an SNMPv2 InformRequest PDU.To send SNMP traps, you must add IP addresses for each trap receiver you want to have. Click the Add button.The IP Trap Entry screen appears.Enter an IP Trap Entry IP address. This is the destination for SNMP trap messages, the IP address of the host acting as an SNMP console.Click the Submit button. Click the Alert icon, and in the resulting page, click the Save and Restart link.

Administrator’s Handbook100Link: IGMP (Internet Group Management Protocol)Multicasting is a method for transmitting large amounts of information to many, but not all, computers over an internet. One common use is to distribute real time voice, video, and data services to the set of computers which have joined a distributed conference. Other uses include updating the address books of mobile computer users in the ﬁeld, or sending out company newsletters to a distribution list.Since a router should not be used as a passive forwarding device, Motorola Netopia® Gateways use a pro-tocol for forwarding multicasting: Internet Group Management Protocol (IGMP).Motorola Netopia® Gateways support IGMP Version 1, Version 2, or, beginning with Motorola Netopia® Firmware Version 7.7, Version 3.See the “Advanced” option in “LAN” on page 49 for more information.IGMP “Snooping” is a feature of Ethernet layer 2 switches that “listens in” on the IGMP conversation between computers and multicast routers. Through this process, it builds a database of where the multi-cast routers reside by noting IGMP general queries used in the querier selection process and by listening to other router protocols.From the host point of view, the snooping function listens at a port level for an IGMP report. The switch then processes the IGMP report and starts forwarding the relevant multicast stream onto the host's port. When the switch receives an IGMP leave message, it processes the leave message, and if appropriate stops the multicast stream to that particular port. Basically, customer IGMP messages although processed by the switch are also sent to the multicast routers.In order for IGMP snooping to function with IGMP Version 3, it must always track the full source ﬁlter state of each host on each group, as was previously done with Version 2 only when Fast Leave support was enabled.IGMP Version 3 supports:IGMP Source Filtering: the ability for group memberships to incorporate source address ﬁltering. This allows “Source-Speciﬁc Multicast” (SSM). By adding source ﬁltering, a Gateway that proxies IGMP can more selec-tively join the speciﬁc multicast group for which there are interested LAN multicast receivers.These features require no user conﬁguration on the Gateway.To conﬁgure IGMP options available in Motorola Netopia® Gateways, click the IGMP link.

101The IGMP page appears.You can set the following options:•IGMP Snooping – checking this checkbox enables the Motorola Netopia® Gateway to “listen in” to IGMP trafﬁc. The Gateway discovers multicast group membership for the purpose of restricting multicast transmissions to only those ports which have requested them. This helps to reduce overall network trafﬁc from streaming media and other bandwidth-intensive IP multicast applications.•Robustness – a way of indicating how sensitive to lost packets the network is. IGMP can recover from robustness minus 1 lost IGMP packet. The default value is 2.•Query Interval– the amount of time in seconds between IGMP General Query messages sent by the querier gate-way. The default query interval is 125 seconds. •Query Response Interval – the maximum amount of time in tenths of a second that the IGMP router waits to receive a response to a General Query message. The default query response interval is 10 seconds and must be less than the query interval.•Unsolicited Report Interval – the amount of time in seconds between repetitions of a particular computer’s initial report of membership in a group. The default unsolicited report interval is 10 seconds.•Querier Version – Select a version of the IGMP Querier from the pull-down menu: v1, v2, or v3. The default v3 allows for backward compatibility mode with the earlier versions, and should not need to be changed. However, for administrative purposes you may select either v1 or v2.•Last Member Query Interval – the amount of time in tenths of a second that the IGMP gateway waits to receive a response to a Group-Speciﬁc Query message. The last member query interval is also the amount of time in seconds between successive Group-Speciﬁc Query messages. The default last mem-ber query interval is 1 second (10 deci-seconds).•Last Member Query Count – the number of Group-Speciﬁc Query messages sent before the gateway assumes that there are no members of the host group being queried on this interface. The default last member query count is 2.•Fast Leave – Checking this checkbox enables a non-standard expedited leave mechanism. The querier keeps track of which client is requesting which channel by IP address. When a leave message is received, the querier can check its internal table to see if there are any more clients on this group. If there are none, it immediately sends an IGMP leave message to the upstream querier. By default, Fast Leave is set to Off.•Log Enable – If you check this checkbox, all IGMP messages on both the LAN and the WAN will be logged.•Wireless Multicast to Unicast conversion – This checkbox only appears if IGMP Snooping is enabled. If you check this checkbox, the Gateway replaces the multicast MAC-address with the physical MAC-address of the wireless client. If there is more than one wireless client interested in the same mul-ticast group, the router will revert to multicasting the stream immediately. When one or more wireless clients leave a group, and the router determines that only a single wireless client is interested in the stream, it will once again unicast the stream.Click the Submit button. Click the Alert icon, and in the resulting page, click the Save and Restart link.

Administrator’s Handbook102Link: UPnPUniversal Plug and Play (UPnP™) is a set of protocols that allows a PC to automatically discover other UPnP devices (anything from an internet gateway device to a light switch), retrieve an XML description of the device and its services, control the device, and subscribe to real-time event notiﬁcation.By default, UPnP is enabled on the Motorola Netopia® Gateway.For Windows XP users, the automatic discovery feature places an icon representing the Motorola Netopia® Gateway automatically in the “My Network Places” folder. Double-clicking this icon opens the Gateway’s web UI.PCs using UPnP can retrieve the Gateway’s WAN IP address, and automatically cre-ate NAT port maps. This means that applications that support UPnP, and are used with a UPnP-enabled Motorola Netopia® Gateway, will not need application layer gateway support on the Motorola Netopia® Gateway to work through NAT.You can disable UPnP, if you are not using any UPnP devices or applications.•Uncheck the UPnP Enabled checkbox, and click the Submit button.•The Alert icon will appear in the upper right corner of the web page. Click the Alert icon, and when prompted, click the Save and Restart link.

103Link: LAN ManagementTR-064 is a LAN-side DSL Gateway conﬁguration speciﬁcation. It is an extension of UPnP. It deﬁnes more services to locally manage the Motorola Netopia® Gateway. While UPnP allows open access to conﬁgure the Gateway's features, TR-064 requires a password to execute any command that changes the Gateway's conﬁguration.TR-064 is enabled by default. To disable it:•Uncheck the Enabled checkbox, and click the Submit button.•The Alert icon will appear in the upper right corner of the web page. Click the Alert icon, and when prompted, click the Save and Restart link.

Administrator’s Handbook104Link: Ethernet BridgeThe Motorola Netopia® Gateway can be used as a bridge, rather than a router. A bridge is a device that joins two networks. As an Internet access device, a bridge connects the home computer directly to the ser-vice provider’s network equipment with no intervening routing functionality, such as Network Address Trans-lation. Your home computer becomes just another address on the service provider’s network. In a DSL connection, the bridge serves simply to convey the digital data information back and forth over your tele-phone lines in a form that keeps it separate from your voice telephone signals.If your service provider’s network is set up to provide your Internet connectivity via bridge mode, you can set your Motorola Netopia® Gateway to be compatible.Bridges let you join two networks, so that they appear to be part of the same physical network. As a bridge for protocols other than TCP/IP, your Gateway keeps track of as many as 512 MAC (Media Access Control) addresses, each of which uniquely identiﬁes an individual host on a network. Your Gateway uses this bridg-ing table to identify which hosts are accessible through which of its network interfaces. The bridging table contains the MAC address of each packet it sees, along with the interface over which it received the packet. Over time, the Gateway learns which hosts are available through its WAN port and/or its LAN port.When conﬁgured in Bridge Mode, the Motorola Netopia® will act as a pass-through device and allow the workstations on your LAN to have public addresses directly on the internet. ☛ NOTE:In this mode the Motorola Netopia® is providing NO ﬁrewall protection as is afforded by NAT. Also, only the workstations that have a public address can access the internet. This can be useful if you have multiple static public IPs on the LAN.Bridging per WAN is supported in conjunction with VLANs – individual WANs can be bridged to the LAN only if the WANs are part of a VLAN. (See “VLAN” on page 107 for more information.) The capability to bridge individual VLANs is supported only if the underlying encapsulation is RFC1483-Bridged (ether-llc).

105Conﬁguring for Bridge Mode1. Browse into the Motorola Netopia® Gateway’s web interface.2. Click on the Conﬁgure button in the upper Menu bar.3. Click on the LAN link.The LAN page appears.4. In the box titled LAN IP Interface (Ethernet 100BT): Make note of the Ethernet IP Address and subnet mask.You can use this address to access the router in the future.5. Click on the Advanced link in the left-hand links toolbar.6. Under the heading of Services, click on the Ether-net Bridge link.The Ethernet Bridge page appears.The appearance of this page varies, depending on your Gateway’s interfaces.7. If available:a. Check the Enable Bridging on Port selection. (This may be Always On.)b. Click Submit.8. If you want the Gateway to do both bridging and routing, check the Enable Concurrent Bridging/Routing checkbox.When this mode is enabled, the Gateway will appear to be a router, but also bridge trafﬁc from the LAN if it has a valid LAN-side address.9. Check the Enable System Bridge checkbox.The window shrinks.

Administrator’s Handbook106b. Click Submit.At this point you should be ready to do the ﬁnal save on the conﬁguration changes you have made. The yellow Alert symbol will appear beneath the Help button on the right-hand end of the menu bar.10. Click on the Alert symbol and you will see whether your changes have been validated.11. If you are satisﬁed with the changes you have made, click Save and Restart in the Save Database box to Apply changes and restart Gateway. You have now conﬁgured your Motorola Netopia® Gateway for bridging, and it will bridge all trafﬁc across the WAN. You will need to make conﬁgurations to your machines on your LAN. These settings must be made in accordance with your ISP. If you ever need to get back into the Motorola Netopia® Gateway again for management reasons, you will need to manually conﬁgure your machine to be in the same subnet as the Ethernet inter face of the Motorola Netopia®, since DHCP server is not operational in bridge mode.

107Link: VLANWhen you click the VLAN link the VLANs page appears.OverviewA Virtual Local Area Network (VLAN) is a network of computers or other devices that behave as if they are connected to the same wire even though they may be physically located on different segments of a LAN. You set up VLANs by conﬁguring the Gateway software rather than hardware. This makes VLANs very ﬂexi-ble. VLANs behave like separate and independent networks.Beginning with Version 7.7.4, VLANs are now strictly layer 2 entities. They can be thought of as virtual Ethernet switches, into which can be added: Ethernet ports, router IP interfaces, ATM PVC/VCC interfaces, SSIDs, and any other physical port such as USB, HPNA, or MOCA. This allows great ﬂexibility on how the components of a system are connected to each other.VLANs are part of Motorola’s VGx Virtual Gateway technology which allows individual port-based VLANs to be treated as separate and distinct “channels.” When data is passed to a Motorola Netopia VGx-enabled broadband gateway, speciﬁc policies, routing, and prioritization parameters can be applied to each individ-ual service, delivering that service to the appropriate peripheral device with the required level of quality of service (QoS). In effect, a single Motorola gateway acts as separate virtual gateways for each distinct ser-vice being delivered.Motorola’s VGx technology maps multiple local VLANs to one or more speciﬁc permanent virtual circuits (PVCs) for DSL, or wide area network VLANs for a ﬁber network. VGx provides service segmentation and QoS controls, service management, and supports delivery of triple play applications: voice for IP Telephony, video for IPTV, and data.Your Gateway supports the following:•Port-based VLANs - these can be used when no trunking is required •Global VLANs - these are used when trunking is required on any port member of the VLAN - Supports 802.1q and 802.1p; both are conﬁgurable •Routed VLANs

Administrator’s Handbook108 - WAN-side VLAN with Multiple WAN IPoE interface support and IP interface-to-VLAN binding - LAN-side VLAN with IP interface-to-VLAN binding - Inter-VLAN routing •Bridged VLANs - these VLANs are used to bridge trafﬁc from LAN to WAN •Prioritization per VLAN and per portEthernet Switching/Policy SetupBefore you conﬁgure any VLANs, the unconﬁgured Gateway is set up as a router composed of a LAN switch, a WAN switch, and a router in the middle, with LAN and WAN IP interfaces connected to their respective switches. These bindings between Ethernet switch ports, IP LAN interface, IP WAN interface and WAN phys-ical ports are automatically created.When you conﬁgure any VLANs, the default bindings are no longer valid, and the system requires explicit binding between IP interfaces and layer 2 inter faces. Each VLAN can be thought of as a layer 2 switch, and enabling each port or interface in a VLAN is analogous to plugging it in to the layer 2 switch.Thereafter, in order for devices to communicate on layer 2, they must be associated in the same VLAN. For devices to communicate at layer 3, the devices must be either on the same VLAN, or on VLANs that have an Inter-VLAN routing group enabled in common.When conﬁguring VLANs you must deﬁne how trafﬁc needs to be forwarded:•If trafﬁc needs to be bridged between LAN and WAN you can create a single VLAN that encompasses the WAN port and LAN ports.•If trafﬁc needs to be routed then you must deﬁne four elements:• LAN-side VLANs• WAN-side VLANs• Associate IP Interfaces to VLANs• Inter-VLAN Routing Groups: conﬁguration of routing between VLANs is done by association of a VLAN to a Routing Group. Trafﬁc will be routed between VLANs within a routing group. The LAN IP Ethernet Interface can be bound to multiple LAN VLANs, but forwarding can be limited between an Ethernet LAN port and a WAN VLAN if you properly conﬁgure Inter-VLAN groups.Inter-VLAN groups are also used to block routing between WAN interfaces. If each WAN IP interface is bound to its own VLAN and if you conﬁgure a different Inter-VLAN group for each WAN VLAN then no rout-ing between WAN IP interfaces is possible. •Example: to route between a VCC and all the LAN ports, which effectively is similar to the default conﬁg-uration without any VLANs:Create a VLAN named "VccWan" consisting of vcc1, ip-vcc1, routing-group 1Create a VLAN named "Lan" consisting of eth0.1, eth0.2, eth0.3, eth0.4, ssid1, ssid2, ssid3, ssid4 (etc.), ip-eth-a, routing-group 1

109An example of multiple VLANs, using a Motorola Netopia® Gateway with VGx managed switch technology, is shown below:A VLAN Model Combining Bridging and RoutingTo conﬁgure VLANs check the Enable checkbox.To create a VLAN select a list item from the main VLAN page and click the Edit button.

Administrator’s Handbook110The VLAN Entry page appears.Check the Enable checkbox, and enter a descriptive name for the VLAN.You can create up to 16 VLANs, and you can also restrict any VLAN, and the computers on it, from adminis-tering the Gateway.•VLAN Name – A descriptive name for the VLAN.•Type – LAN or WAN Port(s) can be enabled on the VLAN. You can choose a type designation as follows:By-Port: indicates that the VLAN is port-based. Trafﬁc sent to this port will be treated as belonging to the VLAN, and will not be forwarded to other ports that are not within a common VLAN segment.Global indicates that the ports joining this VLAN are part of a global 802.1q Ethernet VLAN. This VLAN includes ports on this Router and may include ports within other devices throughout the network. The VID in this case may deﬁne the behavior of trafﬁc between all devices on the network having ports that are members of this VLAN segment.

111•VLAN ID – If you select Global as the VLAN Type, the VLAN ID ﬁeld appears for you to enter a VID. This must be a unique identifying number between 1 and 4094. (A VID of zero (0) is permitted on the Ether-net WAN port only.)•Admin Restricted – If you want to prevent administrative access to the Gateway from this VLAN, check the checkbox.•802.1p Priority Bit: If you set this from the pull-down menu to a value greater than 0, all packets of this VLAN with unmarked priority bits (pbits) will be re-marked to this priority.Click the Submit button.The VLAN Port Conﬁguration screen appears.•Port interfaces available for this VLAN are listed in the left hand column. •Displayed port interfaces vary depending on the kinds of physical ports on your Gateway, for example, Ethernet, USB, and/or wireless.Also, if you have multiple wireless SSIDs deﬁned, these may be displayed as well (See Enable Multiple Wireless IDs on page 59)•For Motorola Netopia® VGx technology models, separate Ethernet switch ports are displayed and may be conﬁgured.To enable any of them on this VLAN, check the associated Enable checkbox(es).Typically you will choose a physical port, such as an Ethernet port (example: eth0.1) or a wireless SSID (example: ssid1).•When you enable an interface, the Tag, Priority, and Promote checkboxes and an 802.1p Priority Bit pull-down menu appear for that interface.

Administrator’s Handbook112Tag – Packets transmitted from this port through this VLAN must be tagged with the VLAN VID. Packets received through this port destined for this VLAN must be tagged with the VLAN VID by the source. The Tag option is only available on Global type ports.Priority – Use any 802.1p priority bits in the VLAN header to prioritize packets within the Gateway’s internal queues, according to DiffServ priority mapping rules. See “Differentiated Services” on page 92 for more information.Promote – Write any 802.1p priority bits into the IP-TOS header bit ﬁeld for received IP packets on this port destined for this VLAN. Write any IP-TOS priority bits into the 802.1p priority bit ﬁeld for tagged IP packets transmitted from this port for this VLAN. All mappings between Ethernet 802.1p and IP-TOS are made according to a pre-deﬁned QoS mapping policy. The pre-deﬁned mapping can now be set in the CLI. See “Queue Conﬁguration” on page 271. See also “Differentiated Services” on page 92 for more information.802.1p Priority Bit – If you set this ﬁeld to a value greater than 0, all packets received on this port with unmarked priority bits (pbits) will be re-marked to this priority. If the port 802.1p PBit is greater than 0, the VLAN 802.1p PBit setting is ignored.•Select an IP Interface for this VLAN if it is to be routed; otherwise leave the default. These selections will vary depending on your IP interfaces. For example, if you have set up multiple VCCs, these will appear in the list as ip-vcc1, ip-vcc2, and so forth.

113•When you select an IP interface, the screen expands to allow you to conﬁgure Inter-Vlan-Groups.Inter-VLAN groups allow VLANs in the group to route trafﬁc to the others; ungrouped VLANs cannot route trafﬁc to each other.•Click the Submit button.•When you are ﬁnished, click the Alert icon in the upper right-hand corner of the screen, and in the resulting screen, click the Save link.•If you want to create more VLANs, click the Advanced link (in the left-hand toolbar) and then the VLAN link in the resulting page, and repeat the process.

Administrator’s Handbook114You can Edit, Clear, Enable, or Disable your VLAN entries by returning to the VLANs page, and selecting the appropriate entry from the displayed list.•When you are ﬁnished, click the Alert icon in the upper right-hand corner of the screen, and in the resulting screen, click the Save and Restart link.To view the settings for each VLAN, select the desired VLAN from the list and click the Details button.

115The screen expands to display the VLAN settings.

Administrator’s Handbook116ExampleThe following is a simple example of how you might conﬁgure some VLANs:You want to conﬁgure a 3347NWG-VGx Gateway with two SSIDs (see “Multiple SSIDs” on page 59 for more information) for two VLANs, allowing both access to the Internet. One SSID will be in the same VLAN as the four ports of the Ethernet Switch, so that those two networks can communicate. The second VLAN will be for the other SSID. The second VLAN will also be denied access to the 3347NWG-VGx web interface and tel-net interface. This setup might be useful if you have a doctor’s ofﬁce or a coffee shop, and you want to keep your customers separated from the rest of the network.1. In the VLANs page, check the Enable checkbox, select VLAN #1 in the VLANs list, and click the Edit button.2. Check the Enable checkbox, and in the VLAN Name box, enter the name you would like.For example, call it Network A.Since this VLAN will be for SSID1 and the Ethernet ports, leave Admin Restricted unchecked. This will give this VLAN access to the Gateway.3. Click the Submit button.4. In the Port Conﬁguration for VLAN:1 page, you add the Port Interfaces you want associ-ated with the VLAN.

117In this case, select all the physical Ethernet ports: eth0.1 through eth0.4, and wireless ssid1. Select ip-eth-a, the IP interface for the group. This will be Inter-Vlan-Group #1. Check the Group-1 checkbox. These ports will be able to communicate with each other.5. Click the Submit button.6. In the VLAN page, select VLAN #2 in the VLANs list, and click the Edit button.The VLAN Name must be given another unique name. For example, call it Network B.Since this is for the second SSID that we don’t want to be given access to the Gateway, check the Admin Restricted checkbox.

Administrator’s Handbook1187. Click the Submit button.8. In the Port Conﬁguration for VLAN: 2 page, you add the Port Interfaces you want asso-ciated with the VLAN.Select the ip-eth-a port interface and check the ssid2 port interface. Make this VLAN a member of Inter-Vlan-Group Group-2.9. Click the Submit button.10. Next, create a VLAN to provide the Inter-Vlan-Groups access to the Internet (WAN).For example, call it WAN VLAN.

119Check the vcc1 checkbox, select the ip-vcc1 IP interface, and check the Inter-Vlan-Group Group-1 and Group-2 checkboxes. Members of Groups 1 and 2 will now be able to communicate with the Internet (WAN), but not with each other.11. Once you have ﬁnished with the conﬁguration of the VLANs, click the Alert icon in the upper right hand corner. This will validate that the settings are legal for your network.12. Click the Save and Restart link.This will restart the Motorola Netopia® Gateway and retain the VLAN conﬁguration.

Administrator’s Handbook120Link: VoIP(supported models only)Voice-over-IP (VoIP) refers to the ability to make voice telephone calls over the Internet. This differs from tra-ditional phone calls that use the Public Switched Telephone Network (PSTN). VoIP calls use an Internet pro-tocol, Session Initiation Protocol (SIP), to transmit sound over a network or the Internet in the form of data packets. Certain Motorola Netopia® Gateway models have two separate voice ports for connecting tele-phone handsets. These models support VoIP. If your Gateway is a VoIP model, you can conﬁgure the VoIP features.When you click the VoIP link, the SIP Line Entry page appears.To enable a VoIP line, select one of the lines from the SIP Line Entry menu that corresponds to the port on the Gateway to which your phone is connected.Click the Edit button. In the resulting screen, check the Enable SIP checkbox.The screen expands to display the features that you can enable for that line.

121SIP Line EntryRegistration Interval (in secs)Length of time the VoIP registration will be valid before it will be renewed. Default is 1 hour.Registrar Server Registration Server name or IP address.Registrar Port Registration Server port. Default is 5060.Proxy Server Proxy server name or IP address.

Administrator’s Handbook122When you are ﬁnished entering the required information, click the Submit button.To conﬁgure the second voice port, return to the SIP Line Entry screen by clicking the VoIP link in the Breadcrumb Trail.When you are ﬁnished, click the Alert icon in the upper right corner of the page, and in the resulting page, click the Save and Restart link.Proxy Port Proxy server port, if required. Default is 5060.Outbound Proxy Server Outbound Proxy server name or IP address, if required.Outbound Proxy Port Outbound Proxy server port, if required. Default is 5060.User Display Name Name of this phone’s user to be displayed on the Home page. Example: “Jacob Q. Smith”SIP User Name Registration user ID. Example: “jqsmith”SIP User Password Registration user password.Auth User ID The authorization ID that authenticates the user to SIP for the speciﬁed phone. Most SIP Servers expect this to be the User Name itself but some may use Auth User ID. Call Features SettingsDTMF Mode Choose the Dual Tone Multi-Frequency Mode:• Inband: Sends the DTMF digits as a normal inband tone.• RFC2833: Sends the DTMF digits as an event as part of the RTP packet header information.• Info: Sends the DTMF digits in the SIP INFO message.Enable End of Dial Marker If you check this checkbox, the Gateway will generate an “end of dial” (#) signal that indicates that the dialed number is complete.Enable Call Fowarding UnconditionallyIf you check this checkbox, all calls will be forwarded to a speci-ﬁed number.The Unconditional Call Fowarding Number ﬁeld will appear for you to enter the number, if enabled.Enable Call Forwarding On BusyIf you check this checkbox, calls will be forwarded to a speciﬁed number if the line is busy.The On Busy Call Fowarding Number ﬁeld will appear for you to enter the number, if enabled.Enable Call Forwarding On No AnswerIf you check this checkbox, calls will be forwarded to a speciﬁed number if there is no answer.The On No Answer Call Fowarding Number ﬁeld will appear for you to enter the number, if enabled.Enable Waiting If you check this checkbox, call waiting is enabled.Enable Conferencing If you check this checkbox, 3-party teleconferencing is enabled.Subscribe for Do Not Dis-turbIf you check this checkbox, the Gateway will reject VoIP calls with-out ringing the phone.Subscribe for MWI If you check this checkbox, Message Waiting Indicator is enabled when new voice mail is received.SIP Line Entry

123The Home page for a VoIP-enabled Gateway with both phone lines registered is shown below.

Administrator’s Handbook124Link: SystemThe System Name defaults to your Gateway's factory identiﬁer combined with its serial number. Some cable-oriented Service Providers use the System Name as an important identiﬁcation and support parame-ter.The System Name can be 1 – 255 characters long; it can include embedded spaces and special charac-ters.The Log Message Level alters the severity at which messages are collected in the Gateway's system log. Do not alter this ﬁeld unless instructed by your Support representative.

125Link: Syslog ParametersYou can conﬁgure a UNIX-compatible syslog client to report a number of subsets of the events entered in the Gateway’s WAN Event History. Syslog sends log-messages to a host that you specify.To enable syslog logging, click on the Syslog Parameters link.Check the Syslog checkbox. The screen expands.•Syslog: Enable syslog logging in the system.•Syslog Host Name/IP Address: Enter the name or the IP Address of the host that should receive sys-log messages.•Facility: From the pull-down menu, select the Syslog facility to be used by the router when generating syslog messages. Options are local0 through local7.•Log Violations: If you check this checkbox, the Gateway will generate messages whenever a packet is discarded because it violates the router's security policy.•Log Access Attempts: If you check this checkbox, the Gateway will generate messages whenever a packet attempts to access the router or tries to pass through the router. This option is disabled by default.•Log Accepted Packets: If you check this checkbox, the Gateway will generate messages whenever a packet accesses the router or passes through the router. This option is disabled by default.☛ NOTE:Syslog needs to be enabled to comply with logging requirements mentioned in The Modular Firewall Certiﬁcation Criteria - Baseline Module - version 4.1 (speciﬁed by ICSA Labs). For more information, please go to the following URL:http://www.icsalabs.com/icsa/docs/html/communities/ﬁrewalls/pdf/4.1/baseline.pdf

Administrator’s Handbook126Log Event MessagesAdministration Related Log Messages1. administrative access attempted:This log-message is generated whenever the user attempts to access the router's management interface.2. administrative access authenticated and allowed:This log-message is generated whenever the user attempts to access the router's management interface and is successfully authenticated and allowed access to the management interface.3. administrative access allowed:If for some reason, a customer does not want password protection for the management interface, this log-message is generated whenever any user attempts to access the router's management interface and is allowed access to the management interface.4. administrative access denied - invalid user name:This log-message is generated whenever the user tries to access the router's management interface and authentication fails due to incor-rect user-name.5. administrative access denied - invalid password:This log-message is generated whenever the user tries to access the router's management interface and authentication fails due to incor-rect password.6. administrative access denied - telnet access not allowed:This log-message is generated whenever the user tries to access the router's Telnet management interface from a Public interface and is not permitted since Remote Management is disabled.7. administrative access denied - web access not allowed:This log-message is generated whenever the user tries to access the router's HTTP management interface from a Public interface and is not permitted since Remote Management is disabled.System Log Messages1. Received NTP Date and Time:This log-message is generated whenever NTP receives Date and time from the server.2. EN: IP up: This log-message is generated whenever Ethernet WAN comes up.3. WAN: Ethernet WAN1 activated at 100000 Kbps:This log-message is generated when the Ethernet WAN Link is up.4. Device Restarted: This log-message is generated when the router has been restarted.DSL Log Messages (most common):1. WAN: Data link activated at <Rate> Kbps (rx/tx)This log message is generated when the DSL link comes up.2.WAN: Data link deactivatedThis log message is generated when the DSL link goes down.3. RFC1483 up This log message is generated when RFC1483 link comes up.4. RFC1483-<WAN-instance>: IP downThis log message is generated when RFC1483 link goes down.

1275. PPP: Channel <ID> up Dialout Proﬁle name: <Proﬁle Name>This log message is generated when a PPP channel comes up.6. PPP-<WAN Instance> down: <Reason>This log message is generated when a PPP channel goes down. The reason for the channel going down is displayed as well.Access-related Log Messages1. permitted: This log-message is generated whenever a packet is allowed to traverse router-interfaces or allowed to access the router itself.2. attempt: This log-message is generated whenever a packet attempts to traverse router-interfaces or attempts to access the router itself.3. dropped - violation of security policy:This log-message is generated whenever a packet, traversing the router or destined to the router itself, is dropped by the ﬁrewall because it violates the expected conditions.4. dropped - invalid checksum:This log-message is generated whenever a packet, traversing the router or destined to the router itself, is dropped because of invalid IP checksum.5. dropped - invalid data length:This log-message is generated whenever a packet, traversing the router or destined to the router itself, is dropped because the IP length is greater than the received packet length or if the length is too small for an IP packet.6. dropped - frag-mented packet:This log-message is generated whenever a packet, traversing the router, is dropped because it is fragmented, stateful inspection is turned ON on the packet's transmit or receive interface, and deny-fragment option is enabled.7. dropped - cannot fragment:This log-message is generated whenever a packet traversing the router is dropped because the packet cannot be sent without frag-mentation, but the do not fragment bit is set.8. dropped - no route found:This log-message is generated whenever a packet, traversing the router or destined to the router itself, is dropped because no route is found to forward the packet.9. dropped - invalid IP version:This log-message is generated whenever a packet, traversing the router or destined to the router itself, is dropped because the IP ver-sion is not 4.10. dropped - possi-ble land attack:This log-message is generated whenever a packet, traversing the router or destined to the router itself, is dropped because the packet is TCP/UDP packet and source IP Address and source port equals the destination IP Address and destination port.11. TCP SYN ﬂood detected:This log-message is generated whenever a SYN packet destined to the router's management interface is dropped because the number of SYN-sent and SYN-receives exceeds one half the number of allow-able connections in the router.12. Telnet receive DoS attack - packets dropped:This log-message is generated whenever TCP packets destined to the router's telnet management interface are dropped due to over-whelming receive data.DSL Log Messages (most common):

Administrator’s Handbook12813. dropped - reas-sembly timeout:This log-message is generated whenever packets, traversing the router or destined to the router itself, are dropped because of reas-sembly timeout.14. dropped - illegal size:This log-message is generated whenever packets, traversing the router or destined to the router itself, are dropped during reassembly because of illegal packet size in a fragment.Access-related Log Messages

129Link: Internal ServersYour Gateway ships with an embedded Web server and support for a Telnet session, to allow ease of use for conﬁguration and maintenance. The default ports of 80 for HTTP and 23 for Telnet may be reassigned. This is necessary if a pinhole is created to support applications using port 80 or 23. See “Pinholes” on page 82. for more information on Pinhole conﬁguration.Web (HTTP) Server Port: To reassign the port number used to access the Motorola Netopia® embedded Web server, change this value to a value greater than 1024. When you next access the embedded Motorola Netopia® Web server, append the IP address with <port number>, (e.g. Point your browser to http://210.219.41.20:8080).Telnet Server Port: To reassign the port number used to access your Motorola Netopia® embedded Telnet server, change this value to a value greater than 1024. When you next access the Motorola Netopia® embedded Telnet server, append the IP address with <port number>, (e.g. telnet 210.219.41.20 2323).You can also use the LAN-side address of the Gateway, 192.168.1.x:8100 to access the web server and 192.168.1.x:2323 to access the telnet server. The value of 0 for an internal server port will disable that server. You can disable Telnet or Web, but not both. If you disabled both ports, you would not be able to reconﬁgure the unit without pressing the reset button.

Administrator’s Handbook130Link: Software HostingSoftware Hosting allows you to host internet applications when NAT is enabled. User(PC) speciﬁes the machine on which the selected software is hosted. You can host different games and software on different PCs.To select the games or software that you want to host for a speciﬁc PC, highlight the name(s) in the box on the left side of the screen. Click the Add button to select the software that will be hosted.To remove a game or software from the hosted list, highlight the game or software you want to remove and click the Remove button.

131List of Supported Games and SoftwareAge of Empires, v.1.0 Age of Empires: The Rise of Rome, v.1.0Age of WondersAsheron's Call Baldur's Gate Battleﬁeld CommunicatorBuddy Phone Calista IP Phone CART Precision Racing, v 1.0Citrix Metaframe/ICA Client Close Combat for Windows 1.0 Close Combat: A Bridge Too Far, v 2.0Close Combat III: The Russian Front, v 1.0Combat Flight Sim: WWII Europe Series, v 1.0Combat Flight Sim 2: WWII Paciﬁc Thr, v 1.0Dark Reign Delta Force (Client and Server) Delta Force 2Diablo II Server Dialpad DNS ServerDune 2000 eDonkey 2000 eMuleF-16, Mig 29 F-22, Lightning 3 Fighter Ace IIFTP GNUtella H.323 compliant (Netmeeting, CUSeeME)Half Life Hellbender for Windows, v 1.0 Heretic IIHexen II Hotline Server HTTPHTTPS ICQ 2001b ICQ OldIMAP Client IMAP Client v.3 Internet PhoneIPSec IPSec IKE Jedi Knight II: Jedi OutcastKali KazaA LimeWireLinks LS 2000 Mech Warrior 3 Mech Warrior 4: VengeanceMedal of Honor Allied Assault Microsoft Flight Simulator 98 Microsoft Flight Simulator 2000Microsoft Golf 1998 Edition, v 1.0Microsoft Golf 1999 Edition Microsoft Golf 2001 EditionMidtown Madness, v 1.0 Monster Truck Madness, v 1.0 Monster Truck Madness 2, v 2.0Motocross Madness 2, v 2.0 Motocross Madness, v 1.0 MSN Game ZoneMSN Game Zone (DX7 an 8 Play)Need for Speed 3, Hot Pursuit Need for Speed, PorscheNet2Phone NNTP Operation FlashPointOutlaws pcAnywhere (incoming) POP-3PPTP Quake II Quake IIIRainbow Six RealAudio Return to Castle Wolfenstein

Administrator’s Handbook132Rename a User(PC)If a PC on your LAN has no assigned host name, you can assign one by clicking the Rename a User(PC) link.To rename a server, select the server from the pull-down menu. Then type a new name in the text box below the pull-down menu. Click the Update button to save the new name.☛ NOTE:The new name given to a server is only known to Software Hosting. It is not used as an identi-ﬁer in other network functions, such as DNS or DHCP.Roger Wilco Rogue Spear ShoutCast ServerSMTP SNMP SSH serverStarCraft Starﬂeet Command StarLancer, v 1.0Telnet TFTP Tiberian Sun: Command and ConquerTimbuktu Total Annihilation Ultima OnlineUnreal Tournament Server Urban Assault, v 1.0 VNC, Virtual Network Comput-ingWestwood Online, Command and ConquerWin2000 Terminal Server XBox Live GamesYahoo Messenger Chat Yahoo Messenger Phone ZNES

133Link: BackupThe purpose of Backup is to provide a recovery mechanism in the event that the primary connection fails. A failure can be either line loss, for example by central site switch failure or physical cable breakage, or loss of end-to-end connectivity. Detection of one of these failures causes the Gateway to switch from using the primary DSL WAN connection to an alternate gateway on the Ethernet LAN. In the event of a loss of primary connectivity you have the option of switching back to the primary circuit automatically once it has recovered its connection.A typical application would be to have a LAN connection from your Gateway to another Gateway that has, for example, another DSL modem or Gateway connection to the Internet, and designating the second gateway as the backup gateway. Should the primary WAN connection fail, trafﬁc would be automatically redirected through your alternate gateway device to maintain Internet connectivity.When you click the Backup link, the Backup Options page appears.Select either manual or automatic from the pull-down menu.•If you choose manual, you will have to switch manually to your alternate gateway in the event of a connection failure.•For fail-over purposes, choose automatic.Manual optionsIf you choose manual, you can also choose Auto Recovery. If you chose Auto Recovery, enter the number of minutes that the system should wait before it assumes that a connection has been re-established. This allows you to be sure that the primary WAN connection is well re-established before the Gateway switches back to it from the backup mode. Minimum value is one minute.•Check the Enable Backup Gateway checkbox.•From the pull-down menu, select the Interface Type to which you want to direct the backup con-nection. If you have deﬁned multiple VCCs, you can choose a secondary one. Otherwise, to backup to an IP device on the LAN, choose IP Address.The screen expands to allow you to enter an IP address of your Backup Gateway.Click the Submit button; click the Alert icon, and in the resulting page, click the Save and Restart link.

Administrator’s Handbook134Once Backup is conﬁgured, a new ﬁeld appears in the Home Page.If your DSL WAN link fails, you can switch to your Backup Gateway by clicking the Force Backup button.Automatic optionsIf you select automatic as your Backup option, the screen expands to allow you to enter additional informa-tion.•Failure Timeout (minutes 1-10) – Enter the number of minutes you want the system to wait before the backup port becomes enabled in the event of primary line failure. This allows you to be sure the WAN connection is not merely brieﬂy interrupted before the gateway switches to backup mode.•Ping Host 1 and Ping Host 2 – Select address or name from the pull-down menu enter IP address(es) or resolvable DNS name(s) that the Gateway will ping.The Gateway will ping both addresses simulta-neously at ﬁve-second intervals, recording the ping responses from each host. The Gateway will proceed into backup mode only if neither of the conﬁgured remote hosts responds.☛ Note:For best results, enter an IP address and not a host name. If a host name is used it may not be resolvable, and may keep the interface down.•While the Gateway is in backup mode, it will continue to ping both hosts via the primary interface. If either host responds to a ping and the Auto Recovery checkbox is checked, the Gateway will revert to the primary interface.•If you chose Auto Recovery, select Recovery Timeout (minutes1-10). Enter the number of minutes you want the system to wait before attempting to switch back to the WAN connection. This allows you to be sure that the WAN connection is well re-established before the gateway switches back to it from the backup mode.•Check the Enable Backup Gateway checkbox

135•From the pull-down menu, select the Interface Type to which you want to direct the backup connection. If you have deﬁned multiple VCCs, you can choose a secondary one. Otherwise, to backup to an IP device on the LAN, choose IP Address.The screen expands to allow you to enter an IP address of your Backup Gateway.Click the Submit button; click the Alert icon, and in the resulting page, click the Save and Restart link.Once Backup is conﬁgured, a new ﬁeld appears in the Home Page.For automatic mode, it should not be necessary to switch to Backup manually. However, you can force a switch to your Backup Gateway by clicking the Force Backup button.

Administrator’s Handbook136Link: Ethernet MAC Override(Only available on models with Ethernet WAN interfaces, such as the 338X-series or VDSL Gateways.)Your Gateway comes with its own MAC (Media Access Control) address, also called the Hardware Address, a 12 character number unique for each LAN-connected device.Your Service Provider, particularly cable service providers, may instruct you to override the default MAC address.If so, check the Enable Override checkbox, and enter the new MAC address in the ﬁeld provided.

137Link: Clear OptionsTo restore the factory conﬁguration of the Gateway, choose Clear Options. You may want to upload your conﬁguration to a ﬁle before performing this function. You can do this using the upload command via the command-line interface. See the upload command on page 238.Clear Options does not clear feature keys or affect the software image.You must restart the Gateway for Clear Options to take effect.

Administrator’s Handbook138Link: Time ZoneWhen you click the Time Zone link, the Time Zone page appears.You can set your local time zone by selecting the number of hours your time zone is distant from Greenwich Mean Time (GMT +12 – -12) from the pull-down menu. This allows you to set the time zone for access con-trols and in general.

139SecurityButton: SecurityThe Security features are available by clicking on the Security toolbar button. Some items of this category do not appear when you log on as User.

Administrator’s Handbook140Link: PasswordsAccess to your Gateway may be controlled through two optional user accounts, Admin and User. When you ﬁrst power up your Gateway, you create a password for the Admin account. The User account does not exist by default. As the Admin, a password for the User account can be entered or existing passwords changed.Create and Change Passwords. You can establish different levels of access security to protect your Motorola Netopia® Gateway settings from unauthorized display or modiﬁcation.•Admin level privileges let you display and modify all settings in the Motorola Netopia® Gateway (Read/Write mode). The Admin level password is created when you ﬁrst access your Gateway.•User level privileges let you display (but not change) settings of the Motorola Netopia® Gateway. (Read Only mode)To prevent anyone from observing the password you enter, characters in the old and new password ﬁelds are not displayed as you type them. To display the Passwords window, click the Security toolbar button on the Home page.Use the following procedure to change existing passwords or add the User password for your Motorola Netopia® Gateway:1. Select the account type from the Username pull-down list.Choose from Admin or User.2. If you assigned a password to the Motorola Netopia® Gateway previously, enter your current password in the Old Password ﬁeld.3. Enter your new password in the New Password ﬁeld.Motorola Netopia®’s rules for a Password are:

141•It can have up to eight alphanumeric characters. •It is case-sensitive. 4. Enter your new password again in the Conﬁrm Password ﬁeld.You conﬁrm the new password to verify that you entered it correctly the ﬁrst time.5. When you are ﬁnished, click the Submit button to store your modiﬁed conﬁguration in the Motorola Netopia® unit’s memory.Password changes are automatically saved, and take effect immediately.

Administrator’s Handbook142Link: FirewallUse a Motorola Netopia® FirewallBreakWater Basic Firewall. BreakWater delivers an easily selectable set of pre-conﬁgured ﬁrewall protection levels. For simple implementation these settings (comprised of three levels) are readily available through Motorola Netopia®’s embedded web server interface.BreakWater Basic Firewall’s three settings are:•ClearSailingClearSailing, BreakWater's default setting, supports both inbound and outbound trafﬁc. It is the only basic ﬁrewall setting that fully interoperates with all other Motorola Netopia® software features. •SilentRunningUsing this level of ﬁrewall protection allows transmission of outbound trafﬁc on pre-conﬁgured TCP/UDP ports. It disables any attempt for inbound trafﬁc to identify the Gateway. This is the Internet equivalent of having an unlisted number.•LANdLockedThe third option available turns off all inbound and outbound trafﬁc, isolating the LAN and disabling all WAN trafﬁc.☛ NOTE: BreakWater Basic Firewall operates independent of the NAT functionality on the Gateway.Conﬁguring for a BreakWater SettingUse these steps to establish a ﬁrewall setting:1. Ensure that you have enabled the BreakWater basic ﬁrewall with the appropriate fea-ture key. See See “Use Motorola Netopia® Software Feature Keys” on page 187. for reference.NOTE: The ﬁrewall is now keyed on by default on the 2200-Series Gateways. 2. Click the Security toolbar button.3. Click Firewall.

1434. Click on the radio button to select the protection level you want. Click Submit. Changing the BreakWater setting does not require a restart to take effect. This makes it easy to change the setting “on the ﬂy,” as your needs change.TIPS for making your BreakWater Basic Firewall Selection Basic Firewall BackgroundAs a device on the Internet, a Motorola Netopia® Gateway requires an IP address in order to send or receive trafﬁc.The IP trafﬁc sent or received have an associated application port which is dependent on the nature of the connection request. In the IP protocol standard the following session types are common applications:By receiving a response to a scan from a port or series of ports (which is the expected behavior according to the IP standard), hackers can identify an existing device and gain a potential opening for access to an internet-connected device.Application Select this Level Other ConsiderationsTypical Internet usage(browsing, e-mail)SilentRunningMulti-player online gamingClearSailing Set Pinholes; once deﬁned, pinholes will be active whenever ClearSailing is set.Restore SilentRunning when ﬁnished.Going on vacation LANdLocked Protects your connection while your away.Finished online use for the dayLANdLocked This protects you instead of disconnecting your Gateway connection.Chatting online or using instant messagingClearSailing Set Pinholes; once deﬁned, pinholes will be active whenever ClearSailing is set.Restore SilentRunning when ﬁnished.•ICMP •HTTP •FTP•SNMP •telnet •DHCP

Administrator’s Handbook144To protect LAN users and their network from these types of attacks, BreakWater offers three levels of increasing protection. The following tables indicate the state of ports associated with session types, both on the WAN side and the LAN side of the Gateway.This table shows how inbound trafﬁc is treated. Inbound means the trafﬁc is coming from the WAN into the WAN side of the Gateway. This table shows how outbound trafﬁc is treated. Outbound means the trafﬁc is coming from the LAN-side computers into the LAN side of the Gateway. Gateway: WAN SideBreakWater Setting >> ClearSailing SilentRunning LANdLockedPort Session Type --------------Port State-----------------------20 ftp data Enabled Disabled Disabled21 ftp control Enabled Disabled Disabled23 telnet external Enabled Disabled Disabled23 telnet Motorola Netopia® serverEnabled Disabled Disabled80 http external Enabled Disabled Disabled80 http Motorola Netopia® server Enabled Disabled Disabled67 DHCP client Enabled Enabled Disabled68 DHCP server Not Applicable Not Applicable Not Applicable161 snmp Enabled Disabled Disabledping (ICMP) Enabled Disabled DisabledGateway: LAN SideBreakWater Setting >> ClearSailing SilentRunning LANdLockedPort Session Type --------------Port State-----------------------20 ftp data Enabled Enabled Disabled21 ftp control Enabled Enabled Disabled23 telnet external Enabled Enabled Disabled23 telnet Motorola Netopia® serverEnabled Enabled Enabled80 http external Enabled Enabled Disabled80 http Motorola Netopia® server Enabled Enabled Enabled67 DHCP client Not Applicable Not Applicable Not Applicable68 DHCP server Enabled Enabled Enabled161 snmp Enabled Enabled Enabledping (ICMP) Enabled Enabled WAN - DisabledLAN -Local Address Only

145☛ NOTE:The Gateway’s WAN DHCP client port in SilentRunning mode is enabled. This feature allows end users to continue using DHCP-served IP addresses from their Service Providers, while hav-ing no identiﬁable presence on the Internet.

Administrator’s Handbook146Link: IPSecWhen you click on the IPSec link, the IPSec conﬁguration screen appears.Your Gateway can support two mechanisms for IPSec tunnels:•IPSec PassThrough supports Virtual Private Network (VPN) clients running on LAN-connected comput-ers. Normally, this feature is enabled.You can disable it if your LAN-side VPN client includes its own NAT interoperability option.Uncheck the Enable IPSec Passthrough checkbox.•SafeHarbour VPN IPSec is a keyed feature that you must purchase. (See “Install Key” on page 187.) It enables Gateway-terminated VPN support.

147SafeHarbour IPSec VPNSafeHarbour VPN IPSec Tunnel provides a single, encrypted tunnel to be terminated on the Gateway, mak-ing a secure tunnel available for all LAN- connected users. This implementation offers the following:•Eliminates the need for VPN client software on individual PCs.•Reduces the complexity of tunnel conﬁguration.•Simpliﬁes the ongoing maintenance for secure remote access.If you have purchased the SafeHarbour IPSec feature key, the IPSec conﬁguration screen offers additional options.A typical SafeHarbour conﬁguration is shown below:

Administrator’s Handbook148Conﬁguring a SafeHarbour VPNUse the following procedure to conﬁgure your SafeHarbour tunnel.1. Obtain your conﬁguration information from your network administrator.The tables “Parameter Descriptions” on page 151 describe the various parameters that may be required for your tunnel. Not all of them need to be changed from the defaults for every VPN tunnel. Consult with your network administrator.2. Complete the Parameter Setup worksheet “IPSec Tunnel Details Parameter Setup Work-sheet” on page 149.The worksheet provides spaces for you to enter your own speciﬁc values. You can print the page for easy reference. IPSec tunnel conﬁguration requires precise parameter setup between VPN devices. The Setup Worksheet (page 149) facilitates setup and assures that the associated variables are identical.

149Table 1: IPSec Tunnel Details Parameter Setup WorksheetParameter Motorola Netopia® Gateway Peer GatewayNamePeer Internal NetworkPeer Internal NetmaskNAT Enable On/OffPAT AddressNegotiation Method Main/AggressiveLocal ID Type IP AddressSubnetHostnameASCIILocal ID Address/ValueLocal ID MaskRemote ID Type IP AddressSubnetHostnameASCIIRemote ID Address/ValueRemote ID MaskPre-Shared Key Type HEXASCIIPre-Shared KeyDH Group 1/2/5PFS Enable Off/OnSA Encrypt Type DES3DESSA Hash Type MD5SHA1Invalid SPI Recovery Off/OnSoft MBytes 1 - 1000000Soft Seconds 60 - 1000000Hard MBytes 1 - 1000000Hard Seconds 60 - 1000000IPSec MTU 100 - 1500 (default)Xauth Enable Off/OnXauth UsernameXauth Password

Administrator’s Handbook1503. Be sure that you have SafeHarbour VPN enabled.SafeHarbour is a keyed feature. See “Install Key” on page 187. for information concerning installing Motorola Netopia® Software Feature Keys.4. Check the Enable SafeHarbour IPSec checkbox.Checking this box will automatically display the SafeHarbour IPSec Tunnel Entry parameters. Enter the initial group of tunnel parameters. Refer to your Setup Worksheet and the “Parameter Descriptions” on page 151 as required.5. Enter the tunnel Name.This parameter does not have to match the peer/remote VPN device. 6. Enter the Peer External IP Address.7. Select the Encryption Protocol from the pull-down menu.8. Select the Authentication Protocol from the pull-down menu.9. Click Add.The Tunnel Details page appears.10.Make the Tunnel Details entries.Enter or select the required settings.Soft MBytes, Soft Seconds, Hard MBytes, and Hard Seconds values do not have to match the peer/remote VPN device.Refer to your “IPSec Tunnel Details Parameter Setup Worksheet” on page 149.)11.Click Update.The Alert button appears.12.Click the Alert button.13.Click Save and Restart.Your SafeHarbour IPSec VPN tunnel is fully conﬁg-ured.

151Parameter DescriptionsThe following tables describe SafeHarbour’s parameters that are used for an IPSec VPN tunnel conﬁgura-tion:Table 2: IPSec Configuration page parametersField DescriptionName The Name parameter refers to the name of the conﬁgured tunnel. This is mainly used as an identiﬁer for the administrator. The Name parameter is an ASCII value and is limited to 31 characters. The tunnel name does not need to match the peer gateway.Peer External IP AddressThe Peer External IP Address is the public, or routable IP address of the remote gateway or VPN server you are establishing the tunnel with.Encryption Protocol Encryption protocol for the tunnel session.Parameter values supported include NONE or ESP.Authentication ProtocolAuthentication Protocol for IP packet header. The three parameter values are None, Encapsulating Security Payload (ESP) and Authentication Header (AH)Key Management The Key Management algorithm manages the exchange of security keys in the IPSec protocol architecture. SafeHarbour supports the standard Inter-net Key Exchange (IKE)Table 3: IPSec Tunnel Details page parametersField DescriptionName The Name parameter refers to the name of the conﬁgured tunnel. This is mainly used as an identiﬁer for the administrator. The Name parameter is an ASCII value and is limited to 31 characters. The tunnel name does not need to match the peer gateway.Peer Internal NetworkThe Peer Internal IP Network is the private, or Local Area Network (LAN) address of the remote gateway or VPN Server you are communicating with. Peer Internal NetmaskThe Peer Internal IP Netmask is the subnet mask of the Peer Internal IP Network.NAT enable Turns NAT on or off for this tunnel.PAT Address If NAT is enabled, this ﬁeld appears. You can specify a Port Address Trans-lation (PAT) address or leave the default all-zeroes (if Xauth is enabled). If you leave the default. the address will be requested from the remote router and dynamically applied to the Gateway.Negotiation MethodThis parameter refers to the method used during the Phase I key exchange, or IKE process. SafeHarbour supports Main or Aggressive Mode. Main mode requires 3 two-way message exchanges while Aggres-sive mode only requires 3 total message exchanges.Local ID type If Aggressive mode is selected as the Negotiation Method, this option appears. Selection options are: IP Address, Subnet, Hostname, ASCIILocal ID Address/ValueIf Aggressive mode is selected as the Negotiation Method, this ﬁeld appears. This is the local (Gateway-side) IP address (or Name Value, if Sub-net or Hostname are selected as the Local ID Type).

Administrator’s Handbook152Local ID Mask If Aggressive mode is selected as the Negotiation Method, and Subnet as the Local ID Type, this ﬁeld appears. This is the local (Gateway-side) sub-net mask.Remote ID Type If Aggressive mode is selected as the Negotiation Method, this option appears. Selection options are: IP Address, Subnet, Hostname, ASCII.Remote ID Address/ValueIf Aggressive mode is selected as the Negotiation Method, this ﬁeld appears. This is the remote (central-ofﬁce-side) IP address (or Name Value, if Subnet or Hostname are selected as the Local ID Type).Remote ID Mask If Aggressive mode is selected as the Negotiation Method, and Subnet as the Remote ID Type, this ﬁeld appears. This is the remote (central-ofﬁce-side) subnet mask.Pre-Shared Key TypeThe Pre-Shared Key Type classiﬁes the Pre-Shared Key. SafeHarbour sup-ports ASCII or HEX typesPre-Shared Key The Pre-Shared Key is a parameter used for authenticating each side. The value can be ASCII or Hex and a maximum of 64 characters. ASCII is case-sensitive.DH Group Difﬁe-Hellman is a public key algorithm used between two systems to determine and deliver secret keys used for encryption. Groups 1, 2 and 5 are supported. PFS Enable Perfect Forward Secrecy (PFS) is used during SA renegotiation. When PFS is selected, a Difﬁe-Hellman key exchange is required. If enabled, the PFS DH group follows the IKE phase 1 DH group.SA Encrypt Type SA Encryption Type refers to the symmetric encryption type. This encryp-tion algorithm will be used to encrypt each data packet. SA Encryption Type values supported include DES and 3DES.SA Hash Type SA Hash Type refers to the Authentication Hash algorithm used during SA negotiation. Values supported include MD5 and SHA1. N/A will display if NONE is chosen for Auth Protocol. Invalid SPI Recovery Enabling this allows the Gateway to re-establish the tunnel if either the Motorola Netopia® Gateway or the peer gateway is rebooted.Soft MBytes Setting the Soft MBytes parameter forces the renegotiation of the IPSec Security Associations (SAs) at the conﬁgured Soft MByte value. The value can be conﬁgured between 1 and 1,000,000 MB and refers to data trafﬁc passed. If this value is not achieved, the Hard MBytes parameter is enforced. This parameter does not need to match the peer gateway.Soft Seconds Setting the Soft Seconds parameter forces the renegotiation of the IPSec Security Associations (SAs) at the conﬁgured Soft Seconds value. The value can be conﬁgured between 60 and 1,000,000 seconds. This param-eter does not need to match the peer gateway.Hard MBytes Setting the Hard MBytes parameter forces the renegotiation of the IPSec Security Associations (SAs) at the conﬁgured Hard MByte value. The value can be conﬁgured between 1 and 1,000,000 MB and refers to data trafﬁc passed. This parameter does not need to match the peer gate-way.Hard Seconds Setting the Hard Seconds parameter forces the renegotiation of the IPSec Security Associations (SAs) at the conﬁgured Hard Seconds value. The value can be conﬁgured between 60 and 1,000,000 seconds This parame-ter does not need to match the peer gateway.Table 3: IPSec Tunnel Details page parameters

153IPSec MTU Some ISPs require a setting of e.g. 1492 (or other value). The default 1500 is the most common and you usually don’t need to change this unless otherwise instructed. Accepted values are from 100 – 1500.This is the starting value that is used for the MTU when the IPSec tunnel is installed. It speciﬁes the maximum IP packet length for the encapsulated AH or ESP packets sent by the router. The MTU used on the IPSec connec-tion will be automatically adjusted based on the MTU value in any received ICMP can't fragment error messages that correspond to IPSec trafﬁc initi-ated from the router. Normally the MTU only requires manual conﬁguration if the ICMP error messages are blocked or otherwise not received by the router.Xauth Enable Extended Authentication (XAuth), an extension to the Internet Key Exchange (IKE) protocol. The Xauth extension provides dual authentication for a remote user’s Motorola Netopia® Gateway to establish a VPN, autho-rizing network access to the user’s central ofﬁce. IKE establishes the tun-nel, and Xauth authenticates the speciﬁc remote user's Gateway. Since NAT is supported over the tunnel, the remote user network can have multi-ple PCs behind the client Gateway accessing the VPN. By using XAuth, net-work VPN managers can centrally control remote user authentication.Xauth Username/PasswordXauth authentication credentials.Table 3: IPSec Tunnel Details page parameters

Administrator’s Handbook154Link: Stateful InspectionAll computer operating systems are vulnerable to attack from outside sources, typically at the operating system or Internet Protocol (IP) layers. Stateful Inspection ﬁrewalls intercept and analyze incoming data packets to determine whether they should be admitted to your private LAN, based on multiple criteria, or blocked. Stateful inspection improves security by tracking data packets over a period of time, examining incoming and outgoing packets. Outgoing packets that request speciﬁc types of incoming packets are tracked; only those incoming packets constituting a proper response are allowed through the ﬁrewall.Stateful inspection is a security feature that prevents unsolicited inbound access when NAT is disabled. You can conﬁgure UDP and TCP “no-activity” periods that will also apply to NAT time-outs if stateful inspection is enabled on the interface. Stateful Inspection parameters are active on a WAN interface only if enabled on your Gateway. Stateful inspection can be enabled on a WAN interface whether NAT is enabled or not.Stateful Inspection Firewall installation procedure☛ NOTE:Installing Stateful Inspection Firewall is mandatory to comply with Required Services Security Policy - Residential Category module - Version 4.1 (speciﬁed by ICSA Labs)For more information please go to the following URL: http://www.icsalabs.com/icsa/docs/html/communities/ﬁrewalls/pdf/4.1/baseline.pdf1. Access the router through the web interface from the private LAN.DHCP server is enabled on the LAN by default.2. The Gateway’s Stateful Inspection feature must be enabled in order to prevent TCP, UDP and ICMP packets destined for the router or the private hosts.This can be done by navigating to Expert Mode -> Security -> Stateful Inspection.•UDP no-activity time-out: The time in seconds after which a UDP session will be terminated, if there is no trafﬁc on the session.•TCP no-activity time-out: The time in seconds after which an TCP session will be terminated, if there is no trafﬁc on the session.

155•DoS Detect: If you check this checkbox, the Gateway will monitor packets for Denial of Service attacks.•Exposed Addresses: The hosts speciﬁed in Exposed Addresses will be allowed to receive inbound traf-ﬁc even if there is no corresponding outbound trafﬁc. This is active only if NAT is disabled on a WAN interface.•Stateful Inspection Options: Enable and conﬁgure stateful inspection on a WAN interface.Exposed AddressesYou can specify the IP addresses you want to expose by clicking the Exposed addresses link.Add, Edit, or delete exposed addresses options are active only if NAT is disabled on a WAN interface. The hosts speciﬁed in exposed addresses will be allowed to receive inbound trafﬁc even if there is no corre-sponding outbound trafﬁc.•Start Address: Start IP Address of the exposed host range.•End Address: End IP Address of the exposed host range•Protocol: Select the Protocol of the trafﬁc to be allowed to the host range from the pull-down menu. Options are Any, TCP, UDP, or TCP/UDP.•Start Port: Start port of the range to be allowed to the host range. The acceptable range is from 1 - 65535•End Port: Protocol of the trafﬁc to be allowed to the host range. The acceptable range is from 1 - 65535

Administrator’s Handbook156You can add more exposed addresses by clicking the Add more Exposed Addresses link. A list of pre-viously conﬁgured exposed addresses appears.Click the Add button to add a new range of exposed addresses.You can edit a previously conﬁgured range by clicking the Edit button, or delete the entry entirely by clicking the Delete button.All conﬁguration changes will trigger the Alert Icon. Click on the Alert icon.This allows you to validate the conﬁguration and reboot the Gateway.Click the Save and Restart link. You will be asked to conﬁrm your choice, and the Gateway will reboot with the new conﬁguration.

157Stateful Inspection OptionsStateful Inspection Parameters are active on a WAN interface only if you enable them on your Gateway.•Stateful Inspection: To enable stateful inspection on this WAN interface, check the checkbox.•Default Mapping to Router: This is disabled by default. This option will allow the router to respond to trafﬁc received on this interface, for example, ICMP Echo requests.☛ NOTE:If Stateful Inspection is enabled on a WAN interface Default Mapping to Router must be enabled to allow inbound VPN terminations to the router.•TCP Sequence Number Difference: Enter a value in this ﬁeld. This value represents the maximum sequence number difference allowed between subsequent TCP packets. If this number is exceeded, the packet is dropped. The acceptable range is 0 – 65535. A value of 0 (zero) disables this check.•Deny Fragments: To enable this option, which causes the router to discard fragmented packets on this interface, check the checkbox. Open Ports in Default Stateful Inspection Installation Port Protocol Description LAN (Private) InterfaceWAN (Public) Interface23 TCP telnet Yes No53 UDP DNS Yes No67 UDP Bootps Yes No68 UDP Bootpc Yes No80 TCP HTTP Yes No137 UDP Netbios-ns Yes No138 UDP Netbios-dgm Yes No161 UDP SNMP Yes No500 UDP ISAKMP Yes No520 UDP Router Yes No

Administrator’s Handbook158Firewall TutorialGeneral ﬁrewall terms☛ Note:Breakwater Basic Firewall (see “BreakWater Basic Firewall” on page 142) does not make use of the packet ﬁlter support and can be used in addition to ﬁltersets Filter rule: A ﬁlter set is comprised of individual ﬁlter rules.Filter set: A grouping of individual ﬁlter rules.Firewall: A component or set of components that restrict access between a protected network and the Internet, or between two networks.Host: A workstation on the network.Packet: Unit of communication on the Internet.Packet ﬁlter: Packet ﬁlters allow or deny packets based on source or destination IP addresses, TCP or UDP ports.Port: A number that deﬁnes a particular type of service.Basic IP packet componentsAll IP packets contain the same basic header information, as follows:This header information is what the packet ﬁlter uses to make ﬁltering decisions. It is important to note that a packet ﬁlter does not look into the IP data stream (the User Data from above) to make ﬁltering deci-sions.Basic protocol typesTCP: Transmission Control Protocol. TCP provides reliable packet delivery and has a retransmission mech-anism (so packets are not lost). RFC 793 is the speciﬁcation for TCP.Source IP Address 163.176.132.18Destination IP Address 163.176.4.27Source Port 2541Destination Port 80Protocol TCPDATA User Data

159UDP: User Datagram Protocol. Unlike TCP, UDP does not guarantee reliable, sequenced packet delivery. If data does not reach its destination, UDP does not retransmit the data. RFC 768 is the speciﬁcation for UDP.There are many more ports deﬁned in the Assigned Addresses RFC. The table that follows shows some of these port assignments.Example TCP/UDP PortsFirewall design rulesThere are two basic rules to ﬁrewall design:•“What is not explicitly allowed is denied.”and•“What is not explicitly denied is allowed.”The ﬁrst rule is far more secure, and is the best approach to ﬁrewall design. It is far easier (and more secure) to allow in or out only certain services and deny anything else. If the other rule is used, you would have to ﬁgure out everything that you want to disallow, now and in the future. Firewall LogicFirewall design is a test of logic, and ﬁlter rule ordering is critical. If a packet is forwarded through a series of ﬁlter rules and then the packet matches a rule, the appropriate action is taken. The packet will not for-ward through the remainder of the ﬁlter rules.For example, if you had the following ﬁlter set...Allow WWW access;Allow FTP access;Allow SMTP access;Deny all other packets.and a packet goes through these rules destined for FTP, the packet would forward through the ﬁrst rule (WWW), go through the second rule (FTP), and match this rule; the packet is allowed through.If you had this ﬁlter set for example....Allow WWW access;TCP Port Service UDP Port Service20/21 FTP 161 SNMP23 Telnet 69 TFTP25 SMTP80 WWW144 News

Administrator’s Handbook160Allow FTP access;Deny FTP access;Deny all other packets.and a packet goes through these rules destined for FTP, the packet would forward through the ﬁrst ﬁlter rule (WWW), match the second rule (FTP), and the packet is allowed through. Even though the next rule is to deny all FTP trafﬁc, the FTP packet will never make it to this rule.Implied rulesWith a given set of ﬁlter rules, there is an Implied rule that may or may not be shown to the user. The implied rule tells the ﬁlter set what to do with a packet that does not match any of the ﬁlter rules. An exam-ple of implied rules is as follows:Example ﬁlter set pageThis is an example of the Motorola Netopia® ﬁlter set page:Implied MeaningY+Y+Y=N If all ﬁlter rules are YES, the implied rule is NO.N+N+N=Y If all ﬁlter rules are NO, the implied rule is YES.Y+N+Y=N If a mix of YES and NO ﬁlters, the implied rule is NO.

161Filter basicsIn the source or destination IP address ﬁelds, the IP address that is entered must be the network address of the subnet. A host address can be entered, but the applied subnet mask must be 32 bits (255.255.255.255).Netopia Embedded Software Version 7.7.4 has the ability to compare source and destination TCP or UDP ports. These options are as follows:Example networkExample ﬁltersExample 1 Incoming packet has the source address of 200.1.1.28Item What it meansNo Compare Does not compare TCP or UDP portNot Equal To Matches any port other than what is deﬁnedLess Than Anything less than the port deﬁnedLess Than or Equal Any port less than or equal to the port deﬁnedEqual Matches only the port deﬁnedGreater Than or Equal Matches the port or any port greaterGreater Than Matches anything greater than the port deﬁnedFilter Rule: 200.1.1.0 (Source IP Network Address)255.255.255.128 (Source IP Mask)Forward = No (What happens on match) DataInternetIP 200.1.1.??Input PacketFilter

Administrator’s Handbook162 This incoming IP packet has a source IP address that matches the network address in the Source IP Address ﬁeld in Netopia Embedded Software Version 7.7.4. This will not forward this packet. Example 2 Incoming packet has the source address of 200.1.1.184.This incoming IP packet has a source IP address that does not match the network address in the Source IP Address ﬁeld in Netopia Embedded Software Version 7.7.4. This rule will forward this packet because the packet does not match. Example 3 Incoming packet has the source address of 200.1.1.184.This rule does not match and this packet will be forwarded. Example 4 Incoming packet has the source address of 200.1.1.104.This rule does match and this packet will not be forwarded. Example 5 Incoming packet has the source address of 200.1.1.96.This rule does match and this packet will not be forwarded. This rule masks off a single IP address.Filter Rule: 200.1.1.0 (Source IP Network Address)255.255.255.128 (Source IP Mask)Forward = No (What happens on match)Filter Rule: 200.1.1.96 (Source IP Network Address)255.255.255.240 (Source IP Mask)Forward = No (What happens on match)Filter Rule: 200.1.1.96 (Source IP Network Address)255.255.255.240 (Source IP Mask)Forward = No (What happens on match)Filter Rule: 200.1.1.96 (Source IP Network Address)255.255.255.255 (Source IP Mask)Forward = No (What happens on match)

163 Link: Packet Filter When you click the Packet Filter link the Filter Sets screen appears.Security should be a high priority for anyone administering a network connected to the Internet. Using packet ﬁlters to control network communications can greatly improve your network’s security. The Packet Filter engine allows creation of a maximum of eight Filter Sets. Each Filter Set can consist of many rules. There can be a maximum of 32 ﬁlter rules in the system. ☛ WARNING: Before attempting to conﬁgure ﬁlters and ﬁlter sets, please read and understand this entire section thoroughly. Motorola Netopia® Gateways incorporating NAT have advanced security features built in. Improperly adding ﬁlters and ﬁlter sets increases the possibility of loss of communication with the Gateway and the Internet. Never attempt to conﬁgure ﬁlters unless you are local to the Gateway.Although using ﬁlter sets can enhance network security, there are disadvantages:• Filters are complex. Combining them in ﬁlter sets introduces subtle interactions, increasing the likelihood of implementation errors.• Enabling a large number of ﬁlters can have a negative impact on performance. Processing of packets will take longer if they have to go through many checkpoints in addition to NAT.• Too much reliance on packet ﬁlters can cause too little reliance on other security methods. Filter sets are not a substitute for password protection, effective safeguarding of passwords, and general awareness of how your network may be vulnerable.Netopia Embedded Software Version 7.7.4’s packet ﬁlters are designed to provide security for the Internet connections made to and from your network. You can customize the Gateway’s ﬁlter sets for a variety of packet ﬁltering applications. Typically, you use ﬁlters to selectively admit or refuse TCP/IP connections from certain remote networks and speciﬁc hosts. You will also use ﬁlters to screen particular types of connec-tions. This is commonly called ﬁrewalling your network.Before creating ﬁlter sets, you should read the next few sections to learn more about how these powerful security tools work. What’s a ﬁlter and what’s a ﬁlter set? A ﬁlter is a rule that lets you specify what sort of data can ﬂow in and out of your network. A particular ﬁlter can be either an input ﬁlter—one that is used on data (packets) coming in to your network from the Inter-net—or an output ﬁlter—one that is used on data (packets) going out from your network to the Internet.A ﬁlter set is a group of ﬁlters that work together to check incoming or outgoing data. A ﬁlter set can consist of a combination of input and output ﬁlters.

Administrator’s Handbook164 How ﬁlter sets work A ﬁlter set acts like a team of customs inspectors. Each ﬁlter is an inspector through which incoming and outgoing packages must pass. The inspectors work as a team, but each inspects every package individu-ally. Each inspector has a speciﬁc task. One inspector’s task may be to examine the destination address of all outgoing packages. That inspector looks for a certain destination—which could be as speciﬁc as a street address or as broad as an entire country—and checks each package’s destination address to see if it matches that destination. A ﬁlter inspects data packets like a customs inspector scrutinizing packages. Filter priority Continuing the customs inspectors analogy, imagine the inspectors lined up to examine a package. If the package matches the ﬁrst inspector’s criteria, the package is either rejected or passed on to its destination, depending on the ﬁrst inspector’s particular orders. In this case, the package is never seen by the remaining inspectors.If the package does not match the ﬁrst inspector’s criteria, it goes to the second inspector, and so on. You can see that the order of the inspectors in the line is very important.For example, let’s say the ﬁrst inspector’s orders are to send along all pack-ages that come from Rome, and the second inspector’s orders are to reject all packages that come from France. If a package arrives from Rome, the ﬁrst inspector sends it along without allowing the second inspector to see it. A package from Paris is ignored by the ﬁrst inspector, rejected by the second inspector, and never seen by the others. A package from London is ignored by the ﬁrst two inspectors, so it’s seen by the third inspector.In the same way, ﬁlter sets apply their ﬁlters in a particular order. The ﬁrst ﬁl-ter applied can forward or discard a packet before that packet ever reaches any of the other ﬁlters. If the ﬁrst ﬁlter can neither forward nor discard the packet (because it cannot match any criteria), the second ﬁlter has a chance to forward or reject it, and so on. Because of this hierarchical structure, each ﬁlter is said to have a priority. The ﬁrst ﬁlter has the highest priority, and the last ﬁlter has the lowest priority.INSPECTORFROM:TO:FROM:TO:FROM:TO:APPROVEDpacketfirstfiltermatch?yesforwarddiscard?to networkdiscard(delete)forwardnoto nextfiltersendor

165 How individual ﬁlters work As described above, a ﬁlter applies criteria to an IP packet and then takes one of three actions: • Forwards the packet to the local or remote network • Blocks (discards) the packet • Ignores the packetA ﬁlter forwards or blocks a packet only if it ﬁnds a match after applying its criteria. When no match occurs, the ﬁlter ignores the packet. A ﬁltering rule The criteria are based on information contained in the packets. A ﬁlter is simply a rule that prescribes cer-tain actions based on certain conditions. For example, the following rule qualiﬁes as a ﬁlter: “Block all Telnet attempts that originate from the remote host 199.211.211.17.” This rule applies to Telnet packets that come from a host with the IP address 199.211.211.17. If a match occurs, the packet is blocked.Here is what this rule looks like when imple-mented as a ﬁlter in Netopia Embedded Software Version 7.7.4: To understand this particular ﬁlter, look at the parts of a ﬁlter. Parts of a ﬁlter A ﬁlter consists of criteria based on packet attributes. A typical ﬁlter can match a packet on any one of the following attributes: • The source IP address and subnet mask (where the packet was sent from) • The destination IP address and subnet mask (where the packet is going) • The TOS bit setting of the packet. Certain types of IP packets, such as voice or multime-dia packets, are sensitive to delays introduced by the network. A delay-sensitive packet is identiﬁed by a special low-latency setting called the TOS bit. It is important for such packets to be received rapidly or the quality of service degrades. • The type of higher-layer Internet protocol the packet is carrying, such as TCP or UDP Port numbers A ﬁlter can also match a packet’s port number attributes, but only if the ﬁlter’s protocol type is set to TCP or UDP, since only those protocols use port numbers. The ﬁlter can be conﬁgured to match the following: • The source port number (the port on the sending host that originated the packet) • The destination port number (the port on the receiving host that the packet is destined for)

Administrator’s Handbook166 By matching on a port number, a ﬁlter can be applied to selected TCP or UDP services, such as Telnet, FTP, and World Wide Web. The following tables show a few common services and their associated port numbers: Port number comparisons A ﬁlter can also use a comparison option to evaluate a packet’s source or destination port number. The comparison options are: • No Compare: No comparison of the port number speciﬁed in the ﬁlter with the packet’s port number. • Not Equal To: For the ﬁlter to match, the packet’s port number cannot equal the port number speciﬁed in the ﬁlter. • Less Than: For the ﬁlter to match, the packet’s port number must be less than the port number speci-ﬁed in the ﬁlter. • Less Than or Equal: For the ﬁlter to match, the packet’s port number must be less than or equal to the port number speciﬁed in the ﬁlter. • Equal: For the ﬁlter to match, the packet’s port number must equal the port number speciﬁed in the ﬁl-ter. • Greater Than: For the ﬁlter to match, the packet’s port number must be greater than the port number speciﬁed in the ﬁlter. • Greater Than or Equal: For the ﬁlter to match, the packet’s port number must be greater than or equal to the port number speciﬁed in the ﬁlter.Other ﬁlter attributesThere are three other attributes to each ﬁlter:•The ﬁlter’s order (i.e., priority) in the ﬁlter set•Whether the ﬁlter is currently active•Whether the ﬁlter is set to forward packets or to block (discard) packetsInternet service TCP port Internet service TCP portFTP 20/21 Finger 79Telnet 23 World Wide Web 80SMTP (mail) 25 News 144Gopher 70 rlogin 513Internet service UDP port Internet service UDP portWho Is 43 TFTP 69World Wide Web 80 who 513SNMP 161

167Putting the parts togetherWhen you display a ﬁlter set, its ﬁlters are displayed as rows in a table:The table’s columns correspond to each ﬁlter’s attributes:•#: The ﬁlter’s priority in the set. Filter number 1, with the highest priority, is ﬁrst in the table.•Fwd: Shows whether the ﬁlter forwards (Yes) a packet or discards (No) it when there’s a match. •Src-IP: The packet source IP address to match.•Src-Mask: The packet source subnet mask to match.•Dst-IP: The packet destination IP address to match.•Dst-Mask: The packet destination IP address to match.•Protocol: The protocol to match. This can be entered as a number (see the table below) or as TCP or UDP if those protocols are used.•Src Port: The source port to match. This is the port on the sending host that originated the packet.•Dst Port: The destination port to match. This is the port on the receiving host for which the packet is intended.•NC: Indicates No Compare, where speciﬁed.Filtering example #1Returning to our ﬁltering rule example from above (see page 165), look at how a rule is translated into a ﬁl-ter. Start with the rule, then ﬁll in the ﬁlter’s attributes:•The rule you want to implement as a ﬁlter is:“Block all Telnet attempts that originate from the remote host 199.211.211.17.”Protocol Number to use Full nameN/A 0 Ignores protocol typeICMP 1 Internet Control Message ProtocolTCP 6 Transmission Control ProtocolUDP 17 User Datagram Protocol

Administrator’s Handbook168•The host 199.211.211.17 is the source of the Telnet packets you want to block, while the destination address is any IP address. How these IP addresses are masked determines what the ﬁnal match will be, although the mask is not displayed in the table that displays the ﬁlter sets (you set it when you create the ﬁlter). In fact, since the mask for the destination IP address is 0.0.0.0, the address for Destination IP address could have been anything. The mask for Source IP address must be 255.255.255.255 since an exact match is desired.• Source IP Address = 199.211.211.17• Source IP address mask = 255.255.255.255• Destination IP Address = 0.0.0.0• Destination IP address mask = 0.0.0.0•Using the tables on page 166, ﬁnd the destination port and protocol numbers (the local Telnet port):• Protocol = TCP (or 6)• Destination Port = 23•The ﬁlter should be enabled and instructed to block the Telnet packets containing the source address shown in step 2:• Forward = uncheckedThis four-step process is how we produced the following ﬁlter from the original rule:

169Filtering example #2Suppose a ﬁlter is conﬁgured to block all incoming IP packets with the source IP address of 200.233.14.0, regardless of the type of connection or its destination. The ﬁlter would look like this:This ﬁlter blocks any packets coming from a remote network with the IP network address 200.233.14.0. The 0 at the end of the address signiﬁes any host on the class C IP network 200.233.14.0. If, for example, the ﬁlter is applied to a packet with the source IP address 200.233.14.5, it will block it.In this case, the mask, must be set to 255.255.255.0. This way, all packets with a source address of 200.233.14.x will be matched correctly, no matter what the ﬁnal address byte is.☛ Note:The protocol attribute for this ﬁlter is Any by default. This tells the ﬁlter to ignore the IP protocol or type of IP packet.Design guidelinesCareful thought must go into designing a new ﬁlter set. You should consider the following guidelines: •Be sure the ﬁlter set’s overall purpose is clear from the beginning. A vague purpose can lead to a faulty set, and that can actually make your network less secure.•Be sure each individual ﬁlter’s purpose is clear.•Determine how ﬁlter priority will affect the set’s actions. Test the set (on paper) by determining how the ﬁlters would respond to a number of different hypothetical packets.•Consider the combined effect of the ﬁlters. If every ﬁlter in a set fails to match on a particular packet, the packet is:• Forwarded if all the ﬁlters are conﬁgured to discard (not forward)• Discarded if all the ﬁlters are conﬁgured to forward• Discarded if the set contains a combination of forward and discard ﬁlters

Administrator’s Handbook170An approach to using ﬁltersThe ultimate goal of network security is to prevent unauthorized access to the network without compromis-ing authorized access. Using ﬁlter sets is part of reaching that goal. Each ﬁlter set you design will be based on one of the following approaches:•That which is not expressly prohibited is permitted.•That which is not expressly permitted is prohibited.It is strongly recommended that you take the latter, and safer, approach to all of your ﬁlter set designs.

Navigation menu