User Guide
Table Of Contents
- Nortel WLAN Security Switch 2300 Series Configuration Guide
- Contents
- How to get Help
- Introducing the Nortel WLAN 2300 System
- Using the Command-Line Interface
- Configuring AAA for Administrative and Local Access
- Configuring and Managing Ports and VLANs
- Configuring and Managing Ports
- Configuring and Managing VLANs
- Managing the Layer 2 Forwarding Database
- Port and VLAN Configuration Scenario
- Configuring and Managing IP Interfaces and Services
- MTU Support
- Configuring and Managing IP Interfaces
- Configuring the System IP Address
- Configuring and Managing IP Routes
- Managing the Management Services
- Configuring and Managing DNS
- Configuring and Managing Aliases
- Configuring and Managing Time Parameters
- Setting the Time Zone
- Configuring the Summertime Period
- Statically Configuring the System Time and Date
- Displaying the Time and Date
- Configuring and Managing NTP
- Adding an NTP Server
- Removing an NTP Server
- Changing the NTP Update Interval
- Resetting the Update Interval to the Default
- Enabling the NTP Client
- Displaying NTP Information
- Managing the ARP Table
- Pinging Another Device
- Logging In to a Remote Device
- Tracing a Route
- IP Interfaces and Services Configuration Scenario
- Configuring SNMP
- Overview
- Configuring SNMP
- Displaying SNMP Information
- Configuring and Managing Mobility Domain Roaming
- Configuring User Encryption
- Configuring AP access points
- AP Overview
- Configuring AP access points
- Specifying the Country of Operation
- Configuring a Template for Automatic AP Configuration
- Configuring AP Port Parameters
- Configuring AP-WSS Security
- Configuring a Service Profile
- Configuring a Radio Profile
- Configuring Radio-Specific Parameters
- Mapping the Radio Profile to Service Profiles
- Assigning a Radio Profile and Enabling Radios
- Disabling or Reenabling Radios
- Displaying AP Information
- Displaying AP Configuration Information
- Displaying a List of Distributed APs
- Displaying a List of Distributed APs that Are Not Configured
- Displaying Connection Information for Distributed APs
- Displaying Service Profile Information
- Displaying Radio Profile Information
- Displaying AP Status Information
- Displaying AP Statistics Counters
- Configuring RF Auto-Tuning
- Wi-Fi Multimedia
- Configuring and Managing Spanning Tree Protocol
- Configuring and Managing IGMP Snooping
- Configuring and Managing Security ACLs
- About Security Access Control Lists
- Creating and Committing a Security ACL
- Mapping Security ACLs
- Modifying a Security ACL
- Using ACLs to Change CoS
- Enabling Prioritization for Legacy Voice over IP
- Security ACL Configuration Scenario
- Managing Keys and Certificates
- Why Use Keys and Certificates?
- About Keys and Certificates
- Creating Keys and Certificates
- Choosing the Appropriate Certificate Installation Method for Your Network
- Creating Public-Private Key Pairs
- Generating Self-Signed Certificates
- Installing a Key Pair and Certificate from a PKCS #12 Object File
- Creating a CSR and Installing a Certificate from a PKCS #7 Object File
- Installing a CA’s Own Certificate
- Displaying Certificate and Key Information
- Key and Certificate Configuration Scenarios
- Configuring AAA for Network Users
- About AAA for Network Users
- AAA Tools for Network Users
- Configuring 802.1X Authentication
- Configuring Authentication and Authorization by MAC Address
- Configuring Web-based AAA
- Configuring Last-Resort Access
- Configuring AAA for Users of Third-Party APs
- Assigning Authorization Attributes
- Overriding or Adding Attributes Locally with a Location Policy
- Configuring Accounting for Wireless Network Users
- Displaying the AAA Configuration
- Avoiding AAA Problems in Configuration Order
- Configuring a Mobility Profile
- Network User Configuration Scenarios
- Configuring Communication with RADIUS
- Managing 802.1X on the WSS Switch
- Managing Sessions
- Managing System Files
- Rogue Detection and Countermeasures
- About Rogues and RF Detection
- Summary of Rogue Detection Features
- Configuring Rogue Detection Lists
- Enabling Countermeasures
- Disabling or Reenabling Active Scan
- Enabling AP Signatures
- Disabling or Reenabling Logging of Rogues
- Enabling Rogue and Countermeasures Notifications
- IDS and DoS Alerts
- Displaying RF Detection Information
- Appendix A: Troubleshooting a WS Switch
- Fixing Common WSS Setup Problems
- Recovering the System Password
- Configuring and Managing the System Log
- Running Traces
- Using Show Commands
- Remotely Monitoring Traffic
- Capturing System Information for Technical Support
- Appendix B: Supported RADIUS Attributes
- Appendix C: Mobility Domain Traffic Ports
- Appendix D: DHCP Server
- Glossary
- Index
- Command Index

552 Rogue Detection and Countermeasures
320657-A
DoS Attacks
When active scan is enabled on APs, WSS Software can detect the following types of DoS attacks:
• RF Jamming—The goal of an RF jamming attack is to take down an entire WLAN by overwhelming the radio
environment with high-power noise. A symptom of an RF jamming attack is excessive interference. If an AP radio
detects excessive interference on a channel, and RF Auto-Tuning is enabled, WSS Software changes the radio to a
different channel.
• Deauthenticate frames—Spoofed deauthenticate frames form the basis for most DoS attacks, and are the basis for
other types of attacks including man-in-the-middle attacks. The source MAC address is spoofed so that clients think
the packet is coming from a legitimate AP. If an AP detects a packet with its own source MAC address, the AP
knows that the packet was spoofed.
• Broadcast deauthenticate frames—Similar to the spoofed deauthenticate frame attack above, a broadcast
deauthenticate frame attack generates spoofed deauthenticate frames, with a broadcast destination address instead
of the address of a specific client. The intent of the attack is to disconnect all stations attached to an AP.
• Disassociation frames—A disassociation frame from an AP instructs the client to end its association with the AP.
The intent of this attack it to disconnect clients from the AP.
• Null probe responses—A client’s probe request frame is answered by a probe response containing a null SSID.
Some NIC cards lock up upon receiving such a probe response.
• Decrypt errors—An excessive number of decrypt errors can indicate that multiple clients are using the same MAC
address. A device’s MAC address is supposed to be unique. Multiple instances of the same address can indicate that
a rogue device is pretending to be a legitimate device by spoofing its MAC address.
• Fake AP—A rogue device sends beacon frames for randomly generated SSIDs or BSSIDs. This type of attack can
cause clients to become confused by the presence of so many SSIDs and BSSIDs, and thus interferes with the
clients’ ability to connect to valid APs. This type of attack can also interfere with RF Auto-Tuning when an AP is
trying to adjust to its RF neighborhood.
• SSID masquerade—A rogue device pretends to be a legitimate AP by sending beacon frames for a valid SSID
serviced by APs in your network. Data from clients that associate with the rogue device can be accessed by the
hacker controlling the rogue device.
• Spoofed AP—A rogue device pretends to be a Nortel AP by sending packets with the source MAC address of the
Nortel AP. Data from clients that associate with the rogue device can be accessed by the hacker controlling the
rogue device.
Note. WSS Software detects a spoofed AP attack based on the fingerprint of
the spoofed AP. Packets from the real AP have the correct signature, while
spoofed packets lack the signature. (See “Enabling AP Signatures” on page 549.)










