User's Manual
Table Of Contents
- Contents
- Contents v
- Figures ix
- Tables xi
- Preface xv
- Appendix A Specifications 157
- Appendix B Factory Configuration 159
- Appendix C CommandLine Syntax 163
- Appendix D Antenna Guidelines 181
- Appendix E CCU/EUM Data Tables 183
- Appendix F Ping Commands 197
- Appendix G SNMP MIB Definitions 199
- Appendix H Operating Statistics 223
- Appendix I IP Plan — Example 241
- Appendix J Acronyms and Glossary 253
- Index 261
- Figures
- Tables
- Preface
- 1 Introduction
- 2 Quick Startup
- 3 Detailed Description
- 4 IP Network Planning
- 5 Radio Network Planning
- 6 Installation/Diagnostic Tools
- 7 Configuring the CCU
- 7.1 CCU and EUM Serial Number, MAC Address, and Station ID
- 7.2 Setting the CCU Password
- 7.3 Configuring the CCU RF Parameters
- 7.4 Configuring CCU IP Parameters
- 7.5 Configuring DHCP Relay
- 7.6 Configuring Port Filtering
- 7.7 Configuring the SNTP/UTC Time Clock
- 7.8 Configuring SNMP
- 7.9 Adding EUMs to the Authorization Table
- 8 Configuring the EUM
- 9 Installing the EUM
- 9.1 Before you Start the EUM Installation
- 9.2 Other EUM Programming Considerations
- 9.3 Installation Overview
- 9.4 Installation Procedures
- 9.4.1 Opening the Box
- 9.4.2 Turning off the End-user’s Cordless Phones
- 9.4.3 Choosing a Location for the EUM and Antenna
- 9.4.4 Connecting the EUM Components
- 9.4.5 Conducting a Preliminary Check of the EUM
- 9.4.6 Positioning the Antenna
- 9.4.7 Mounting the Antenna
- 9.4.8 Connecting the End-user’s PC
- 9.4.9 Obtaining Valid IP Addresses for the End-user’s PC
- 9.4.10 Testing the Data Link
- 9.4.11 Configuring the Browser Application
- 9.4.12 Completing the Installation
- 9.4.13 Baselining the Installation
- 9.4.14 Troubleshooting
- 10 Maintaining the Network
- 11 Monitoring the Network
- 12 Troubleshooting
- 13 Specialized Applications
- Appendix A Specifications
- Appendix B Factory Configuration
- Appendix C CommandLine Syntax
- Appendix D Antenna Guidelines
- Appendix E CCU/EUM Data Tables
- Appendix F Ping Commands
- Appendix G SNMP MIB Definitions
- MIB-II Elements Supported from RFC-1213
- WaveRider CCU Enterprise MIBs
- CCU Base MIB
- CCU General Information Group
- CCU Radio Configuration Group
- CCU Radio Statistics Group
- CCU Radio General Statistics Group
- CCU Radio Driver Statistics Group
- CCU Radio MAC Statistics Group
- CCU Ethernet Statistics Group
- CCU Modem Information MIB
- CCU Registration Information MIB
- CCU Registration Table
- CCU Authorization Information MIB
- CCU Authorization Table
- CCU RFC MIB-II Traps
- WaveRider EUM Enterprise MIBs
- EUM RFC MIB-II Traps
- Appendix H Operating Statistics
- Appendix I IP Plan — Example
- Appendix J Acronyms and Glossary
- Index

4 IP Network Planning
APCD-LM043-4.0 57
4.3 Network Address Translation
The following address translation alternatives are listed for reference purposes. Choose the
best alternative for your system. Your choice depends on the number of available registered
IP addresses. It also depends on the nature of your subscriber base; for example, static NAT
may be required to support some of your business users, but dynamic NAT may be adequate
for most of your home users.
Static NAT
Static NAT maps an unregistered IP address to a registered IP address on a one-to-one basis.
This method of translation is recommended if, for example, end users are using VPN facilities
to access remote applications.
Dynamic NAT
Dynamic NAT maps an unregistered IP address to a registered IP address, taken from a pool
of registered IP addresses. This method of translation is useful when you have a large number
of unregistered users who wish to access the Internet. Depending on the traffic pattern, 10
registered IP addresses may be able to serve 40 end users.
Overloading
Overloading, which is a form of dynamic NAT, maps multiple unregistered IP addresses to a
single registered IP address by using different ports. This technique is also known as port
address translation (PAT), single-address NAT, or port-level multiplexed NAT. PAT greatly
reduces the number of necessary registered IP addresses. When overloading is configured,
the router maintains enough information from higher-level protocols to translate the registered
address back to the unregistered address for traffic inbound from the Internet.