User Manual
Table Of Contents
- Contents
- Chapter 1 About This Manual
- Chapter 2 Introduction
- About the NETGEAR ProSafe 802.11g Wireless Access Point WG302
- Key Features
- AutoCell-The Self-Organizing Wireless Network
- 802.11g Standards-based Wireless Networking
- Autosensing Ethernet Connections with Auto Uplink
- Compatible and Related NETGEAR Products
- System Requirements
- What’s In the Box?
- Hardware Description
- Front Panel
- Rear Panel
- Chapter 3 Basic Installation and Configuration
- Wireless Equipment Placement and Range Guidelines
- Cabling Requirements
- Default Factory Settings
- Understanding WG302 Wireless Security Options
- Installing the WG302 Wireless Access Point
- Logging in to the WG302 Using Its Default IP Address
- Basic IP Settings
- Wireless Settings
- Security Profiles
- Before You Change the SSID and WEP Settings
- Setting up and Testing Basic Wireless Connectivity
- Configuring the Radius Server Settings
- Configuring Network Authentication
- Entering WEP Data Encryption Keys
- Restricting Wireless Access by MAC Address
- Chapter 4 Management
- Remote Management
- Using the Secure Telnet Interface
- How to Use the CLI via the Console Port
- CLI Commands
- SNMP Remote Management
- Viewing the Activity Log
- Viewing General Information
- Viewing Statistics
- Viewing the Available Wireless Station List
- Upgrading the Wireless Access Point Firmware
- Configuration File Management
- Backing up and Restoring the Configuration
- Erasing the Configuration
- Using the Reset Button to Restore Factory Default Settings
- Changing the Administrator Password
- AutoCell Rogue AP Detection
- AutoCell Rogue Station Detection
- Chapter 5 Advanced Configuration
- Understanding Advanced IP Settings for Wireless Clients
- Configuring Advanced Wireless LAN Settings
- AutoCell Overview
- AutoCell Configuration Options
- Auto RF Management
- Wi-Fi Multimedia (WMM) Setup
- Hotspot Settings
- Configuring Wireless LAN Parameters
- Wireless Bridging and Repeating
- Point-to-Point Bridge Configuration
- Multi-Point Bridge Configuration
- Repeater with Wireless Client Association
- Configuring NAT
- Configuring QoS Queues
- Setting up Guest Access
- Chapter 6 Troubleshooting
- No lights are lit on the access point.
- The Wireless LAN activity light does not light up.
- The LAN light is not lit.
- I cannot access the Internet or the LAN with a wireless capable computer.
- I cannot connect to the WG302 to configure it.
- When I enter a URL or IP address I get a timeout error.
- Using the Reset Button to Restore Factory Default Settings
- Appendix B Wireless Networking Basics
- Wireless Networking Overview
- Infrastructure Mode
- Ad Hoc Mode (Peer-to-Peer Workgroup)
- Network Name: Extended Service Set Identification (ESSID)
- Authentication and WEP Data Encryption
- 802.11 Authentication
- Open System Authentication
- Shared Key Authentication
- Overview of WEP Parameters
- Key Size
- WEP Configuration Options
- Wireless Channels
- WPA and WPA2 Wireless Security
- How Does WPA Compare to WEP?
- How Does WPA Compare to WPA2 (IEEE 802.11i)?
- What are the Key Features of WPA and WPA2 Security?
- Is WPA/WPA2 Perfect?
- Product Support for WPA/WPA2
- Appendix C Command Line Reference
Command Line Reference C-1
v0.1, December 2005
Appendix C
Command Line Reference
In addition to the Web based user interface, the NETGEAR ProSafe 802.11g Wireless Access
Point WG302 includes a command line interface (CLI) for administering the access point. The
CLI lets you view and modify status and configuration information.
The following topics provide an introduction to the class structure upon which the CLI is based,
CLI commands, and examples of using the CLI to get or set configuration information on an
access point or cluster of APs:
•
“Configurable CLI and Web UI Settings Comparison”
• “Quick View of Commands and How to Get Help”
• “Keyboard Shortcuts and Tab Completion Help”
Configurable CLI and Web UI Settings Comparison
The command line interface (CLI) and the Web user interface (UI) to the WG302 Wireless Access
Point are designed to suit the preferences and requirements for different types of users or
scenarios. Most administrators will probably use both UIs in different contexts. Some features
(such as Clustering) can only be configured from the Web UI and, conversely, some details and
more complex configurations are only available through the CLI.
The CLI is particularly useful in that it provides an interface to which you can write programmatic
scripts for AP configurations. Also, the CLI can be made available through a serial port, so it can
be used even if the network connection is not functioning. Finally, the CLI may be less
resource-intensive than a Web interface.