D-Link DSR 150, DSR 150N, DSR 250, DSR 250N, DSR 500, DSR 500N, DSR 1000, DSR 1000N Router User manual

Add to My manuals
317 Pages

Below you will find brief information for DSR 150, DSR 150N, DSR 250, DSR 250N, DSR 500, DSR 500N. This document will provide you with a comprehensive overview of the device. You can get a better perspective of different features that routers provide, and the advantages of each particular configuration. You will be guided through various settings and how to make adjustments to meet your needs.

advertisement

DSR Series Unified Services Router User Manual | Manualzz

User Manual

Unified Services Router

D-Link Corporation

Copyright © 2014 http://www.dlink.com

Unified Services Router

User Manual

User Manual

DSR-150 / 150N / 250 / 250N

DSR-500 / 500N / 1000 / 1000N

Unified Services Router

Version 2.02

Copyright © 2014

Copyright Notice

This publication, including all photographs, illustrations and software, is protected under international copyright laws, with all rights reserved. Neither this manual, nor any of the material contained herein, may be reproduced without written consent of the author.

Disclaimer

The information in this document is subject to change without notice. The manufacturer makes no representations or warranties with respect to the contents hereof and specifically disclaim any implied warranties of merchantability or fitness for any particular purpose. The manufacturer reserves the right to revise this publication and to make changes from time to time i n the content hereof without obligation of the manufacturer to notify any person of such revision or changes.

Limitations of Liability

UNDER NO CIRCUMSTANCES SHALL D -LINK OR ITS SUPPLIERS BE LIABLE FOR

DAMAGES OF ANY CHARACTER (E.G. DAMAGES FOR LOSS OF PR OFIT, SOFTWARE

RESTORATION, WORK STOPPAGE, LOSS OF SAVED DATA OR ANY OTHER

COMMERCIAL DAMAGES OR LOSSES) RESULTING FROM THE APPLICATION OR

IMPROPER USE OF THE D-LINK PRODUCT OR FAILURE OF THE PRODUCT, EVEN IF D -

LINK IS INFORMED OF THE POSSIBILITY OF SUCH D AMAGES. FURTHERMORE, D-

LINK WILL NOT BE LIABLE FOR THIRD -PARTY CLAIMS AGAINST CUSTOMER FOR

LOSSES OR DAMAGES. D-LINK WILL IN NO EVENT BE LIABLE FOR ANY DAMAGES IN

EXCESS OF THE AMOUNT D-LINK RECEIVED FROM THE END-USER FOR THE

PRODUCT.

1

Unified Services Router

User Manual

Table of Contents

Chapter 1.

Introduction ........................................................................................................................... 11

1.1

About this User Manual

.......................................................................................... 12

1.2

Typographical Conventions

................................................................................... 12

Chapter 2.

Configuring Your Network: LAN Setup ............................................................................. 13

2.1

LAN Configuration

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

2.1.1

LAN DHCP Reserved IPs ...................................................................................... 17

2.1.2

LAN DHCP Leased Clients .................................................................................... 19

2.1.3

LAN Configuration in an IPv6 Network

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

2.1.4

Configuring IPv6 Router Advertisements ............................................................ 21

2.2

VLAN Configuration

................................................................................................ 25

2.2.1

Associating VLANs to ports ................................................................................... 27

2.2.2

Multiple VLAN Subnets

.......................................................................................... 30

2.2.3

VLAN configuration

................................................................................................. 31

2.3

Configurable Port: DMZ Setup

.............................................................................. 32

2.4

Universal Plug and Play (UPnP)

........................................................................... 35

2.5

Captive Portal .......................................................................................................... 36

2.5.1

Captive Portal Setup

............................................................................................... 37

2.5.2

Captive Portals on a VLAN .................................................................................... 41

Chapter 3.

Connecting to the Internet: WAN Setup ........................................................................... 43

3.1

Internet Setup Wizard ............................................................................................. 43

3.2

WAN Configuration

................................................................................................. 46

3.2.1

WAN Port IP address ............................................................................................. 47

3.2.2

WAN DNS Servers

................................................................................................. 47

3.2.3

DHCP WAN

............................................................................................................. 48

3.2.4

PPPoE ...................................................................................................................... 48

3.2.5

Russia L2TP and PPTP WAN

............................................................................... 51

3.2.6

Russia Dual Access PPPoE

.................................................................................. 52

3.2.7

WAN Configuration in an IPv6 Network ............................................................... 56

3.2.8

Checking WAN Status

............................................................................................ 58

3.2.9

VLAN ON WAN

....................................................................................................... 59

3.3

Bandwidth Controls

................................................................................................. 60

3.3.1

Bandwidth Controls in Bridge Mode

..................................................................... 63

3.4

Features with Multiple WAN Links

........................................................................ 66

3.4.1

Auto Failover ............................................................................................................ 66

3.4.2

Load Balancing ........................................................................................................ 67

3.4.3

Protocol Bindings

.................................................................................................... 68

3.4.4

IP Aliasing

................................................................................................................ 69

3.5

Routing Configuration

............................................................................................. 71

3.5.1

Routing Mode .......................................................................................................... 71

3.5.2

Dynamic Routing (RIP)

.......................................................................................... 73

3.5.3

Static Routing

.......................................................................................................... 73

3.5.4

OSPFv2 .................................................................................................................... 75

3.5.5

OSPFv3 .................................................................................................................... 77

3.5.6

6to4 Tunneling

......................................................................................................... 79

3.5.7

ISATAP Tunnels ...................................................................................................... 80

3.6

Configurable Port - WAN Option

.......................................................................... 82

2

Unified Services Router

User Manual

3.7

WAN3 (3G) Configuration ...................................................................................... 82

3.8

WAN Port Settings .................................................................................................. 84

Chapter 4.

Wireless Access Point Setup

............................................................................................. 86

4.1

Wireless Settings Wizard

....................................................................................... 86

4.1.1

Wireless Network Setup Wizard

........................................................................... 89

4.1.2

Add Wireless Device with WPS ............................................................................ 89

4.1.3

Manual Wireless Network Setup .......................................................................... 90

4.2

Wireless Profiles ..................................................................................................... 90

4.2.1

WEP Security

.......................................................................................................... 91

4.2.2

WPA or WPA2 with PSK

........................................................................................ 92

4.3

Creating and Using Access Points

....................................................................... 93

4.3.1

Primary benefits of Virtual APs:

............................................................................ 97

4.4

Tuning Radio Specific Settings

............................................................................. 97

4.5

WMM

......................................................................................................................... 98

4.6

Wireless distribution system (WDS)

................................................................... 100

4.7

Advanced Wireless Settings ................................................................................ 101

4.8

Wi-Fi Protected Setup (WPS) ............................................................................. 102

Chapter 5.

Securing the Private Network .......................................................................................... 105

5.1

Firewall Rules ........................................................................................................ 105

5.2

Defining Rule Schedules ..................................................................................... 106

5.3

Configuring Firewall Rules

................................................................................... 108

5.4

Configuring IPv6 Firewall Rules

.......................................................................... 113

5.4.1

Firewall Rule Configuration Examples

............................................................... 115

5.5

Security on Custom Services

.............................................................................. 119

5.6

ALG support

........................................................................................................... 121

5.7

VPN Passthrough for Firewall ............................................................................. 122

5.8

Bridge Mode Firewall ............................................................................................ 123

5.9

Application Rules .................................................................................................. 125

5.10

Web Content Filtering

........................................................................................... 126

5.10.1

Static Content Filtering ......................................................................................... 127

5.10.2

Approved URLs

..................................................................................................... 127

5.10.3

Blocked Keywords

................................................................................................ 128

5.10.4

Export Web Filter .................................................................................................. 129

5.10.5

Dynamic WCF ....................................................................................................... 130

5.11

IP/MAC Binding ..................................................................................................... 132

5.12

Intrusion Prevention (IPS) .................................................................................... 133

5.13

Protecting from Internet Attacks

......................................................................... 134

5.14

IGMP Proxy to manage multicast traffic

............................................................ 136

Chapter 6.

IPsec / PPTP / L2TP VPN ................................................................................................ 137

6.1

VPN Wizard

........................................................................................................... 138

6.2

Configuring IPsec Policies

................................................................................... 141

6.2.1

Extended Authentication (XAUTH) ..................................................................... 145

6.2.2

Internet over IPsec tunnel .................................................................................... 145

6.3

Configuring VPN clients ....................................................................................... 146

3

Unified Services Router

User Manual

6.4

PPTP / L2TP Tunnels ........................................................................................... 146

6.4.1

PPTP Tunnel Support

.......................................................................................... 146

6.4.2

L2TP Tunnel Support ........................................................................................... 148

6.5

GRE Tunnel Support ............................................................................................ 151

6.6

OpenVPN Support

................................................................................................ 153

6.6.1

OpenVPN Remote Network ................................................................................ 154

6.6.2

OpenVPN Authentication ..................................................................................... 155

Chapter 7.

SSL VPN

............................................................................................................................. 157

7.1

Groups and Users

................................................................................................. 159

7.1.1

Users and Passwords

.......................................................................................... 165

7.1.2

Adding many users to the Local User Database .............................................. 166

7.2

Using SSL VPN Policies

...................................................................................... 168

7.2.1

Using Network Resources ................................................................................... 170

7.3

Application Port Forwarding

................................................................................ 171

7.4

SSL VPN Client Configuration

............................................................................ 174

7.5

User Portal

............................................................................................................. 177

7.5.1

Creating Portal Layouts ....................................................................................... 177

Chapter 8.

Advanced Configuration Tools ......................................................................................... 180

8.1

USB Device Setup ................................................................................................ 180

8.2

USB share port ...................................................................................................... 181

8.3

SMS service

........................................................................................................... 183

8.4

External Authentication

........................................................................................ 184

8.4.1

POP3 Server

.......................................................................................................... 184

8.4.2

NT Domain Server ................................................................................................ 186

8.4.3

RADIUS Server

..................................................................................................... 187

8.4.4

Active Directory Server

........................................................................................ 189

8.4.5

LDAP Server .......................................................................................................... 190

8.5

Authentication Certificates ................................................................................... 191

8.6

Advanced Switch Configuration

.......................................................................... 194

8.7

Package Manager

................................................................................................. 194

Chapter 9.

Administration & Management ......................................................................................... 198

9.1

Configuration Access Control

.............................................................................. 198

9.1.1

Admin Settings ...................................................................................................... 199

9.1.2

License Updates ................................................................................................... 200

9.1.3

Remote Management

........................................................................................... 201

9.1.4

CLI Access ............................................................................................................. 203

9.2

SNMP Configuration

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

9.3

Configuring Time Zone and NTP

........................................................................ 205

9.4

Log Configuration

.................................................................................................. 206

9.4.1

Defining What to Log

............................................................................................ 206

9.4.2

Sending Logs to E-mail or Syslog ...................................................................... 209

9.4.3

Event Log Viewer in GUI

..................................................................................... 211

9.5

Backing up and Restoring Configuration Settings ........................................... 212

9.6

Generating DBGLOGs ......................................................................................... 214

9.7

Upgrading Router Firmware

................................................................................ 214

4

Unified Services Router

User Manual

9.8

Upgrading Router Firmware via USB ................................................................. 215

9.9

Dynamic DNS Setup ............................................................................................. 216

9.10

Using Diagnostic Tools ........................................................................................ 217

9.10.1

Ping

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

9.10.2

Trace Route

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

9.10.3

DNS Lookup .......................................................................................................... 220

9.10.4

Router Options ...................................................................................................... 220

9.11

Localization ............................................................................................................ 221

Chapter 10.

Router Status and Statistics

............................................................................................. 222

10.1

System Overview .................................................................................................. 222

10.1.1

Device Status

........................................................................................................ 222

10.1.2

Resource Utilization

.............................................................................................. 225

10.2

Traffic Statistics

..................................................................................................... 227

10.2.1

Wired Port Statistics

............................................................................................. 227

10.2.2

Wireless Statistics

................................................................................................. 227

10.3

Active Connections ............................................................................................... 228

10.3.1

Sessions through the Router

............................................................................... 228

10.3.2

Wireless Clients

..................................................................................................... 228

10.3.3

LAN Clients ............................................................................................................ 229

10.3.4

Active VPN Tunnels

.............................................................................................. 229

Chapter 11.

Trouble Shooting

................................................................................................................ 233

11.1

Internet connection

............................................................................................... 233

11.2

Date and time ........................................................................................................ 235

11.3

Pinging to Test LAN Connectivity ....................................................................... 235

11.3.1

Testing the LAN path from your PC to your router

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

11.3.2

Testing the LAN path from your PC to a remote device

................................. 236

11.4

Restoring factory-default configuration settings

............................................... 237

Chapter 12.

Credits ................................................................................................................................. 239

Appendix A.

Glossary .............................................................................................................................. 240

Appendix B.

Factory Default Settings

................................................................................................... 243

Appendix C.

Standard Services Available for Port Forwarding & Firewall Configuration .............. 244

Appendix D.

Log Output Reference ....................................................................................................... 245

Appendix E.

RJ-45 Pin-outs

.................................................................................................................... 300

Appendix F.

New Wi Fi Frequency table ( New appendix section )

................................................. 301

Appendix G.

Product Statement ............................................................................................................. 304

5

Unified Services Router

User Manual

List of Figures

Figure 1: Setup page for LAN TCP/IP settings (a) ................................................................................ 16

Figure 2: Setup page for LAN TCP/IP settings (b)

................................................................................ 16

Figure 3: LAN DHCP Reserved IPs

......................................................................................................... 18

Figure 4: LAN DHCP Leased Clients ...................................................................................................... 19

Figure 5: IPv6 LAN and DHCPv6 configuration ..................................................................................... 20

Figure 6: Configuring the Router Advertisement Daemon

................................................................... 23

Figure 7: IPv6 Advertisement Prefix settings

......................................................................................... 25

Figure 8: Adding VLAN memberships to the LAN ................................................................................. 27

Figure 9: Port VLAN list

............................................................................................................................. 29

Figure 10: Configuring VLAN membership for a port

............................................................................ 30

Figure 11: Multiple VLAN Subnets ........................................................................................................... 31

Figure 12: VLAN Configuration

................................................................................................................. 32

Figure 13: DMZ configuration

................................................................................................................... 34

Figure 14: UPnP Configuration ................................................................................................................. 36

Figure 15: Active Runtime sessions

........................................................................................................ 37

Figure 16: Captive Portal Profile List

....................................................................................................... 38

Figure 17: Customized Captive Portal Setup ......................................................................................... 39

Figure 18: Blocking specific clients by their MAC address

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

Figure 19: VLAN based configuration of Captive Portals

..................................................................... 42

Figure 20: Internet Connection Setup Wizard ........................................................................................ 44

Figure 21: Manual WAN configuration ..................................................................................................... 48

Figure 22: PPPoE configuration for standard ISPs

............................................................................... 49

Figure 23: WAN configuration for Japanese Multiple PPPoE (part 1) ................................................ 50

Figure 24: WAN configuration for Japanese Multiple PPPoE (part 2)(its in figure 22 itself) ........... 51

Figure 25: Russia L2TP ISP configuration

.............................................................................................. 52

Figure 26: Russia Dual access PPPoE configuration

........................................................................... 53

Figure 27: IPv6 WAN Setup page ............................................................................................................ 57

Figure 28: Connection Status information for both WAN ports

............................................................ 59

Figure 29: Enabling VLAN on WAN ......................................................................................................... 60

Figure 30: List of Configured Bandwidth Profiles ................................................................................... 61

Figure 31: Bandwidth Profile Configuration

............................................................................................ 62

Figure 32: Traffic Selector Configuration

................................................................................................ 63

Figure 33: Bridge Bandwidth Profile Configuration ................................................................................ 65

Figure 34: Bridge Traffic Selector Configuration

.................................................................................... 65

6

Unified Services Router

User Manual

Figure 35: Load Balancing is available when multiple WAN ports are configured and Protocol

Bindings have been defined

................................................................................................... 68

Figure 36: Protocol binding setup to associate a service and/or LAN source to a WAN and/or destination network .................................................................................................................. 69

Figure 37: Configuring the IP Alias

.......................................................................................................... 69

Figure 38: IP Alias Configuration

.............................................................................................................. 70

Figure 39: Routing Mode to determine traffic routing between WAN and LAN ................................. 72

Figure 40: Static route configuration fields

............................................................................................. 75

Figure 41: OSPFv2 configured parameters

............................................................................................ 76

Figure 42: OSPFv2 configuration ............................................................................................................. 77

Figure 43: OSPFv3 configured parameters ............................................................................................ 78

Figure 44: OSPFv3 configuration

............................................................................................................. 79

Figure 45: 6 to 4 tunneling ......................................................................................................................... 79

Figure 46: ISATAP Tunnels Configuration

.............................................................................................. 81

Figure 47: WAN3 configuration for 3G internet

...................................................................................... 83

Figure 48: Physical WAN port settings .................................................................................................... 85

Figure 49: Wireless Network Setup Wizards .......................................................................................... 87

Figure 50: List of Available Profiles shows the options available to secure the wireless link

......... 91

Figure 51: Profile configuration to set network security ........................................................................ 92

Figure 52: Virtual AP configuration .......................................................................................................... 94

Figure 53: List of configured access points (Virtual APs) shows one enabled access point on the radio, broadcasting its SSID

................................................................................................... 96

Figure 54: Radio card configuration options ........................................................................................... 98

Figure 55: Wi-Fi Multimedia

...................................................................................................................... 99

Figure 56: Wireless Distribution System

............................................................................................... 100

Figure 57: Advanced Wireless communication settings ..................................................................... 102

Figure 58: WPS configuration for an AP with WPA/WPA2 profile

..................................................... 103

Figure 59: List of Available Firewall Rules

............................................................................................ 106

Figure 60: List of Available Schedules to bind to a firewall rule ........................................................ 107

Figure 61: Example where an outbound SNAT rule is used to map an external IP address

(209.156.200.225) to a private DMZ IP address (10.30.30.30)

...................................... 111

Figure 62: The firewall rule configuration page allows you to define the To/From zone, service, action, schedules, and specify source/destination IP addresses as needed.

............... 112

Figure 63: The IPv6 firewall rule configuration page allows you to define the To/From zone, service, action, schedules, and specify source/destination IP addresses as needed.

114

Figure 64: List of Available IPv6 Firewall Rules ................................................................................... 115

Figure 65: Schedule configuration for the above example.

................................................................ 118

Figure 66: List of user defined services.

............................................................................................... 120

7

Unified Services Router

User Manual

Figure 67: Custom Services configuration ............................................................................................ 120

Figure 68: Available ALG support on the router.

.................................................................................. 122

Figure 69: Passthrough options for VPN tunnels ................................................................................. 123

Figure 70: List of Configured Firewall Rules for the Bridge

................................................................ 124

Figure 71: Bridge Firewall Rule configuration

...................................................................................... 124

Figure 72: List of Available Application Rules showing 4 unique rules ............................................ 126

Figure 73: Content Filtering used to block access to proxy servers and prevent ActiveX controls from being downloaded

......................................................................................................... 127

Figure 74: Two trusted domains added to the Approved URLs List

................................................. 128

Figure 75: One keyword added to the block list ................................................................................... 129

Figure 76: Export Approved URL list

..................................................................................................... 130

Figure 77: Dynamic WCF

........................................................................................................................ 130

Figure 78: The following example binds a LAN host’s MAC Address to an IP address served by

DSR. If there is an IP/MAC Binding violation, the violating packet will be dropped and logs will be captured

.............................................................................................................. 132

Figure 79: Intrusion Prevention features on the router ....................................................................... 134

Figure 80: Protecting the router and LAN from internet attacks ........................................................ 135

Figure 81: Enabling IGMP Proxy for the LAN

....................................................................................... 136

Figure 82: Example of Gateway-to-Gateway IPsec VPN tunnel using two DSR routers connected to the Internet .......................................................................................................................... 137

Figure 83: Example of three IPsec client connections to the internal network through the DSR

IPsec gateway

........................................................................................................................ 138

Figure 84: VPN Wizard launch screen .................................................................................................. 139

Figure 85: IPsec policy configuration

..................................................................................................... 142

Figure 86: IPsec policy configuration continued (Auto policy via IKE)

.............................................. 144

Figure 87: IPsec policy configuration continued (Auto / Manual Phase 2) ...................................... 145

Figure 88: PPTP tunnel configuration

– PPTP Client

.......................................................................... 147

Figure 89: PPTP VPN connection status

.............................................................................................. 147

Figure 90: PPTP tunnel configuration

– PPTP Server

........................................................................ 148

Figure 91: L2TP tunnel configuration

– L2TP Server

.......................................................................... 149

Figure 92: L2TP tunnel configuration

– L2TP Client

........................................................................... 151

Figure 93: GRE Tunnel configuration

.................................................................................................... 152

Figure 94: OpenVPN configuration ........................................................................................................ 154

Figure 95: OpenVPN Remote Network

................................................................................................. 154

Figure 96: OpenVPN Authentication ...................................................................................................... 155

Figure 97: Example of clientless SSL VPN connections to the DSR ................................................ 158

Figure 98: List of groups

.......................................................................................................................... 159

8

Unified Services Router

User Manual

Figure 99: User group configuration ...................................................................................................... 160

Figure 100: SSLVPN Settings

................................................................................................................ 161

Figure 101: Group login policies options ............................................................................................... 162

Figure 102: Browser policies options

..................................................................................................... 163

Figure 103: IP policies options

................................................................................................................ 164

Figure 104: Available Users with login status and associated Group ............................................... 165

Figure 105: User configuration options ................................................................................................. 166

Figure 106: Import a CSV file with multiple users to the User Database

......................................... 167

Figure 107: List of SSL VPN polices (Global filter) .............................................................................. 168

Figure 108: SSL VPN policy configuration ............................................................................................ 169

Figure 109: List of configured resources, which are available to assign to SSL VPN policies

..... 171

Figure 110: List of Available Applications for SSL Port Forwarding

.................................................. 173

Figure 111: SSL VPN client adapter and access configuration ......................................................... 175

Figure 112: Configured client routes only apply in split tunnel mode

............................................... 176

Figure 113: List of configured SSL VPN portals. The configured portal can then be associated with an authentication domain .............................................................................................. 177

Figure 114: SSL VPN Portal configuration

........................................................................................... 179

Figure 115: USB Device Detection

........................................................................................................ 181

Figure 116: USB SharePort .................................................................................................................... 182

Figure 117: SMS Service

– Send SMS

................................................................................................. 183

Figure 118: SMS Service

– Receive SMS

............................................................................................ 184

Figure 119: POP3 Authentication Server configuration ...................................................................... 185

Figure 120: POP3 CA file upload ........................................................................................................... 186

Figure 121: NT Domain Authentication Server configuration

............................................................. 187

Figure 122: RADIUS Server configuration

............................................................................................ 188

Figure 123: Active Directory Authentication Server configuration ..................................................... 189

Figure 124: LDAP Authentication Server configuration

...................................................................... 191

Figure 125: Certificate summary for IPsec and HTTPS management ............................................. 193

Figure 126: Advanced Switch Settings .................................................................................................. 194

Figure 127: Device Drivers

...................................................................................................................... 195

Figure 128: Installation of driver/language pack

.................................................................................. 196

Figure 129: Selection of Installed Language ........................................................................................ 197

Figure 130: User Login policy configuration

......................................................................................... 199

Figure 131: Admin Settings

..................................................................................................................... 200

Figure 132: License upload field and List of Active Licenses ............................................................ 201

Figure 133: Remote Management from the WAN

............................................................................... 202

9

Unified Services Router

User Manual

Figure 134: Web GUI Management from the WAN ............................................................................. 203

Figure 135: SNMP Users, Traps, and Access Control

........................................................................ 204

Figure 136: SNMP system information for this router ......................................................................... 205

Figure 137: Date, Time, and NTP server setup

................................................................................... 206

Figure 138: Facility settings for Logging

............................................................................................... 207

Figure 139: Log configuration options for traffic through router ......................................................... 209

Figure 140: IPv6 Log configuration options for traffic through router ................................................ 209

Figure 141: E-mail configuration as a Remote Logging option

.......................................................... 210

Figure 142: Syslog server configuration for Remote Logging (continued) ....................................... 211

Figure 143: VPN logs displayed in GUI event viewer ......................................................................... 212

Figure 144: Restoring configuration from a saved file will result in the current configuration being overwritten and a reboot

....................................................................................................... 213

Figure 145: Firmware version information and upgrade option ......................................................... 215

Figure 146: Firmware upgrade and configuration restore/backup via USB

..................................... 216

Figure 147: Dynamic DNS configuration

............................................................................................... 217

Figure 148: Router diagnostics tools available in the GUI ................................................................. 218

Figure 149: Sample trace route output

.................................................................................................. 220

Figure 150: Localization

........................................................................................................................... 221

Figure 151: Device Status display .......................................................................................................... 223

Figure 152: Device Status display (continued) ..................................................................................... 225

Figure 153: Resource Utilization statistics

............................................................................................ 226

Figure 154: Resource Utilization data (continued) .............................................................................. 226

Figure 155: Resource Utilization data (continued) .............................................................................. 226

Figure 156: Physical port statistics

........................................................................................................ 227

Figure 157: AP specific statistics

............................................................................................................ 228

Figure 158: List of current Active Firewall Sessions ............................................................................ 228

Figure 159: List of connected 802.11 clients per AP

........................................................................... 229

Figure 160: List of LAN hosts ................................................................................................................. 229

Figure 161: List of current Active VPN Sessions ................................................................................. 231

10

Unified Services Router

User Manual

Chapter 1.

Introduction

D-Link Services Routers offer a secure, high performance networking solution to address the growing needs of small and medium businesses. Integrated high-speed IEEE 802.11n and 3G wireless technologies offer comparable performance to traditional wired networks, but with fewer limitations. Optimal network security is provided via features such as virtual private network (VPN) tunn els, IP Security (IPsec), Point-to-Point

Tunneling Protocol (PPTP), Layer 2 Tunneling Protocol (L2TP), and Secure Sockets

Layer (SSL). Empower your road warriors with clientless remote access anywhere and anytime using SSL VPN tunnels.

With the D-Link Services Router you are able to experience a diverse set of benefits:

Comprehensive Management Capabilities

The DSR-500, DSR-500N, DSR-1000 and DSR-1000N include dual-WAN

Gigabit Ethernet which provides policy-based service management ensuring maximum productivity for your business operations. The failover feature maintains data traffic without disconnecting when a landline connection is lost.

The Outbound Load Balancing feature adjusts outgoing traffic across two WAN interfaces and optimizes the system perfor mance resulting in high availability.

The solution supports configuring a port as a dedicated DMZ port allowing you to isolate servers from your LAN.

DSR-150/150N/250/250N producst have a single WAN interface, and thus i t does not support Auto Failover and Load Balancing scenarios.

Superior Wireless Performance

Designed to deliver superior wireless performance, the DSR -500N and DSR-

1000N include 802.11 a/b/g/n support, allowing for operation on either the 2.4

GHz or 5 GHz radio bands. Multiple In Multiple O ut (MIMO) technology allows the DSR-500N and DSR-1000N to provide high data rates with minimal “dead spots” throughout the wireless coverage area.

DSR-150N, DSR-250N and DSR-500N support the 2.4GHz radio band only.

Flexible Deployment Options

The DSR-1000 / 1000N supports Third Generation (3G) Networks via an extendable USB 3G dongle. This 3G network capability offers an additional secure data connection for networks that provide critical services. The DSR -

1000N can be configured to automatically switch to a 3G network whenever a physical link is lost.

Robust VPN features

A fully featured virtual private network (VPN) provides your mobile workers and branch offices with a secure link to your network. The DSR-150/150N/250/250N,

DSR-500/500N and DSR-1000 /1000N are capable of simultaneously managing

5, 5, 10, 20 Secure Sockets Layer (SSL) VPN tunnels respectively, empowering your mobile users by providing remote access to a central corporate database.

Site-to-site VPN tunnels use IP Security (IPsec) Protocol, Point-to-Point

Tunneling Protocol (PPTP), or Layer 2 Tunneling Protocol (L2TP) to facilitate

11

Unified Services Router

User Manual branch office connectivity through encrypted virtual links. The DSR-150/150N,

DSR-250/250N, DSR-500/500N and DSR-1000/1000N support 10, 25, 35 and 75 simultaneous IPsec VPN tunnels respectively .

Efficient D-Link Green Technology

As a concerned member of the global community, D -Link is devoted to providing eco-friendly products. D-Link Green Wi-Fi and D-Link Green Ethernet save power and prevent waste. The D -Link Green WLAN scheduler reduces wireless power automatically during off-peak hours. Likewise the D-Link Green Ethernet program adjusts power usage based on the detected cable length and link status.

In addition, compliance with RoHS (Restriction of Hazardous Substances) and

WEEE (Waste Electrical and Electronic Equipment) directives make D -Link

Green certified devices the environmentally responsible choice.

Support for the 3G wireless WAN USB dongle is only available for DSR-1000 and DSR-1000N.

1.1 About this User Manual

This document is a high level manual to allow new D-Link Services Router users to configure connectivity, setup VPN tunnels, establish firewall rules and perform general administrative tasks. Typical deployment and use case scenarios are described in each section. For more detailed setup instructions and explanations of each configuration parameter, refer to the online help that can be accessed from each page in the router

GUI.

1.2 Typographical Conventions

The following is a list of the various terms, followed by an example of how that term is represented in this document:

Product Name – D-Link Services Router. o

Model numbers DSR-500/500N/1000/1000N/250/250N/150/150N

GUI Menu Path/GUI Navigation –

Monitoring > Router Status

Important note –

12

Chapter 2.

Configuring Your Network: LAN Setup

It is assumed that the user has a machine for management connected to the LAN to the router. The LAN connection may be through the wired Ethernet ports available on the router, or once the initial setup is complete, the DSR may also be managed through its wireless interface as it is bridged with the LAN.

Access the router’s graphical user interface (GUI) for management by using any web browser, such as

Microsoft Internet Explorer or Mozilla Firefox:

Go to

http://192.168.10.1

(default IP address) to display the router’s management login screen.

Default login credentials for the management GUI:

Username:

admin

Password:

admin

If the router’s LAN IP address was changed, use that IP address in the navigation bar of the browser to access the router’s management UI.

2.1 LAN Configuration

Network > LAN > LAN Settings

By default, the router functions as a Dynamic Host Configuration Protocol (DHCP) server to the hosts on the WLAN or LAN network. With DHCP, PCs and other LAN devices can be assigned IP addresses as well as addresses for DNS servers, Windows Internet Name Service (WINS) servers, and the default gateway. With the DHCP server enabled the router’s IP address serves as the gateway address for LAN and WLAN clients. The PCs in the LAN are a ssigned IP addresses from a pool of addresses specified in this procedure. Each pool address is tested before it is assigned to avoid duplicate addresses on the

LAN.

For most applications the default DHCP and TCP/IP settings are satisfactory. If you want another PC on your network to be the DHCP server or if you are manually configuring the network settings of all of your PCs, set the DHCP mode to ‘none’. DHCP relay can be used to forward DHCP lease information from another LAN device that is the network’s DHCP server; this is particularly useful for wireless clients.

Instead of using a DNS server, you can use a Windows Internet Naming Service (WINS) server. A

WINS server is the equivalent of a DNS server but uses the NetBIOS protocol to resolve hostnames.

The router includes the WINS server IP address in the DHCP configuration when acknowledging a

DHCP request from a DHCP client.

You can also enable DNS proxy for the LAN. When this is enabled the router then as a proxy for all

DNS requests and communicates with the ISP’s DNS servers. When disabled all DHCP clients receive the DNS IP addresses of the ISP.

To configure LAN Connectivity, please follow the steps below:

1.

In the LAN Setup page, enter the following information for your router:

IP address (factory default: 192.168.10.1).

Unified Services Router

User Manual

If you change the IP address and click Save Settings, the GUI will not respond. Open a new connection to the new IP address and log in again. Be sure the LAN host (the machine used to manage the router) has obtained IP address from newly assigned pool (or has a static IP address in the router’s LAN subnet) before accessing the router via changed IP address.

Subnet mask (factory default: 255.255.255.0).

2.

In the DHCP section, select the DHCP mode:

None: the router’s DHCP server is disabled for the LAN

DHCP Server. With this option the router assigns an IP address within the specified range plus additional specified information to any LAN device that requests DHCP served addresses.

DHCP Relay: With this option enabled, DHCP clients on the LAN can receive IP address leases and corresponding information from a DHCP server on a different subnet. Specify the

Relay Gateway, and when LAN clients make a DHCP request it will be passed along to the server accessible via the Relay Gateway IP address .

If DHCP is being enabled, enter the following DHCP server parameters:

Starting and Ending IP Addresses: Enter the first and last continuous addresses in the IP address pool. Any new DHCP client joining the LAN is assigned an IP address in this range.

The default starting address is 192.168.10 .2. The default ending address is 192.168.1 0.100.

These addresses should be in the same IP address subnet as the router’s LAN IP address. You may wish to save part of the subnet range for devices with statically as signed IP addresses in the LAN.

Primary and Secondary DNS servers: If configured domain name system (DNS) servers are available on the LAN enter the ir IP addresses here.

Default Gateway: By default this setting has the router’s LAN IP address. It can be customized to any valid IP within the LAN subnet, in the event that the network’s gateway is not this router. In this case the DHCP server will give the configured IP address as the

Default Gateway to its DHCP clients.

Domain Name: This is the network doma in name used for identification.

WINS Server (optional): Enter the IP address for the WINS server or, if present in your network, the Windows NetBIOS server.

Lease Time: Enter the time, in hours, for which IP addresses are leased to clients.

Relay Gateway: Enter the gateway address. This is the only configuration parameter required in this section when DHCP Relay is selected as its DHCP mode

3.

In the DNS Host Name Mapping section:

14

Unified Services Router

User Manual

Host Name: Provide a valid host name

IP address: Provide the IP address of the host name,

4.

In the LAN proxy section:

Enable DNS Proxy: To enable the router to act as a proxy for all DNS requests and communicate with the ISP’s DNS servers, click the checkbox.

5.

Click Save Settings to apply all changes.

15

Unified Services Router

Figure 1: Set up page f or LAN TCP/ IP set ting s ( a)

User Manual

Figure 2: Set up page f or LAN TCP/ IP set ting s ( b)

16

Unified Services Router

2.1.1 LAN DHCP Reserved IPs

User Manual

Network > LAN > LAN DHCP Reserved IPs

The router’s DHCP server can assign TCP/IP configurations to computers in the LAN explicitly by adding client's network interface hardware address and the IP address to be assigned to that client in

DHCP server's database. Whenever DHCP server receives a request from c lient, hardware address of that client is compared with the hardware address list present in the database, if an IP address is already assigned to that computer or device in the database , the customized IP address is configured otherwise an IP address is assigned to the client automatically from the DHCP pool.

Computer Name

: The user defined name for the LAN host.

IP Addresses

: The LAN IP address of a host that is reserved by the DHCP server.

MAC Addresses

: The MAC address that will be assigned the rese rved IP address when it is on the

LAN.

Associate with IP/MAC Binding

: When the user enables this option the Computer Name, IP and MAC addresses are associated with the IP/MAC binding.

The actions that can be taken on list of reserved IP addresses are:

Select

: Selects all the reserved IP addresses in the list.

Edit

: Opens the LAN DHCP Reserved IP Configuration page to edit the selected binding rule.

Delete

: Deletes the selected IP address reservation(s)

Add

: Opens the LAN DHCP Reserved IP Configuration page to add a new binding rule.

17

Unified Services Router

Figure 3: LA N DHC P Reserve d IPs

User Manual

Note the following limits for the number of DHCP Reserved IP addresses per product:

DSR-150/150N: 32

DSR-250/250N:

DSR-500/500N:

64

96

18

Unified Services Router

User Manual

DSR-1000/1000N: 128

2.1.2 LAN DHCP Leased Clients

Setup > Network Information > DHCP Clients > LAN Leased Clients

This page provides the list of clients connect to LAN DHCP server.

Figure 4: LA N DHC P Lease d Client s

IP Addresses

: The LAN IP address of a host that matches the reserved IP list.

MAC Addresses

: The MAC address of a LAN host that has a configured IP address reservation.

2.1.3 LAN Configuration in an IPv6 Network

Network > IPv6 > LAN Settings > IPv6 LAn Settings

(1) In IPv6 mode, the LAN DHCP server is disabled by default (similar to IPv4 mode). The DHCPv6 server will serve IPv6 addresses from configured address pools with the IPv6 Prefix Length assigned to the LAN.

IPv4 / IPv6 mode must be enabled in the

Advanced > IPv6 > IP mode

to enable IPv6 configuration options.

19

Unified Services Router

User Manual

LAN Settings

The default IPv6 LAN address for the router is

fec0::1

. You can change this 128 bit IPv6 address based on your network requirements. The other field that defines the LAN settings for the router is the prefix length. The IPv6 network (subnet) is identified by the initial bits of the address called the prefix. By default this is

64

bits long. All hosts in the network have common initial bits for their IPv6 address; the number of common initial bits in the network’s addresses is set by the prefix length field.

Figure 5: IPv 6 L AN and DH CPv6 c onf iguration

If you change the IP address and click Save Settings, the GUI will not respond. Open a new connection to the new IP address and log in again. Be sure the LAN host (the machine used to manage the router) has obtained IP address from newly assigned pool (or has a static IP address in the router’s LAN subnet) before accessing the router via changed IP address.

As with an IPv4 LAN network, the router has a DHCPv6 server. If enabled, the router assigns an IP address within the specified range plus additional specified information to any LAN PC that requests

DHCP served addresses.

20

Unified Services Router

User Manual

The following settings are used to configure the DHCPv6 server:

DHCP Mode: The IPv6 DHCP server is either stateless or stateful. If stateless is selected an external IPv6 DHCP server is not required as the IPv6 LAN hosts are auto -configured by this router. In this case the router advertisement daemon (RADVD) must be configured on this device and ICMPv6 router discovery messages are used by the host for auto -configuration. There are no managed addresses to serve the LAN nodes. If stateful is selected the IPv6 LAN host will rely on an external DHCPv6 server to provide required configuration settings

The domain name of the DHCPv6 server is an optional setting

Server Preference is used to indicate the preference level of this DHCP server. DHCP advertise messages with the highest server preference value to a LAN host are preferred over other DHCP server advertise messages. The default is 255.

The DNS server details can be manually entered here (primary/secondary options. An alternative is to allow the LAN DHCP client to receive the DNS server det ails from the ISP directly. By selecting Use DNS proxy, this router acts as a proxy for all DNS requests and communicates with the ISP’s DNS servers (a WAN configuration parameter).

Primary and Secondary DNS servers: If there is configured domain name system (DNS) servers available on the LAN enter the IP addresses here.

Lease/Rebind time sets the duration of the DHCPv6 lease from this router to the LAN client.

IPv6 Address Pools

This feature allows you to define the IPv6 delegation prefix for a range of I P addresses to be served by the gateway’s DHCPv6 server. Using a delegation prefix you can automate the process of informing other networking equipment on the LAN of DHCP information specific for the assigned prefix.

Prefix Delegation

The following settings are used to configure the Prefix Delegation:

Prefix Delegation: Select this option to enable prefix delegation in DHCPv6 server. This option can be selected only in Stateless Address Auto Configuration mode of DHCPv6 server.

Prefix Address: IPv6 prefix address in the DHCPv6 server prefix pool

Prefix Length: Length prefix address

2.1.4 Configuring IPv6 Router Advertisements

Router Advertisements are analogous to IPv4 DHCP assignments for LAN clients, in that the router will assign an IP address and suppor ting network information to devices that are configured to accept such details. Router Advertisement is required in an IPv6 network is required for stateless auto configuration of the IPv6 LAN. By configuring the Router Advertisement Daemon on this router, the

DSR will listen on the LAN for router solicitations and respond to these LAN hosts with router advisements.

21

Unified Services Router

User Manual

RADVD

Network > IPv6 > LAN Settings > Router Advertisement

To support stateless IPv6 auto configuration on the LAN, set the RADVD status to Enable. The following settings are used to configure RADVD:

Advertise Mode: Select Unsolicited Multicast to send router advertisements (RA’s) to all interfaces in the multicast group. To restrict RA’s to well-known IPv6 addresses on the LAN, and thereby reduce overall network traffic, select Unicast only.

Advertise Interval: When advertisements are unsolicited multicast packets, this interval sets the maximum time between advertisements from the interface. The actual duration between advertisements is a random value between one third of this field and this field. The default is

30 seconds.

RA Flags: The router advertisements (RA’s) can be sent with one or both of these flags. Chose

Managed to use the administered /sta teful protocol for address auto configuration. If the Other flag is selected the host uses administered/stateful protocol for non-address auto configuration.

Router Preference: this low/medium/high parameter determines the preference associated with the RADVD process of the router. This is useful if there are other RADVD enabled devices on the LAN as it helps avoid conflicts for IPv6 clients.

MTU: The router advertisement will set this maximum transmission unit (MTU) value for all nodes in the LAN that are auto configured by the router. The default is 1500.

Router Lifetime: This value is present in RA’s and indicates the usefulness of this router as a default router for the interface. The default is 3600 seconds. Upon expiration of this value, a new RADVD exchange must take place between t he host and this router.

22

Unified Services Router

Figure 6: Co nf iguri ng the Ro uter A dverti se ment Dae mon

User Manual

Advertisement Prefixes

Network > IPv6 > LAN Settings > Advertisement Prefixes

The router advertisements configured with advertisement prefixes allow this router to inform hosts how to perform stateless address auto configuration. Router advertisements contain a list of subnet prefixes that allow the router to determine neighbors and whether the host is on the same link as the router.

The following prefix options are available for the router advertisements:

IPv6 Prefix Type: To ensure hosts support IPv6 to IPv4 tunnel select the 6to4 prefix type.

Selecting Global/Local/ISATAP will allow the nodes to support all other IPv6 routing options

SLA ID: The SLA ID (Site-Level Aggregation Identifier) is available when 6to4 Prefixes are selected. This should be the interface ID of the router’s LAN interface used for router advertisements.

IPv6 Prefix: When using Global/Local/ISATAP prefixes, this field is used to define the IPv6 network advertised by this router.

23

Unified Services Router

User Manual

IPv6 Prefix Length: This value indicates the number contiguous, higher order bits of the IPv6 address that define up the network portion of the address. Typically this is 64.

Prefix Lifetime: This defines the duration (in seconds) that the requesting node is allowed to use the advertised prefix. It is analogous to DHCP lease time in an IPv4 network.

24

Unified Services Router

Figure 7: IPv 6 A dve rtise ment Pref ix settings

User Manual

2.2 VLAN Configuration

The router supports virtual network isolation on the LAN with the use of VLANs. LAN devices can be configured to communicate in a sub network defined by VLAN identifiers. LAN ports can be assigned

25

Unified Services Router

User Manual unique VLAN IDs so that traffic to and from that physical p ort can be isolated from the general LAN.

VLAN filtering is particularly useful to limit broadcast packets of a device in a large network

VLAN support is enabled by default in the router. In the VLAN Configuration page, enable VLAN support on the router and then proceed to the next section to define the virtual network.

Network > VLAN > VLAN Settings

The Available VLAN page shows a list of configured VLANs by name and VLAN ID. A VLAN membership can be created by clicking the Add button below the List of Available VLANs.

A VLAN membership entry consists of a VLAN identifier and the numerical VLAN ID which is assigned to the VLAN membership. The VLAN ID value can be any number from 2 to 4091. VLAN ID

1 is reserved for the default VLAN, which is used for unt agged frames received on the interface. By enabling Inter VLAN Routing, you will allow traffic from LAN hosts belonging to this VLAN ID to pass through to other configured VLAN IDs that have Inter VLAN Routing enabled.

26

Unified Services Router

Figure 8: A ddi ng V LAN me mber shi ps to the L AN

User Manual

2.2.1 Associating VLANs to ports

27

Unified Services Router

User Manual

In order to tag all traffic through a specific LAN port with a VLAN ID, you can associate a VLAN to a physical port.

Network > VLAN > Port VLAN

VLAN membership properties for the LAN and wireless LAN are listed on this page. The VLAN Port table displays the port identifier, the mode setting for that port and VLAN membership information.

The configuration page is accessed by selecting one of the four physical ports or a configured access point and clicking Edit.

The edit page offers the following configuration options:

Mode: The mode of this VLAN can be G eneral, Access, or Trunk. The default is access.

In General mode the port is a member of a user selectable set of VLANs. The port sends and receives data that is tagged or untagged with a VLAN ID. If the data into the port is untagged, it is assigned the defined PVID. In the configuration from Figure 4, Port 3 is a General port with PVID 3, so untagged data into Port 3 will be assigned PVID 3. All tagged data sent out of the port with the same PVID will be untagged. This is mode is typically used with IP

Phones that have dual Ethernet ports. Data coming from phone to the switch port on the router will be tagged. Data passing through the phone from a connected device will be untagged.

28

Unified Services Router

Figure 9: Port V LA N list

User Manual

In Access mode the port is a member of a single VLAN (and only one). All data going into and out of the port is untagged. Traffic through a port in access mode looks like any other

Ethernet frame.

In Trunk mode the port is a member of a user selectable set of VLANs. All data going into and out of the port is tagged. Untagged coming into the port is not forwarded, except for the default VLAN with PVID=1, which is untagged. Trunk ports multiplex traffic for multiple

VLANs over the same physical link.

Select PVID for the port when the General mode is selected.

Configured VLAN memberships will be displayed on the VLAN Membership Configuration for the port. By selecting one more VLAN membership options for a General or Trunk port, traffic can be routed between t he selected VLAN membership IDs

29

Unified Services Router

User Manual

The DSR-150 / 150N does not support General mode for port VLANs due to hardware limitations.

Figure 10 : C onf iguri ng V L AN me mber shi p f or a port

2.2.2 Multiple VLAN Subnets

Network > VLAN > VLAN Settings

This page shows a list of available multi -VLAN subnets. Each configured VLAN ID can map directly to a subnet within the LAN. Each LAN port can be assigned a unique IP address and a VLAN specific

DHCP server can be configured to assign IP address leases to devices on this VLAN.

VLAN ID

: The PVID of the VLAN that will have all member devices be part of the same subne t range.

IP Address

: The IP address associated with a port assigned this VLAN ID.

Subnet Mask

: Subnet Mask for the above IP Address

30

Unified Services Router

Figure 11 : Multi ple V LAN Subnets

User Manual

2.2.3 VLAN configuration

Network > VLAN > VLAN Settings

This page allows enabling or disabling the VLAN function on the router. Virtual LANs can be created in this router to provide segmentation capabilities for firewall rules and VPN policies. The LAN network is considered the default VLAN. Check the Enable VLAN box to add VLAN functionality to the LAN.

31

Unified Services Router

Figure 12 : V LA N Co nf iguratio n

User Manual

2.3 Configurable Port: DMZ Setup

This router supports one of the physical ports to be configured as a secondary WAN Ethernet port or a dedicated DMZ port. A DMZ is a sub network that is open to the public but behind the firew all. The

DMZ adds an additional layer of security to the L AN, as specific services/ports t hat are exposed to the internet on the DMZ do not have to be exposed on the LAN. It is recommended that hosts that must be

32

Unified Services Router

User Manual exposed to the internet (such as web or email servers) be placed in the DMZ network. Firewall rules can be allowed to permit access specific services/ports to the DMZ from both the LAN or WAN. In the event of an attack to any of the DMZ nodes, the LAN is not necessarily vulnerable as well.

Network > Internet > DMZ DHCP Reserved IPs

DMZ configuration is identical to the LAN configuration. There are no restrictions on the IP address or subnet assigned to the DMZ port, other than the fact that it cannot be identical to the IP address given to the LAN interface of this gateway.

33

Unified Services Router

Figure 13 : DM Z conf iguration

User Manual

34

Unified Services Router

User Manual

For DSR-500N and DSR-1000N, in order to configure a DMZ port, the router’s configurable port must be set to DMZ in the

Setup > Internet Settings > Configurable Port

page.

For DSR-150N and DSR-250N, enabling DMZ will result in port 8 of the LAN switch being used for a dedicated DMZ port. The other 7 LAN ports remain unchanged .

2.4 Universal Plug and Play (UPnP)

Network > LAN > UPnP

Universal Plug and Play (UPnP) is a feature that allows the router to discovery devices on the network that can communicate with the router and allow for auto configuration. If a network device is detected by UPnP, the router can open internal or external ports for the traffic protocol required by that network device.

Once UPnP is enabled, you can configure the router to detect UPnP -supporting devices on the LAN (or a configured VLAN). If disabled, the router will not allow for automatic device configuration.

Configure the following settings to use UPnP:

Advertisement Period: This is the frequency that the router broadcasts UPnP information over the network. A large value will minimize network traffic but cause delays in identifying new UPnP devices to the network.

Advertisement Time to Live: This is expressed in hops for each UPnP packet. This is the number of steps a packet is allowed to propagate before being discarded. Small values will limit the UPnP broadcast range. A default of 4 is typical for networks with few switches.

35

Unified Services Router

Figure 14 : UP nP Co nf iguratio n

User Manual

UPnP Port map Table

The UPnP Port map Table has the details of UPnP devices that respond to the router’s advertisements.

The following information is displayed for each detected device:

Active: A yes/no indicating whether the port of the UPnP device that established a connection is currently active

Protocol: The network protocol (i.e. HTTP, FTP, etc.) used by the DSR

Int. Port (Internal Port): The internal ports opened by UPnP (if any)

Ext. Port (External Port): The external ports opened by UPnP (if any)

IP Address: The IP address of the UPnP device detected by this router

Click Refresh to refresh the portmap table and search for any new UPnP devices.

2.5 Captive Portal

LAN users can gain internet access via web portal authentication with the DSR. Also referred to as

Run-Time Authentication, a Captive Portal is ideal for a web café scenario where users initiate HTTP connection requests for web access but are not interested in accessing any LAN services. Firewall policies underneath will define which users require authentication for HTTP access, and when a matching user request is made the DSR will intercept the request and promp t for a username /

36

Unified Services Router

User Manual password. The login credentials are compared against the Runtime Authentication users in user database prior to granting HTTP access.

DSR-150/150N/250/250N does not have support for the Captive Portal feature.

Captive Portal is available for LAN users only and not for DMZ hosts.

Status > Network Information > CaptivePortal Sessions

The active run time internet sessions through the router’s firewall are listed in the below table. These users are present in the local or external user database and have had their login credentials approved for internet access. A ‘Disconnect’ button allows the DSR admin to selective ly drop an authenticated user. The “Block MAC” button will result in the selected client being added to the blocked list, and the current and future sessions from this client will be prevented.

Figure 15 : Acti ve R unti me sessio ns

2.5.1 Captive Portal Setup

Security > Authentication > Login Profiles

Captive Portal is a security mechanism to selectively provide authentication on certain interfaces.

This page displays configured custom Captive Portal profiles and indicates which are in use.

37

Unified Services Router

Figure 16 : C aptive P ortal Prof ile List

User Manual

List of Available Profiles: Any one of these profiles can be used for Captive Portal Login page while enabling Captive Portal.

Click “Add” in the Captive Portal setup page to allow defining custo mized captive portal login page information (Page Background Color, Header Details, Header Caption, Login Section Details,

Advertisement Details, Footer Details and Captive Portal Header Image).

Security > Authentication > Login Profiles

To create a new Captive Portal, a profile with a unique polic y name is to be created. The profile governs the entry screen shown to new sessions, and the browser message and background color / header can be customized to identify the service provi der for internet access.

38

Unified Services Router

Figure 17 : C usto mi zed C apti ve Portal Se tup

User Manual

39

Unified Services Router

User Manual

Security > Firewall > Blocked Clients

Access for specific clients can be regulated by the Captive Portal as well. The Block Client page allows one to define a MAC address that will always be denied access through all configured Captive

Portals.

40

Unified Services Router

Figure 18 : Bloc king sp ecif ic client s by t heir MAC a ddress

User Manual

2.5.2 Captive Portals on a VLAN

Network > VLAN > VLAN Settings

Captive Portals can be enabled on a per -VLAN basis. Hosts of a particular VLAN can be directed to authenticate via the Captive Portal, which may be a customized portal with unique instructions and branding as compared to another VLAN. The most critical asp ect of this configuration page is choosing the authentication server. All users (VLAN hosts) that want to gain internet access via the selected Captive Portal will be authenticated through the selected server.

41

Unified Services Router

Figure 19 : V LA N ba sed c onf igura tio n of Captive Port als

User Manual

42

Unified Services Router

User Manual

Chapter 3.

Connecting to the Internet: WAN Setup

This router has two WAN ports that can be used to establish a connection to the internet. The following

ISP connection types are supported: DHCP, Static, PPPoE, PPTP, L2TP, 3G Internet (via USB modem).

It is assumed that you have arranged for internet service with your Internet Service Provider (ISP). Please contact your ISP or network administrator for the configuration information that will be required to setup the router.

3.1 Internet Setup Wizard

Setup > Wizard > Internet

The Internet Connection Setup Wizard is available for users new to networking. By going through a few straightforward configuration pages you can take the information provided by your ISP to get your

WAN connection up and enable internet access for your network.

43

Unified Services Router

Figure 20 : Inter net Connectio n Set up W izar d

User Manual

44

Unified Services Router

User Manual

45

Unified Services Router

User Manual

You can start using the Wizard by logging in with the administrator password for the router. Once authenticated set the time zone that you are located in, and then choose the type of ISP connection type:

DHCP, Static, PPPoE, PPTP, L2TP. Depending on the connection type a username/password may be required to register this router with the ISP. In most cases the default settings can be used if the ISP did not specify that parameter. The last step in the Wizard is to click the Connect button, which confi rms the settings by establishing a link with the ISP. Once connected, you can move on and configure other features in this router.

3G Internet access with a USB modem is supported on WAN 3. The Internet Connection Setup

Wizard assists with the primary WAN p ort (WAN1) configuration only.

3.2 WAN Configuration

Network > Internet > WAN1Settings

You must either allow the router to detect WAN connection type automatically or configure manually the following basic settings to enable Internet connectivity:

ISP Connection type: Based on the ISP you have selected for the primary WAN link for this router, choose Static IP address, DHCP client, Point-to-Point Tunneling Protocol (PPTP), Point -to-Point

Protocol over Ethernet (PPPoE), Layer 2 Tunneling Protocol (L2TP). Required fields for the selected ISP type become highlighted. Enter the following information as needed and as provided by your ISP:

46

Unified Services Router

User Manual

PPPoE Profile Name. This menu lists configured PPPoE profiles, particularly useful when configuring multiple PPPoE connecti ons (i.e. for Japan ISPs that have multiple PPPoE support).

ISP login information. This is required for PPTP and L2TP ISPs.

User Name

Password

Secret (required for L2TP only)

MPPE Encryption: For PPTP links, your ISP may require you to enable Microsoft Point -to-Point

Encryption (MPPE).

Split Tunnel (supported for PPTP and L2TP connection). This setting allows your LAN hosts to access internet sites over this WAN link while still permitting VPN traffic to be directed to a VPN configured on this WAN port.

If split tunnel is enabled, DSR won’t expect a default route from the ISP server. In such case, user has to take care of routing manually by configuring the routing from Static Routing page.

Connectivity Type: To keep the connection always on, click Keep Connected. To log out after the connection is idle for a period of time (useful if your ISP costs are based on logon times), click Idle

Timeout and enter the time, in minutes, to wait before dis connecting in the Idle Time field.

My IP Address: Enter the IP address assigned to you by the ISP.

Server IP Address: Enter the IP address of the PPTP or L2TP server.

DSR-150/150N/250/250N doesn’t have a dual WAN support.

3.2.1 WAN Port IP address

Your ISP assigns you an IP address that is either dynamic (newly generated each time you log in) or static (permanent). The IP Address Source option allows you to define whether the address is statically provided by the ISP or should be received dynamicall y at each login. If static, enter your IP address,

IPv4 subnet mask, and the ISP gateway’s IP address. PPTP and L2TP ISPs also can provide a static

IP address and subnet to configure, however the default is to receive that information dynamically from the ISP.

3.2.2 WAN DNS Servers

The IP Addresses of WAN Domain Name Servers (DNS) are typically provided dynamically from the

ISP but in some cases you can define the static IP addresses of the DNS servers. DNS servers map

Internet domain names (example: www.google. com) to IP addresses. Click to indicate whether to get

DNS server addresses automatically from your ISP or to use ISP -specified addresses. If it’s latter, enter addresses for the primary and secondary DNS servers. To avoid connectivity problems, ensure that you enter the addresses correctly.

47

Unified Services Router

3.2.3 DHCP WAN

User Manual

For DHCP client connections, you can choose the MAC address of the router to register with the ISP.

In some cases you may need to clone the LAN host’s MAC address if the ISP is registered with that

LAN host.

Figure 21 : Ma nual WAN conf igur atio n

3.2.4 PPPoE

Network > Internet > WAN1Settings

The PPPoE ISP settings are defined on the WAN Configuration page. There are two types of PPPoE

ISP’s supported by the DSR: the standard username/password PPPoE and J apan Multiple PPPoE.

48

Unified Services Router

Figure 22 : PPPoE co nf iguratio n f or sta ndard ISPs

User Manual

Most PPPoE ISP’s use a single control and data connection, and require username / password credentials to login and authenticate the DSR with the ISP. The ISP connection type for this case is

“PPPoE (Username/Password)”. The GUI will prompt you for authentication, service, and connection settings in order to establish the PPPoE link.

For some ISP’s, most popular in Japan, the use of “Japanese Multiple PPPoE” is required in order to establish concurrent primary and secondary PPPoE connections between the DSR and the ISP. The

Primary connection is used for the bulk of data and internet traffi c and the Secondary PPPoE connection carries ISP specific (i.e. control) traffic between the DSR and the ISP.

49

Unified Services Router

User Manual

Figure 23 : W AN c onf iguration f or Japanese Multi ple PPPoE (part 1)

There are a few key elements of a multiple PPPoE connection:

Primary and secondary connections are concurrent

Each session has a DNS server source for domain name lookup, this can be assigned by the ISP or configured through the GUI

50

Unified Services Router

User Manual

The DSR acts as a DNS proxy for LAN users

Only HTTP requests that specifically identify the secondary connection’s domain name (for example

*.flets) will use the secondary profile to access the content available through this secondary PPPoE terminal. All other HTTP / HTTPS requests go through the primary PPPoE connection.

When Japanese multiple PPPoE is configured and secondary connection is up, some predefined routes are added on that interface. These routes are needed to access the internal domain of the ISP where he hosts various services.

These routes can even be configured through the static routing page as well.

Figure 24 : W AN c onf iguration f or Japanese Multi ple PPPoE (part 2) (i ts i n f igure 22 itself )

3.2.5 Russia L2TP and PPTP WAN

For Russia L2TP WAN connections, you can choose the address mode of the connection to get an IP address from the ISP or configure a static IP address provided by the ISP. For DHCP client connections, you can choose the MAC address of the router to register with the ISP. In some cases you may need to clone the LAN host’s MAC address if the ISP is registered with that LAN host.

51

Unified Services Router

Figure 25 : R ussia L2 TP ISP co nf iguratio n

User Manual

3.2.6 Russia Dual Access PPPoE

For Russia dual access PPPoE connections, you can choose the address mode of the connection to get an IP address from the ISP or configure a static IP address provided by the ISP.

52

Unified Services Router

Figure 26 : R ussia D ual acce ss PPPoE co nf iguratio n

User Manual

53

Unified Services Router

User Manual

54

Unified Services Router

User Manual

55

Unified Services Router

User Manual

3.2.7 WAN Configuration in an IPv6 Network

Network > IPv6 > WAN1Settings

For IPv6 WAN connections, this router can have a static IPv6 address or receive connection information when configured as a DHCPv6 client. In the case where the ISP assigns you a fixed address to access the internet, the static configuration settings must be completed. In addition to the

IPv6 address assigned to your router, the IPv6 prefix length defined by the ISP is needed. The default

IPv6 Gateway address is the server at the ISP that this router will con nect to for accessing the internet.

The primary and secondary DNS servers on the ISP’s IPv6 network are used for resolving internet addresses, and these are provided along with the static IP address and prefix length from the ISP.

56

Unified Services Router

User Manual

When the ISP allows you to obtain the WAN IP settings via DHCP, you need to provide details for the DHCPv6 client configuration. The DHCPv6 client on the gateway can be either stateless or stateful. If a stateful client is selected the gateway will connect to the ISP’s DHCPv6 ser ver for a leased address. For stateless DHCP there need not be a DHCPv6 server available at the ISP, rather

ICMPv6 discover messages will originate from this gateway and will be used for auto configuration.

A third option to specify the IP address and prefix length of a preferred DHCPv6 server is available as well.

Figure 27 : IP v6 W A N Se tup page

Prefix Delegation: Select this option to request router advertisement prefix from any available

DHCPv6 servers available on the ISP, the obtained prefix is updated to the advertised prefixes on the

LAN side. This option can be selected only in State less Address Auto Configuration mode of DHCPv6

Client.

When IPv6 is PPPoE type, the followin g PPPoE fields are enabled.

Username: Enter the username required to log in to the ISP.

Password: Enter the password required to login to the ISP.

Authentication Type: The type of Authentication in use by the profile: Auto -

Negotiate/PAP/CHAP/MS-CHAP/MS-CHAPv2.

Dhcpv6 Options: The mode of Dhcpv6 client that will start in this mode: disable dhcpv6/stateless dhcpv6/stateful dhcpv6/stateless dhcpv6 with prefix delegation.

Primary DNS Server: Enter a valid primary DNS Server IP Address.

57

Unified Services Router

User Manual

Secondary DNS Server: Enter a valid secondary DNS Server IP Address.

Click Save Settings to save your changes.

3.2.8 Checking WAN Status

Status > System Information > Device > WANx

The connection status and a summary of configured settings for all WAN interfaces are available on the WAN Status page. You can view the following key connection status information for each WAN port:

Connection time: The connection uptime

Connection type: Dynamic or Static IP address

Connection state: This is whether the WAN is connected or disconnected to an ISP. The Link

State is whether the physical WAN connection in place; the Link State can be up (i.e. cable inserted) while the WAN connection state is down.

IP address / subnet mask: IP Address assigned

Gateway IP address: WAN Gateway Address

58

Unified Services Router

Figure 28 : C onnecti on Sta tus i nf ormatio n f or bo th WA N por ts

User Manual

The WAN status page allows you to Enable or Disable static WAN links. For WAN settings that are dynamically received from the ISP, you can Renew or Release the link parameters if required.

3.2.9 VLAN ON WAN

This page allows you to set up your internet connection if it uses tagged VLAN headers for interacting with the ISP. Ensure that you have the Internet connection information such as the IP Addresses,

Account Information etc. This information is usually provided by your ISP or network administrator.

With VLAN on WAN support the router is able to get addresses to access the tagged interface.

Network>Internet>WAN1 Settings

59

Unified Services Router

Figure 29 : E na bling V LAN o n WA N

User Manual

3.3 Bandwidth Controls

Network > Internet > Traffic Management > Bandwidth Profilers

Bandwidth profiles allow you to regulate the traffic flow from the LAN to WAN 1 or WAN 2. This is useful to ensure that low priority LAN users (l ike guests or HTTP service) do not monopolize the available WAN’s bandwidth for cost-savings or bandwidth-priority-allocation purposes.

Bandwidth profiles configuration consists of enabling the bandwidth control feature from the GUI and adding a profile which defines the co ntrol parameters. The profile can then be associated with a traffic selector, so that bandwidth profile can be applied to the traffic matching the selectors. Selectors are elements like IP addresses or services that would trigger the configured bandwidth r egulation.

60

Unified Services Router

Figure 30 : Li st of C onf igured Ba ndwi dt h Prof iles

User Manual

To create a new bandwidth profile, click Add in the List of Bandwidth Profiles. The following configuration parameters are used to define a bandwidth profile:

Profile Name: This identifier is used to associate the configured profile to the traffic selector

You can choose to limit the bandwidth either using priority or rate.

If using priority “Low”, “High”, and “Medium” can be selected. If there is a low priority profile associated with traffic selector A and a high priority profile associated with traffic selector B, then the WAN bandwidth allocation preference will be to traffic selector B packets.

For finer control, the Rate profile type can be used. With this option the minimum and maximum bandwidth allowed by this profile can be limited.

Choose the WAN interface that the profile should be associated with .

61

Unified Services Router

Figure 31 : Ba ndw idt h Prof ile Co nf igurat ion

User Manual

Network > Internet > Traffic Management > Bridge Traffic Selectors

Once a profile has been created it can then be associated with a traffic flow from the LAN to WAN. To create a traffic selector, click Add on the Traffic Selectors page. Traffic selector configuration binds a bandwidth profile to a type or source of LAN traffic with the following settings:

Available profiles: Assign one of the defined bandwidth profiles

Service: You can have the selected bandwidth regulation apply to a specific service (i.e. FTP) from the LAN. If you do not see a service that you want, you can configure a custom service through the

Advanced > Firewall Settings > Custom Services

page. To have the profile apply to all services, select ANY.

Traffic Selector Match Type: this defines the parameter t o filter against when applying the bandwidth profile. A specific machine on the LAN can be identified via IP address or MAC address, or the profile can apply to a LAN port or VLAN group. As well a wireless network can be selected by its BSSID for bandwidth shaping. In order to restrict services from all IP addresses or specific subnets, the subnet mask field can be configured in conjunction with the IP address to regulate inbound traffic.

62

Unified Services Router

Figure 32 : Traf f ic Selector Co nf iguratio n

User Manual

3.3.1 Bandwidth Controls in Bridge Mode

Network > Internet > Traffic Management > Bridge Bandwidth Profile Configuration

Network > Internet > Traffic Management > Bridge Traffic Selectors

63

Unified Services Router

User Manual

The above traffic management applies to classical or NAT routing modes . When the system is in bridge mode (where the LAN1 and WAN2/DMZ ports are in the same network), traffic management factors in traffic type and bandwidth available on the ports part of the bridge .

For Bandwidth Profiles, the major difference between the o ptions available in bridge mode compared to standard classical / NAT routing mode is the interface options are not applicable. There is no association of the bandwidth profile with a particular outbound or inbound interface as this profile can only apply to the bridge network. Similarly, Traffic Selectors for bridge mode do not factor in port / SSID / VLAN as these concepts to not apply to the bridge network.

64

Unified Services Router

Figure 33 : Bri dge B andwidt h Prof ile Co nf iguratio n

User Manual

Figure 34 : Bri dge Tr af f ic Selector Conf ig uratio n

65

Unified Services Router

User Manual

3.4 Features with Multiple WAN Links

This router supports multiple WAN links. This allows you to take advantage of failover and load balancing features to ensure certain internet dependent services are prioritized in the event of unstable

WAN connectivity on one of the ports.

Network > Internet > WAN Mode

To use Auto Failover or Load Balancing, WAN link failure detection must be configured. This involves accessing DNS servers on the internet or ping to an internet address (user defined) . If required, you can configure the number of retry attempts when the link seems to be disconne cted or the threshold of failures that determines if a WAN port is down.

3.4.1 Auto Failover

In this case one of your WAN ports is assigned as the primary internet link for all internet traffic. The secondary WAN port is used for redundancy in case the primary l ink goes down for any reason. Both

WAN ports (primary and secondary) must be configured to connect to the respective ISP’s before enabling this feature. The secondary WAN port will remain unconnected until a failure is detected on the primary link (either port can be assigned as the primary). In the event of a failure on the primary port, all internet traffic will be rolled over to the backup port. When configured in Auto Failover mode, the link status of the primary WAN port is checked at regular intervals as defined by the failure detection settings.

Note that bothWAN1, WAN2 and WAN3 can be configured as the primary internet link.

Auto-Rollover using WAN port

Primary WAN: Selected WAN is the primary link ( WAN1/WAN2/WAN3)

Secondary WAN: Selected WAN is the secondary link.

66

Unified Services Router

User Manual

Failover Detection Settings: To check connectivity of the primary internet link, one of the following failure detection methods can be selected:

DNS lookup using WAN DNS Servers: DNS Lookup of the DNS Servers of the primary link is used to detect primary WAN connectivity.

DNS lookup using DNS Servers: DNS Lookup of the custom DNS Servers can be specified to check the connectivity of the primary link.

Ping these IP addresses: These IP's will be pinged at regular intervals to check the connec tivity of the primary link.

Retry Interval is: The number tells the router how often it should run the above configured failure detection method.

Failover after: This sets the number of retries after which failover is initiated.

DSR-1000, DSR-1000N, DSR-500, DSR-500N, DSR-250, DSR-250N, DSR-150, and DSR-150N support 3G USB Modem as a failover link when the internet access is lost.

3.4.2 Load Balancing

This feature allows you to use multiple WAN links (and presumably multiple ISP’s) simultaneously.

After configuring more than one WAN port, the load balancing option is available to carry traffic over more than one link. Protocol bindings are used to segregate and assign services over one WAN port in order to manage internet flow. The configured failure detection method is used at regular intervals on all configured WAN ports when in Load Balancing mode.

DSR currently support three algorithms for Load Balancing:

Round Robin

: This algorithm is particularly useful when the connection speed of one WAN port greatly differs from another. In this case you can define protocol bindings to route low -latency services (such as VOIP) over the higher -speed link and let low-volume background traffic (such as

SMTP) go over the lower speed link. Protocol binding is explained in next section.

Spillover

: If Spillover method is selected, the primary WAN acts as a dedicated link until a defined bandwidth threshold are reached. After this, the secondary WAN will be used for new conne ctions.

Inbound connections on the secondary WAN are permitted with this mode, as the spillover logic governs outbound connections moving from the primary to secondary WAN. You can configure spillover mode by using following options:

Load Tolerance: It is the percentage of bandwidth after which the router s witches to secondary

WAN.

Max Bandwidth: This sets the maximum bandwidth tolerable by the primary WAN for outbound traffic.

If the link bandwidth of outbound traffic goes above the load tolerance value of max b andwidth, the router will spillover the next connections to secondary WAN.

For example, if the maximum bandwidth of primary WAN is 1 Kbps and the load tolerance is set to

70. Now every time a new connection is established the bandwidth increases. After a certain number of connections say bandwidth reached 70% of 1Kbps, the new outbound connections will be spilled over to secondary WAN. The maximum value of load tolerance is 80 % and the minimum is 20%.

67

Unified Services Router

User Manual

DSR-1000, DSR-1000N, DSR-500 and DSR-500N support the traffic load balancing between physical WAN port and the 3G USB Modem.

Load balancing is particularly useful when the connection speed of one WAN port greatly differs from another. In this case you can define protocol bindings to route low -latency services (such as VOIP) over the higher-speed link and let low-volume background traffic (such as SMTP) go over the lower speed link.

Figure 35 : Lo ad Bal ancing i s av ailable w hen multi ple W AN ports are conf igure d and

Protocol Bi ndi ng s have bee n def ined

3.4.3 Protocol Bindings

Network > Routing > Protocol Binding

Protocol bindings are useful when the Load Balancing feature is in use. Choosing from a list of configured services or any of the user -defined services, the type of traffic can be assigned to go over only one of the available WAN ports. For increased flexibility the source network or machines can be specified as well as the destination network or machines. For example the VOIP traffic for a set of

LAN IP addresses can be assigned to one WAN and any VOIP traffic from the remaining IP addresses

68

Unified Services Router

User Manual can be assigned to the other WAN link. Protocol bindings are only applicable when load balancing mode is enabled and more than one WAN is configured.

Figure 36 : Protocol binding setup to a ssociate a service a nd/ or LA N so urce to a WAN and/or desti nati on netw ork

3.4.4 IP Aliasing

Network > Internet > IP Aliasing

A single WAN ethernet port can be accessed via multiple IP addresses by adding an alias to the port.

This is done by configuring an IP Alias address.

-

Figure 37 : C onf iguri ng t he IP Alias

69

Unified Services Router

Interface: Sets the interface on which IP Alias is being configured.

IP Address: Sets the IP address of the IP Alias.

Subnet Mask: Sets the Subnet Mask of the IP Alias.

Click Save Settings to save your changes.

Click Don't Save Settings to revert to the previous settings.

Figure 38 : IP Alia s Conf ig uratio n

User Manual

List of IP Aliases

The List of IP Aliases displays the configured IP Aliases on the router.

Interface Name: The interface on which the Alias was configured.

IP Address: The IP Address of the configured IP Alias.

Subnet Mask: The Subnet Mask of the configured IP Alias.

Edit: Opens the IP Alias configuration page to edit the selected IP Alias.

Add: Opens the IP Alias configuration page to add a new IP Alias.

Delete: Deletes the selected IP Aliases.

70

Unified Services Router

User Manual

3.5 Routing Configuration

Routing between the LAN and WAN will impact the way this router handles traffic that is received on any of its physical interfaces. The routing mode of the gateway is core to the behavior of the traffic flow between the secure LAN and the internet.

3.5.1 Routing Mode

Network > Internet > Routing

This device supports classical routing, network address translation (NAT), and transport mode routing.

With classical routing, devices on the LAN can be directly accessed from the internet by their public IP addresses (assuming appropriate firewall settings). If your ISP has assigned an IP address for each of the computers that you use, select Classic Routing.

NAT is a technique which allows several computers on a LAN to share an Internet connection.

The computers on the LAN use a "private" IP address range while the WAN port on the router is configured with a single "public" IP address. Along with connection sharing, NAT also hides internal IP addresses from the computers on the Internet. NAT is required if your ISP has assigned only one IP address to you. The computers that connect through the router will need to be assigned

IP addresses from a private subnet.

When Transparent Routing Mode is enabled, NAT is not performed on traffic between LAN and

WAN. Broadcast and multicast packets that arrive on the LAN interface are switched to the WAN and vice versa, if they do not get filtered by firewall or VPN policies. To maintain the LAN and

WAN in the same broadcast domain select Transparent mode , which allows bridging of traffic from LAN to WAN and vice versa, except for router -terminated traffic and other management traffic. All DSR features (such as 3G modem support) ar e supported in transparent mode assuming the LAN and WAN are configured to be in the same broadcast domain.

NAT routing has a feature called “NAT Hair -pinning” that allows internal network users on the

LAN and DMZ to access internal servers ( e.g. an internal FTP server) using their externallyknown domain name. This is also referred to as “NAT loopback” since LAN generated traffic is redirected through the firewall to reach LAN servers by their external name.

When Bridge Mode routing is enabled, the first physical LAN port and secondary WAN/DMZ

(port 2) interfaces are bridged together at Layer 2, creating an aggregate network. The other LAN ports and the primary WAN (WAN1) are not part of this bridge, and the router asks as a NAT device for these other ports. With Bridge mode for the LAN port 1 and WAN2/DMZ interfaces,

L2 and L3 broadcast traffic as well as ARP / RARP packets are passed through. When WAN2

71

Unified Services Router

User Manual receives tagged traffic the tag information will be removed before the packet is forwarded to the

LAN port 1 interface.

Bridge mode option is available on DSR -500 / 500N / 1000 / 1000N products only.

Figure 39 : R outing Mode to deter mi ne t raf f ic routing betw een W AN and L A N

72

Unified Services Router

3.5.2 Dynamic Routing (RIP)

User Manual

DSR- 150/150N/250/250N does not support RIP.

Setup > Internet Settings > Routing Mode

Dynamic routing using the Routing Information Protocol (RIP) is an Interior Gateway Protocol (IGP) that is common in LANs. With RIP this router can exchange routing information with other supported routers in the LAN and allow for dynamic adjustment of routing tables in order to adapt to modifications in the LAN without interrupting traffic flow.

The RIP direction will define how this router sends and receives RIP packets. Choose between:

Both: The router both broadcasts its routing table and also processes RIP information received from other routers. This is the recommended setting in order to fully utilize RIP capabilities.

Out Only: The router broadcasts its routing table periodically but does not accept RIP information from other routers.

In Only: The router accepts RIP information from other routers, but does not broadcast its routing table.

None: The router neither broadcasts its route table nor does it accept any RIP packets f rom other routers. This effectively disables RIP.

The RIP version is dependent on the RIP support of other routing devices in the LAN.

Disabled: This is the setting when RIP is disabled.

RIP-1 is a class-based routing version that does not include subnet information. This is the most commonly supported version.

RIP-2 includes all the functionality of RIPv1 plus it supports subnet information. Though the data is sent in RIP-2 format for both RIP -2B and RIP-2M, the mode in which packets are sent is different. RIP-2B broadcasts data in the entire subnet while RIP-2M sends data to multicast addresses.

If RIP-2B or RIP-2M is the selected version, authentication between this router and other routers

(configured with the same RIP version) is required. MD5 authentication is used in a first/second key exchange process. The authentication key validity lifetimes are configurable to ensure that the routing information exchange is with current and supported routers detected on the LAN.

3.5.3 Static Routing

Network > Routing >Static Routes

Advanced > IPv6 > IPv6 Static Routing

Manually adding static routes to this device allows you to define the path selection of traffic from one interface to another. There is no communication between this router and other devices to account for

73

Unified Services Router

User Manual changes in the path; once configured the static route will be active and effective until the network changes.

The List of Static Routes displays all routes that have been added manually by an administrator and allows several operations on the static routes. The List of IPv4 Static Routes and List of IPv6 Static

Routes share the same fields (with one exception):

Name: Name of the route, for identification and management .

Active: Determines whether the route is active or inactive. A route can be added to the table and made inactive, if not needed. This allows routes to be used as needed without deleting and re-adding the entry. An inactive route is not broadcast if RIP is enabled.

Private: Determines whether the route can be shared with other routers when RIP is enable d.

If the route is made private , then the route will not be shared in a RIP broadcast or multicast.

This is only applicable for IPv4 static routes.

Destination: the route will lead to this destination host or IP address.

IP Subnet Mask: This is valid for IPv4 networks only, and identifies the subnet that is affected by this static route

Interface: The physical network interface (WAN1, WAN2, WAN3, DMZ or LAN), through which this route is accessible.

Gateway: IP address of the gateway through which the dest ination host or network can be reached.

Metric: Determines the priority of the route. If multiple routes to the same destination exist, the route with the lowest metric is chosen.

74

Unified Services Router

Figure 40 : Static ro ute co nf igurati on f ie lds

User Manual

3.5.4 OSPFv2

Network > Routing > OSPF

OSPF is an interior gateway protocol that routes Internet Protocol (IP) packets solely within a single routing domain. It gathers link state information from available routers and constructs a topology map of the network.

OSPF version 2 is a routing protocol which described in RFC2328 - OSPF Version 2. OSPF is IGP

(Interior Gateway Protocols).OSPF is widely used in large networks such as ISP backbone and enterprise networks.

75

Unified Services Router

User Manual

DSR-150, DSR-150N, DSR-250 and DSR-250 don't support OSPFv2.

Figure 41 : OSPFv 2 c onf igured para meter s

Interface: The physical network interface on which OSPFv2 is Enabled/Disabled.

Status: This column displays the Enable/Disable state of OSPFv2 for a particular interface.

Area: The area to which the interface belongs. Two routers having a common segment; their interfaces have to belong to the same area on that segment. The interfaces should belong to the same subnet and have similar mask.

Priority: Helps to determine the OSP Fv2 designated router for a network. The router with the highest priority will be more eligible to become Designated Router. Setting the value to 0, makes the router ineligible to become Designated Router. The default value is 1.Lower value means higher pr iority.

HelloInterval: The number of seconds for HelloInterval timer value. Setting this value, Hello packet will be sent every timer value seconds on the specified interface. This value must be the same for all routers attached to a common network. The de fault value is 10 seconds.

DeadInterval: The number of seconds that a device’s hello packets must not have been seen before its neighbors declare the OSPF router down. This value must be the same for all routers attached to a common network. The default value is 40 seconds.

OSPF requires these intervals to be exactly the same between two neighbors. If any of these intervals are different, these routers will not become neighbors on a particular segment

Cost: The cost of sending a packet on an OSPFv2 interfac e.

Authentication Type:. This column displays the type of authentication to be used for OSPFv2.If

Authentication type is none the interface does not authenticate OSPF packets. If Authentication Type is Simple then OSPF packets are authenticated using simple text key. If Authentication Type is MD5 then the interface authenticates OSPF packets with MD5 authentication.

76

Unified Services Router

Figure 42 : OSPFv 2 c onf igurati on

User Manual

3.5.5 OSPFv3

Network > IPv6 > OSPFv3

Open Shortest Path First version 3 (OSPFv3) supports IPv6 . To enable an OSPFv3 process on a router, you need to enable the OSPFv3 process globally, assign the OSPFv3 process a router ID, and enable the OSPFv3 process on related interfaces.

DSR-150, DSR-150N, DSR-250 and DSR-250 don't support OSPFv3.

77

Unified Services Router

Figure 43 : OSPFv 3 c onf igured para meter s

User Manual

Interface: The physical network interface on which OSPFv3 is Enabled/Disabled.

Status: This column displays the Enable/Disable state of OSPFv3 for a particular interface.

Priority: Helps to determine the OSPFv3 designated router for a network. The router with the highest priority will be more eligible to become Designated Router. Setting the value to 0, makes the router ineligible to become Designated Router. The default value is 1.Lower Value means higher priority.

HelloInterval: The number of seconds for HelloInterval timer value. Setting this value, Hello packet will be sent every timer value seconds on the specified interface. This value must be the same for all routers attached to a common network. The default value is 10 seconds.

DeadInterval: The number of seconds that a device’s hello packets must not have been seen before its neighbors declare the OSPF router down. This value must be the same for all routers attached to a common network. The default value is 40 seconds.

OSPF requires these intervals to be exactly the same between two neighbors. If any of these intervals are different, these routers will not become neighbors on a particular segment

Cost: The cost of sending a packet on an OSPFv3 interface.

78

Unified Services Router

Figure 44 : OSPFv 3 c onf igurati on

User Manual

3.5.6 6to4 Tunneling

Network > IPv6 > 6 to 4 Tunneling

6to4 is an Internet transition mechanism for migrating from IPv4 to IPv6, a system that allows IPv6 packets to be transmitted over an IPv4 network. Select the check box to

Enable Automatic Tunneling

and allow traffic from an IPv6 LAN to be sent over an IPv4 Option to reach a remote IPv6 network.

Figure 45 : 6 to 4 t un neling

79

Unified Services Router

3.5.7 ISATAP Tunnels

User Manual

Network > IPv6 > ISATAP Tunnels

ISATAP (Intra-Site Automatic Tunnel Addressing Protocol) is an IPv6 transition mechanism meant to transmit IPv6 packets between dual -stack nodes on top of an IPv4 network. ISATAP specifies an IPv6 -

IPv4 compatibility address format as well as a means for site border router discovery. ISATAP also specifies the operation of IPv6 over a specific link layer - that being IPv4 used as a link layer for IPv6.

80

Unified Services Router

Figure 46 :

I S A T A P T u n n e l s C o n f i g u r a t i o n

User Manual

ISATAP Subnet Prefix: This is the 64-bit subnet prefix that is assigned to the logical ISATAP subnet for this intranet. This can be obtained from your ISP or internet registry, or derived from RFC 4193.

End Point Address: This is the endpoint address for the tunnel that starts with this router. The endpoint can be the LAN interface (assuming the LAN is an IPv4 network), or a specific LAN IPv4 address.

IPv4 Address: The end point address if not the entire LAN.

81

Unified Services Router

User Manual

3.6 Configurable Port - WAN Option

This router supports one of the physical ports to be configured as a secondary WAN Ethernet port or a dedicated DMZ port. If the port is selected to be a secondary WAN interface, all configuration pages relating to WAN2 are enab led.

3.7 WAN3 (3G) Configuration

This router supports one of the physic al ports WAN3 to be configured for 3G internet access.

Network > Internet > WAN3 Settings

WAN3 configuration for the 3G USB modem is available only on WAN 3 interface.

There are a few key elements of WAN 3 configuration.

Reconnect Mode: Select one of the following options o

Always On: The connection is always on. o

Username: Enter the username required to log in to the ISP. o

On Demand: The connection is automatically ended if it is idle for a specified number of minutes. Enter the number of minutes in the Maximum Idle Time field. This feature is useful if your ISP charges you based on the amount of time that you are connected.

Password: Enter the password required to login to the ISP.

Dial Number: Enter the number to dial to the ISP.

Authentication Protocol: Select one of None, PAP or CHAP Authentication Protocols to connect to the ISP.

APN: Enter the APN (Access Point Name) provided by the ISP.

Domain Name System (DNS) Servers

Domain name servers (DNS) convert Internet names such as www.dlink.com, to IP addresses to route traffic to the correct resources on the Internet. If you configure your router to get an IP address dynamically from the ISP, then you need to specify the DNS server source in this section.

DNS Server Source: Choose one of the following options: o

Get Dynamically from ISP: Choose this option if your ISP did not assign a static DNS IP address. o

Use These DNS Servers: Choose this option if your ISP assigned a static DNS IP address for you to use. Also complete the fields that are highlighted white in this section. o

Primary DNS Server: Enter a valid primary DNS Server IP Address. o

Secondary DNS Server: Enter a valid secondary DNS Server IP Address.

82

Unified Services Router

User Manual

Configurable Port: This page allows you to assign the functionality intended for the Configurable

Port. Choose from the following options: o

WAN: If this option is selected, configure the WAN 3. The WAN Mode options are now available as there are two WAN ports for the gateway. o

DMZ: If this option is selected, you are able to configure the DMZ port on the DMZ

Configuration menu.

Click Save Settings to save your changes.

Click Don't Save Settings to revert to the previous settings .

Figure 47 : W AN3 co nf iguratio n f or 3G i nt ernet

Cellular 3G internet access is available on WAN 3 via a 3G USB modem for DSR-1000 and DSR-1000N.

The cellular ISP that provides the 3G data plan will provide the authentication requirements to establish a connection. The dial Number and APN are specific to the cellular carriers. Once the connection type settings are configured and saved, navigate to the WAN status page (Network > Internet > WAN#

Settings) and Enable the WAN3 link to establish the 3G connection.

The 3G USB modem can be configured as the third WAN in DSR-1000 and DSR- 1000N.

83

Unified Services Router

User Manual

3.8 WAN Port Settings

Network > Internet > WAN1 Settings

The physical port settings for each WAN link can be defined here. If your ISP account defines the WAN port speed or is associated with a MAC address, this in formation is required by the router to ensure a smooth connection with the network.

The default MTU size supported by all ports is 1500. This is the largest packet size that can pass through the interface without fragmentation. This size can be increased, however large packets can introduce network lag and bring down the interface speed. Note that a 1500 byte size packet is the largest allowed by the Ethernet protocol at the network layer.

The port speed can be sensed by the router when Auto is selected. With this option the optimal port settings are determined by the router and network. The duplex (half or full) can be defined based on the port support, as well as one of three port speeds: 10 Mbps, 100 Mbps and 1000 Mbps (i.e. 1 Gbps). The default setting is 100 Mbps for all ports.

The default MAC address is defined during the manufacturing process for the interfaces, and can uniquely identify this router. You can customize each WAN port’s MAC address as needed, either by letting the WAN port assume the current LAN host’s MAC address or by entering a MAC address manually.

84

Unified Services Router

Figure 48 : Physical WAN por t settings

User Manual

The 3G USB Modem can be configured as dedicated WAN2 for DSR -500 and DSR-500N as well as dedicated WAN3 for DSR-1000 and DSR-1000N.

85

Unified Services Router

User Manual

Chapter 4.

Wireless Access Point Setup

This router has an integrated 802.11n radio that allows you to create an access point for wireless LAN clients. The security/encryption/authentication options are grouped in a wireless Profile, and each configured profile will be available for selection in the AP configuration menu. The profile defines various parameters for the AP, including the security between the wireless client and the AP, and can be shared between multiple APs instances on the same device when needed.

Up to four unique wireless networks can be created by configuring multiple “virtual” APs. Each such virtual AP appears as an independent AP (unique SSID) to supported clients in the environment, but is actually running on the same physical radio integrated with this router.

You will need the following information to configure your wireless network:

Types of devices expected to access the wireless network and their supported Wi -Fi™ modes

The router’s geographical region

The security settings to use for securing the wireless network.

Profiles may be thought of as a grouping of AP parameters that can then be applied to not just one but multiple AP instances (SSIDs), thus avoiding duplication if the same parameters are to be used on multiple AP instances or SSIDs.

4.1 Wireless Settings Wizard

Setup > Wizard > Wireless Settings

The Wireless Network Setup Wizard is available for users new to networking. By going through a few straightforward configuration pages you can enable a Wi -Fi™ network on your LAN and allow supported 802.11 clients to connect to the configured Access Point.

86

Unified Services Router

Figure 49 : Wireless Netw or k Set up Wi za rds

User Manual

87

Unified Services Router

User Manual

88

Unified Services Router

User Manual

4.1.1 Wireless Network Setup Wizard

This wizard provides a step-by-step guide to create and secure a new access point on the router. The network name (SSID) is the AP identifier that will be detected by supported clients. The Wizard uses a TKIP+AES cipher for WPA / WPA2 security; depending on support on the client side, devices associate with this AP using ei ther WPA or WPA2 security with the same pre -shared key.

The wizard has the option to automatically generate a network key for the AP. This key is the preshared key for WPA or WPA2 type security. Supported clients that have been given this PSK can associate with this AP. The default (auto-assigned) PSK is “passphrase”.

The last step in the Wizard is to click the Connect button, which confirms the settings and enables this AP to broadcast its availability in the LAN.

4.1.2 Add Wireless Device with WPS

With WPS enabled on your router, the selected access point allows supported WPS clients to join the network very easily. When the Auto option for connecting a wireless device is chose, you will be presented with two common WPS setup options:

Personal Identification Number (PIN):

The wireless device that supports WPS may have an alphanumeric PIN, and if entered in this field the AP will establish a link to the client. Click

Connect to complete setup and connect to the client.

89

Unified Services Router

User Manual

Push Button Configuration (PBC):

for wireless devices that support PBC, press and hold down on this button and within 2 minutes, click the PBC connect button. The AP will detect the wireless device and establish a link to the client.

You need to enable at least one AP with WPA/WPA2 security and also enable WPS in the

Advanced > Wireless Settings > WPS

page to use the WPS wizard.

4.1.3 Manual Wireless Network Setup

This button on the Wizard page will link to the

Setup> Wireless Settings> Access Points

page.

The manual options allow you to create new APs or modify the parameters of APs created by the

Wizard.

4.2 Wireless Profiles

Wireless > General > Profiles

The profile allows you to assign the security type, encryption and authentication to use when connecting the AP to a wireless client. The default mode is “open”, i.e. no security. This mode is insecure as it allows any compatible wireless clients to connec t to an AP configured with this security profile.

To create a new profile, use a unique profile name to identify the combination of settings. Configure a unique SSID that will be the identifier used by the clients to communicate to the AP using this profi le.

By choosing to broadcast the SSID, compatible wireless clients within range of the AP can detect this profile’s availability.

The AP offers all advanced 802.11 security modes, including WEP, WPA, WPA2 and WPA+WPA2 options. The security of the Access p oint is configured by the Wireless Security Type section:

Open: select this option to create a public “open” network to allow unauthenticated devices to access this wireless gateway.

WEP (Wired Equivalent Privacy): this option requires a static (pre -shared) key to be shared between the AP and wireless client. Note that WEP does not support 802.11n data rates; is it appropriate for legacy 802.11 connections.

WPA (Wi-Fi Protected Access): For stronger wireless security than WEP, choose this option. The encryption for WPA will use TKIP and also CCMP if required. The authentication can be a pre-shared key (PSK), Enterprise mode with RADIUS server, or both. Note that WPA does not support 802.11n data rates; is it appropriate for legacy 802.11 connections.

WPA2: this security type uses CCMP encryption (and the option to add TKIP encryption) on either

PSK (pre-shared key) or Enterprise ( RADIUS Server) authentication.

WPA + WPA2: this uses both encryption algorithms, TKIP and CCMP. WPA clients will use TKIP and WPA2 clients will use CCMP encryption algorithms.

90

Unified Services Router

User Manual

“WPA+WPA2” is a security option that allows devices to connect to an AP using the strongest security that it supports. This mode allows legacy devices that only support WPA2 keys (such as an older wireless printer) to connect to a secure AP where all the other wireless clients are using

WPA2.

Figure 50 : Li st of A vailable Prof iles sho ws th e optio ns avail able t o sec ure t he w ireless link

4.2.1 WEP Security

If WEP is the chosen security option, you must set a unique static key to be shared with clients that wish to access this secured wireless network. This static key can be generate d from an easy-toremember passphrase and the selected encryption length.

Authentication: select between Open System, or Shared Key schemes

Encryption: select the encryption key size -- 64 bit WEP or 128 bit WEP. The larger size keys provide stronger encryption, thus making the key more difficult to crack

WEP Passphrase: enter an alphanumeric phrase and click Generate Key to generate 4 unique

WEP keys with length determined by the encryption key size. Next choose one of the keys to be used for authentication. The selected key must be shared with wireless clients to connect to this device.

91

Unified Services Router

Figure 51 : Prof ile conf iguratio n to set ne tw or k sec urity

User Manual

4.2.2 WPA or WPA2 with PSK

A pre-shared key (PSK) is a known passphrase configured on the AP and client both and is used to authenticate the wireless client. An acceptable passphrase is between 8 to 63 characters in length.

92

Unified Services Router

User Manual

4.3 Creating and Using Access Points

Wireless > General > Access Points

Once a profile (a group of security settings) is created, it can be assigned to an AP on the router. The

AP SSID can be configured to broadcast its availability to the 802.11 environment can be used to establish a WLAN network.

The AP configuration page allows you to create a new AP and link to it one of the available profiles. This router supports multiple AP’s referred to as virtual access point s (VAPs). Each virtual AP that has a unique SSIDs appears as an independent access point to clients. This valuable feature allows the router’s radio to be configured in a way to optimize security and throughput for a group of clients as required by the use r. To create a VAP, click the “add” button on the

Wireless > General > Access Points

page. After setting the AP name, the profile dropdown menu is used to select one of the configured profiles.

The AP Name is a unique identifier used to manage the AP from the GUI, and is not the SSID that is detected by clients when the AP has broadcast enabled.

93

Unified Services Router

Figure 52 : V irtual A P conf igurati on

User Manual

94

Unified Services Router

User Manual

A valuable power saving feature i s the start and stop time control for this AP. You can conserve on the radio power by disabling the AP when it is not in use. For example on evenings and weekends if you know there are no wireless clients, the start and stop time will enable/disable the ac cess point automatically.

Once the AP settings are config ured, you must enable the AP on the radio on the

Wireless > General

> Access Points

page. The status field changes to “Enabled” if the AP is available to accept wireless clients. If the AP is configured to broadcast its SSID (a profile parameter), a green check mark indicating it is broadcasting will be shown in the List of Available Access points .

95

Unified Services Router

User Manual

Figure 53 : Li st of co nf igured access points (Virt ual APs) sho w s one ena bled ac cess point o n t he ra dio , broadca sti ng it s SSID

The clients connected to a particular AP can be viewed by using the Status Button on the List of

Available Access Points. Traffic statistics are shown for that individual AP, as compared to the summary stats for each AP on the Statistics table. Connected clients are sorted by the MAC address and indicate the security parameters used by the wireless link, as well as the time connected to this particular

AP. Clicking the Details button next to the connecte d client will give the detailed send and receive traffic statistics for the wireless link between this AP and the client.

96

Unified Services Router

User Manual

4.3.1 Primary benefits of Virtual APs:

Optimize throughput: if 802.11b, 802.11 g, and 802.11n clients are expected to access the

LAN via this router, creating 3 VAPs will allow you to manage or shape traffic for each group of clients. A unique SSID can be created for the network of 802.11b clients and another SSID can be assigned for the 802.11n clients. Each can have different security parameters – remember, the SSID and security of the link is determined by the profile. In this way legacy clients can access the network without bringing down the overall throughput of more capable

802.11n clients.

Optimize security: you may wish to suppo rt select legacy clients that only offer WEP security while using WPA2 security for the majority of clients for the radio. By creating two VAPs configured with different SSIDs and different security parameters, both types of clients can connect to the LAN. Since WPA2 is more secure, you may want to broadcast this SSID and not broadcast the SSID for the VAP with WEP since it is meant to be used for a few legacy devices in this scenario.

4.4 Tuning Radio Specific Settings

Wireless > General > Radio Settings

The Radio Settings page lets you configure t he channels and power levels available for the AP’s enabled on the DSR. The router has a dual band 802.11n radio, meaning either 2.4 GHz or 5 GHz frequency of operation can be selected (not concurrently though). Based on the selected operating frequency, the mode selection will let you define whether legacy connections or only 802.11n connections (or both) are accepted on configured APs.

97

Unified Services Router

Figure 54 : R adio car d co nf iguratio n opti ons

User Manual

The ratified 802.11n support on this radio requires selecting the appropriate broadcast (NA or NG etc.) mode, and then defining the channel spacing and control side band for 802.11n traffic. The default settings are appropriate for most networks. For example, changing the channel spacing to 40 MHz can improve bandwidth at the expense of supporting earlier 802.11n clients.

The available transmission channels are governed by regulatory constraints based on the region setting of the router. The maximum transmission power is similarly governed by regulatory limits; you have the option to decrease from the default maximum to reduce the signal strength of traffic out of the radio.

4.5 WMM

Wireless > Advanced > WMM

Wi-Fi Multimedia (WMM) provides basic Quality of service (Q oS) features to IEEE 802.11 networks.

WMM prioritizes traffic according to four Access Categories (AC) - voice, video, best effort, and background.

98

Unified Services Router

Figure 55 : Wi-Fi M ultime dia

User Manual

Profile Name

:

This field allows you to select the available profiles in wireless settings.

Enable WMM

:

This field allows you to enable WMM to improve multimedia transmission.

Default Class of Service

:

This field allows you to select the available Access Categories (voice, video, best effort, and background).

99

Unified Services Router

User Manual

4.6 Wireless distribution system (WDS)

Wireless > Advanced > WDS

Wireless distribution system is a system enabling the wireless interconnection of access points in a network. This feature is only guaranteed to work only between devices of the same type .

Figure 56 : Wireless Distri butio n Syste m

This feature is only guaranteed to work only between devices of the same type (i.e. using the same chipset/driver). For example between two DSR250N boxes, or betwee n two DSR1000N. It should also interoperate between a DSR 1000N and DSR 500 N boxes since they are based on the same chipset/driver.

When the user enables the WDS links use the same security configuration as the default access point.

The WDS links do not have true WPA/WPA2 s upport, as in there is no WPA key handshake performed.

Instead the Session Key to be used with a WDS Peer is computed using a hashing function (similar to the one used for computing a WPA PMK). The inputs to this function are a PSK (configurable by an administrator from the WDS page) and an internal "magic" string (non -configurable).

In effect the WDS links use TKIP/AES encryption, depending on the encryption configured for the default AP. In case the default AP use s mixed encryption (TKIP + AES).T he WDS link will use the

AES encryption scheme.

100

Unified Services Router

User Manual

For a WDS link to function properly the Radio settings on the WDS peers have to be the same.

The WDS page would consist of two sections. The first section provides general WDS settings shared by all its WDS peers.

WDS Enable

- This would be a check box

WDS Encryption - Displays the type of encryption used. It could be one of OPEN/64 bit WEP/128 bit

WEP/TKIP/AES (Use the term being used throughout the box i.e. either CCMP or AES).

WDS Passphrase

- This is required if the encryption selected is TKIP/CCMP. We would expect it to be within 8~63 ASCII characters. In the WDS configuration page this field is mandatory and has to be same on the two WDS peers, when the security is configured in TKIP/AES mode. The WDS links use this as the PSK for the connection.

DUT's Mac Address

- This would be the mac address of this box. This should be configured in the peer's WDS configuration page to be able to establish a WDS link with this box . This field in the WDS

Configuration section displays the device's mac address, which needs to be specified on the WDS peer for making a connection to this device (Similarly the WDS peers MAC address will have to be specified on this device for the WDS link to be established between the two devices).

The second section will have the list of configured WDS peers with buttons to Add/Delete Peer entries.

We support up to a maximum of 4 WDS links per box.

The both devices need to have same wireless settings (wireless mode, encryption, authentication method, WDS passphrase, WDS MAC address and wireless SSID) when we confi gure WDS features in DSR router.

The "Add WDS Peer" section allows the user to specify a WDS peer. The "WDS Peers" table displays the list of WDS peers currently configured on the device. A maximum of 4 WDS peers can be specified in any given mode.

4.7 Advanced Wireless Settings

Wireless > Advanced > Advanced Sttings

Sophisticated wireless administrators can modify the 802.11 communication parameters in this page.

Generally, the default settings are appropriate for most networks. Please refer to the GUI integrated help text for further details on the use of each configuration parameter.

101

Unified Services Router

Figure 57 : A dv ance d Wireless co mmunic ation set tings

User Manual

4.8 Wi-Fi Protected Setup (WPS)

Wireless > Advanced > WPS

WPS is a simplified method to add supporting wireless clients to the network. WPS is only applicable for APs that employ WPA or WPA2 security. To use WPS, select the eligible VAPs from the dropdown list of APs that have been configured with this security and enable WPS status for this AP.

The WPS Current Status section outlines the security, authentication, and encryption settings of the selected AP. These are consistent with the AP’s profile. There are two setup options avai lable for

:

Personal Identification Number (PIN):

The wireless device that supports WPS may have an alphanumeric PIN, if so add the PIN in this field. The router will connect within 60 seconds of clicking the “Configure via PIN” button immediately below t he PIN field. There is no LED indication that a client has connected.

Push Button Configuration (PBC):

for wireless devices that support PBC, press and hold down on this button and within 2 minutes click the PBC connect button. The AP will detect the wirel ess device and establish a link to the client.

More than one AP can use WPS, but only one AP can be used to establish WPS links to client at any given time.

102

Unified Services Router

User Manual

Figure 58 : WP S co nf iguratio n f or a n AP w ith WPA/WP A2 pr of ile

103

Chapter 5.

Securing the Private Network

You can secure your network by creating and applying rules that your router uses to selectively block and allow inbound and outbound Internet traffic. You then specify how and to whom the rules apply. To do so, you must define the following:

Services or traffic types (example s: web browsing, VoIP, other standard services and also custom services that you define)

Direction for the traffic by specifying the source and destination of traffic ; this is done by specifying the “From Zone” (LAN/WAN/DMZ) and “To Zone” ( LAN/WAN/DMZ)

Schedules as to when the router should apply rules

Any Keywords (in a domain name or on a URL of a web page) that the router should allow or block

Rules for allowing or blocking inbound and outbound Internet traffic for specified services on specified schedules

MAC addresses of devices that should not access the internet

Port triggers that signal the router to allow or block access to specified services as defined by port number

Reports and alerts that you want the router to send to you

You can, for example, establish restricted -access policies based on time -of-day, web addresses, and web address keywords. You can block Internet access by applications and services on the

LAN, such as chat rooms or games. You can block just certain groups of PCs on your network from being accessed by the WAN or public DMZ network .

5.1 Firewall Rules

Security > Firewall > Firewall Rules > IPv4 Firewall Rules

Inbound (WAN to LAN/DMZ) rules restrict access to traffic entering your network, selectively allowing only specific outside users to access specific local resources. By default all access from the insecure WAN side are blocked from accessing the secure

LAN, except in response to requests from the LAN or DMZ. To allow outside devices to access services on the secure LAN, you must create an inbound firewall rule for each service.

If you want to allow incoming traffic, you must make the router’s WAN port IP address known to the public. This is called “exposing yo ur host.” How you make your address known depends on how the WAN ports are configured; for this router you may use the

IP address if a static address is assigned to the WAN port, or if your WAN address is dynamic a DDNS (Dynamic DNS) name can be used.

Outbound (LAN/DMZ to WAN) rules restrict access to traffic leaving your network, selectively allowing only specific local users to access specific outside resources . The default outbound rule is to allow access from the secure zone (LAN) to either the public

DMZ or insecure WAN. On other hand the default outbound rule is to deny access from

Unified Services Router

User Manual

DMZ to insecure WAN. You can change this default behavior in the

Firewall Settings

> Default Outbound Policy

page. When the default outbound policy is allow always, you can to block hosts on the LAN from accessing internet services by creating an outbound firewall rule for each service.

Figure 59 : Li st of A vailable Firew all Rules

5.2 Defining Rule Schedules

Security > Firewall > Schedules

Firewall rules can be enabled or disabled automatically if they are associated with a configured schedule. The schedule configuration page allows you to define days of the week and the time of day for a new schedule, and then this schedule can be selected in the firewall rule configuration page.

All schedules will follow the time in the routers configured time zone. Refer to the section on choosing your Time Zone and configuring NTP servers for more information.

106

Unified Services Router

Figure 60 : Li st of A vailable Sc hedules t o bi nd to a f irewall rule

User Manual

107

Unified Services Router

User Manual

5.3 Configuring Firewall Rules

Security > Firewall > Firewall Rules > IPv4 Firewall Rules

All configured firewall rules on the router are displayed in the Firewall Rules list. This list also indicates whether the rule is enabled (active) or not, and gives a summary of the From/To zone as well as the services or users that the rule affects.

To create a new firewall rules, follow the steps below:

1.

View the existing rules in the List of Available Firewall Rules table.

2.

To edit or add an outbound or inbound services rule, do the following:

To edit a rule, click the checkbox next to the rule and click E dit to reach that rule’s configuration page.

To add a new rule, click Add to be taken to a new rule’s configuration page. Once created, the new rule is automatically added to the original table.

3.

Chose the From Zone to be the source of originating traffic: either the secure LAN, public

DMZ, or insecure WAN. For an inbound rule WAN should be selected as the From Zone.

4.

Choose the To Zone to be the destination of traffic covered by this rule. If the From Zone is the WAN, the To Zone can be the public DMZ or secure LAN. Similarly if the From

Zone is the LAN, then the To Zone can be the public DMZ or insecure WAN.

5.

Parameters that define the firewall rule include the following:

Service: ANY means all traffic is affected by this rule. For a specific service the drop down list has common services, or you can select a custom defined service.

Action & Schedule: Select one of the 4 actions that this rule defines:

BLOCK always, ALLOW always, BLOCK b y schedule otherwise

ALLOW, or ALLOW by schedule otherwise BLOCK . A schedule must be preconfigured in order for it to be available in the dropdown list to assign to this rule.

Source & Destination users: For each relevant category, select the users to which the rule applies:

Any (all users)

Single Address (enter an IP address)

Address Range (enter the appropriate IP address range)

108

Unified Services Router

User Manual

Log: traffic that is filtered by this rule can be logged; this requires configuring the router’s logging feature separately.

QoS Priority: Outbound rules (where To Zone = insecure WAN only) can have the traffic marked with a QoS priority tag. Select a priority level:

Normal-Service: ToS=0 (lowest QoS)

Minimize-Cost: ToS=1

Maximize-Reliability: ToS=2

Maximize-Throughput: ToS=4

Minimize-Delay: ToS=8 (highest QoS)

6.

Inbound rules can use Destination NAT (DNAT) for managing traffic from the WAN.

Destination NAT is available when the To Zone = DMZ or secure LAN.

With an inbound allow rule you can enter the internal server address that is hosting the selected service.

You can enable port forwarding for an incoming service specific rule

(From Zone = WAN) by selecting the appropriate checkbox. This will allow the selected service traffic from the internet to reach the appropriate LAN port via a port forwarding rule.

Translate Port Number: With port forwarding, the incoming traffic to be forwarded to the port number entered here.

External IP address: The rule can be bound to a specific WAN interface by selecting either the primary WAN or configurable port WAN as the source IP address for incoming traffic.

This router supports multi-NAT and so the External IP address does not necessarily have to be the WAN address. On a single WAN interface, multiple public IP addresses are supported. If your ISP assigns you more than one public

IP address, one of these can be used as your primary IP address on the WAN port , and the others can be assigned to servers on the LAN or DMZ. In this way the

LAN/DMZ server can be accessed from the internet by its aliased public IP address.

7.

Outbound rules can use Source NAT (SNAT) in order to map (bind) all LAN/DMZ traffic matching the rule parameters to a specific WAN interface or external IP address (usually provided by your ISP).

109

Unified Services Router

User Manual

Once the new or modified rule parameters are saved, it appears in the master list of firewall rules. To enable or disable a rule, click the checkbox ne xt to the rule in the list of firewall rules and choose Enable or Disable.

The router applies firewall rules in the order listed. As a general rule, you should move the strictest rules (those with the most specific services or addresses) to the top of the list. To reorder rules, click the checkbox next to a rule and click up or down.

110

Unified Services Router

User Manual

Figure 61 : Ex a mple w here an out bo und SN AT r ule i s use d to map a n ex ternal IP a ddress (209. 156. 200. 225) to a priv ate DM Z IP address (1 0.30 .30. 30 )

111

Unified Services Router

User Manual

Figure 62 : T he f irewall rule co nf igurati o n page all ow s y ou to def ine t he

To/Fro m zo ne, servi ce, actio n, sche dule s, and specif y so urce/desti na tion IP addresses as nee de d.

112

Unified Services Router

User Manual

5.4 Configuring IPv6 Firewall Rules

Security > Firewall > Firewall Rules > IPv4 Firewall Rules

All configured IPv6 firewall rules on the router are displayed in the Firewall Rules list.

This list also indicates whether the rule is enabled (active) or not, and gives a summary of the From/To zone as well as the services or users that the rule affects.

113

Unified Services Router

User Manual

Figure 63 : T he IPv6 f irew all rule conf iguration pa ge allows y ou t o def ine the T o/Fro m zo ne, service, actio n, sche dules, a nd specif y so urce/desti na tion IP addresses as nee de d.

114

Unified Services Router

Figure 64 : Li st of A vailable IPv6 Firew all Rule s

User Manual

5.4.1 Firewall Rule Configuration Examples

Example 1:

Allow inbound HTTP traffic to the DMZ

Situation:

You host a public web server on your local DMZ network. You want to allow inbound HTTP requests from any outside IP address to the IP address of your web server at any time of day.

Solution:

Create an inbound rule as follows.

Parameter

From Zone

To Zone

Service

Action

Send to Local Server (DNAT IP)

Destination Users

Log

Value

Insecure (WAN1/WAN2/WAN3)

Public (DMZ)

HTTP

ALLOW always

192.168.5.2 (web server IP address)

Any

Never

Example 2:

Allow videoconferencing from range of outside IP addresses

115

Unified Services Router

User Manual

Situation:

You want to allow incoming videoconferencing to be initiated from a restricted range of outside IP addresses (132.177.88.2 - 132.177.88.254), from a branch office.

Solution:

Create an inbound rule as follows. In the example, CUSeeMe (the video conference service used) connections are allowed only from a specified range of external IP addresses.

Parameter

From Zone

To Zone

Service

Action

Send to Local Server (DNAT IP)

Destination Users

From

To

Enable Port Forwarding

Value

Insecure (WAN1/WAN2/WAN3)

Secure (LAN)

CU-SEEME:UDP

ALLOW always

192.168.10.11

Address Range

132.177.88.2

134.177.88.254

Yes (enabled)

Example 3:

Multi-NAT configuration

Situation:

You want to configure multi -NAT to support multiple public IP addresses on one WAN port interface.

Solution:

Create an inbound rule that configures the firewall to host an additional public IP address. Associate this address with a web server on the DMZ. If you arrange with your ISP to have more than one public IP address for your use, you can use the additional public IP addresses to map to servers on your LAN. One of these public IP addresses is used as the primary IP address of the router. This address is used to provide Internet access to your LAN PCs through NAT. The other addresses are available to map to your DMZ servers.

The following addressing scheme is used to illustrate this procedure:

WAN IP address: 10.1.0.118

LAN IP address: 192.168.10.1; subnet 255.255.255.0

Web server host in the DMZ, IP address: 192.168.12.222

Access to Web server: (simulated) public IP address 10.1.0.52

Parameter

From Zone

To Zone

Service

Action

Value

Insecure (WAN1/WAN2/WAN3)

Public (DMZ)

HTTP

ALLOW always

116

Unified Services Router

User Manual

Send to Local Server (DNAT IP)

Destination Users

From

WAN Users

Log

192.168.12.222 ( web server local IP address)

Single Address

10.1.0.52

Any

Never

Example 4:

Bloc

Example 4:

Block traffic by schedule if generated from specific range of machines

Use Case:

Block all HTTP traffic on the weekends if the request originates from a specific group of machines in the LAN having a known range of IP addresses, and anyone coming in through the Network from the WAN (i.e. all remote users).

Configuration:

1.

Setup a schedule:

To setup a schedule that affects traffic on weekends only, navigate to Security:

Schedule, and name the schedule “Weekend”

Define “weekend” to mean 12 am Saturday morning to 12 am Monday morning

– all day Saturday & Sunday

In the Scheduled days box, check that you want the schedule to be active for

“specific days”. Select “Saturday” and “Sunday”

In the scheduled time of day, select “all day” – this will apply the schedule between 12 am to 11:59 pm of the selected day.

Click apply – now schedule “Weekend” isolates all day Saturday and Sunday from the rest of the week.

117

Unified Services Router

Figure 65 : Sc hedule conf iguratio n f or t he abo ve ex ample.

User Manual

2.

Since we are trying to block HTTP requests, it is a service with To Zone: Insecure

(WAN1/WAN2/WAN3) that is to be blocked according to schedule “Weekend”.

3.

Select the Action to “Block by Schedule, otherwise allow”. This will take a predefined schedule and make sure the rule is a blocking rule during the defined dates/times. All other times outside the schedule will not be affected by this firewall blocking rule

118

Unified Services Router

User Manual

4.

As we defined our schedule in schedule “Weekend”, this is available in the dropdown menu

5.

We want to block the IP range assigned to the marketing group. Let’s say they have IP

192.168.10.20 to 192.168.10.30. On the Source Users dropdown, select Address Range and add this IP range as the From and To IP addresses.

6.

We want to block all HTTP traffic to any services going to the insecure zone. The

Destination Users dropdown should be “any”.

7.

We don’t need to change default QoS priority or Logging (unless desired) – clicking apply will add this firewall rule to the list of firewall rules.

8.

The last step is to enable this firewall rule. Select the rule, and click “enable” below the list to make sure the firewall rule is active

5.5 Security on Custom Services

Security > Firewall > Custom Services

Custom services can be defined to add to the list of services available during firewall rule configuration. While common services have known TCP/UDP/ICMP ports for traffic, many custom or uncommon applications exist in the LAN or WAN. In the custom service configuration menu you can define a range of ports and identify the traffic type (TCP/UDP/ICMP) for this service. Once defined, the new service will appear in the services list of the firewall rules configuration menu.

119

Unified Services Router

Figure 66 : Li st of user def ined services .

User Manual

Figure 67 : C usto m Services conf igur atio n

Created services are available as options for firewall rule configuration.

Name: Name of the service for identification and management purposes.

Type: The layer 3 Protocol that the service uses. (TCP, UDP, BOTH, ICMP or ICMPv6)

Port Type: This fields allows to select Port Range or Multiple Ports

ICMP Type: This field is enabled when the layer 3 protocol (in the Type field) is selected as ICMP or ICMPv6. The ICMP type is a numeric value that can range between

0 and 40, while for ICMPv6 the type ranges from 1 to 255. For a list of ICMP types, visit the following URL: http://www.iana.org/assignments/icmp -parameters.

Start Port: The first TCP, UDP or BOTH port of a range that the service uses. If the service uses only one port, then the Start Port will be the same as the Finish Port.

120

Unified Services Router

User Manual

Finish Port: The last port in the range that the service uses. If the service uses only one port, then the Finish Port will be the same as the Start Port.

Port: The port that the service uses.

5.6 ALG support

Security > Firewall > ALGs > SMTP ALGs

Application Level Gateways (ALGs) are security component that enhance the firewall and NAT support of this router to seamlessly support application layer protocols. In some cases enabling the ALG will allow the firewall to use dynamic ephemeral TCP/

UDP ports to communicate with the known ports a particular client application (such as H.323 or RTSP) requires, without which the admin would have to open large number of ports to accomplish the same support. Because the ALG understands the protocol used by the specific application that it supports, it is a very secure and efficient way of introducing support for client applications through the router’s firewall.

121

Unified Services Router

Figure 68 : A vaila ble ALG support on t he router .

User Manual

5.7 VPN Passthrough for Firewall

Security > Firewall > VPN Passthrough

This router’s firewall settings can be configured to allow encrypted VPN traffic for

IPsec, PPTP, and L2TP VPN tunnel connections between the LAN and internet. A specific firewall rule or service is not appropriate to introduce this passthrough support; instead the appropriate check boxes in the VPN Passthrough page must be enabled.

122

Unified Services Router

Figure 69 : Pa sst hro ug h o ptio ns f or V PN tunnel s

User Manual

5.8 Bridge Mode Firewall

Security > Firewall > Firewall Rules > Bridge Firewall rules

When Bridge is the selected system routing mode, Layer 2 level firewall rules are available to manage network traffic. These firewall rules will be applied between the two ports that are part of the bridge: LAN1 and the WAN2/DMZ physical ports.

Bridge mode option is available on DSR -500 / 500N / 1000 / 1000N products only.

123

Unified Services Router

Figure 70 : Li st of C onf igured Firew all Rule s f or t he Bridge

User Manual

Firewall rules configured for the bridge will filter traffic based on protocol, outgoing range of ports and/or the incoming range of ports. The processing is at L2 and can apply either to the LAN1 port or the WAN2/DMZ port (not both).

Figure 71 : Bri dge Fi rew all Rule co nf igur ation

124

Unified Services Router

User Manual

5.9 Application Rules

Security > Firewall > Dynamic Port Forwarding

Application rules are also referred to as p ort triggering. This feature allows devices on the LAN or DMZ to request one or more ports to be forwarded to them. Port triggering waits for an outbound request from the LAN/DMZ on one of the defined outgoing ports, and then opens an incoming port for that specified type of traffic. This can be thought of as a form of dynamic port forwarding while an application is transmitting data over the opened outgoing or incoming port(s).

Port triggering application rules are more flexible than static port forwarding that is an available option when configuring firewall rules. This is because a port triggering rule does not have to reference a specific LAN IP or IP range. As well ports are not left open when not in use, thereby providing a level of security that port forwarding does not offer.

Port triggering is not appropriate for servers on the LAN, since there is a dependency on the LAN device making an outgoing connection before incoming ports are opened.

Some applications require that when external devices connect to them, they recei ve data on a specific port or range of ports in order to function properly. The router must send all incoming data for that application only on the required port or range of ports. The router has a list of common applications and games with corresponding o utbound and inbound ports to open. You can also specify a port triggering rule by defining the type of traffic (TCP or UDP) and the range of incoming and outgoing ports to open when enabled.

125

Unified Services Router

User Manual

Figure 72 : Li st of A vailable A pplica tio n Rule s showi ng 4 uni que r ules

The application rule status page will list any active rules, i.e. incoming ports that are being triggered based on outbound requests from a defined outgoing port.

5.10 Web Content Filtering

The gateway offers some standard web filtering options to allow the admin to easily create internet access policies between the secure LAN and insecure WAN. Instead of creating policies based on the type of traffic (as is the case when using firewall rules ), web based content itself can be used to determine if traffic is allowed or dropped.

126

Unified Services Router

5.10.1 Static Content Filtering

User Manual

Security > Web Content Filter > Static Filtering

Content filtering must be enabled to configure and use the subsequent features (list of

Trusted Domains, filtering on Blocked Keywords, etc.). Proxy servers, which can be used to circumvent certain firewall rules and thus a potential security gap, can be blocked for all LAN devices. Java applets can be prevented from being downloaded from internet sites, and similarly the gateway can prevent ActiveX controls from being downloaded via Internet Explorer. For added security cookies, which typically contain session information, can be blocked as well for all devices on the private network.

Figure 73 : C ontent Filtering use d t o bl o c k access t o prox y se rvers a nd prevent Acti ve X co ntrols f ro m being dow nloa ded

5.10.2 Approved URLs

Security > Web Content Filter > Static Filtering > Approved URl

The Approved URLs is an acceptance list for all URL domain names. Domains added to this list are allowed in any form. For example, if the domain “yahoo” is added to this list then all of the following URL’s are permitted access from the LAN: www.yahoo.com, yahoo.co.uk, etc. Import/export from a text or CSV file for Approved

URLs is also supported

127

Unified Services Router

User Manual

Figure 74 : Tw o tr ust ed do mai ns a dde d to the A ppro ved UR Ls List

5.10.3 Blocked Keywords

Security > Web Content Filter > Static Filtering > Blocked Keywords

Keyword blocking allows you to block all website URL’s or site content that contains the keywords in the configured list. This is lower priority than the Approved URL List; i.e. if the blocked keyword is present in a site allowed by a Trusted Domain in the

Approved URL List, then access to that site will be allowed. Import/export from a text or CSV file for keyword blocking is also supported.

128

Unified Services Router

Figure 75 : One keyw ord a dded to t he blo c k list

User Manual

5.10.4 Export Web Filter

Security > Web Content Filter > Static Filtering > Approved URL

Export Approved URLs: Feature enables the user to export the URLs to be allowed to a .csv (comma-separated value) file which can then be downloaded to the local host.

The user has to click the export button to get the csv file.

Export Blocked Keywords: This feature enables the user to export the keywords to be blocked to a csv file which can then be downloaded to the local host. The user has to click the export button to get the csv file .

129

Unified Services Router

Figure 76 : Ex port A ppro ved URL li st

User Manual

5.10.5 Dynamic WCF

Security > Web Content Filter > Dynamic Filtering

Figure 77 : D yna mic WCF

130

Unified Services Router

User Manual

This feature allows the administrator to block access from a range of web content categories. The router must be upgraded with the the WCF license and then the Content

Filtering option, which allows the user to filter out internet sites, needs to be enabled.

The Dynamic Content Filtering configuration page will let the administrator choose from a range of pre-defined categories to be blocked. When enabled, acces s to a website belonging to one of these configured categories will be blocked with an error page.

Adult Content: Sites that host explicit sex content, nudity and sites that use profanity.

News: Sites that offer news and information on current events, incl uding newspapers, broadcasters and other publishers.

Job Search: Sites that offer job listings, interview coaching and other employment-related services.

Gambling: Sites that offer online gambling or information about gambling.

Travel/Tourism: Sites with travel and tourism information like city maps and services including planning trips, reservations for bus/train/airlines, hotel booking etc.

Shopping: Online shops, catalogs, auction sites and classified ads etc.

Entertainment: Websites for TV, movies, ent ertainment news etc. and sites hosting video content of movies, TV streaming etc.

Chatrooms/IM: Social networking sites, chartrooms and instant messaging sites.

Dating Sites: Online dating, matchmaking, relationship advice, personal ads and web pages related to marriage.

Game Sites: Sites that offer online games, MORPG and information about computer games, cheat codes etc.

Investment Sites: Sites for brokerages, trusts, insurance and other investments related organizations.

E-banking: Sites providing online banking services offered by financial institutions

Crime/Terrorism: Sites providing information on anti -social activities like murder, sabotage, bombing etc.

Personal Beliefs/Cults: Sites about religion, places of worship, religious groups, and occultism.

131

Unified Services Router

User Manual

Politics: Sites about politics, elections and legislation and sites that promote a politician or political party.

Sports: Sites about sports teams, fan clubs, and generally about all kinds of sports.

 www Email Sites: Websites that allow users to send and/ or receive email through a web accessible email account.

5.11 IP/MAC Binding

Network > LAN > LAN DHCP Reserved IPs

Another available security measure is to only allow outbound traffic (from the LAN to

WAN) when the LAN node has an IP address matching the MAC a ddress bound to it.

This is IP/MAC Binding, and by enforcing the gateway to validate the source traffic’s

IP address with the unique MAC Address of the configured LAN node, the administrator can ensure traffic from that IP address is not spoofed. In the event of a violation (i.e. the traffic’s source IP address doesn’t match up with the expected MAC address having the same IP address) the packets will be dropped and can be logged for diagnosis.

Figure 78 : T he f ollo w ing ex ample bind s a LAN ho st’ s MAC Address t o a n

IP a ddre ss serve d by DSR . If t here is an IP/MAC Bi ndi ng

132

Unified Services Router

User Manual

violatio n, the violati ng pac ke t will be dr opped and lo gs w ill be capt ured

5.12 Intrusion Prevention (IPS)

Security > Firewall > IPs

The gateway’s Intrusion Prevention System (IPS) prevents malicious attacks from the internet from accessing the private network. Static attack signatures loaded to the DSR allow common attacks to be detected and prevented. The checks can be enabled between the WAN and DMZ or LAN, and a running counter will allow the administrator to see how many malicious intrusion attempts from the WAN have been detected and prevented.

DSR-150/150N does not support Intrusion Prevention S ystem.

133

Unified Services Router

Figure 79 : Intr usi on Preventio n f eature s on the router

User Manual

5.13 Protecting from Internet Attacks

Security > Firewall >Attack Checks

Attacks can be malicious security breaches or unintentional network issues that render the router unusable. Attack checks allow you to manage WAN security threats such as continual ping requests and discovery via ARP scans. TCP and UDP flood attack checks can be enabled to manage extreme usage of WAN resources.

Additionally certain Denial-of-Service (DoS) attacks can be blocked. These at tacks, if uninhibited, can use up processing power and bandwidth and prevent regular network services from running normally. ICMP packet flooding, SYN traffic flooding, and Echo storm thresholds can be configured to temporarily suspect traffic from the offending source.

134

Unified Services Router

Figure 80 : Protecti ng the router a nd LA N f rom internet atta c ks

User Manual

WAN Security Checks

:

Enable Stealth Mode: If Stealth Mode is enabled, the router will not respond to port scans from the WAN. This makes it less susceptible to discovery and attacks.

Block TCP Flood: If this option is enabled, the router will drop all invalid TCP packets and be protected from a SYN flood attack.

LAN Security Checks

:

Block UDP Flood: If this option is enabled, the router will not ac cept more than 20 simultaneous, active UDP connections from a single computer on the LAN.

UDP Connection Limit: You can set the number of simultaneous active UDP connections to be accepted from a single computer on the LAN; the default is 25

ICSA Settings

:

Block ICMP Notification: selecting this prevents ICMP packets from being identified as such. ICMP packets, if identified, can be captured and used in a Ping (ICMP) flood

DoS attack.

Block Fragmented Packets: selecting this option drops any fragmented pac kets through or to the gateway

Block Multicast Packets: selecting this option drops multicast packets, which could indicate a spoof attack, through or to the gateway.

DoS Attacks:

SYN Flood Detect Rate (max/sec): The rate at which the SYN Flood can be dete cted.

135

Unified Services Router

User Manual

Echo Storm (ping pkts/sec): The number of ping packets per second at which the router detects an Echo storm attack from the WAN and prevents further ping traffic from that external address.

ICMP Flood (ICMP pkts/sec): The number of ICMP packets per s econd at which the router detects an ICMP flood attack from the WAN and prevents further ICMP traffic from that external address.

The ping on LAN interfaces is enabled in default. To disable the ping response from LAN hosts to the LAN/WAN port of the device uncheck the "Allow Ping from LAN" option.

5.14 IGMP Proxy to manage multicast traffic

Network > LAN > IGMP Setup

IGMP snooping allows the router to ‘listen’ in on IGMP network traffic through the router. This then allows the router to filter multicast traffic and direct this only to hosts that need this stream. This is helpful when there is a lot of multicast traffic on the network (say from an IPTV application) where all LAN hosts do not need to receive this multicast traffic. Enabling IGMP snooping allows the router to regulate the amount of multicast traffic on the network, to prevent flooding all LAN hosts.

Active IGMP snooping is referred to IGMP Proxy, and this is available on your router.

Figure 81 : E na bling IGMP Prox y f or the LAN

Enable IGMP Proxy: selecting this allows the router to listen in on IGMP traffic through the network, and manage multicast streams bound for the LAN

In the event that aWAN uses Russia Dual Access PPTP / L2TP connection, the outbound interface for IGMP traffic can be selected. Either the physical link (DHCP) or the PPP link (PPTP / L2TP) can be designated t o carry IGMP outbound traffic. This applies to any WAN that uses Russia Dual Access PPTP, which is set at based on the

WAN configuration. This setting is specific for Russia Dual Access ISPs where streaming services are run on the physical links only.

136

Unified Services Router

User Manual

Chapter 6.

IPsec / PPTP / L2TP VPN

A VPN provides a secure communication channel (“tunnel”) between two gateway routers or a remote PC client. The following types of tunnels can be created:

Gateway-to-gateway VPN: to connect two or more routers to secure traffic between remote sites.

Remote Client (client-to-gateway VPN tunnel): A remote client initiat es a VPN tunnel as the IP address of the remote PC client is not known in advance. The g ateway in this case acts as a responder.

Remote client behind a NAT router: The client has a dynamic IP address and is behind a NAT Router. The remote PC client at the NAT router initia tes a VPN tunnel as the

IP address of the remote NAT router is not known in advance. T he gateway WAN port acts as responder.

PPTP server for LAN / WAN PPTP client connections.

L2TP server for LAN / WAN L2TP client connections.

Figure 82 : Ex a mple of Gatew ay -to-Ga tew ay IPsec V PN t unnel usi ng tw o

DSR ro uters connect ed to the Inter net

137

Unified Services Router

User Manual

Figure 83 : Ex a mple of three IP sec client connecti ons t o t he i nternal netw or k thro ug h t he DSR IPsec gatew ay

6.1 VPN Wizard

Setup > Wizard > VPN Wizard

You can use the VPN wizard to quickly create both IKE and VPN policies. Once the

IKE or VPN policy is created, you ca n modify it as required.

138

Unified Services Router

Figure 84 : V PN Wi zard la unch screen

User Manual

To easily establish a VPN tunnel using VPN Wizard, follow the steps below:

1.

Select the VPN tunnel type to create

The tunnel can either be a gateway to gateway connection (site-to-site) or a tunnel to a host on the internet (remote access).

Set the Connection Name and pre -shared key: the connection name is used for management, and the pre -shared key will be required on the VPN client or gateway to establish the tunnel. The pre-shared key has a maximum length of 64 digits.

Determine the local gateway for this tunnel; if there is more than one WAN configured the tunnel can be configured for either of the gateways.

2.

Configure Remote and Local WAN address for the tunnel endpoints

Remote Gateway Type: identify the remote endpoint of the tunnel by FQDN or static

IP address

Remote WAN IP address / FQDN: This field is enabled only if the peer you are trying to connect to is a Gateway. For VPN Clients, this IP address or Internet Name is determined when a connection request is received from a client.

Local Gateway Type: identify this router’s endpoint of the tunnel by FQDN or static

IP address

Local WAN IP address / FQDN: This field can be left blank if you are not using a different FQDN or IP address than the one specified in the WAN port’s configuration.

139

Unified Services Router

User Manual

3.

Configure the Secure Connection Remote Accessibility fields to identify the remote network:

Remote LAN IP address: address of the LAN behind the peer gateway

Remote LAN Subnet Mask: the subnet mask of the LAN behind the peer

Note:

The IP address range used on the remote LAN must be different from the

IP address range used on the local LAN.

4.

Review the settings and click Connect to establish the tunnel.

The Wizard will create an Auto IPsec policy with the following default values for a

VPN Client or Gateway policy (these can be accessed from a link on the Wizard page):

Parameter

Exchange Mode

ID Type

Local WAN ID

Remote WAN ID

Encryption Algorithm

Authentication Algorithm

Authentication Method

PFS Key-Group

Life Time (Phase 1)

Life Time (Phase 2)

NETBIOS

Default value from Wizard

Aggressive (Client policy ) or Main (Gateway policy)

FQDN wan_local.com (only applies to Client policies) wan_remote.com (only applies to Client policies)

3DES

SHA-1

Pre-shared Key (max 64 digits)

DH-Group 2(1024 bit)

24 hours

8 hours

Enabled (only applies to Gateway policies)

The VPN Wizard is the recommended method to set up an Auto IPsec policy.

Once the Wizard creates the matching IKE and VPN policies required by the

Auto policy, one can modify the required fields through the edit link. Refer to the online help for details.

Easy Setup Site to Site VPN Tunnel:

If you find it difficult to configure VPN policies through VPN wizard use easy setup site to site VPN tunnel. This will add VPN policies by importing a file containing

VPN policies.

140

Unified Services Router

User Manual

6.2 Configuring IPsec Policies

VPN > IPSec VPN > Policies

An IPsec policy is between this router and another gateway or this router and an IPsec client on a remote host. The IPsec mode can be either tunnel or transport depending on the network being traversed between the two policy endpoints.

Transport: This is used for end -to-end communication between this router and the tunnel endpoint, either another IPsec gateway or an IPsec VPN client on a host. Only the data payload is encrypted and the IP header is not modified or encrypted.

Tunnel: This mode is used for network-to-network IPsec tunnels where this gateway is one endpoint of the tunnel. In this mode the entire IP packet including the header is encrypted and/or authenticated.

When tunnel mode is selected, you can enable NetBIOS and DHCP over IPsec. DHCP over IPsec allows this router to serve IP leases to hosts on the remote LAN. As well in this mode you can define the single IP address, range of IPs, or subnet on both the loca l and remote private networks that can communicate over the tunnel.

141

Unified Services Router

Figure 85 : IP sec poli cy conf igura tio n

User Manual

142

Unified Services Router

User Manual

Once the tunnel type and endpoints of the tunnel are defined you can determine the

Phase 1 / Phase 2 negotiation to use for the tunnel. This is covered in the IPsec mode setting, as the policy can be Manual or Auto. For Auto policies, the Internet Key

Exchange (IKE) protocol dynamically exchanges keys between two IPsec hosts. The

Phase 1 IKE parameters are used to d efine the tunnel’s security association details. The

Phase 2 Auto policy parameters cover the security association lifetime and encryption/authentication details of the phase 2 key negotiation.

The VPN policy is one half of the IKE/VPN policy pair requir ed to establish an Auto

IPsec VPN tunnel. The IP addresses of the machine or machines on the two VPN endpoints are configured here, along with the policy parameters required to secure the tunnel

143

Unified Services Router

User Manual

Figure 86 : IP sec poli cy conf igura ti o n co ntinue d (Auto policy via IK E)

A Manual policy does not use IKE and instead relies on manual keying to exchange authentication parameters between the two IPsec hosts. The incoming and outgoing security parameter index (SPI) values must be mirrored on the remote tunnel endpoint.

As well the encryption and integrity algorithms and keys must match on the remote

IPsec host exactly in order for the tunnel to establi sh successfully. Note that using Auto policies with IKE are preferred as in some IPsec implementations the SPI (security parameter index) values require conversion at each endpoint.

DSR supports VPN roll-over feature. This means that policies configured o n primary

WAN will rollover to the secondary WAN in case of a link failure on a primary WAN.

This feature can be used only if your WAN is configured in Auto-Rollover mode.

144

Unified Services Router

User Manual

Figure 87 : IP sec poli cy conf igura tio n co ntinue d (Auto / M anual Pha se 2 )

6.2.1 Extended Authentication (XAUTH)

You can also configure extended authentication (XAUTH). Rather than configure a unique VPN policy for each user, you can configure the VPN gateway router to authenticate users from a stored list of user accounts or with an external authentication server such as a RADIUS server. With a user database, user accounts created in the router are used to authenticate users.

With a configured RADIUS server, the router connects to a RADIUS server and passes to it the credentials that it receives from the VPN client. You can secure the connection between the router and the RADIUS server with the authentication protocol supported by the server (PAP or CHAP). For RADIUS – PAP, the router first checks in the user database to see if the user credentials are available; if they are not, the router connects to the RADIUS server.

6.2.2 Internet over IPsec tunnel

In this feature all the traffic will pass through the VPN Tunnel and from the Remote

Gateway the packet will be routed to Internet. On the remote gateway side, the outgoing packet will be SNAT'ed.

145

Unified Services Router

User Manual

6.3 Configuring VPN clients

Remote VPN clients must be configured with the same VPN policy parameters used in the VPN tunnel that the client wishes to use: encryption, authentication, life time, and

PFS key-group. Upon establishing these authentication parameters, the VPN Client user database must also be populated with an account to give a user access to the tunnel.

VPN client software is required to establish a VPN tunnel between the router and remote endpoint. Open source software (such as OpenVPN or Openswan) as well as Microsoft IPsec VPN software can be configured with the required IKE policy parameters to establish an IPsec VPN tunnel. Refer to the client software guide for detailed instructions on setup as well as the router’s o nline help.

The user database contains the list of VPN user accounts that are authorized to use a given VPN tunnel. Alternatively VPN tunnel users can be authenticated using a configured RADIUS database. Refer to the online help to determine how to popula te the user database and/or configure RADIUS authentication.

6.4 PPTP / L2TP Tunnels

This router supports VPN tunnels from either PPTP or L2TP ISP servers. The router acts as a broker device to allow the ISP's server to create a TCP control connection between the LAN VPN client and the VPN server.

6.4.1 PPTP Tunnel Support

VPN > PPTP VPN > Client

PPTP VPN Client can be configured on this router. Using this client we can access remote network which is local to PPTP server. Once client is enabled, the user can access

VPN > PPTP VPN > Active Users

page and establish PPTP VPN tunnel clicking Connect. To disconnect the tunnel, click Drop.

146

Unified Services Router

Figure 88 : PPTP t unnel co nf iguratio n – PPTP Client

User Manual

Figure 89 : PPTP V PN co nnectio n st atus

VPN > PPTP VPN > Server

A PPTP VPN can be established through this router. Once enabled a PPTP server is available on the router for LAN and WAN PPTP client users to access. Once the PPTP server is enabled, PPTP clients that are within the range of configured IP addresses of allowed clients can reach the router’s PPTP server. Once authenticated by the PPTP server (the tunnel endpoint), PPTP clients have access to the network managed by the router.

The range of IP addresses allocated to PPTP clients can coincide with the LAN subnet.

As well the PPTP server will default to local PPTP user authentication, but can be configured to employ an external authentication server should one be configured.

147

Unified Services Router

Figure 90 : PPTP t unnel co nf iguratio n – PPTP Server

User Manual

6.4.2 L2TP Tunnel Support

VPN > L2TP VPN > Server

A L2TP VPN can be established through this router. Once enabled a L2TP server is available on the router for LAN and WAN L2TP client users to access. Once the L2TP server is enabled, L2TP clients that are within the range of configured IP addresses of allowed clients can reach the router’s L2TP server. Once authenticated by the L2TP server (the tunnel endpoint), L2TP clients have access to the network managed by the router.

148

Unified Services Router

Figure 91 : L2 TP t unnel co nf iguratio n – L2TP Server

User Manual

149

Unified Services Router

User Manual

VPN > L2TP VPN > Client

A L2TP VPN Client can be configured on this router. Using this client we can access remote network which are local to the L2TP server. Once the client is enabled, the user can access Status > Active VPN page and establish L2TP VPN tunnel clicking Connect. To disconnect the tunnel, click Drop .

A L2TP VPN can be established through this router. Once enabled a L2TP server is available on the router for LAN and WAN L2TP client users to access. Once the

L2TP server is enabled, L2TP clients that are configured with the remote L2TP network server range (IP address and Netmask) can reach an endpoint router’s L2TP

150

Unified Services Router

User Manual server. Once authenticated by the L2TP s erver (the tunnel endpoint), L2TP clients have access to the local network managed by the router.

Figure 92 : L2 TP t unnel co nf iguratio n – L2TP Clie nt

6.5 GRE Tunnel Support

VPN > GRE > GRE Tunnels

GRE tunnels allow for broadcast traffic on the LAN of the router to be passed over the internet and received by remote LAN hosts. This is primarily useful in the D-

Link Discovery Protocol (DDP) application where broadcast traffic from one LAN host is to be received by all LAN hosts in the local subnets of the GRE endpoints.

Note the following limits for the number of supported GRE tunnels per product:

DSR-150/150N:

DSR-250/250N:

DSR-500/500N:

5

10

15

151

Unified Services Router

User Manual

DSR-1000/1000N: 20

There are two simple steps involved in establishing a GRE tunnel on the router:

1. Create a GRE tunnel from the GUI

2. Setup a static route for the remote local networks using the GRE tunnel

Figure 93 : GR E T unnel co nf iguratio n

When creating the GRE tunnel, the IP Address should be a unique address that identifies that GRE tunnel endpoint. It will be referenced in the other router’s static route as the Gateway IP address. The Remote End Address in the GRE tunnel configuration page is the WAN IP address of the other endpoint router.

Once the tunnel is established, a static route on the router can be made using the interface set to the configured GRE tunnel name. The destination IP address of the static route is the remote LAN subnet, and the route’s gateway IP address will be the

152

Unified Services Router

User Manual

GRE tunnel IP of the terminating router (the same router that manages the remote

LAN subnet). Once these two steps are completed, all DDP broadcast traffic can flow between remote LAN subnets via the GRE Tunne l.

6.6 OpenVPN Support

VPN > Open VPN > Settings

OpenVPN allows peers to authenticate each other using a pre -shared secret key, certificates, or username/password. When used in a multiclie nt-server configuration, it allows the server to release an authentication certificate for every client, using signature and Certificate authority. An Open VPN can be established through this router. Check/Uncheck this and click save se ttings to start/stop the OpenVPN server.

Mode: OpenVPN daemon mode. It can run in server mode, client mode or access server client mode. In access server client mode, the user has to download the auto login profile from the OpenVPN Access Server and upload the same to connect.

Server IP: OpenVPN server IP address to which the client connects

(applicable in client mode).

VPN Network: Address of the Virtual Network.

VPN Netmask: Netmask of the Virtual Network.

Port: The port number on which OpenVPN server (or Access Server) runs.

Tunnel Protocol: The protocol used to communicate with the remote host. Ex:

TCP, UDP. UDP is the default.

Encryption Algorithm: The cipher with which the packets are encrypted. Ex:

BF-CBC, AES-128, AES-192 and AES-256. BF-CBC is the default

Hash algorithm: Message digest algorithm used to authenticate packets. Ex:

SHA1, SHA256 and SHA512. SHA1 is the default.

Tunnel Type: Select Full Tunnel to redirect all the traffic through the tunnel.

Select Split Tunnel to redirect traffic to specified resources ( added via

OpenVPN client routes) through the tunnel. Full Tunnel is the default.

Enable Client to Client communication: Enable this to allow OpenVPN clients to communicate with each other in split tunnel case. Disabled by default.

Upload Access Server Client Configuration: The user has to download the auto login profile and upload here to connect this router to the OpenVPN

Access Server.

Certificates: Select the set of certificates OpenVPN server uses. First Row:

Set of certificates and keys the server uses . Second Row: Set of certificates and keys newly uploaded.

Enable TLS Authentication Key: Enabling this adds TLS authentication which adds an additional layer of authentication. Can be checked only when the TLS key is uploaded. Disabled by default.

Click Save Settings to save the settings.

153

Unified Services Router

Figure 94 : Ope nV PN conf igura tion

User Manual

6.6.1 OpenVPN Remote Network

VPN > Open VPN > Remote Networks

This page allows the user to add/edit a remote network and netmask which allows the other OpenVPN clients to reach this network.

Figure 95 : Ope nV PN Re mote Netw or k

Common Name

: Common Name of the OpenVPN client certificate.

154

Unified Services Router

Remote Network

: Network address of the remote resource.

Subnet Mask

: Netmask of the remote resource.

6.6.2 OpenVPN Authentication

VPN > Open VPN > Authentication

This page allows the user to upload required certificates and keys.

Figure 96 : Ope nV PN Authe nticati on

User Manual

Trusted Certificate (CA Certificate)

: Browse and upload the pem formatted CA

Certificate.

Server/Client Certificate

: Browse and upload the pem formatted Server/Client

Certificate.

155

Unified Services Router

User Manual

Server/Client Key

: Browse and upload the pem formatted Server/Client Key.

DH Key

: Browse and upload the pem formatted Diffie Hellman Key.

TLS Authentication Key

: Browse and upload the pem formatted TLS Authentication

Key.

156

Chapter 7.

SSL VPN

The router provides an intrinsic SSL VPN feature as an alternate to the standard IPsec

VPN. SSL VPN differs from IPsec VPN mainly by removing the requirement of a preinstalled VPN client on the remote host. Instead, users can securely login through the

SSL User Portal using a standard web browser and receive access to configured network resources within the corporate LAN. The router supports multiple concurrent sessions to allow remote users to access the LAN over an encrypted link through a customizable user portal interface, and each SSL VPN user can be assigned unique privileges and network resource access levels.

The remote user can be provided different options for SSL service through this router:

VPN Tunnel

: The remote user’s SSL enabled browser is used in place of a VPN client on the remote host to establish a secure VPN tunnel. A SSL VPN client (Active-

X or Java based) is installed in the remote host to allow the client to join the corporate

LAN with pre-configured access/policy privileges. At this point a virtual network interface is created on the user’s host and this will be assigned an IP address and

DNS server address from the router. Once established, the host machine can access allocated network resources.

Port Forwarding

: A web-based (ActiveX or Java) client is installed on the client machine again. Note that Port Forwarding service only supports TCP connections between the remote user and the router. The router administrator can define specific services or applications that are available to remote port forwarding users instead of access to the full LAN like the VPN tunnel.

ActiveX clients are used when the remote user acces ses the portal using the

Internet Explorer browser. The Java client is used for other browsers like Mozilla

Firefox, Netscape Navigator, Google Chrome, and Apple Safari.

Unified Services Router

User Manual

Figure 97 : Ex a mple of clientless SSL V PN co nnectio ns t o t he DSR

158

Unified Services Router

User Manual

7.1 Groups and Users

Security > Authentication > User Database > Groups

The group page allows creating, editing and deleting groups. The groups are associated to set of user types. The lists of available groups are displayed in the “List of Group” page with Group name and description of group.

Click Add to create a group.

Click Edit to update an existing group.

Click Delete to clear an existing group.

Figure 98 : Li st of gr oups

Group configuration page allows creating a group with a different type of users. The user types are as follows:

PPTP User: These are PPTP VPN tunnel LAN users that can establish a tunnel with the PPTP server on the WAN.

L2TP User: These are L2TP VPN tunnel LAN users that can establish a tunnel with the L2TP server on the WAN.

Xauth User: This user’s authentication is performed by an externally configured

RADIUS or other Enterprise server. It is not part of the local user database.

SSLVPN User: This user has access to the SSL VPN services as determined by the group policies and authentication domain of which it is a member. The domain-determined SSL VPN portal will be displayed when logging in with this user type.

Admin: This is the router’s super-user, and can manage the router, use SSL

VPN to access network resources, and login to L2TP/PPTP servers on the

WAN. There will always be one default administrator user for the GUI

159

Unified Services Router

User Manual

Guest User (read-only): The guest user gains read only access to the GUI to observe and review configuration settings. The guest does n ot have SSL VPN access.

Captive Portal User: Captive portal users obtain internet access via approval from the router. The access is determined based on captive portal policies.

Idle Timeout: This is the login timeout period for users of this group.

Figure 99 : U ser gro up co nf iguratio n

When SSLVPN users are selected, the SSLVPN settings are displayed with the following parameters as captured in SSLVPN Settings. As per the Authentication Type

SSL VPN details are configured.

Authentication Type: The authentication Type can be one of the following:

Local User Database (default), RADIUS-PAP, RADIUS-CHAP, RADIUS-

MSCHAP, RADIUS-MSCHAPv2, NT Domain, Active Directory and LDAP.

Authentication Secret: If the domain uses RADIUS authentication then the authentication secret is required (and this has to match the secret configured on the RADIUS server).

Workgroup: This is required is for NT domain authentication. If there are multiple workgroups, user can enter the details for up to two workgroups.

LDAP Base DN: This is the base domain name for the LDAP authentication server. If there are multiple LDAP authentication servers, user s can enter the details for up to two unique LDAP Base DN.

Active Directory Domain: If the domain uses the Active Directory authentication, the Active Directory domain name is required. Users configured in the Active Directory database are given access to the SSL VPN portal with their Active Directory username and password. If there are multiple Active

Directory domains, user can enter the details for up to two authentication domains.

160

Unified Services Router

User Manual

Timeout: The timeout period for reaching the authentication server.

Retries: The number of retries to authenticate with the authenti cation server after which the DSR stops trying to reach the server.

Figure 10 0: SSLV PN Setti ng s

161

Unified Services Router

User Manual

Login Policies

To set login policies for the group, s elect the corresponding group click “Login policies”. The following parameters are configured:

Group Name: This is the name of the group that can have its login policy edited

Disable Login: Enable to prevent the users of this group from logging into the devices management interface(s)

Deny Login from WAN interface: Enable to prevent the users of this group from logging in from a WAN (wide area network) interface. In this case only login through LAN is allowed.

Figure 10 1: Gro up l ogin policie s o ptio ns

Policy by Browsers

To set browser policies for the group, select the corresponding group click “ Policy by

Browsers”. The following parameters are configured:

Group Name: This is the name of the group that can have its login policy edited

Deny Login from Defined Browsers: The list of defi ned browsers below will be used to prevent the users of this group from logging in to the routers GUI. All non-defined browsers will be allowed for login for this group.

162

Unified Services Router

User Manual

Allow Login from Defined Browsers: The list of defined browsers below will be used to allow the users of this group from logging in to the routers GUI. All non-defined browsers will be denied for login for this group.

Defined Browsers: This list displays the web browsers that have been added to the Defined Browsers allotment, upon which group login policies can be defined. (Check Box at First Column Header): Selects all the defined browsers in the table.

Delete: Deletes the selected browser(s).

You can add to the list of Defined Browsers by selecting a client browser from the drop down menu and clicking Add. This browser will then appear in the above list of Defined Browsers.

Click Save Settings to save your changes.

Figure 10 2: Brow ser policies o ptio ns

Policy by IP

To set policies bye IP for the group, select the corresponding group click “Policy by

IP”. The following parameters are configured:

Group Name: This is the name of the group that can have its login policy edited

163

Unified Services Router

User Manual

Deny Login from Defined Browsers: The list of defined browsers below will be used to prevent the users of this group from logging in to the routers GUI. All non-defined browsers will be allowed for login for this group.

Allow Login from Defined Browsers: The list of defined browsers below will be used to allow the users of this group from logging in to the routers GUI. All non-defined browsers will be denied for login for this group.

Defined Browsers: Displays the web browsers that have been added to the

Defined Browsers list, upon which group login policies can be defined.

Check Box At First Column Header : Selects all defined browsers in the table.

Delete: Deletes the selected browser(s).

You can add to the list of Defined Browsers by selecting a client browser from the drop down menu and clicking Add. This browser will then appear in the above list of Defined Browsers.

Click Save Settings to save your changes.

Figure 10 3: IP polici es o ptio ns

.

164

Unified Services Router

User Manual

Login Policies, Policy by Browsers, Policy by IP are applicable SSL VPN user only.

Security > Authentication > User Database > Users

The Users page allows the administrator to add, edit or delete existing groups. Each user is associated to configured groups. The Lists of Available Users is displayed in the “List of Users” page with User name, associated group and Login status.

Click Add to create a user.

Click Edit to update an existing user.

Click Delete to clear an existing user

Figure 10 4: Availa bl e User s w ith logi n st atus a nd a ssociate d Group

7.1.1 Users and Passwords

Security > Authentication > User Database > Users > Add New Users

The user configurations allow creating users associated to group. The user settings contain the following key components:

User Name: This is unique identifier of the user.

First Name: This is the user’s first name

Last Name: This is the user’s last name

Select Group: A group is chosen from a list of configured groups.

Password: The password associated with the user name.

165

Unified Services Router

User Manual

Confirm Password: The same password as above is to be re-entered to prevent against typing errors.

Idle Timeout: The session timeout for the user.

It is recommended that passwords contains no dictionary words from any language, and is a mixture of letters (both uppercase and lowercase), numbers, and symbols. The password can be up to 30 characters.

Figure 10 5: User co nf iguration o ptio ns

7.1.2 Adding many users to the Local User Database

Security > Authentication > User Database > Get User DB

The DSR administrator can add users to the local built -in database directly via an appropriately-formatted comma separated value (CSV) file. The advantage of this feature is to allow for a large number of users to be added to the system with one operation, and the same file can be uploaded to multiple DSR devices as needed. Once uploaded the specific users in the local user database can be modified via the GUI as needed.

166

Unified Services Router

User Manual

Figure 10 6: Import a C SV f ile w ith mul t iple users to the U se r Da ta ba se

The following parameters must be used to define the User database CSV file.

1.

Create an empty text file with a .csv extension

2.

Each line in the file corresponds to a single user entry. Every line should end with carriage return equivalent of CRLF . Do not add comments or other text in this file.

3.

Formatting rules: a) All the fields must be enclosed within double quotes. b) Consecutive fields are seperated by commas. c) There should be no leading or trailing spaces in a line. d) There should be no spaces between fields.

Each line in the CSV user database file should follow the following format:

"UserName","FirstName","LastName","GroupName","MultiLogin","Password"

The above sample has fields that can assume the following valu es:

Username (text field): Name of the user and identifier in the DSR’s database, and so it must be unique in the local user database.

FirstName (text field): This is a user detail and need not be unique.

LastName (text field): This is a user detail and need not be unique.

GroupName (text field): The group that is associated with this user.

MultiLogSup (Boolean value): With this enabled (“1”), then multiple users can share a single username and password.

Password (text field): password to assign for th is username

The Group for a corresponding user (“GroupName” in the CSV) must be created via the GUI in advance of the User Database CSV upload action.

None of the above fields can be left empty or NULL in the User Database CSV.

167

Unified Services Router

User Manual

7.2 Using SSL VPN Policies

VPN > SSL VPN > SSL VPN Server Policy

SSL VPN Policies can be created on a Global, Group, or User level. User level policies take precedence over Group level policies and Group level policies take precedence over Global policies. These policies can be applied to a specific network resource, IP address or ranges on the LAN, or to different SSL VPN services supported by the router.

The List of Available Policies can be filtered based on whether it applies to a user, group, or all users (global).

A more specific policy takes precedence over a generic policy when both are applied to the same user/group/global domain. I.e. a policy for a specific IP address takes precedence over a policy for a range of addresses containing the IP address already referenced.

Figure 10 7: Li st of SSL V PN police s (Glo bal f ilter)

To add a SSL VPN policy, you must first assign it to a user, group, or make it global

(i.e. applicable to all SSL VPN users). If the policy is for a group, the available configured groups are shown in a drop down menu and one must be selected. Similarly, for a user defined policy a SSL VPN user must be chosen from the available list of configured users.

The next step is to define the policy details. The policy name is a unique identifier for this rule. The policy can be assigned to a specific Network Resource (details follow in the subsequent section), IP address, IP network, or all devices on the LAN of the router.

Based on the selection of one of these four options, the approp riate configuration fields are required (i.e. choosing the network resources from a list of defined resources, or defining the IP addresses). For applying the policy to addresses the port range/port number can be defined.

The final steps require the policy permission to be set to either permit or deny access to the selected addresses or network resources. As well the policy can be specified for one or all of the supported SSL VPN services (i.e. VPN tunnel)

168

Unified Services Router

User Manual

Once defined, the policy goes into effect immediat ely. The policy name, SSL service it applies to, destination (network resource or IP addresses) and permission (deny/permit) is outlined in a list of configured policies for the router.

Figure 10 8: SSL V PN policy co nf igurati on

To configure a policy for a single user or group of users, enter the following information:

Policy for: The policy can be assigned to a group of users, a single user, or all users (making it a global policy). To customize the policy for specific users or groups, the user can select from the Available Groups and Available Users drop down.

Apply policy to: This refers to the LAN resources managed by the DSR, and the policy can provide (or prevent) access to network resources, IP address, IP network, etc.

Policy name: This field is a unique name for identifying the policy. IP address:

Required when the governed resource is identified by its IP address or range of addresses.

Mask Length: Required when the governed resource is identified by a range of addresses within a subnet.

ICMP: Select this option to include ICMP traffic

Port range: If the policy governs a type of traffic, this field is used for defining

TCP or UDP port number(s) corresponding to the governed traffic. Leaving the starting and ending port range blank corresponds to all UDP and TCP traffic.

Service: This is the SSL VPN service made available by this policy. The services offered are VPN tunnel, port forwarding or both.

Defined resources: This policy can provide access to specific network resources. Network resources must be configured in advance of creating the policy to make them available for selection as a defined resource. Network resources are created with the following information

169

Unified Services Router

User Manual

Permission: The assigned resources defined by this poli cy can be explicitly permitted or denied.

7.2.1 Using Network Resources

VPN > SSL VPN > Resources

Network resources are services or groups of LAN IP addresses that are used to easily create and configure SSL VPN policies. This shortcut saves time when creating similar policies for multiple remote SSL VPN users.

Adding a Network Resource involves creating a unique name to identify the resource and assigning it to one or all of the supported SSL services. Once this is done, editing one of the created network resources allows you to configure the object type (either

IP address or IP range) associated with the service. The Network Address, Mask

Length, and Port Range/Port Number can all be defined for this resource as required .

A network resource can be defined by configuring the following in the GUI:

Resource name: A unique identifier name for the resource.

Service: The SSL VPN service corresponding to the resource (VPN tunnel, Port

Forwarding or All).

170

Unified Services Router

User Manual

Figure 10 9: Li st of conf igured reso urces, w hich are availa ble to a ssi gn to

SSL V PN policies

7.3 Application Port Forwarding

Setup > VPN Settings > SSL VPN Server > Port Forwarding

Port forwarding allows remote SSL users to access specified network applications or services after they login to the User Portal and launch the Port Forwarding service.

Traffic from the remote user to the router is detected and re-routed based on configured port forwarding rules.

Internal host servers or TCP applications must be specified as being made acces sible to remote users. Allowing access to a LAN server requires entering the local server IP

171

Unified Services Router

User Manual address and TCP port number of the application to be tunneled. The table below lists some common applications and corresponding TCP port numbers:

TCP Application

FTP Data (usually not needed)

FTP Control Protocol

SSH

Telnet

SMTP (send mail)

HTTP (web)

POP3 (receive mail)

NTP (network time protocol)

Citrix

Terminal Services

VNC (virtual network computing)

23

25

80

110

Port Number

20

21

22

123

1494

3389

5900 or 5800

As a convenience for remote users, the hostname (FQDN) of the network server can be configured to allow for IP address resolution. This host name resolution provides users with easy-to-remember FQDN’s to access TCP applications instead of error -prone IP addresses when using the Port Forwarding service through the SSL User Portal.

To configure port forwarding, following are required:

Local Server IP address: The IP address of th e local server which is host ing the application.

TCP port: The TCP port of the application

Once the new application is defined it is displayed in a list of configured applications for port forwarding. allow users to access the private network servers by using a hostname instead of an IP address, the FQDN corresponding to the IP address is defined in the port forwarding host configuration section.

Local server IP address: The IP address of the local server hosting the application. The application should be configured in advance.

Fully qualified domain name: The domain na me of the internal server is to be specified

Once the new FQDN is configured, it is displayed in a list of configured hosts for port forwarding.

Defining the hostname is optional as minimum requirement for port forw arding is identifying the TCP application and local server IP address. The local server

IP address of the configured hostname must match the IP address of the configured application for port forwarding.

172

Unified Services Router

User Manual

Figure 11 0: Li st of Availa b le Applicatio ns f or SSL Port For w arding

173

Unified Services Router

User Manual

7.4 SSL VPN Client Configuration

VPN > SSL VPN > SSL VPN Clients

An SSL VPN tunnel client provides a point -to-point connection between the browser side machine and this router. When a SSL VPN client is launched from the user portal, a "network adapter" with an IP address from the corporate subnet, DNS and WINS settings is automatically created. This allows local applications to access services on the private network without any special network configuration on t he remote SSL VPN client machine.

It is important to ensure that the virtual (PPP) interface address of the VPN tunnel client does not conflict with physical devices on the LAN. The IP address range for the SSL

VPN virtual network adapter should be either in a different subnet or non-overlapping range as the corporate LAN.

The IP addresses of the client’s network interfaces (Ethernet, Wireless, etc.) cannot be identical to the router’s IP address or a server on the corporate LAN that is being accessed through the SSL VPN tunnel.

174

Unified Services Router

Figure 11 1: SSL VPN client a dapter a nd access conf ig uratio n

User Manual

The router allows full tunnel and split tunnel support. Full tunnel mode just sends all traffic from the client across the VPN tunnel to the rou ter. Split tunnel mode only sends traffic to the private LAN based on pre -specified client routes. These client routes give the SSL client access to specific private networks, thereby allowing access control over specific LAN services.

Client level configuration supports the following:

Enable Split Tunnel Support: With a split tunnel, only resources which are referenced by client routes can be accessed over the VPN tunnel. With full tunnel support (if the split tunnel option is disabled the DSR acts in full tunnel mode) all addresses on the private network are accessible over the VPN tunnel.

Client routes are not required.

DNS Suffix: The DNS suffix name which will be given to the SSL VPN client.

This configuration is optional.

Primary DNS Server: DNS server IP address to set on the network adaptor created on the client host. This configuration is optional.

Secondary DNS Server: Secondary DNS server IP address to set on the network adaptor created on the client host. This configuration is optional.

Client Address Range Begin: Clients who connect to the tunnel get a DHCP served IP address assigned to the network adaptor from the range of addresses beginning with this IP address

Client Address Range End: The ending IP address of the DHCP range of addresses served to the client network adaptor.

VPN > SSL VPN > Client Routes

If the SSL VPN client is assigned an IP address in a different subnet than the corporate network, a client route must be added to allow access to the private LAN through the

VPN tunnel. As well a static route on the private LAN’s firewall (typically this router) is needed to forward private traffic through the VPN Firewall to the remote SSL VPN

175

Unified Services Router

User Manual client. When split tunnel mode is enabled, the user is required to configure routes for

VPN tunnel clients:

Destination network: The network address of the LAN or the subnet information of the destination network from the VPN tunnel clients’ perspective is set here.

Subnet mask: The subnet information of the destination network is set here.

Figure 11 2: Co nf igured client routes onl y apply in split t unnel mode

Steps to Install/Uninstall SSLVPN tunnel in MA C OS

1.Open terminal and run "visudo" as root and it will open sudoers file

176

Unified Services Router

User Manual

2. Add "username ALL=NOPASSWD: /usr/sbin/chown,/bin/chmod,/bin/rm" at the bottom of the sudoers file, save and close the file. (Username is the user name of the MAC account but not SSLVPN user name).

While uninstalling SSLVPN tunnel, when it asks for password, enter th e MAC user account password but not the root password or SSL VPN user password

7.5 User Portal

VPN > SSL VPN > Portal Layouts

When remote users want to access the private network through an SSL tunnel (either using the Port Forwarding or VPN tunnel service), they login through a user portal.

This portal provides the authentication fields to provide the appropriate access levels and privileges as determined by the router administrator. The domain where the user account is stored must be specified, and the domai n determines the authentication method and portal layout screen presented to the remote user.

Figure 11 3: Li st of conf igured SSL V PN portal s. The conf igured portal can t hen be associa t ed w ith an a uthe ntic ation do mai n

7.5.1 Creating Portal Layouts

Setup > VPN Settings > SSL VPN Server > Portal Layouts

The router allows you to create a custom page for remote SSL VPN users that is presented upon authentication. There are various fields in the portal that are customizable for the domain, and this allows the router administrator to communicate details such as login instructions, available services, and other usage details in the portal visible to remote users. During domain setup, configured portal layouts are available to select for all users authenticated by the domain.

177

Unified Services Router

User Manual

The default portal LAN IP address is

https://192.168.10.1/scgibin/userPortal/portal.

This is the same page that opens when the “User

Portal” link is clicked on the SSL VPN menu of the router GUI.

The router administrator creates and edits portal layouts from the configuration pages in the SSL VPN menu. The portal name, title, banner name, and banner contents are all customizable to the intended users for this portal. The portal name is appended to the

SSL VPN portal URL. As well, the users assigned to this portal (through their authentication domain) can be presented with one or more of the router’s supported

SSL services such as the VPN Tunnel page or Port Forwarding page.

To configure a portal layout and theme, following information is needed:

Portal layout name: A descriptive name for the custom portal that is being configured. It is used as part of the SSL portal URL.

Portal site title: The portal web browser window title that appears when the client accesses this portal. This field is optional.

Banner title: The banner title that is displayed to SSL VPN clients prior t o login. This field is optional.

Banner message: The banner message that is displayed to SSL VPN clients prior to login. This field is optional.

Display banner message on the login page: The user has the option to either display or hide the banner message in the login page.

HTTP meta tags for cache control: This security feature prevents expired web pages and data from being stored in the client’s web browser cache. It is recommended that the user selects this option.

ActiveX web cache cleaner: An ActiveX cache control web cleaner can be pushed from the gateway to the client browser whenever users login to this SSL

VPN portal.

SSL VPN portal page to display: The User can either enable VPN tunnel page or Port Forwarding, or both depending on the SSL services to display on this portal.

Once the portal settings are configured, the newly configured portal is added to the list of portal layouts.

VPN>SSL VPN>Portal Layout>Add New SSl VPN Portal Layout

This pages allows the admin to create a custom SSL VPN portal layout. This new portal is for local DB authentication using the SSL VPN group user, and then the port forward connection for this local database portal is available.

178

Unified Services Router

Figure 11 4: SSL V PN Portal conf igur ati on

User Manual

179

Unified Services Router

User Manual

Chapter 8.

Advanced Configuration Tools

8.1 USB Device Setup

Status > System Information > USB Status

The D-Link Services Router has a USB interface for printer access, file sharing and on the DSR-1000 / DSR-1000N models, 3G modem support. There is no configuration on the GUI to enable USB device support. Upon inserting your USB storage device, printer cable or 3G modem the DSR router will automatically detect the type of connected peripheral.

USB Mass Storage: also referred to as a “share port”, files on a USB disk connected to the DSR can be accessed by LAN users as a network drive.

USB Printer: The DSR can provide the LAN with access to printers connected through the USB. The printer driver will have to be installed on the LAN host and traffic will be routed through the DS R between the LAN and printer.

USB 3G modem: A 3G modem dongle can be plugged in and used as a secondary

WAN. Load balancing, auto-failover, or primary WAN access can be configured through the 3G interface.

To configure printer on a Windows machine, f ollow below given steps:

Click 'Start' on the desktop.

Select ‘Printers and faxes’ option.

Right click and select 'add printer' or click on 'Add printer' present at the left menu.

Select the 'Network Printer' radio button and click next (select "device isn 't listed in case of Windows7").

Select the 'Connect to printer using URL' radio button ('Select a shared printer by name ‘in case of Windows 7) and give the following URL http://<Router's LAN IP address>:631/printers/<Model Name> (Model Name can be found in the USB status page of router's GUI).

Click 'next' and select the appropriate driver from the displayed list.

Click on 'next' and 'finish' to complete adding the printer.

180

Unified Services Router

Figure 11 5: USB Dev ice Detectio n

User Manual

8.2 USB share port

Maintenance > Administration > USB SharePort

This page allows configure the SharePort feature available in this router.

181

Unified Services Router

Figure 11 6: USB Sha rePort

User Manual

USB-1

:

Enable USB Printer: Select this option to allow the USB printer connected to the router to be shared across the network.

The USB printer can be accessed on any LAN host (with appropriate printer driver installed) connected to the router by using the following command in the host's add printers window http://<Router's IP:631>/printers/<Device Model> (Device Model can be found in the

USB settings page).

Enable Sharing: Select this option to allow the USB storage device connected to the router to be shared across the network.

USB-2:

Enable USB Printer: Select this option to allow the USB printer connected to the router to be shared across the network.

The USB printer can be accessed on any LAN host (with appropriate printer driver installed) connected to the router by using the following command in the host's add printers window http://<Router's IP:631>/printers/<Device Model> (Device Model can be found in the

USB settings page).

Enable Sharing: Select this option to allow the USB storage device connected to the router to be shared across the network.

Sharing Enabled interfaces

:

The LAN interfaces on which USB sharing is enabled, at least one interface must be selected to begin sharing.

Enable Printer: Enables printer sharing on the selected interface.

Enable Storage: Enables storage device sharing on the selected interface.

182

Unified Services Router

User Manual

8.3 SMS service

Maintenance > Administration > SMS Service > Inbox

The D-Link Services Router has a USB interface to connect 3G modem support to send and receive Short Messaging Service. The received messages can be seen in the Inbox and allows the user to create a new SMS. If WAN3 is used in dedicated wan mode, load balancing mode or if 3G USB Device is not connected to router then the controls on this page will be greyed out.

Figure 11 7: SMS Ser vice – Se nd SMS

The following details are displayed in SMS INBOX page:

Sno: Displays the serial number of message in the inbox.

Sender: Displays the sender of the particular message.

TimeStamp: Displays the time when the message was sent

Text: Displays the content of the particular Message.

The following actions are performed:

Delete: Deletes the SMS having that particular Sno. Only one message can be deleted at a time.

Refresh: Updates the inbox with new SMS (if any).

Reply: Lets the user create a new SMS in reply to a particular message by the selected sender. “Receiver" field in the createSms.htm page is filled with the sender's number.

Forward: Lets the user forward a selected SMS. "Text Message" field in the createSms.htm page is filled with the "Text" of the se lected message.

183

Unified Services Router

Figure 11 8: SMS Ser vice – Receive SMS

User Manual

The following details to be provided in Create Message page:

Receiver: Enter the phone number of the intended receiver of the message.

Text Message: Enter the body of the message here

Click Send Message to send the message.

Click Don't Save Settings to reset Receiver and Text Message fields.

8.4 External Authentication

The local user database present in the router itself is typically used for granting management access for the GUI or CLI. External authentication servers are typically more secure, and can be used for allowing wireless AP connections, authenticating

IPsec endpoints, and even allowing access via a Captive Portal on the VLAN. This section describes the available au thentication servers on the router, and also the configuration requirements.

In all cases, the “Server Checking” button is used to verify connectivity to the configured server(s).

8.4.1 POP3 Server

Security > Authentication >External Auth Server > POP3 Server

POP3 is an application layer protocol most commonly used for e -mail over a TCP/IP connection. The authentication server can be used with SSL encrypti on over port

995to send encrypted traffic to the POP3 server. The POP3 server’s certificate is verified by a user-uploaded CA certificate. If SSL encryption is not used, port 110 will be used for the POP3 authentication traffic.

The DSR router acts only as a POP3 client to authenticate a user by contacting an external POP3 server. This authentication option is available for IPsec, PPTP/L2TP

184

Unified Services Router

User Manual

Server and Captive Portal users. Note that POP3 for PPTP / L2TP servers is supported only with PAP and not with CHAP / MSCHAP / MSCHAPv2 encryption.

Figure 11 9: POP3 A ut hentica tion Server conf igura tion

The “Server Checking” button is used to verify connectivity to the configured server(s). A CA file is used as part of the POP3 negotiation to verify the conf igured authentication server identity. Each of the 3 configured servers can have a unique CA used for authentication.

185

Unified Services Router

Figure 12 0: POP3 C A f ile upl oa d

User Manual

8.4.2 NT Domain Server

Security > Authentication >External Auth Server > NT Domain

The NT Domain server allows users and hosts to authenticate themselves via a pre configured Workgroup field. Typically Windows or Samba servers are used to manage the domain of authentication for the centralized directory of authorized users.

186

Unified Services Router

Figure 12 1: NT Do main Authe nticati on Server conf iguratio n

User Manual

8.4.3 RADIUS Server

Security > Authentication > External Auth Server > RADIUS Server

Enterprise Mode for wireless security uses a RADIUS Server for WPA and/or WPA2 security. A RADIUS server must be configured and accessible by the router to authenticate wireless client connections to an AP enabled with a profile that uses

RADIUS authentication.

The Authentication IP Address is required to identify the server. A secondary

RADIUS server provides redundancy in the event that the primary server cannot be reached by the router when needed.

187

Unified Services Router

User Manual

Authentication Port: the port for the RADIUS server connection

Secret: enter the shared secret that allows this router to log into the specified

RADIUS server(s). This key must match the shared secret on the RADIUS Server.

The Timeout and Retries fields are used to either move to a secondary server if the primary cannot be reached, or to give up the RADIUS authentication attempt if communication with the server is not possible.

Figure 12 2: RA DIU S Server co nf iguratio n

188

Unified Services Router

8.4.4 Active Directory Server

User Manual

Security > Authentication >External Auth Server > AD Server

Active Directory authentication is an enhanced version of NT Domain authentication.

The Kerberos protocol is leveraged for authentication of users, who are grouped in

Organizational Units (OUs). In particular the Active Directory server can support more than a million users given is structure while the NT Domain server is limited to thousands.

The configured Authentication Servers and Active Directory domain(s) are used to validate the user with the directory of users on the external Windows based server.

This authentication option is common for SSL VPN client users and is also useful for

IPsec / PPTP / L2TP client authentication.

Figure 12 3: Active D irectory A ut hentica t ion Server co nf igura tion

189

Unified Services Router

8.4.5 LDAP Server

User Manual

Security > Authentication >External Auth Server > LDAP Server

The LDAP authentication method uses LDAP to exchange authentication credentials between the router and external server. The LDAP server maintains a large database of users in a directory structure, so users with t he same username but belonging to different groups can be authenticated since the user information is stored in a hierarchal manner. Also of note is that configuring a LDAP server on Windows or

Linux servers is considerably less complex than setting up NT Domain or Active

Directory servers for user authentication.

The details configured on the router will be passed for authenticating the router and its hosts. The LDAP attributes, domain name (DN), and in some cases the administrator account & password are key fields in allowing the LDAP server to authenticate the router.

190

Unified Services Router

Figure 12 4: L DAP A ut hentica tion Server conf igura tion

User Manual

8.5 Authentication Certificates

VPN > IPSec VPN > Certificates > Trusted Certificates

This gateway uses digital certificates for IPsec VPN authentication as well as SSL validation (for HTTPS and SSL VPN authentication). You can obtain a digital certificate from a well-known Certificate Authority (CA) such as VeriSign, or generate and sign your own certificate using functionality available on this gateway. The gateway comes with a self-signed certificate, and this can be replaced by one signed by a CA as per your networking requirements. A CA certificate provides strong assurance of the server’s identity and is a requirement for most corporate network VPN solutions.

191

Unified Services Router

User Manual

The certificates menu allows you to view a list of certificates (both from a CA and self signed) currently loaded on the gateway. The following certificate data is displayed in the list of Trusted (CA) certificates:

CA Identity (Subject Name): The certificate is issued to this person or organization

Issuer Name: This is the CA name that issued this certificate

Expiry Time: The date after which this Trusted certificate becomes inv alid

A self certificate is a certificate issued by a CA identifying your device (or self -signed if you don’t want the identity protection of a CA). The Active Self Certificate table lists the self certificates currently loaded on the gateway. The following information is displayed for each uploaded self certificate:

Name: The name you use to identify this certificate, it is not displayed to IPsec

VPN peers or SSL users.

Subject Name: This is the name that will be displayed as the owner of this certificate. This should be your official registered or company name, as IPsec or

SSL VPN peers are shown this field.

Serial Number: The serial number is maintained by the CA and used to identify this signed certificate.

Issuer Name: This is the CA name that issued (signed) this certificate

Expiry Time: The date after which this signed certificate becomes invalid – you should renew the certificate before it expires.

To request a self certificate to be signed by a CA, you can generate a Certificate Signing

Request from the gateway by entering identification parameters and pass ing it along to the CA for signing. Once signed, the CA’s Trusted Certificate and signed certificate from the CA are uploaded to activate the self -certificate validating the identity of this gateway. The self certificate is then used in IPsec and SSL connections with peers to validate the gateway’s authenticity.

192

Unified Services Router

User Manual

Figure 12 5: Certif icate summary f or IP sec and HTTP S ma na geme nt

193

Unified Services Router

User Manual

8.6 Advanced Switch Configuration

Maintenance > Management > Power Saving

The DSR allows you to adjust the power consumption of the hardware based on your actual usage. The two “green” options available for your LAN switch are Power Saving by Link Status and Length Detection State. With “Power Saving by Link Status” option enabled, the total power consumption by the LAN switch is dependent function of on the number of connected ports. The overall current draw when a single port is connected is less than when all the ports are connected. With “Length De tection State” option enabled, the overall current supplied to a LAN port is reduced when a smaller cable length is connected on a LAN port.

Jumbo Frames support can be configured as an advanced switch configuration. Jumbo frames are Ethernet frames with more than 1500 bytes of payload. When this option is enabled, the LAN devices can exchange information at Jumbo frames rate.

Figure 12 6: Advance d Switch Setti ng s

8.7 Package Manager

Maintenance > Administration > Package Manager

A package is a set of files which are installed by the router from D -Link’s repositories.

This feature allows users to download new drivers for supported USB devices and language packs to enable multi-lingual support for the router’s management interface .

Multi-lingual support via the package manager allows the user to choose a language of choice so that the entire textual content in the router’s user interface is presented in the selected language.

DSR-1000, DSR-1000N, DSR-500, and DSR-500N support the Package Manager feature.

This feature supports a single driver and single language pack to be stored in the router

(i.e. these files are available for use after device reboot) . There are 2 types of installations supported by this feature:

194

Unified Services Router

User Manual

1.

Manual Installation: Upon selecting manual installation, the user has to download the package which will then display the available languages that the router GUI now supports.

Only drivers provided by D-Link can be used for manual installation. A validation process will be performed during installation.

2.

Auto Installation:

By selecting the link “click here” the Auto installation of the package is exercised. A page showing the list of available drivers / language packs is displayed from which the user can select and instal l one of the options.

For this type of installation the router must be able to access the internet, as this will allow the user to download the package from a repository server which consists of all the available languages.

Figure 12 7: Device Drivers

Device Drivers: Users can install drivers manually or can install from the listed drivers.

List of Device Drivers: It allows the user to install or uninstall the available drivers.

Manual Install: User can upload the provided driver package for installation.

195

Unified Services Router

User Manual

Browse: The user can choose the package to upload. Click on “Install” to save your changes.

Figure 12 8: Install at ion of driver/lang ua ge pac k

196

Unified Services Router

User Manual

Upon clicking on the link “click here”, a page showing the list of device drivers is displayed.

Driver: Description of the driver name.

Description: This describes the type of language installation pack supported.

Installed: All the language installation packs or option 3G Driver for ThreeG V -1.0 displayed in the list of device drivers are shown in Red color by default since none of them have been selected. When a particular language installation pack or if Option

Driver for ThreeG V-1.0 is selected then the button turns green in color.

Action: It consists of 2 options:

Install 1.0: Click on “Install 1.0” to install a particular Langua ge pack.

Remove: To remove the installed language pack, click on “Remove”.

Manual Install: User can upload the provided driver package for installation.

Install History: This displays the history of the language packs installed/uninstalled previously along with the respective date and time to show when they were installed/uninstalled.

Figure 12 9: Selectio n of Installe d La ng uage

Once the language has been selected by the user from the list of Device Drivers, the

“Set Language” option under “Tools” menu will display the selected language. The user must select the language from the drop down l ist of “Set Language” and save the settings so that this configuration is applied in its entirety.

197

Unified Services Router

User Manual

Chapter 9.

Administration & Management

9.1 Configuration Access Control

The primary means to configure this gateway via the browser -independent GUI. The

GUI can be accessed from LAN node by using the gateway’s LAN IP address and HTTP, or from the WAN by using the gateway’s WAN IP address and HTTPS (HTTP over

SSL).

Administrator and Guest users are permitted to login to the router’s management interface. The user type is set in the

Advanced > Users > Users

page. The Admin or

Guest user can be configured to access the router GUI from the LAN or the Internet

(WAN) by enabling the corresponding Login Policy.

198

Unified Services Router

Figure 13 0: User Lo gin policy c onf igura t ion

User Manual

9.1.1 Admin Settings

Maintenance > Administration > System settings

199

Unified Services Router

This page allows one to set the name of the router.

Figure 13 1: Admi n Setting s

User Manual

9.1.2 License Updates

Maintenance > Administration > Licsense Update

Certain features available in the DSR require a license. The licence is presented in the form of a code specific for this particular router, which when activated enables the use of this feature for a fixed duration. A license code is provided based on the router’s

MAC Address, so it is unique to that particular device.

Each license has the following three parameters:

Model: The license key model as it relates to the feature being enabled.

Activation Code: The specific activiation code corresponding to th is license.

Expires: Licenses can either have a fixed duration, which would be displayed in this column, or are perpetual for the life of this router.

Currently, dynamic web content filtering (WCF) is the only license -controlled feature available in the DSR products.

200

Unified Services Router

Figure 13 2: Lice nse uplo ad f ield a nd List of Active Licenses

User Manual

9.1.3 Remote Management

Maintenance > Management > Remote Management

Both HTTPS and telnet access can be restricted to a subset of IP addresses. The router administrator can define a known PC, single IP address or range of IP addresses that are allowed to access the GUI with HTTPS. The opened port for SSL traffic can be changed from the default of 443 at the same time as defining the allowed remote management IP address range.

201

Unified Services Router

Figure 13 3: Re mote Manage me nt f ro m t he WAN

User Manual

Maintenance > Administration > Web GUI Management

This feature restricts management access via the GUI to a predefined set of IP addresses or VLAN subnets. When enabled, the GUI management access can be restricted for all LAN hosts, and instead enabled only via a specific IP address or specific VLAN subnet.

When this feature is enabled:

Access will be allowed by the configured IP address or VLAN subnet, and no other LAN hosts will be allowed to access the GUI management interface.

Only the GUI management is affected. CLI / SNMP are not affected by this control

User will still need administrator credentials to modify configuration settings

202

Unified Services Router

Figure 13 4: We b GU I Ma nage me nt f ro m the W AN

User Manual

9.1.4 CLI Access

In addition to the web -based GUI, the gateway supports SSH and Telnet management for command-line interaction. The CLI login credentials are shared with the GUI for administrator users. To access the CLI, type “cli” in the SSH or console prompt and login with administrator user credentials.

9.2 SNMP Configuration

Maintenance > Management > SNMP

SNMP is an additional manageme nt tool that is useful when multiple routers in a network are being managed by a central Master system . When an external SNMP manager is provided with this router’s Management Information Base (MIB) file, the manager can update the router’s hierarchal variables to view or update configuration parameters. The router as a managed device has an SNMP agent that allows the MIB configuration variables to be accessed by the Master (the SNMP manager). The Access

Control List on the router identifies managers in the network that have read-only or read-write SNMP credentials. The Traps List outlines the port over which notifications from this router are provided to the SNMP community (managers) and also the SNMP version (v1, v2c, v3) for the trap.

203

Unified Services Router

Figure 13 5: SNMP U sers, Tra ps, a nd Acc ess Co ntrol

User Manual

Maintenance > Management > SNMP > SNMP System Info

The router is identified by an SNMP manager via the System Information. The identifier settings The SysName set here is also used to identi fy the router for SysLog logging.

204

Unified Services Router

Figure 13 6: SNMP syste m i nf or matio n f or thi s ro uter

User Manual

9.3 Configuring Time Zone and NTP

Maintenance > Administration

> Date and Time

You can configure your time zone, whether or not to adjust for Day light Savings Time, and with which Network Time Protocol (NTP) server to synchronize the date and time.

You can choose to set Date and Time manually, which will store the information on the router’s real time clock (RTC). If the router has access to the internet, the most accurate mechanism to set the router time is to enable NTP server communication.

Accurate date and time on the router is critical for firewall schedules, Wi -Fi power saving support to disable APs at certain times of the day, and accurat e logging.

Please follow the steps below to configure the NTP server:

1.

Select the router’s time zone, relative to Greenwich Mean Time (GMT).

2.

If supported for your region, click to Enable Daylight Savings.

3.

Determine whether to use default or custom Network Time Protocol (NTP) servers. If custom, enter the server addresses or FQDN.

205

Unified Services Router

Figure 13 7: Date, Ti me, a nd NTP server setup

User Manual

9.4 Log Configuration

This router allows you to capture log messages for traffic through the firewall, VPN, and over the wireless AP. As an administrator you can monitor the type of traffic that goes through the router and also be notified of potential attacks or errors when they are detected by the router. The following sections describe the log configuration sett ings and the ways you can access these logs.

9.4.1 Defining What to Log

Maintenance > Log Settings > Facility Logs

The Logs Facility page allows you to determine the granularity of logs to receive from the router. There are three core components of the router, referred to as Facilities:

Kernel: This refers to the Linux kernel. Log messages that correspond to this facility would correspond to traffic through the firewall or network stack.

System: This refers to application and management level features available on this router, including SSL VPN and administrator changes for managing the unit.

Wireless: This facility corresponds to the 802.11 driver used for providing AP functionality to your network.

Local1-UTM: This facility corresponds to IPS (Intrusion Prevention System) which helps in detecting malicious intrusion attempts from the WAN.

For each facility, the following events (in order of severity) can be logged:

Emergency, Alert, Critical, Error, Warning, Notification, Information, Debugging.

When a particular severity level is selected, all events with severity equal to and greater than the chosen severi ty are captured. For example if you have configured

CRITICAL level logging for the Wireless facility, then 802.11 logs with severities

CRITICAL, ALERT, and EMERGENCY are logged. The severity levels available for logging are:

206

Unified Services Router

EMERGENCY: system is unusable

ALERT: action must be taken immediately

CRITICAL: critical conditions

ERROR: error conditions

WARNING: warning conditions

NOTIFICATION: normal but significant condition

INFORMATION: informational

DEBUGGING: debug-level messages

Figure 13 8: Facility setti ngs f or Loggi ng

User Manual

The display for logging can be customized based on where the logs are sent, ei ther the Event Log viewer in the GUI (the Event Log viewer is in the

Status > Logs

page) or a remote Syslog server for later review. E-mail logs, discussed in a subsequent section, follow the same configuration as logs configured for a Syslog server.

Maintenance > Log Settings > Routing Logs

This page allows you to determine the type of traffic through the router that is logged for display in Syslog, E -mailed logs, or the Event Viewer. Denial of service attacks, general attack information, login attempts, dropped packets, and similar events can be captured for review by the IT administrator.

207

Unified Services Router

User Manual

Traffic through each network segment (LAN, WAN, DMZ) can be tracked based on whether the packet was accepted or dropped by the firewall.

Accepted Packets are those that were successfully transferred through the corresponding network segment (i.e. LAN to WAN). This option is particularly useful when the Default Outbound Policy is “Block Always” so the IT admin can monitor traffic that is passed through the firewall.

Example: If Accept Packets from LAN to WAN is enabled and there is a firewall rule to allow SSH traffic from LAN, then whenever a LAN machine tries to make an SSH connection, those packets will be accepted and a message will be logged. ( Assuming the log option is set to Allow for the SSH firewall rule.)

Dropped Packets are packets that were intentionally blocked from being transferred through the corresponding network segment. This option is useful when the Default

Outbound Policy is “Allow Always”.

Example: If Drop Packets from LAN to WAN is enabled and there is a firewall rule to block SSH traffic from LAN, then whenever a LAN machine tries to make an SSH connection, those packets will be dropped and a message will be logged. (Make sure the log option is s et to allow for this firewall rule.)

Enabling accepted packet logging through the firewall may generate a significant volume of log messages depending on the typical network traffic. This is recommended for debugging purposes only.

In addition to network segment logging, unicast and multicast traffic can be logged.

Unicast packets have a single destination on the network, whereas broadcast (or multicast) packets are sent to all possible destinations simultaneously. One other useful log control is to log packets that are dropped due to configured bandwidth profiles over a particular interface. This data will indicate to the admin whether the bandwidth profile has to be modified to account for the desired internet traffic of LAN users.

208

Unified Services Router

Figure 13 9: L og co nf iguratio n options f or traf f ic throug h ro ut er

User Manual

Maintenance > Log Settings > IPv6 logs

This page allows you to configure the IPv6 logging

Figure 14 0: IPv6 Lo g conf igur atio n o pti ons f or traf f ic through ro uter

9.4.2 Sending Logs to E-mail or Syslog

Maintenance > Log Settings > Remote Logs

Once you have configured the type of logs that you want the router to collect, they can be sent to either a Syslog server or an E -Mail address. For remote logging a key configuration field is the Remote Log Identifier. Every logged message will contain the configured prefix of the Remote Log Identifier, so that syslog servers or email addresses that receive logs from more than one router can sort for the relevant device’s logs.

209

Unified Services Router

User Manual

Once you enable the option to e -mail logs, enter the e-mail server’s address (IP address or FQDN) of the SMTP server. The router will connect to this server when sending e-mails out to the configured addresses. The SMTP port and return e-mail addresses are required fields to allow the router to package the logs and send a valid e-mail that is accepted by one of the configured “send -to” addresses. Up to three email addresses can be configured as log recipients.

In order to establish a connection with the conf igured SMTP port and server, define the server’s authentication requirements. The router supports Login Plain (no encryption) or CRAM-MD5 (encrypted) for the username and password data to be sent to the SMTP server. Authentication can be disabled if the server does not have this requirement. In some cases the SMTP server may send out IDENT requests, and this router can have this response option enabled as needed.

Once the e-mail server and recipient details are defined you can determine when the router should send out logs. E-mail logs can be sent out based on a defined schedule by first choosing the unit (i.e. the frequency) of sending logs: Hourly, Daily, or

Weekly. Selecting Never will disable log e -mails but will preserve the e-mail server settings.

Figure 14 1: E - mail c onf igurati on as a Re mo te Lo gging o ptio n

An external Syslog server is often used by network administrator to collect and store logs from the router. This remote device typically has less memory constraints tha n the local Event Viewer on the router’s GUI, and thus can collect a considerable number of logs over a sustained period. This is typically very useful for debugging network issues or to monitor router traffic over a long duration.

210

Unified Services Router

User Manual

This router supports up to 8 concurrent Syslog servers. Each can be configured to receive different log facility messages of varying sever ity. To enable a Syslog server select the checkbox next to an empty S yslog server field and assign the IP address or

FQDN to the Name field. The selected facility and severity level messages will be sent to the configured (and enabled) S yslog server once you save this configuration page’s settings.

Figure 14 2: Sy slog server conf iguratio n f or Remote Lo ggi ng ( conti nue d )

9.4.3 Event Log Viewer in GUI

Status > Logs > View All Logs

The router GUI lets you observe configured log messages from the Status menu.

Whenever traffic through or to the router matches the settings determined in the

Tools

> Log Settings > Logs Facility

or

Tools > Log Settings > Logs Configuration

pages, the corresponding log message will be displayed in this window with a timestamp.

It is very important to have accurate system time (manually set or from a NTP server) in order to understand log messages.

Status > Sysytem Information > All Logs > IPSec VPN Logs

This page displays IPsec VPN log messages as determined by the configuration settings for facility and severity. This data is useful when evaluating IPsec VPN traffic and tunnel health.

211

Unified Services Router

Figure 14 3: VPN l og s displaye d i n GUI e vent viewer

User Manual

9.5 Backing up and Restoring Configuration

Settings

Maintenance > Firmware&config. > Backup/restore

You can back up the router’s custom configuration settings to restore them to a different device or the same router after some other changes. During backup, your settings are saved as a file on your host. You can restore the router's saved settings from this file as well. This page will also allow you revert to factory default settings or execute a soft reboot of the router. This page also allows you to download and automate the dbglog package, agrouping of system status, statistics, and support logs that are useful for D -

Link support to diagnose router issues.

IMPORTANT!

During a restore operation, do NOT try to go online, turn off the router, shut down the PC, or do anything else to the router until the operation is complete. This will take approximately 1 minute. Once the LEDs are turned off, wait a few more seconds before doing anything with the router.

For backing up configuration or restoring a previously saved configuration, please follow the steps below:

1.

To save a copy of your current settings, click the Backup button in the Save Current

Settings option. The browser initiates an export of the configuration file and prompts to save the file on your host.

2.

If there is a USB storage device currently plugged in to the system, you can enable

Autobackup of the configuration file to the USB file system. The snapshot of current configuration settings will be updated on the USB file system and overwrite any files with the same filename (i.e. if there was an earlier configuration backup done to this location).

212

Unified Services Router

User Manual

3.

To restore your saved settings from a backup file, click Browse then locate the file on the host. After clicking Restore, the router begins importing the file’s saved configuration settings. After the restore, the router reboots automatically with the restored settings.

4.

To erase your current settings and revert to factory default settings, click the Default button. The router will then restore configuration settings to factory defaults and will reboot automatically. (See Appendix B for the factory default parameters for the router).

Figure 14 4: Rest oring conf igur atio n f rom a saved f ile will result i n t he current co nf igura tio n being overwritten and a re boo t

The configuration file can be encrypted during the backup process by enabling encryption. This will ensure confidential information like system username / passwords are not available for view by unauthorized sources. Selecting this option will apply to configuration files backed up on the host as well as a USB drive.

213

Unified Services Router

User Manual

9.6 Generating DBGLOGs

Tools > System

This page also allows you to download a nd automate the debug log (a.k.a. “dbglog”) package, agrouping of system status, statistics, and support logs that are useful for D -

Link support to diagnose router issues.

Clicking the download link for the debug logs will result in the package being saved on the host machine used to manage this router. This package (a compressed archive) can then be sent to D-Link support for evauation.

9.7 Upgrading Router Firmware

Maintenance > Firmware&config. > Firmware upgrade > Using System (PC)

You can upgrade to a newer software version from the Administration web page. In the

Firmware Upgrade section, to upgrade your firmware, click Browse, locate and select the firmware image on your host, and click Upgrade. After the new firmware image is validated, the new image is written to flash, and the router is automatically rebooted with the new firmware. The Firmware Information and also the

Status > Device Info

> Device Status

page will reflect the new firmware version.

IMPORTANT!

During firmware upgrade, do NOT try to go online, turn off the

DSR, shut down the PC, or interrupt the process in anyway until the operation is complete. This should take only a minute or so including the reboot p rocess.

Interrupting the upgrade process at specific points when the flash is being written to may corrupt the flash memory and render the router unusable without a lowlevel process of restoring the flash firmware (not through the web GUI).

214

Unified Services Router

Figure 14 5: Fir mw ar e versio n i nf orma tio n a nd upgra de o pti o n

User Manual

This router also supports an automated notification to determine if a newer firmware version is available for this router. By clicking the Check Now button in the notification section, the router will check a D -Link server to see if a newer firmware version for this router is available for download and update the Status field below.

IMPORTANT!

After firmware 1.04B13, new user database architecture is introduced. The new user database is easier to setup and more intuitively to use.

When users upgrade DSR’s firmware to 1.04B13 or latter, DSR will automatically merge users in the old database into the new one. However, all user databases will be swept away when users downgrade firm ware from 1.04B13 to the older one, e.g. 1.03B43. Please keep in mind: backup your user database for further restoring once you decide to downgrade firmware to the older on e.

9.8 Upgrading Router Firmware via USB

Maintenance > Firmware&config. > Firmware upgrade > Using USb

This page allows user to upgrade the firmware, backup and restore the settings using a

USB storage key.

215

Unified Services Router

User Manual

Figure 14 6: Fir mw ar e upgrade a nd c onf iguratio n re store/ bac kup vi a USB

9.9 Dynamic DNS Setup

Network > Internet > Dynamic DNS > Dynamic DNS WAN1 Settings

Dynamic DNS (DDNS) is an Internet service that allows routers with varying public IP addresses to be located using Internet domain names. To use DDNS, you must setup an account with a DDNS provider such as DynDN S.org, D-Link DDNS, or Oray.net.

Each configured WAN can have a different DDNS service if required. Once configured, the router will update DDNS services changes in the WAN IP address so that features that are dependent on accessing the router’s WAN via FQDN will be directed to the correct IP address. When you set up an account with a DDNS service, the host and domain name, username, password and wildcard support will be provided by the account provider.

216

Unified Services Router

Figure 14 7: Dy na mic DN S co nf igura tion

User Manual

9.10 Using Diagnostic Tools

Maintenance > Management > Diagnostics > Network Tools

The router has built in tools to allow an administrator to evaluate the communication status and overall network health.

217

Unified Services Router

Figure 14 8: Ro uter diag no stics tool s ava ilable i n t he GUI

User Manual

218

Unified Services Router

User Manual

9.10.1 Ping

This utility can be used to test connectivity between this router and another device on the network connected to this router. Enter an IP address and click PING . The command output will appear indicating the ICMP echo request status.

9.10.2 Trace Route

This utility will display all the routers present between the destin ation IP address and this router. Up to 30 “hops” (intermediate routers) between this router and the destination will be displayed.

219

Unified Services Router

Figure 14 9: Sa mple t race route out put

User Manual

9.10.3 DNS Lookup

To retrieve the IP address of a Web, FTP, Mail or any other server on the Internet, type the Internet Name in the text box and click Lookup. If the host or domain entry exists, you will see a response with the IP address. A message stating “Unknown

Host” indicates that the specified Internet Name does not exist.

This feature assumes there is internet access available on the WAN link(s) .

9.10.4 Router Options

The static and dynamic routes configured on this router can be shown by clicking

Display for the corresponding routing table. Clicking the Packet Trace button will allow the router to capture and display traffic through the DSR between the LAN and

WAN interface as well. This information is often very useful in debugging traffic and routing issues.

220

Unified Services Router

User Manual

9.11 Localization

Maintenance > Administration > Set Language

The router GUI displays content in English by default. T he package manager feature has to be enabled so that the appropriate language of the installed language pack age is shown. The user must configure the package manager feature under Advanced settings first, in order to install a language package.

Figure 15 0: L ocali za tion

221

Unified Services Router

Chapter 10.

Router Status and Statistics

User Manual

10.1 System Overview

The Status page allows you to get a detailed overview of the system configuration. The settings for the wired and wireless interfaces are displayed in the DSR Status page, and then the resulting hardware resource and router usage details are summarized on the router’s Dashboard.

10.1.1 Device Status

Status > System Information > Device > System

The DSR Status page gives a summary of the router configuration settings configured in the Setup and Advanced menus. The static hardware serial number and current firmware version are presented in the General section. The WAN and LAN interface information shown on this page are based on the administrator configuration parameters. The radio band and channel settings are presented below along with all configured and active APs that are enabled on this router.

222

Unified Services Router

Figure 15 1: Device Status di spla y

User Manual

223

Unified Services Router

User Manual

224

Unified Services Router

Figure 15 2: Device Status di spla y (co nti nued)

User Manual

10.1.2 Resource Utilization

Status > Device Info > Dashboard

The Dashboard page presents hardware and usage statistics. The CPU and Memory utilization is a function of the available hardware and current configuration and traffic through the router. Interface statistics for the wired connections (LAN, WAN1,

WAN2/DMZ, VLANs) provide indication of packets through and packets dropped by the interface. Click refresh to have this page retrieve the most current statistics.

225

Unified Services Router

Figure 15 3: Reso urc e Utili zatio n st atisti cs

User Manual

Figure 15 4: Reso urc e Utili zatio n da ta (c onti nue d)

Figure 15 5: Reso urc e Utili zatio n da ta (c onti nue d)

226

Unified Services Router

10.2 Traffic Statistics

10.2.1 Wired Port Statistics

User Manual

Status > Network Information > Device Statistics

Detailed transmit and receive statistics for each physical port are presented here. Each interface (WAN1, WAN2/DMZ, LAN, and VLANs) have port specific packet level information provided for review. Transmitted/received packets, port collisions, and the cumulating bytes/sec for transmit/receive directions are provided for each interface along with the port up time. If you suspect issues with any of the wired ports, this table will help diagnose uptime or transmit level issues with the port.

The statistics table has auto-refresh control which allows display of the most current port level data at each page refresh. The default auto-refresh for this page is 10 seconds.

Figure 15 6: P hysic al port st ati stics

10.2.2 Wireless Statistics

Status > Network Information > Wireless Statistics

The Wireless Statistics tab displays the incrementing traffic statistics for each enabled access point. This page will give a snapshot of how much traffic is being transmitted over each wireless link. If you suspect that a radio or VAP may be down, the details on this page would confirm if traffic is being sent and received th rough the VAP.

The clients connected to a particular AP can be viewed by using the S tatus Button on the list of APs in the

Setup > Wireless > Access Points

page. Traffic statistics are shown for that individual AP, as compared to the summary stats for eac h AP on this

Statistics page. The poll interval (the refresh rate for the statistics) can be modified to view more frequent traffic and collision statistics.

227

Unified Services Router

Figure 15 7: AP speci f ic statistics

User Manual

10.3 Active Connections

10.3.1 Sessions through the Router

Status > Network Information > Active Sessions

This table lists the active internet sessions through the router’s firewall. The session’s protocol, state, local and remote IP addresses are shown.

Figure 15 8: Li st of cu rrent Active Firew all Se ssio ns

10.3.2 Wireless Clients

Status > Network Information > Wireless Clients

The clients connected to a particular AP can be viewed on this page. Connected clients are sorted by the MAC address and indicate the security parameters use d by the wireless link, as well as the time connected to the corresponding AP.

228

Unified Services Router

User Manual

The statistics table has auto-refresh control which allows display of the most current port level data at each page refresh. The default auto-refresh for this page is 10 seconds.

Figure 15 9: Li st of connected 802. 11 clie nt s per AP

10.3.3 LAN Clients

Status > Network Information > LAN Clients

The LAN clients to the router are identified by a n ARP scan through the LAN switch.

The NetBIOS name (if available), IP address and MAC address of discovered LAN hosts are displayed.

Figure 16 0: Li st of L AN ho st s

10.3.4 Active VPN Tunnels

Status > Network Information > Active VPNs >IPsec SAs

You can view and change the status (connect or drop) of the router’s IPsec security associations. Here, the active IPsec SAs (security associations) are listed along with

229

Unified Services Router

User Manual the traffic details and tunnel state. The traffic is a cumulative measure of transmitted/received packets since the tunn el was established.

If a VPN policy state is “IPsec SA Not Established”, it can be enabled by clicking the

Connect button of the corresponding policy. The Active IPsec SAs table displays a list of active IPsec SAs. Table fields are as follows.

Field

Policy Name

Endpoint

Tx (KB)

Tx (Packets)

State

Description

IKE or VPN policy associated with this SA.

IP address of the remote VPN gateway or client.

Kilobytes of data transmitted over this SA.

Number of IP packets transmitted over this SA.

Status of the SA for IKE policies: Not Connected or IPsec SA Established.

230

Unified Services Router

Figure 16 1: Li st of current Active V PN Sessio ns

User Manual

All active SSL VPN connections, both for VPN tunnel and VPN Port forwarding, are displayed on this page as well. Table fields are as follows.

231

Unified Services Router

User Manual

Field

User Name

IP Address

Local PPP Interface

Peer PPP Interface IP

Connect Status

Description

The SSL VPN user that has an active tunnel or port forwarding session to this router.

IP address of the remote VPN client.

The interface (WAN1 or WAN2) through which the session is active.

The assigned IP address of the virtual network adapter.

Status of the SSL connection between this router and the remote VPN client: Not

Connected or Connected.

232

Unified Services Router

Chapter 11.

Trouble Shooting

User Manual

11.1 Internet connection

Symptom:

You cannot access the router’s web -configuration interface from a PC on your LAN.

Recommended action:

1.

Check the Ethernet connection between the PC and the router.

2.

Ensure that your PC’s IP address is on the same subnet as the router. If you are using the recommended addressing scheme, your PC’s address should be in the range 192.168.10.2 to 192.168.10.254.

3.

Check your PC’s IP address. If the PC cannot reach a DHCP server, some versions of

Windows and Mac OS generate and assign an IP address. These auto-generated addresses are in the range 169.254.x.x. If your IP address is in this range, check the connection from the PC to the firewall and reboot your PC.

4.

If your router’s IP address has changed and you don’t know what it is, reset the router configuration to factory defaults (this sets the firewall’s IP address to 192.168.10.1).

5.

If you do not want to reset to factory default settings and lose your configuration, reboot the router and use a packet sniffer (such as Ethereal™) to capture packets sent during the reboot. Look at the Address Resolution Protocol (ARP) packets to locate the router’s LAN interface address.

6.

Launch your browser and ensure that Java, JavaScript, or ActiveX is enabled. If you are using Internet Explorer, click Refresh to ensure that the Java applet is loaded. Close the browser and launch it again.

7.

Ensure that you are using the correct login information. The factory default login name is admin and the password is password. Ensure that CAPS LOCK is off when entering this information.

Symptom:

Router does not save configuration changes.

Recommended action:

1.

When entering configuration settings, click Apply before moving to another menu or tab; otherwise your changes are lost.

2.

Click Refresh or Reload in the browser. Your changes may have been made, but the browser may be caching the old configuration.

Symptom:

Router cannot access the Internet.

233

Unified Services Router

User Manual

Possible cause:

If you use dynamic IP addresses, your router may not have requested an IP address from the ISP.

Recommended action:

1.

Launch your browser and go to an external site such as www.google.com

.

2.

Access the firewall’s configuration main menu at http://192.168.10.1

.

3.

Select

Monitoring > Router Status

.

4.

Ensure that an IP address is shown for the WAN port. If 0.0.0.0 is shown, your firewall has not obtained an IP address from your ISP. See the next symptom.

Symptom:

Router cannot obtain an IP address from the ISP.

Recommended action:

1.

Turn off power to the cable or DSL modem.

2.

Turn off the router.

3.

Wait 5 minutes, and then reapply power to the cable or DSL modem.

4.

When the modem LEDs indicate that it has resynchronized with the ISP, reapply power to the router. If the router still cannot obtain an ISP address, see the next symptom.

Symptom:

Router still cannot obtain an IP address from the ISP.

Recommended action:

1.

Ask your ISP if it requires a login program — PPP over Ethernet (PPPoE) or some other type of login.

2.

If yes, verify that your configured login name and password are correct.

3.

Ask your ISP if it checks for your PC's hostname.

4.

If yes, select

Network Configuration > WAN Settings > Ethernet ISP

Settings

and set the account name to the PC hostname of your ISP account.

5.

Ask your ISP if it allows only one Ethernet MAC address to connect to the Internet, and therefore checks for your PC’s MAC address.

6.

If yes, inform your ISP that you have bought a new network device, and ask them to use the firewall’s MAC address.

7.

Alternatively, select

Network Configuration > WAN Settings > Ethernet IS P

Settings

and configure your router to spoof your PC’s MAC address.

Symptom:

Router can obtain an IP address, but PC is unable to load Internet pages.

234

Unified Services Router

User Manual

Recommended action:

1.

Ask your ISP for the addresses of its designated Domain Name System (DNS) servers.

Configure your PC to recognize those addresses. For details, see your operating system documentation.

2.

On your PC, configure the router to be its TCP/IP gateway.

11.2 Date and time

Symptom:

Date shown is January 1, 1970.

Possible cause:

The router has not yet successfully reached a network time server

(NTS).

Recommended action:

1.

If you have just configured the router, wait at least 5 minutes, select

Administration >

Time Zone

, and recheck the date and time.

2.

Verify your Internet access settings.

Symptom:

Time is off by one hour.

Possible cause:

The router does not automatically adjust for Daylight Savings Time.

Recommended action:

1.

Select

Administration > Time Zone

and view the current date and time settings.

2.

Click to check or uncheck “Automatically adjust for Daylight Savings Time”, then click

Apply.

11.3 Pinging to Test LAN Connectivity

Most TCP/IP terminal devices and firewalls contain a ping utility that sends an ICMP echo-request packet to the designated device. The DSR responds with an echo reply.

Troubleshooting a TCP/IP network is made very easy by using the ping utility in your

PC or workstation.

11.3.1 Testing the LAN path from your PC to your router

1.

From the PC’s Windows toolbar, select Start > Run.

2.

Type ping <IP_address> where <IP_address> is the router’s IP address. Example: ping

192.168.10.1.

3.

Click OK.

235

Unified Services Router

User Manual

4.

Observe the display:

If the path is working, you see this message sequence:

Pinging <IP address> with 32 bytes of data

Reply from <IP address>: bytes=32 time=NN ms TTL=xxx

If the path is not working, you see this message sequence:

Pinging <IP address> with 32 bytes of data

Request timed out

5.

If the path is not working, Test the physical connections between PC and router

If the LAN port LED is off, go to the “LED displays” section on pa ge B-

1 and follow instructions for “LAN or Internet port LEDs are not lit.”

Verify that the corresponding link LEDs are lit for your network interface card and for any hub ports that are connected to your workstation and firewall.

6.

If the path is still not up, test the network configuration:

Verify that the Ethernet card driver software and TCP/IP software are installed and configured on the PC.

Verify that the IP address for the router and PC are correct and on the same subnet.

11.3.2 Testing the LAN path from your PC to a remote device

1.

From the PC’s Windows toolbar, select Start > Run.

2.

Type ping -n 10 <IP_address> where -n 10 specifies a maximum of 10 tries and <IP address> is the IP address of a remote device such as your ISP’s DNS server. Example: ping -n 10 10.1.1.1.

3.

Click OK and then observe the display (see the previous procedure).

4.

If the path is not working, do the following:

Check that the PC has the IP address of your firewall listed as the default gateway. (If the IP configuration of your PC is assigned by DHCP, this information is not visible in your PC’s Network Control Panel.)

236

Unified Services Router

User Manual

Verify that the network (subnet) address of your PC is different from the network address of the remote device.

Verify that the cable or DSL modem is connected and functioning.

Ask your ISP if it assigned a hostname to your PC.

If yes, select

Network Configuration > WAN Settings > Ethernet ISP Settings

and enter that hostname as the ISP account name.

Ask your ISP if it rejects the Ethernet MAC addresses of all but one of your PCs.

Many broadband ISPs restrict access by allowing traffic from the MAC address of only your broadband modem; but some ISPs additionally restrict access to the MAC address of just a single PC connected to that modem. If this is the case, configure your firewall to clone or spoof the MAC address from the authorized PC.

11.4 Restoring factory-default configuration settings

To restore factory-default configuration settings, do either of the following:

1.

Do you know the account password and IP address?

If yes, select

Maintenance > Firmware & Config > Soft Reboot

and click Default.

If you do not, do the following: o

On the rear panel of the router, press and hold the Reset button about 10 seconds, until the test LED lights and then blinks. o

Release the button and wait for the router to reboot.

2.

If the router does not restart automatically; manually restart it to make the default settings effective.

3.

After a restore to factory defaults —whether initiated from the configuration interface or the Reset button — the following settings apply:

LAN IP address: 192.168.10.1

Username: admin

Password: admin

DHCP server on LAN: enabled

WAN port configuration: Get configuration via DHCP

237

Chapter 12.

Credits

Microsoft, Windows are registered trademarks of Microsoft Corp.

Linux is a registered trademark of Linus Torvalds.

UNIX is a registered trademark of The Open Group.

Unified Services Router

Appendix A.

Glossary

User Manual

Address Resolution Protocol. Broadcast protocol for mapping IP addresses to MAC addresses.

ARP

CHAP

Challenge-Handshake Authentication Protocol. Protocol for authenticating users to an ISP.

DDNS

DHCP

DNS

FQDN

FTP

HTTP

IKE

IPsec

ISAKMP

ISP

MAC Address

MTU

NAT

Dynamic DNS. System for updating domain names in real time. Allows a domain name to be assigned to a device with a dynamic IP address.

Dynamic Host Configuration Protocol. Protocol for allocating IP addresses dynamically so that addresses can be reused when hosts no longer need them.

Domain Name System. Mechanism for translating H.323 IDs, URLs, or e-mail IDs into IP addresses. Also used to assist in locating remote gatekeepers and to map IP addresses to hostnames of administrative domains.

Fully qualified domain name. Complete domain name, including the host portion. Example: serverA.companyA.com.

File Transfer Protocol. Protocol for transferring files between network nodes.

Hypertext Transfer Protocol. Protocol used by web browsers and web servers to transfer files.

Internet Key Exchange. Mode for securely exchanging encryption keys in ISAKMP as part of building a VPN tunnel.

IP security. Suite of protocols for securing VPN tunnels by authenticating or encrypting IP packets in a data stream. IPsec operates in either transport mode (encrypts payload but not packet headers) or tunnel mode (encrypts both payload and packet headers).

Internet Key Exchange Security Protocol. Protocol for establishing security associations and cryptographic keys on the Internet.

Internet service provider.

Media-access-control address. Unique physical-address identifier attached to a network adapter.

Maximum transmission unit. Size, in bytes, of the largest packet that can be passed on. The

MTU for Ethernet is a 1500-byte packet.

Network Address Translation. Process of rewriting IP addresses as a packet passes through a router or firewall. NAT enables multiple hosts on a LAN to access the Internet using the single public IP address of the LAN’s gateway router.

NetBIOS

NTP

PAP

Microsoft Windows protocol for file sharing, printer sharing, messaging, authentication, and name resolution.

Network Time Protocol. Protocol for synchronizing a router to a single clock on the network, known as the clock master.

Password Authentication Protocol. Protocol for authenticating users to a remote access server or ISP.

240

Unified Services Router

PPPoE

PPTP

RADIUS

RSA

TCP

UDP

VPN

WINS

XAUTH

User Manual

Point-to-Point Protocol over Ethernet. Protocol for connecting a network of hosts to an ISP without the ISP having to manage the allocation of IP addresses.

Point-to-Point Tunneling Protocol. Protocol for creation of VPNs for the secure transfer of data from remote clients to private servers over the Internet.

Remote Authentication Dial-In User Service. Protocol for remote user authentication and accounting. Provides centralized management of usernames and passwords.

Rivest-Shamir-Adleman. Public key encryption algorithm.

Transmission Control Protocol. Protocol for transmitting data over the Internet with guaranteed reliability and in-order delivery.

User Data Protocol. Protocol for transmitting data over the Internet quickly but with no guarantee of reliability or in-order delivery.

Virtual private network. Network that enables IP traffic to travel securely over a public TCP/IP network by encrypting all traffic from one network to another. Uses tunneling to encrypt all information at the IP level.

Windows Internet Name Service. Service for name resolution. Allows clients on different IP subnets to dynamically resolve addresses, register themselves, and browse the network without sending broadcasts.

IKE Extended Authentication. Method, based on the IKE protocol, for authenticating not just devices (which IKE authenticates) but also users. User authentication is performed after device authentication and before IPsec negotiation.

241

Unified Services Router

User Manual

242

Appendix B.

Factory Default Settings

Feature Description Default Setting

Device login

Internet

Connection

User login URL

User name (case sensitive)

Login password (case sensitive)

WAN MAC address

WAN MTU size

Port speed

IP address

IPv4 subnet mask

RIP direction

RIP version

RIP authentication

Local area network

(LAN)

DHCP server

DHCP starting IP address

DHCP ending IP address

Time zone

Time zone adjusted for Daylight Saving Time

SNMP

Remote management

Firewall

Inbound communications from the Internet

Outbound communications to the Internet

Source MAC filtering

Stealth mode http://192.168.10.1 admin admin

Use default address

1500

Autosense

192.168.10.1

255.255.255.0

None

Disabled

Disabled

Enabled

192.168.10.2

192.168.10.100

GMT

Disabled

Disabled

Disabled

Disabled (except traffic on port

80, the HTTP port)

Enabled (all)

Disabled

Enabled

Unified Services Router

User Manual

Appendix C.

Standard Services Available for

Port Forwarding & Firewall

Configuration

ANY

AIM

BGP

BOOTP_CLIENT

BOOTP_SERVER

CU-SEEME:UDP

CU-SEEME:TCP

DNS:UDP

DNS:TCP

FINGER

FTP

HTTP

HTTPS

ICMP-TYPE-3

ICMP-TYPE-4

ICMP-TYPE-5

ICMP-TYPE-6

ICMP-TYPE-7

IRC

NEWS

NFS

NNTP

PING

POP3

PPTP

ICMP-TYPE-8

ICMP-TYPE-9

ICMP-TYPE-10

ICMP-TYPE-11

ICMP-TYPE-13

ICQ

IMAP2

IMAP3

RCMD

REAL-AUDIO

REXEC

RLOGIN

RTELNET

RTSP:TCP

RTSP:UDP

SFTP

SMTP

SNMP:TCP

SNMP:UDP

SNMP-TRAPS:TCP

SNMP-TRAPS:UDP

SQL-NET

SSH:TCP

SSH:UDP

STRMWORKS

TACACS

TELNET

TFTP

VDOLIVE

244

Unified Services Router

User Manual

Appendix D.

Log Output Reference

Facility: System (Networking)

Log Message

DBUpdate event: Table: %s opCode:%d rowId:%d networkIntable.txt not found sqlite3QueryResGet failed

Interface is already deleted in bridge removing %s from bridge %s... %s adding %s to bridge %s... %s stopping bridge... stopping bridge... stopping bridge...

%s:DBUpdate event: Table: %s opCode:%d rowId:%d

Severity Log Message

BridgeConfig: too few arguments to

DEBUG command %s

BridgeConfig: too few arguments to

DEBUG command %s

DEBUG ddnsDisable failed

DEBUG ddnsDisable failed

DEBUG failed to call ddns enable

DEBUG ddnsDisable failed

Severity

ERROR

ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

ERROR

ERROR

ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

Error in executing DB update

DEBUG handler ERROR Wan is not up

%s:DBUpdate event: Table: %s opCode:%d rowId:%d doDNS:failed doDNS:failed doDNS:Result = FAILED doDNS:Result SUCCESS

Write Old Entry: %s %s %s: to %s

Write New Entry: %s %s #%s : to %s

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

DEBUG Illegal invocation of ddnsView (%s) ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

DEBUG ddns: SQL error: %s ERROR

DEBUG Illegal operation interface got deleted ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

Write Old Entry: %s %s %s: to %s

Write New Entry: %s %s #%s : to %s ifStaticMgmtDBUpdateHandler: returning with " nimfLinkStatusGet: buffer: \ nimfLinkStatusGetErr: returning with status: %d nimfAdvOptSetWrap: current Mac

Option: %d nimfAdvOptSetWrap: current Port

Speed Option: %d nimfAdvOptSetWrap: current Mtu

Option: %d nimfAdvOptSetWrap: looks like we are reconnecting. " nimfAdvOptSetWrap: Mtu Size: %d

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG ddns: SQL error: %s

DEBUG sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s

DEBUG ddnsDisable failed ddns: SQL error: %s

Failed to call ddns enable ddns: SQL error: %s sqlite3QueryResGet failed.Query:%s

Failed to call ddns enable ddnsDisable failed

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR nimfAdvOptSetWrap: NIMF table is %s DEBUG ddns: SQL error: %s nimfAdvOptSetWrap:WAN_MODE

TRIGGER

ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR nimfAdvOptSetWrap: MTU: %d DEBUG Failed to call ddns enable nimfAdvOptSetWrap: MacAddress: %s DEBUG ddns: SQL error: %s nimfAdvOptSetWrap: old Mtu Flag: %d DEBUG ddnsDisable failed

ERROR

ERROR

ERROR

245

Unified Services Router

User Manual nimfAdvOptSetWrap: user has changed

MTU option nimfAdvOptSetWrap: MTU: %d

DEBUG ddns: SQL error: %s ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR nimfAdvOptSetWrap: old MTU size: %d DEBUG sqlite3QueryResGet failed.Query:%s ERROR nimfAdvOptSetWrap: old Port Speed

Option: %d nimfAdvOptSetWrap: old Mac Address

DEBUG ddnsDisable failed ERROR

Option: %d DEBUG ddns: SQL error: %s ERROR nimfAdvOptSetWrap: MacAddress: %s DEBUG sqlite3QueryResGet failed.Query:%s ERROR

Setting LED [%d]:[%d] For %s l2tpEnable: command string: %s nimfAdvOptSetWrap: handling reboot scenario

DEBUG

DEBUG sqlite3QueryResGet failed.Query:%s ddnsDisable failed

DEBUG failed to call ddns enable nimfAdvOptSetWrap: INDICATOR = %d DEBUG ddns: SQL error: %s

ERROR

ERROR

ERROR

ERROR nimfAdvOptSetWrap: UpdateFlag: %d nimfAdvOptSetWrap: returning with status: %s nimfGetUpdateMacFlag: MacTable Flag is: %d nimfMacGet: Mac Option changed nimfMacGet: Update Flag: %d nimfMacGet: MacAddress: %s nimfMacGet: MacAddress: %s nimfMacGet: MacAddress: %s nimfMacGet: MacAddress: %s

DEBUG

DEBUG

DEBUG failed to open %s

DEBUG ddnsDisable failed

DEBUG Error opening the lanUptime File

Error Opening the lanUptime File. failed to open %s

ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

Error in executing DB update

DEBUG ERROR

DEBUG handler

Failed to open the resolv.conf file.

Exiting./n ERROR

DEBUG

Could not write to the resolv.conf file.

Exiting. ERROR

ERROR

ERROR

ERROR

ERROR nimfMacGet: MacAddress: %s DEBUG failed to query networkInterface table ERROR nimfMacGet:Mac option Not changed \ DEBUG failed to query networkInterface table ERROR nimfMacGet: MacAddress: %s nimfMacGet: MacAddress: %s nimfMacGet: MacAddress: %s nimfMacGet: returning with status: %s

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

DEBUG failed to enable IPv6 forwarding

DEBUG failed to set capabilities on the "

DEBUG failed to enable IPv6 forwarding

ERROR

ERROR

ERROR

Now in enableing LanBridge function DEBUG failed to set capabilities on the " sucessfully executed the command %s DEBUG failed to disable IPv6 forwarding

ERROR

ERROR

Now in disableing LanBridge function DEBUG failed to set capabilities on the " ERROR sucessfully executed the command %s DEBUG failed to open %s configPortTblHandler:Now we are in

Sqlite Update " DEBUG Could not create ISATAP Tunnel

The Old Configuration of ConfiPort was:%s

The New Configuration of ConfiPort was:%s

The user has deselected the configurable port failed query %s failed query %s

DEBUG Could not destroy ISATAP Tunnel

ERROR

ERROR

ERROR

DEBUG Could not configure ISATAP Tunnel ERROR

DEBUG

DEBUG

DEBUG

Could not de-configure ISATAP

Tunnel nimfStatusUpdate: updating

NimfStatus failed nimfStatusUpdate: updating

NimfStatus failed

ERROR

ERROR

ERROR failed query %s

%s:DBUpdate event: Table: %s opCode:%d rowId:%d

DEBUG

DEBUG nimfLinkStatusGet: determinig link's status failed nimfLinkStatusGet: opening status file failed

ERROR

ERROR

246

Unified Services Router

%s:DBUpdate event: Table: %s opCode:%d rowId:%d

%s:%d SIP ENABLE: %s sipTblHandler:failed to update ifStatic sipTblHandler:failed to update

Configport

%s:%d SIP DISABLE: %s

%s:%d SIP SET CONF: %s

Failed to open %s: %s

Failed to start sipalg

Failed to stop sipalg

Failed to get config info

Network Mask: 0x%x

RTP DSCP Value: 0x%x

Need more arguments

Invalid lanaddr

Invalid lanmask

Invalid option

Failed to set config info

Unknown option sshdTblHandler pPort: %s pProtocol: %s pListerAddr: %s pKeyBits: %s pRootEnable: %s pRsaEnable: %s pDsaEnable: %s pPassEnable: %s pEmptyPassEnable: %s pSftpEnable: %s pScpEnable: %s

User Manual

DEBUG Failed to commit ERROR

DEBUG ifStatusDBUpdate: Failed to begin " ERROR

DEBUG %s: SQL error: %s ERROR

DEBUG %s: Failed to commit " nimfNetIfaceTblHandler: unable to

DEBUG get LedPinId nimfNetIfaceTblHandler: unable to

DEBUG

DEBUG get LedPinId nimfNetIfaceTblHandler: unable to get LedPinId

DEBUG %s: unable to kill dhclient

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG nimfAdvOptSetWrap: unable to get current Mac Option nimfAdvOptSetWrap: unable to get current Port " nimfAdvOptSetWrap: unable to get current MTU Option nimfAdvOptSetWrap: error getting

Mac Address from " nimfAdvOptSetWrap: unable to get the MTU

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG nimfAdvOptSetWrap: error setting interface advanced " nimfAdvOptSetWrap: error getting

MTU size nimfAdvOptSetWrap: unable to get

Mac Address nimfAdvOptSetWrap: error setting interface advanced " nimfAdvOptSetWrap: failed to get old connectiontype nimfAdvOptSetWrap: old connection type is: %s nimfAdvOptSetWrap: failed to get old MTU Option nimfAdvOptSetWrap: error getting

MTU size nimfOldFieldValueGet: failed to get old " nimfOldFieldValueGet: user has changed MTU size

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG nimfAdvOptSetWrap: failed to get old Port Speed " nimfAdvOptSetWrap: user has changed Port Speed nimfAdvOptSetWrap: failed to get old Mac Address " nimfAdvOptSetWrap: user has changed Mac Address " nimfAdvOptSetWrap: unable to get

Mac Address nimfAdvOptSetWrap:Failed to

RESET the flag nimfAdvOptSetWrap: setting advanced options failed

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

247

Unified Services Router

pSshdEnable: %s pPrivSep: %s

%s:DBUpdate event: Table: %s opCode:%d rowId:%d

Re-Starting sshd daemon.... sshd re-started successfully. sshd stopped . failed query %s vlan disabled, not applying vlan configuration.. failed query %s failed query %s no ports present in this vlanId %d failed query %s vlan disabled, not applying vlan configuration.. disabling vlan enabling vlan vlan disabled, not applying vlan configuration.. no ports present in this vlanId %d failed query %s vlan disabled, not applying vlan configuration.. removing %s from bridge%s... %s adding %s to bridge%d... %s restarting bridge...

[switchConfig] Ignoring event on port number %d restarting bridge... executing %s ... %s removing %s from bridge%s... %s adding %s to bridge%d... %s

[switchConfig] Ignoring event on %s restarting bridge...

[switchConfig] Ignoring event on port number %d

[switchConfig] executing %s ... %s restarting bridge...

UserName: %s

Password: %s

IspName: %s

DialNumber: %s

User Manual

DEBUG

DEBUG

DEBUG nimfAdvOptSetWrap: interface advanced options applied nimfGetUpdateMacFlag: unable to get Flag from MacTable nimfMacGet: Updating MAC address failed

ERROR

ERROR

ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

DEBUG error executing the command %s

DEBUG error executing the command %s

ERROR

ERROR

DEBUG error executing the command %s

DEBUG disableLan function is failed to disable ConfigPort"

ERROR

ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

Unable to Disable configurable port

DEBUG from ERROR

DEBUG configPortTblHandler has failed ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

DEBUG

Error in executing DB update handler ERROR

ERROR DEBUG sqlite3QueryResGet failed

DEBUG

DEBUG

DEBUG

Failed to execute switchConfig for port\

Failed to execute switchConfig for port enable

Failed to execute ifconfig for port enable

ERROR

ERROR

ERROR

ERROR DEBUG Failed to execute ethtool for\

DEBUG

Failed to execute switchConfig for port disable

DEBUG

Failed to execute ifconfig for port disable

DEBUG sqlite3QueryResGet failed

ERROR

ERROR

ERROR

DEBUG sqlite3_mprintf failed

DEBUG sqlite3QueryResGet failed

Failed to execute switchConfig for

DEBUG

DEBUG port mirroring

Usage:%s <DB Name> <Entry

Name> <logFile> <subject>

DEBUG sqlite3QueryResGet failed

Could not get all the required

DEBUG variables to email the Logs.

DEBUG runSmtpClient failed

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

DEBUG getaddrinfo returned %s ERROR

DEBUG file not found ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

DEBUG No memory to allocate

Failed to Open SSHD Configuration

DEBUG File

ERROR

ERROR

248

Unified Services Router

User Manual

Apn: %s

GetDnsFromIsp: %s

IdleTimeOutFlag: %s

IdleTimeOutValue: %d

AuthMetho: %d executing %s ... %s removing %s from bridge%d... %s adding %s to bridge%d... %s stopping bridge... restarting bridge...

Could not configure 6to4 Tunnel

Interface

Could not de-configure 6to4 Tunnel

Interface

DEBUG

DEBUG

Ipaddress should be provided with accessoption 1

Subnetaddress should be provided with accessoption 2

DEBUG Failed to restart sshd failed to restart 6to4 tunnel interfaces

BridgeConfig: too few arguments to command %s

BridgeConfig: unsupported command

%d DEBUG Failed to clear vlan for oldPVID %d

Failed to execute vlanConfig binary

DEBUG for port number %d BridgeConfig returned error=%d sqlite3QueryResGet failed

Error in executing DB update handler

DEBUG Failed to clear vlan for %d

DEBUG Failed to set vlan entry for vlan %d

DEBUG

Failed to set vlan entries, while enabling \ sqlite3QueryResGet failed

Failed to remove vlan Interface for vlanId \ sqlite3QueryResGet failed

Invalid oidp passed

Invalid oidp passed

DEBUG sqlite3QueryResGet failed

DEBUG

DEBUG

Failed to execute vlanConfig binary for port number %d

Failed to execute vlanConfig binary for vlanId %d

DEBUG Failed to enable vlan

Failed to get oid from the tree threegEnable: Input to wrapper %s

DEBUG Failed to disable vlan

Failed to set vlanPort table entries,

DEBUG while \ threegEnable: spawning command %s DEBUG Failed to enable vlan threegMgmtHandler: query string: %s threegMgmtHandler: returning with status: %s adding to dhcprealy ifgroup failed adding to ipset fwDhcpRelay failed

Disabling Firewall Rule for DHCP Relay

Protocol

Enabling Firewall Rule for DHCP Relay

Protocol prerouting Firewall Rule add for Relay failed prerouting Firewall Rule add for Relay failed

DEBUG sqlite3_mprintf failed

DEBUG

DEBUG

Access port can be present only in single vlan

Failed to execute vlanConfig binary for vlanId %d

ERROR

ERROR

ERROR

DEBUG unable to open the " ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

Error in executing DB update

DEBUG ERROR

DEBUG handler

Error in executing DB update handler ERROR

ERROR DEBUG unknown vlan state

DEBUG

Failed to execute vlanConfig binary for vlanId %d ERROR

ERROR DEBUG sqlite3_mprintf failed

Access port can be present only in

DEBUG single vlan

Failed to execute vlanConfig binary

DEBUG for vlanId %d

ERROR

ERROR

ERROR DEBUG unknown vlan state

DEBUG

Failed to execute vlanConfig binary for port number %d ERROR

DEBUG unknown vlan state

DEBUG

Error in executing DB update handler

DEBUG unknown vlan state

Failed to execute vlanConfig binary

DEBUG for vlanId %d

DEBUG unknown vlan state

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

249

Unified Services Router

User Manual

%s: SQL get query: %s

%s: sqlite3QueryResGet failed

%s: no result found

%s: buffer overflow

%s: value of %s in %s table is: %s

%s: returning with status: %s dnsResolverConfigure: addressFamily:

%d dnsResolverConfigure: LogicalIfName:

%s chap-secrets File found

PID File for xl2tpd found pid: %d options.xl2tpd file found options.xl2tpd file not found

Conf File for xl2tpd found xl2tpd.conf not found

Chap Secrets file found

Chap Secrets file not found

%s:DBUpdate event: Table: %s opCode:%d rowId:%d chap-secrets File found

PID File for pptpd found pid: %d

PID File for pptpd interface found pid: %d options.pptpd file found options.pptpd file not found

Conf File for pptpd found pptpd.conf not found

Chap Secrets file found

Chap Secrets file not found

%s:DBUpdate event: Table: %s opCode:%d rowId:%d chap-secrets File found pppoeMgmtTblHandler: MtuFlag: %d pppoeMgmtTblHandler: Mtu: %d pppoeMgmtTblHandler:

IdleTimeOutFlag: %d

DEBUG

Failed to execute vlanConfig binary for port number %d

DEBUG Failed to clear vlan for oldPVID %d

DEBUG

Failed to execute vlanConfig binary for port number %d

DEBUG Failed to clear vlan for %d

DEBUG Failed to set vlan entry for vlan %d

Failed to set vlan entries, while

DEBUG

DEBUG enabling \

Failed to execute vlanConfig binary for port number %d

DEBUG

Failed to execute vlanConfig binary for vlanId %d

DEBUG Failed to enable vlan

DEBUG Failed to disable vlan

Failed to set vlanPort table entries,

DEBUG while \

DEBUG Failed to enable vlan

DEBUG unknown vlan state

DEBUG threegMgmtInit: unable to open the database file %s

DEBUG threegConnEnable: failed to get the

WanMode

DEBUG threegEnable:spawning failed threegDisable: unable to kill ppp

DEBUG daemon

DEBUG threegMgmtHandler: Query: %s

DEBUG threegMgmtHandler: error in executing database update

DEBUG

Error in executing DB update handler

DEBUG are we getting invoked twice ??

DEBUG could not open %s to append could not write nameserver %s to

DEBUG %s could not write nameserver %s to

DEBUG %s

DEBUG could not open %s to truncate

DEBUG dnsResolverConfigMgmtInit: unable to open the "

DEBUG resolverConfigDBUpateHandler: sqlite3QueryResGet "

DEBUG could not configure DNS resolver dnsResolverConfigure: could not

DEBUG write nameserver:%s,"

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

DEBUG unboundMgmt: unable to open the " ERROR

DEBUG ioctl call Failed-could not update active user Details ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

DEBUG Can't kill xl2tpd ERROR

DEBUG xl2tpd restart failed ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

250

Unified Services Router

User Manual pppoeMgmtTblHandler:

IdleTimeOutValue: %d DEBUG failed to get field value pppoeMgmtTblHandler: UserName: %s DEBUG failed to get field value

ERROR

ERROR pppoeMgmtTblHandler: Password: %s DEBUG sqlite3QueryResGet failed.Query:%s ERROR pppoeMgmtTblHandler: DNS specified:

%s DEBUG sqlite3QueryResGet failed.Query:%s ERROR pppoeMgmtTblHandler: Service: %s pppoeMgmtTblHandler: StaticIp: %s pppoeMgmtTblHandler: NetMask: %s pppoeMgmtTblHandler: AuthOpt: %d pppoeMgmtTblHandler: Satus: %d pppoeEnable: ppp dial string: %s pppoeMgmtDBUpdateHandler: returning with status: %s pptpMgmtTblHandler: MtuFlag: %d pptpMgmtTblHandler: Mtu: %d pptpMgmtTblHandler: IdleTimeOutFlag:

%d pptpMgmtTblHandler:

IdleTimeOutValue: %d pptpMgmtTblHandler: GetDnsFromIsp:

%d

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG unboundMgmt: unable to open the " writing options.xl2tpd failed

DEBUG xl2tpdStop failed

DEBUG writing xl2tpd.conf failed writing options.xl2tpd failed xl2tpdStop failed xl2tpdStart failed

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR writing Chap-secrets/Pap-Secrets

DEBUG failed ERROR xl2tpdStop failed xl2tpdStart failed

ERROR

ERROR pptpMgmtTblHandler: UserName: %s pptpMgmtTblHandler: Password: %s pptpMgmtTblHandler: dynamic MyIp configured pptpMgmtTblHandler: MyIp: %s

DEBUG sqlite3QueryResGet failed.Query:%s ERROR writing Chap-secrets/Pap-Secrets

DEBUG failed ERROR

DEBUG xl2tpdStop failed ERROR pptpMgmtTblHandler: ServerIp: %s

DEBUG xl2tpdStart failed ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

DEBUG writing Chap-secrets/Pap-Secrets failed ERROR

DEBUG

Error in executing DB update handler ERROR

DEBUG unboundMgmt: unable to open the " ERROR pptpMgmtTblHandler: StaticIp: %s pptpMgmtTblHandler: NetMask: %s pptpMgmtTblHandler:

MppeEncryptSupport: %s pptpMgmtTblHandler: SplitTunnel: %s pptpEnable: ppp dial string: %s pptpEnable: spawning command %s

DEBUG

DEBUG

DEBUG

DEBUG

Can't kill pptpd pptpd restart failed

Can't kill pptpd failed to get field value

ERROR

ERROR

ERROR

ERROR

PID File for dhcpc found pid: %d pptpMgmtDBUpdateHandler: query string: %s pptpMgmtDBUpdateHandler: returning with status: %s dhcpcReleaseLease: dhcpc release command: %s dhcpcMgmtTblHandler: MtuFlag: %d dhcpcMgmtTblHandler: Mtu: %d

DHCPv6 Server started successfully.

DHCPv6 Server stopped successfully

DHCPv6 Client started successfully.

DEBUG failed to get field value ERROR

DEBUG unboundMgmt: unable to open the " ERROR

DEBUG

DEBUG

DEBUG writing options.pptpd failed pptpdStop failed writing pptpd.conf failed

DEBUG writing options.pptpd failed

DEBUG pptpdStop failed

DEBUG pptpdStart failed writing Chap-secrets/Pap-Secrets

DEBUG failed

Error in executing DB update

DEBUG handler

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

251

Unified Services Router

User Manual

DHCPv6 Client stopped successfully.

DHCPv6 Client Restart successful l2tpMgmtTblHandler: MtuFlag: %d l2tpMgmtTblHandler: Mtu: %d l2tpMgmtTblHandler: IspName: %s l2tpMgmtTblHandler: UserName: %s l2tpMgmtTblHandler: Password: %s l2tpMgmtTblHandler: AccountName: %s l2tpMgmtTblHandler: DomainName: %s l2tpMgmtTblHandler: Secret: not specified l2tpMgmtTblHandler: Secret: %s l2tpMgmtTblHandler: dynamic MyIp configured l2tpMgmtTblHandler: MyIp: %s l2tpMgmtTblHandler: ServerIp: %s

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG pppStatsUpdate: unable to get default MTU pppoeMgmtInit: unable to open the database file %s pppoeDisable: unable to kill ppp daemon pppoeMultipleEnableDisable: pppoe enable failed pppoeMultipleEnableDisable: pppoe disable failed pppoeMgmtTblHandler: unable to get current Mtu Option pppoeMgmtTblHandler: unable to get the Mtu pppoeMgmtTblHandler: pppoe enable failed pppoeMgmtDBUpdateHandler: failed query: %s pppoeMgmtDBUpdateHandler: error in executing " pptpMgmtInit: unable to open the database file %s pptpEnable: error executing command: %s pptpEnable: unable to resolve address: %s

DEBUG pptpEnable: inet_aton failed l2tpMgmtTblHandler: StaticIp: %s l2tpMgmtTblHandler: NetMask: %s l2tpMgmtTblHandler: SplitTunnel: %s needToStartHealthMonitor: returning with status: %s l2tpEnable: command string: %s l2tpEnable: command: %s l2tpEnable: command string: %s

PID File for dhcpc found pid: %d l2tpMgmtDBUpdateHandler: query string: %s l2tpMgmtDBUpdateHandler: returning with status: %s

DEBUG pptpEnable: inet_aton failed

DEBUG pptpEnable:spawning failed pptpDisable: unable to kill ppp

DEBUG

DEBUG daemon pptpMgmtTblHandler: unable to get current MTU Option

DEBUG

DEBUG

DEBUG

DEBUG pptpMgmtTblHandler: unable to get the Mtu pptpMgmtTblHandler: dbRecordValueGet failed for %s " pptpMgmtTblHandler: pptp enable failed pptpMgmtTblHandler: pptp disable failed

DEBUG

DEBUG pptpMgmtDBUpdateHandler: sqlite3QueryResGet " pptpMgmtDBUpdateHandler: error in executing "

RADVD started successfully

RADVD stopped successfully empty update. nRows=%d nCols=%d

Wan is not up or in load balencing mode threegMgmtHandler: no row found. nRows = %d nCols = %d pppoeMgmtDBUpdateHandler: empty update.

ERROR

ERROR

ERROR

ERROR

DEBUG Illegal invocation of dhcpConfig (%s) ERROR dhcpLibInit: unable to open the

DEBUG database file %s ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

WARN dhcpcMgmtInit: unable to open the database file %s ERROR

WARN dhcpcReleaseLease: unable to release lease ERROR

WARN

WARN dhcpcEnable: unable to kill dhclient dhcpcEnable: enabling dhcpc failed on: %s

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

252

Unified Services Router

User Manual dhcpcEnable: dhclient already running on: %s WARN dhcpcDisable: unable to kill dhclient ERROR dhcpcDisable: delete failed for dhclient.leases ERROR dhcpcDisable: deleted dhclient.leases l2tpMgmtInit: unable to open the database file %s l2tpEnable: unable to resolve address:

%s l2tpEnable: inet_aton failed

The Enable Command is %s l2tpEnable:Executing the Command failed

WARN

ERROR dhcpcDisable: failed to reset the ip dhcpcMgmtTblHandler: unable to get

ERROR current Mtu Option dhcpcMgmtTblHandler: unable to get

ERROR

ERROR

ERROR the Mtu dhcpcMgmtTblHandler: dhclient enable failed dhcpcMgmtTblHandler: dhcpc release failed l2tpDisable: command string: %s ERROR l2tpDisable: unable to stop l2tp session ERROR l2tpMgmtTblHandler: unable to get current MTU option l2tpMgmtTblHandler: unable to get the

ERROR

Mtu l2tpMgmtTblHandler: dbRecordValueGet failed for %s " dhcpcMgmtTblHandler: dhcpc disable failed dhcpcMgmtDBUpdateHandler: failed query: %s dhcpcMgmtDBUpdateHandler: error in executing "

ERROR DHCPv6 Client start failed.

ERROR DHCPv6 Client stop failed.

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR l2tpMgmtTblHandler: l2tpEnable failed ERROR l2tpMgmtTblHandler: disabling l2tp failed l2tpMgmtDBUpdateHandler:

ERROR sqlite3QueryResGet " l2tpMgmtDBUpdateHandler: error in executing failed to create/open DHCPv6 client

" failed to write DHCPv6 client configuration file

ERROR failed to restart DHCPv6 Client

ERROR failed to create/open DHCPv6

Server "

Illegal invocation of tcpdumpConfig

(%s)

Failed to start tcpdump

ERROR Restoring old configuration..

ERROR

DHCPv6 Server configuration update failed

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

Failed to stop tcpdump

Invalid tcpdumpEnable value

ERROR

ERROR

DHCPv6 Server Restart failed sqlite3QueryResGet failed.Query:%s

ERROR

ERROR

Facility: System (VPN)

Log Message Severity Log Message

%d command not supported by eapAuth DEBUG PEAP key derive: ERROR pCtx NULL.

Current cert subject name= %s

DEBUG

DEBUG

PEAP context is NULL: ERROR

Constructing P2 response: ERROR

X509_STORE_CTX_get_ex_data failed. DEBUG innerEapRecv is NULL: ERROR

Cannot get cipher, no session est. DEBUG Decrypting TLS data: ERROR

%s:

SSL_ERROR_WANT_X509_LOOKUP DEBUG Wrong identity size: ERROR err code = (%d) in %s DEBUG

Wrong size for extensions packet:

ERROR

BIO_write: Error

Decrypting: BIO reset failed

Encrypting BIO reset: ERROR

DEBUG

DEBUG

DEBUG innerEapRecv is NULL: ERROR.

Inner EAP processing: ERROR

TLS handshake: ERROR.

Severity

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

253

Unified Services Router

User Manual

BIO_read: Error

EAP state machine changed from %s to

%s.

EAP state machine changed from %s to

%s.

Received EAP Packet with code %d

Response ID %d

Response Method %d

Created EAP/PEAP context: OK

DEBUG Sending P1 response: ERROR

DEBUG

Unexpected tlsGlueContinue return value.

DEBUG

DEBUG

DEBUG

No more fragments in message.

ERROR

No phase 2 data or phase 2 data buffer NULL: ERROR

Allocating memory for PEAP Phase 2 payload: ERROR

DEBUG TLS encrypting response: ERROR

DEBUG

Setting message in fragment buffer:

ERROR

DEBUG

Allocating TLS read buffer is NULL:

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR Deleted EAP/PEAP context: OK

Upper EAP sent us: decision = %d method state = %d

P2 decision=(%d); methodState=(%d)

Writing message to BIO: ERROR.

Encrypted (%d) bytes for P2

P2: sending fragment.

P2: message size = %d

P2: sending unfragmented message.

P1: Sending fragment.

P1: Total TLS message size = (%d)

P1: sending unfragmented message. peapFragFirstProcess: TLS record size to receive = (%d)

Setting version %d

PEAP pkt rcvd: data len=(%d) flags=(%d) version=(%d)

Got PEAP/Start packet.

DEBUG

DEBUG

DEBUG

DEBUG

Setting last fragment: ERROR

Getting message: ERROR

Processing PEAP message: ERROR

Setting fragment: ERROR

ERROR

ERROR

ERROR

ERROR

DEBUG Creating receive buffer: ERROR

DEBUG Setting first fragment: ERROR

DEBUG Sending P1 response: ERROR

DEBUG

DEBUG

NULL request (or response) PDU or

NULL context: ERROR

Expecting start packet, got something else: ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

DEBUG Protocol version mismatch: ERROR

Processing PEAP message (from

DEBUG frag): ERROR

ERROR

ERROR

DEBUG Processing PEAP message: ERROR ERROR

Got first fragment

Got fragment (n)

Got last fragment

Got unfragmented message

Got frag ack.

Ext AVP parsed: flags=(0x%x)

Mandatory bit not set: WARNING

Ext AVP parsed: type=(%d)

Ext AVP parsed: value=(%d)

Got PEAPv0 success!

Got PEAPv0 failure! pCtx NULL.

DEBUG Processing PEAP message: ERROR ERROR

DEBUG

DEBUG

DEBUG

Indicated length not valid: ERROR

Did not get Acknowledged result:

ERROR

Cannot understand AVP value:

ERROR

ERROR

ERROR

ERROR

ERROR DEBUG eapExtResp is NULL: ERROR

DEBUG eapWscCtxCreate:

EAPAUTH_MALLOC failed.

DEBUG eapWscProcess: umiIoctl req to WSC failed, status = %d

DEBUG eapWscCheck: Invalid frame

ERROR

ERROR

ERROR

DEBUG eapWscBuildReq: Invalid state %d eapWscProcessWscResp: Invalid

DEBUG data recd pData = %p, dataLen"

Data received for invalid context,

DEBUG

DEBUG dropping it eapWscProcessWscResp: Build

Request failed

DEBUG

DEBUG eapWscProcessWscResp: Invalid state %d eapWscProcessWscResp: Message processing failed 0x%X

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

254

Unified Services Router

User Manual

Authenticator response check: Error

Authenticator response check: Failed

MS-CHAP2 Response AVP size = %u

DEBUG eapWscProcessWscData: Invalid notification recd %d

DEBUG unable to initialize MD5

DEBUG

MDString: adpDigestInit for md5 failed

Created EAP/MS-CHAP2 context: OK. DEBUG EAPAUTH_MALLOC failed. pCtx NULL. DEBUG EAPAUTH_MALLOC failed.

Deleted EAP/MS-CHAPv2 context: OK DEBUG NULL context created: Error

Not authenticated yet.

Authenticator response invalid

EAP-MS-CHAPv2 password changed. rcvd. opCode %d.

DEBUG NULL context received: Error

DEBUG Authenticator ident invalid.

DEBUG

Success request message invalid:

Error

DEBUG Plugin context is NULL

DEBUG Deriving implicit challenge: Error pCtx NULL.

TLS message len changed in the fragment, ignoring.

no data to send while fragment ack received.

TLS handshake successful.

DEBUG

DEBUG

Generating NT response: Error

NULL in/out buffer: Error

DEBUG Incorrect vendor id.

DEBUG

Allocating memory for outBuff:

ERROR

DEBUG AVP code not recognized

Created EAP/TTLS context: OK

Deleted EAP/TTLS context: OK

No more fragments in message.

ERROR

Upper EAP sent us: method state = %d; decision = %d

P2: sending fragment.

P2 send unfragmented message.

P1: sending fragment.

P1: sending unfragmented message.

\tTLSMsgLen = 0x%x

Send req ptr = 0x%x; Send resp ptr =

0x%x

P2 decision=(%d); methodState=(%d)

Default EAP: method state = %d; decision = %d

TTLS pkt: data len=(%d) flags=(0x%x)

DEBUG EAPAUTH_MALLOC failed.

Converting password to unicode:

DEBUG Error

DEBUG Generating password hash: Error.

Generating password hash hash:

DEBUG Error.

DEBUG Generating master key: Error.

DEBUG

Generating first 16 bytes of session key: Error.n

DEBUG

DEBUG

DEBUG

DEBUG

Generating second 16 bytes of session key: Error.n

Converting password to unicode:

Error

Constructing failure response:

ERROR

Error checking authenticator response.

Got start

Got first fragment (n).

Got fragment (n).

Got last fragment

DEBUG Error generating NT response.

DEBUG

Username string more than 256

ASCII characters: ERROR

DEBUG Invalid Value-Size.

Invalid MS-Length. Got (%d),

DEBUG expected (%d)

Got unfragmented message.

DEBUG Error constructing response.

DEBUG Got type (%d), expecting (%d)

DEBUG

Cannot handle message; opCode =

%d Got frag ack.

Rcvd. AVP Code-%u: flags-0x%x: len-

%u: vendorId-%u: "

MOD EAP: method state from upper =

%d; decision = %d

DEBUG

DEBUG

EAPAUTH_MALLOC failed. tlsGlueCtxCreate failed.

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

255

Unified Services Router

User Manual

Got AVP len = %ul. Should be less than

16777215

AVP length extract: Error pFB is NULL

Requesting message before assembly complete pFB is NULL pFB is NULL

Buffer cannot hold message: ERROR pFB is NULL: Error pFB is NULL

TLS_FB* is NULL. pFB->msgBuff is NULL.

Error calculating binary.

Error calculating binary. adpDigestInit for SHA1 failed. adpDigestInit for SHA1 failed.

E = %d

R = %d

Could not initialize des-ecb adpDigestInit for MD4 failed.

DEBUG client certificate must be set in the profile. ERROR

DEBUG received TLS message length too big. ERROR

DEBUG

DEBUG

DEBUG total frags len > initial total TLS length. total frags len > initial total TLS length. total data rcvd(%d) doesnt match the initial "

ERROR

ERROR

ERROR

DEBUG couldnt write %d data to TLS buffer.

DEBUG invalid flags %s passed to eapTlsBuildResp.

ERROR

DEBUG EAPAUTH_MALLOC failed.

DEBUG tlsGlueCtxCreate failed.

DEBUG Context NULL: ERROR

ERROR

ERROR

ERROR

ERROR

DEBUG Setting profile to glue layer: ERROR. ERROR

ERROR DEBUG _eapCtxCreate failed.

%d authentication not enabled in the

DEBUG

DEBUG system.

Initializing inner non-EAP auth plugin:

ERROR

DEBUG TTLS key derive: ERROR

DEBUG

DEBUG

TTLS context from EAP plugin is

NULL: ERROR

Allocating memory for TTLS Phase 2 payload: ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR DEBUG TLS Encrypting response: ERROR

Allocating TLS read buffer is NULL:

DEBUG

DEBUG

ERROR

Inner authentication (id: %d) unhandled

DEBUG innerEapRecv is NULL: ERROR.

ERROR

ERROR

ERROR adpDigestInit for SHA1 failed. adpDigestInit for SHA1 failed.

Error converting received auth reponse to bin.

Gnerating challenge hash: Error

Generating password hash: Error

Generating challenge response: Error

Conn cipher name=%s ver=%s: %s

Send req ptr = 0x%x; Send resp ptr =

0x%x

Request ptr = 0x%x;

Response ptr = 0x%x

Rcvd. AVP Code - %ul

Rcvd. AVP flags - 0x%02x

Rcvd. AVP len - %ul

Rcvd. AVP vendor id - %ul

\tCode = %d

\tIdent = %d

\tLen = %d

\tType = %d

\tOpCode = %d

\tMSID = %d

DEBUG Decrypting TLS data: ERROR

DEBUG Processing Phase 2 method: Error

ERROR

ERROR

DEBUG Writing message to BIO: ERROR.

DEBUG TLS handshake: ERROR.

DEBUG

Unexpected tlsGlueContinue return value.

DEBUG

NULL request (or response) PDU or

NULL context

ERROR

ERROR

ERROR

DEBUG Protocol version mismatch: ERROR

DEBUG

DEBUG

Creating receive buffer: ERROR

DEBUG Setting first fragment: ERROR

Setting fragment: ERROR

DEBUG Setting last fragment: ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

DEBUG Getting message: ERROR ERROR

DEBUG Processing TTLS message: ERROR ERROR

DEBUG Processing TTLS message: ERROR ERROR

DEBUG Processing TTLS message: ERROR ERROR

DEBUG Decapsulating AVP: ERROR

DEBUG Processing EAP receive: Error

DEBUG AVP code not EAP: Error

ERROR

ERROR

ERROR

256

Unified Services Router

User Manual

\tmsLen = %d

\tvalSize = %d

Frag Buffer bytes left = (%d)

Stripped username=(%s) digestLen = %d.

ClearText =

CipherText = digestLen = %d. digestLen1 = %d. digestLen2 = %d. password change is not allowed for this user completed writing the policy completed writing the SA completed writing the proposal block cmdBuf: %s

X509_DEBUG : Invalid Certificate for the generated"

X590_ERROR : Failed to create File

'%s' x509TblHandler pCertType: %s pRowQueryStr: %s x509SelfCertTblHandler pRowQueryStr: %s

%s:DBUpdate event: Table: %s opCode:%d rowId:%d umiRegister failed eapAuthHandler: Invalid data received

EAPAUTH_MALLOC failed. malloc failed.

BIO_new_mem_buf failed. malloc failed.

BIO_new_mem_buf failed.

SSL_CTX_new (TLSv1_client_method) failed. unable to set user configured CIPHER list %s

Certificate verification failed.

Server name match failed. Got (%s) expected "

DEBUG Encapsulating AVP: ERROR

DEBUG profile %s doesnt exist.

DEBUG profile %s is in use.

DEBUG profile %s already exists.

DEBUG EAPAUTH_MALLOC failed

DEBUG User not found.

EAP-MD5 not enabled in system

DEBUG

DEBUG configuration.

EAP-MSCHAPV2 not enabled in system configuration.

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

EAP-TLS not enabled in system configuration.

EAP-TTLS not enabled in system configuration.

EAP-PEAP not enabled in system configuration.

EAP-WSC not enabled in system configuration.

PAP not enabled in system configuration.

CHAP not enabled in system configuration.

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

MSCHAP not enabled in system configuration.

MSCHAPV2 not enabled in system configuration.

PAP/Token not enabled in system configuration.

EAP-MD5 not enabled in system configuration.

EAP-MSCHAPV2 not enabled in system config.

EAP-TLS not enabled in system configuration.

EAP-TTLS and EAP-PEAP are not valid as inner"

DEBUG invalid innerAuth %d.

DEBUG profile %s doesnt exist.

ERROR

Re-assembling fragments incorrect size

ERROR Error creating cipher context.

ERROR Error initializing cipher context.

ERROR Error creating digest context.

ERROR Error initializing digest context.

ERROR Error initializing DES in Klite

ERROR Error initializing MD4 in Klite

ERROR Error initializing RC4 in Klite

ERROR Error initializing SHA in Klite

ERROR Error cleaning cipher context.

ERROR Error destroying cipher context.

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

257

Unified Services Router

User Manual

SSL_CTX_use_certificate_file (cert,

PEM) failed.

SSL_CTX_use_PrivateKey_file failed. private key does not match public key

ERROR Error cleaning digest context.

ERROR Error destroying digest context.

ERROR Error stripping domain name.

SSL_CTX_load_verify_locations failed ERROR Error cleaning digest context.

SSL_new failed.

Both SSL_VERIFY_PEER and

SSL_VERIFY_NONE set: Error

EAPAUTH_MALLOC failed.

ERROR Error cleaning digest context.

Challenge not present in failure

ERROR packet.

EAPAUTH_MALLOC failed. eapTimerCreate failed.

ERROR Wrong challenge length.

ERROR

Incorrect password change version value.

ERROR Error generating password hash. eapCtxDelete:pCtx == NULL eapRole != EAP_ROLE_PEER or

EAP_ROLE_AUTHENTICATOR pEapCtx == NULL or pPDU == NULL. received EAP pdu bigger than

EAP_MTU_SIZE. received EAP pdu bigger than

EAP_MTU_SIZE. state machine is in invalid state.

ERROR Error generating password hash.

Error encrypting password hash with

ERROR block

ERROR Could not initialize des-ecb

ERROR Error cleaning cipher context. unable to create method context. method ctxCreate failed. method profile set failed. state machine is in invalid state.

Only StandAlone authenticator supported currently. state machine is in invalid state.

BuildReq operation failed

No method ops defined for current method

ERROR Error cleaning cipher context.

ERROR Error cleaning digest context.

ERROR Error cleaning digest context.

ERROR adpDigestInit for SHA1 failed.

ERROR X509_ERROR : .Query:%s

X509_ERROR : Invalid Certificate for

ERROR the "

ERROR

ERROR

ERROR invalid x509 certificate

Couldn't get the x509 cert hash

Memory allocation failed

Process operation failed state machine is in invalid state.

Packet length mismatch %d, %d eapAuthTypeToType: Invalid eapAuthType %d eapTypeToAuthType: Invalid eapType

%d

ERROR FileName too lengthy

ERROR Couldn't execute command

ERROR Memory allocation failed

ERROR Memory allocation failed

ERROR invalid certificate data unable to create method context. method ctxCreate failed.

Invalid condition, methodState = %d, respMethod = %d

A EAP Ctx map already exists eapTimerCreate: Currently unsupported for Peer role eapTimerStart: Currently unsupported for Peer role eapTimerDestroy: Currently unsupported for Peer role eapTimerCancel: Currently unsupported for Peer role eapTimerHandler: Currently unsupported for Peer role

ERROR .Query:%s

ERROR .Query:%s

ERROR Memory allocation failed

X509_ERROR : Failed to validate the

ERROR certficate "

ERROR Memory allocation failed

ERROR

ERROR

ERROR

ERROR

ERROR

.Query:%s

Invalid Sign Key Length : %d

Invalid Hash Alg : %d

Invalid Sign Alg : %d

No Memory Available

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

258

Unified Services Router

User Manual pCtx is NULL: ERROR tlsGlueCtxCreate failed eapVars is NULL

Context NULL: ERROR

Initializing inner EAP auth: ERROR pCtx is NULL: ERROR

Memory Allocation Failed

ERROR Certificate Request Failed

ERROR File Open Failed

ERROR File is Empty

ERROR Memory Allocation Failed

ERROR

ERROR

ERROR

ERROR

ERROR File Open Failed

ERROR File is Empty

ERROR

ERROR

ERROR Error in executing DB update handler ERROR

Facility: System (Admin)

Log Message

Usage:%s <DBFile>

Severity Log Message

DEBUG unable to register to UMI

Could not open database: %s

CPU LOG File not found

MEM LOG File not found cpuMemUsageDBUpdateHandler: update query: %s

Printing the whole list after inserting

%s at %d(minute) %d(hour)

%d(dayOfMonth) %d(month)" adpCmdExec exited with return code=%d

%s op=%d row=%d sqlite3_mprintf failed

DEBUG sqlite3QueryResGet failed

DEBUG radSendtoServer: socket: %s

DEBUG radSendtoServer: bind() Failed: %s:

%s

DEBUG radRecvfromServer: recvfrom()

Failed: %s

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG radRecvfromServer: Packet too small from %s:%d: %s radCheckMsgAuth: Invalid Message-

Authenticator length in" radDictLoad: couldn't open dictionary

%s: %s radBuildAndSendReq: Invalid

Request Code %d radPairAssign: bad attribute value length radPairAssign: unknown attribute type %d sqlite3QueryResGet failed: query=%s

Printing the whole list after delete

%s at %d(minute) %d(hour)

%d(dayOfMonth) %d(month)"

Printing the whole list after inserting

%s at %d(minute) %d(hour)

%d(dayOfMonth) %d(month)" email logs: No logging events enabled

%s

DEBUG radPairNew: unknown attribute %d radPairGen: Attribute(%d) has invalid

DEBUG

DEBUG length radPairValue: unknown attribute type

%d

DEBUG radPairValueLen: unknown attribute type %d

DEBUG

DEBUG radPairLocate: Attribute(%d) has invalid length radPairUnpackDefault: Unknown-

Attribute[%d]:

Mail sent and the Database is reset.

Disabled syslog server

DEBUG radConfigure: can't open %s: %s radConfigure: %s: line %d: bogus

DEBUG

Event logs are full, sending logs to email DEBUG format: %s radConfAssert: No AuthServer

Specified

Email logs sending failed DEBUG radConfAssert: No Default Timeout

Specified

Packing attribute: %s

Server found: %s, secret: %s

DEBUG

DEBUG radConfAssert: No Default Retry

Count Specified radExtractMppeKey: Invalid MS-

MPPE-Key Length

Severity

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

259

Unified Services Router

User Manual

Packed Auth. Reqest: code:%d, id:%d, len:%d

Sending Packet to %x:%d ....

Receiving Reply Packet....

Verified Reply Packet Integrity

Generated Reply Attribute-Value pairs

Verified Message-Authenticator

Unloaded RADIUS Dictionary

Adding Dictionary Attribute %s

Adding Dictionary Value %s

Loaded Dictionary %s

Adding Dictionary Attribute '%s'

Adding Dictionary Value %s

Receiving attribute: %s

Processing attribute: %s

Processing attribute: %s

Processing attribute: %s

Processing attribute: %s radConfGet: "

Added Server %s:%d with "

Added Server %s:%d with "

Default Timeout Set to %d

Default Retry Count Set to %d

%s - %s : %d

Deleting Server %s:%d with "

Adding RowId:%d to Server %s:%d with

" rowIds: %d - %d

Deleting Server %s:%d with "

RADIUS Deconfigured

Found Option %s on line %d of file %s

Setting Option %s with value %s

RADIUS Configured

%d : Server %s:%d with "

DBUpdate event: Table: %s opCode:%d rowId:%d

Host IP address: %s

Adding Packet for existing cookie:%p

Adding Packet and cookie:%p

Releasing Packet and cookie:%p

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG radVendorMessage: Invalid Length in

Vendor Message radVendorMessage: Unknown

Vendor ID received:%d radVendorAttrGet: Invalid Length in

Vendor Message radVendorAttrGet: Unknown Vendor

ID:%d radVendorMessagePack: Unknown

Vendor ID:%d radGetIPByName: couldn't resolve hostname: %s

ERROR

ERROR

ERROR

ERROR

ERROR

DEBUG ERROR

DEBUG radGetHostIP: couldn't get hostname ERROR

DEBUG radGetHostIP: couldn't get host IP address ERROR

DEBUG RADIUS dictionary loading failed

DEBUG Failed to set default timeout value

ERROR

ERROR

DEBUG Failed to set default retries value

ERROR: incomplete DB update

DEBUG

DEBUG information. old values result does not contain 2 rows

ERROR

ERROR

DEBUG sqlite3QueryResGet failed

ERROR

ERROR

DEBUG empty update. nRows=%d nCols=%d ERROR

DEBUG Error in executing DB update handler ERROR

DEBUG sqlite3QueryResGet failed ERROR

DEBUG Invalid SQLITE operation code - %d ERROR

DEBUG sqlite3QueryResGet failed ERROR

DEBUG empty result. nRows=%d nCols=%d ERROR

DEBUG sqlite3QueryResGet failed ERROR

DEBUG empty result. nRows=%d nCols=%d ERROR

DEBUG

RADIUS Accounting Exchange

Failed ERROR

DEBUG Unable to set debug for radAcct.

Unable to set debug level for

DEBUG radAcct.

ERROR

ERROR

DEBUG ERROR: option value not specified ERROR

DEBUG ERROR: option value not specified ERROR

DEBUG Unable to initialize RADIUS

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG radEapMsgQueueAdd: Invalid EAP packet length(%d) radEapRecvTask: invalid EAP code:%d radEapRecvTask: Packet length mismatch %d, %d

No attributes received in Access-

Challenge message

No State Attribute in Access-

Challenge message

DEBUG radEapRecvTask: "

DEBUG failed to initialize UMI

DEBUG umiRegister failed. errno=%d

DEBUG Invalid arguments to ioctl handler

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

260

Unified Services Router

User Manual

Releasing Packet with cookie:%p

Received EAP-Identity from Pnac: %s

Filling User-Name: %s

Filling State:

Filling EAP-Message:

DEBUG radEapSendRtn: Invalid Arguments

DEBUG radEapSendRtn: failed to allocate buffer

ERROR

DEBUG umiIoctl failed failed to initialize EAP message

DEBUG queue

ERROR

ERROR

DEBUG Unable to set debug for radEap.

ERROR

ERROR

DEBUG Unable to set debug level for radEap. ERROR

DEBUG ERROR: option value not specified ERROR

Filling Service-Type: %d

Filling Framed-MTU: %d

Received Access-Challenge from

Server

Sending Reply EAP Packet to Pnac

Error sending packet to Pnac

RADIUS Authentication Failed; "

RADIUS Authentication Successful; "

Got Packet with cookie:%p

Next DNS Retry after 1 min

Next Synchronization after"

Next Synchronization after"

Next Synchronization after %d \

Primary is not available, "

Secondary is not available, "

Invalid value for use default servers, "

No server is configured, "

DEBUG ERROR: option value not specified ERROR

DEBUG could not initialize MGMT framework ERROR

DEBUG Unable to initialize RADIUS

DEBUG Unable to set debug for radEap.

ERROR

ERROR

DEBUG Unable to set debug level for radEap. ERROR

DEBUG

DEBUG

ERROR: option value not specified

Unable to initialize RADIUS

ERROR

ERROR

DEBUG Invalid username or password

DEBUG Unable to set debug for radAuth.

DEBUG

Unable to set debug level for radAuth.

ERROR

ERROR

ERROR

DEBUG ERROR: option value not specified ERROR

DEBUG Unable to initialize RADIUS

Invalid username, challenge or

DEBUG response

ERROR

DEBUG Unable to set debug for radAuth.

DEBUG

Unable to set debug level for radAuth.

ERROR

ERROR

ERROR

DEBUG ERROR: option value not specified ERROR

Backing off for %d seconds

Requesting time from %s

Synchronized time with %s

Received KOD packet from %s

DEBUG Unable to initialize RADIUS

DEBUG Invalid username or password

ERROR

ERROR

No suitable server found %s DEBUG usage : %s <DB fileName>

Received Invalid Length packet from %s DEBUG ntpd : umi initialization failed

Received Invalid Version packet from

%s DEBUG ntpd : ntpInit failed

ERROR

ERROR

Received Invalid Mode packet from %s DEBUG ntpd : ntpMgmtInit failed

Request Timed out from %s

Looking Up %s

DEBUG

There was an error while getting the timeZoneChangeScript."

ERROR

ERROR

ERROR

DEBUG unexpected reply from %d cmd=%d ! ERROR

Timezone difference :%d

Could not open file: %s

Could not read data from file ntpTblHandler status: %d tz: %d

DayLightsaving: %d pNtpControl-

>ServerNames[PRIMARY_SERVER]:

%s

DEBUG

DEBUG

DEBUG Unable to initialize ntpControl ntpMgmt : Couldn't open database

DEBUG %s

ERROR : incomplete DB update

DEBUG information

ERROR

ERROR

ERROR

DEBUG empty update. nRows=%d nCols=%d ERROR

DEBUG Error in executing DB update handler ERROR

DEBUG cmd %d not supported. caller %d default reached requestNtpTime: Invalid addr

ERROR

ERROR

ERROR

261

Unified Services Router

User Manual pNtpControl-

>ServerNames[SECONDARY_SERVE

R]: %s

DS: %d pPriServ %s pSecServ %s

Making request from %d --> %d sent request dst(%d) <-- src(%d) using option %d received request too small!(%d bytes)

Received a UMI request from %d sent a reply src(%d) ---> dst(%d) umiRegister (%x,%x,%x,%x) srcId=%d(%s) --> destId=%d(%s) cmd=%d inLen=%d outLen=%d waiting for reply...Giving Up

No request in the list after semTake reply timeout timeout after semTake srcId=%d(%s) <-- destId=%d(%s) cmd=%d

DEBUG failed to take lock for compId: %d

DEBUG umiIoctlArgsToBuf: failed to allocate memory

DEBUG umiRecvFrom: could not allocate memory

ERROR

ERROR

DEBUG adpMalloc failed context with ID: %d already

DEBUG registered

Failed to allocate memory for

DEBUG

DEBUG

DEBUG creating UMI context

Failed to create recvSem for UMI context

Failed to create mutex locks for UMI context

DEBUG

Failed to create mutex recvQLock for

UMI context

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

DEBUG Invalid arguments to umiIoctl

ERROR

ERROR

DEBUG could not find the destination context ERROR

DEBUG memPartAlloc for %d size failed

Un-registerting component with Id %d failed to send ioctl request: dst(%d) <--- src(%d) processed a reply dst(%d) <-- src(%d) DEBUG id=%d handler=%x request with no result option dst(%d) <-- Received NULL buffer in src(%d) DEBUG umiBufToIoctlArgs() usbMgmtInit: unable to open the cmd = %s DEBUG database file %s cmdstring is %s %s:%d DEBUG call to printConfig failed

Calling printerConfig binary ...

DEBUG memPartAlloc for %d size failed

DEBUG

No Handler registered for this UMI context

DEBUG

Couldn't find component with ID

(%d),"

Calling unmount for USB ...

Calling mount for USB ... usbdevice is %d %s:%d

DEBUG Failed to Disable Network Storage"

DEBUG

DEBUG

Some error occurred while removing device

Some error occurred while removing device

DEBUG Sqlite update failed

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

Query string: %s sqlite3QueryResGet failed.Query:%s

%s: 1. usb is already disconnected for old usb type. "

%s: 2.call disable for new usb type !

%s: 3. usb is already disconnected for old usb type. "

DEBUG failed to take lock for compId: %d failed to convert ioctl args to buffer

DEBUG for"

ERROR

ERROR

DEBUG request timeout dst(%d) <-- src(%d) ERROR

DEBUG Failed to enable printer properly

DEBUG Failed to mount device on system

DEBUG

Failed to enable network storage device"

DEBUG Failed to mount device on system

ERROR

ERROR

ERROR

ERROR

%s: 4. Disabled old usb type . Now " usbdevice is %d %s:%d

USB: failed to begin transaction: %s

USB: SQL error: %s pSetString = %s

DEBUG Sqlite update failed

DEBUG USB1 Touch failed

DEBUG USB2 Touch failed

DEBUG Sqlite update failed

DEBUG Failed query: %s

ERROR

ERROR

ERROR

ERROR

ERROR

262

Unified Services Router

User Manual

USB: failed to commit transaction: %s

USB: updated table: %s

USB: returning with status: %s

%s:DBUpdate event: Table: %s opCode:%d rowId:%d executing %s status =%d executing %s

%s returned status=%d

%s returned status=%d

DEBUG

DEBUG

Failed to execute usb database update handler

Usage:%s <DBFile> <opType>

<tblName> <rowId>

ERROR

ERROR

DEBUG Illegal invocation of snmpConfig (%s) ERROR

DEBUG Invalid Community Access Type

DEBUG Invalid User Access Type

DEBUG Invalid Security Level

DEBUG Invalid Authentication Algorithm

DEBUG Invalid Privacy Algorithm

ERROR

ERROR

ERROR

ERROR

ERROR snmpd.conf not found

[SNMP_DEBUG] : Fwrite Successful

DEBUG Invalid Argument

Failed to allocate memory for

DEBUG engineID

[SNMP_DEBUG]: Failed to get host

DEBUG address [SNMP_DEBUG] : Fwrite failed radPairGen: received unknown attribute

%d of length %d radPairGen: %s has unknown type radPairLocate: unknown attribute %ld of length %d

WARN

WARN

WARN radPairLocate: %s has unknown type WARN

[SNMP_DEBUG] : FOPEN failed sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s

Invalid Security Level

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

Illegal invocation of cpuMemUsage (%s) ERROR Invalid Authentication Algorithm cpuMemUsageDBUpdateHandler: SQL error: %s ERROR Invalid Privacy Algorithm unable to open the DB file %s umiInit failed unable to register to UMI

Error Reading from the Database. short DB update event request!

Error in executing DB update handler

adpListNodeRemove : Returned with an error command too long. Try increasing " failed to allocate memory for

CRON_NODE sqlite3QueryResGet failed

There was an error while reading the schedules. unable to register to UMI short DB update event request! malloc(DB_UPDATE_NODE) failed short ifDev event request! sqlite3_mprintf failed

ERROR Failed to Get Host Address

ERROR Invalid version

ERROR

ERROR

ERROR

ERROR snmp v3 Trap Configuration Failed ERROR

ERROR sqlite3QueryResGet failed query:%s ERROR

ERROR sqlite3QueryResGet failed.Query:%s ERROR

ERROR

Failed to Open Snmp Configuration

File ERROR

ERROR

ERROR Failed to write snmpv3 users entries ERROR

ERROR

ERROR

ERROR

Failed to write access control entries

Failed to write snmp trap entries

Failed to write system entries.

Failed to restart snmp

ERROR %s failed with status

ERROR Error in executing DB update handler

ERROR %s: Unable to open file: %s

ERROR RADVD start failed

ERROR RADVD stop failed failed to create/open RADVD

ERROR configuration file %s

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR no component id matching %s umiIoctl (%s,

UMI_CMD_DB_UPDATE(%d)) failed. ERROR sqlite3_mprintf failed sqlite3_mprintf failed no component id matching %s

ERROR Restoring old configuration..

ERROR failed to write/update RADVD configuration file

ERROR upnpDisableFunc failed

ERROR upnpEnableFunc failed

ERROR

ERROR

ERROR

263

Unified Services Router

User Manual umiIoctl (%s,

UMI_CMD_IFDEV_EVENT(%d)) failed. ERROR sqlite3QueryResGet failed.Query:%s ERROR klogctl(9) failed malloc failed for %d bytes klogctl(4) failed emailLogs: Invalid Number of

Arguments!! Exiting.

ERROR

ERROR

ERROR

ERROR

Error in executing DB update handler unable to open the DB file %s umiInit failed unable to register to UMI

ERROR short DB update event request!

ERROR

ERROR

ERROR

ERROR

ERROR sqlite3QueryResGet failed

Could not execute the smtpClient.

Error while cleaning the database.Exiting. %s

ERROR

ERROR short ifDev event request! sqlite3_mprintf failed

%s failed. status=%d

ERROR

ERROR

ERROR

Facility: System (Firewall)

Log Message Severity Log Message Severity

Enabling rule for protocol binding.

Disabling rule for protocol binding.

DEBUG Disable all NAT rules.

DEBUG Enable all NAT rules.

DEBUG

DEBUG

Enabling Remote SNMP on WAN.

Disabling Remote SNMP on WAN wan traffic counters are restared

Traffic limit has been reached

Traffic meter monthly limit has been changed to %d.

DEBUG Enabling NAT URL filter rules.

DEBUG Restarting all NAT rules.

DEBUG

DEBUG

Deleting schedule based firewall rules from DB.

Update schedule based firewall rules in DB.

DEBUG

DEBUG

DEBUG Deleting schedule based firewall rules. DEBUG

DEBUG

DEBUG

Enabling traffic meter for only dowload. DEBUG Restart schedule based firewall rules. DEBUG

Enabling traffic meter for both directions. DEBUG inter vlan routing enabled DEBUG

Enabling traffic meter with no limit. DEBUG inter vlan routing disabled DEBUG

DEBUG

DEBUG

Email alert in traffic meter disabled.

Email alert in traffic meter enabled.

Traffic Meter:Monthly limit %d MB has been "

Traffic Metering: Adding rule to drop all traffic

DEBUG

DEBUG

DEBUG

DEBUG

Disabling Content Filter for %d

Enabling Content Filter for %d

./src/firewall/linux/user/firewalld.c:59:# undef ADP_DEBUG2

./src/firewall/linux/user/firewalld.c:61:# define ADP_DEBUG2 printf

Traffic Metering: %sabling Email traffic DEBUG Enabling Source MAC Filtering

Disabling attack checks for IPv6 rules. DEBUG Disabling Source MAC Filtering

Enabling attack checks for IPv6 rules. DEBUG

Adding MAC Filter Policy for Block &

Permit Rest

Configuring one to one NAT settings with %s private start IP "

Deleting forward one to one NAT having setting %s private start"

Disabling attack check for Block ping to

WAN interface.

Disabling attack check for Stealth mode for tcp

Disabling attack check for Stealth mode for udp

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

Adding MAC Filter Policy for Permit &

Block Rest

Restarting Source MAC Address

Policy

Disabling Firewall Rule for DHCP

Relay Protocol

Enabling Firewall Rule for DHCP

Relay Protocol prerouting Firewall Rule add for Relay failed

Disabling attack check for TCP Flood. DEBUG prerouting Firewall Rule add for Relay failed

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

264

Unified Services Router

User Manual

Disabling attack check for UDP Flood.

Disabling attack check for IPsec.

Disabling attack check for PPTP.

DEBUG

DEBUG

Deleting MAC Filter Policy for Address

%s

Adding MAC Filter Policy for Address

%s

DEBUG

DEBUG

DEBUG Disabling Firewall Rules for DMZ host DEBUG

Disabling attack check for L2TP. DEBUG Enabling Firewall Rules for DMZ host DEBUG

Disabling Firewall Rules for Spill Over

Disabling attack check for UDP Flood. DEBUG Load Balancing

Disabling Firewall Rules for Load

DEBUG

Disabling attack check for IPsec.

Disabling attack check for PPTP.

DEBUG

DEBUG

Balancing

Enabling Firewall Rules for Load

Balancing

DEBUG

DEBUG

Disabling attack check for L2TP. DEBUG

Enabling Firewall Rules for Spill Over

Load Balancing DEBUG

Enabling attack check for Block ping to

WAN "

Enabling attack check for Stealth Mode for tcp.

Enabling attack check for Stealth Mode for udp.

Enabling attack check for TCP Flood.

DEBUG

DEBUG

DEBUG

DEBUG

Enabling Firewall Rules for Auto

Failover

Enabling Firewall Rules for Load

Balancing .

Enabling Firewall Rules for Spill Over

Load Balancing .

Enabling Firewall Rules for Auto

Failover

DEBUG

DEBUG

DEBUG

DEBUG

Enabling attack check for UDP Flood.

Enabling attack check for IPsec.

Enabling attack check for PPTP.

Enabling attack check for L2TP.

DEBUG

DEBUG

DEBUG

DEBUG

Deleting BlockSites Keyword \

Enabling BlockSites Keyword \

Disabling BlockSites Keyword \

Updating BlockSites Keyword from \

DEBUG

DEBUG

DEBUG

DEBUG

Enabling attack check for UDP Flood.

Enabling attack check for IPsec.

Enabling attack check for PPTP.

DEBUG Inserting BlockSites Keyword \

DEBUG Deleting Trusted Domain \

DEBUG Adding Trusted Domain \

DEBUG

Restarting Schedule Based Firewall

Rules

DEBUG

DEBUG

DEBUG

DEBUG Enabling attack check for L2TP.

Enabling DoS attack check with %d

SyncFlood detect rate, "

Disabling DoS attack check having %d

SyncFlood detect rate,"

Enabling ICSA Notification Item for

ICMP notification.

Enabling ICSA Notification Item for

Fragmented Packets.

Enabling ICSA Notification Item for

Multi cast Packets.

Disabling ICSA Notification Item for

ICMP notification.

Disabling ICSA Notification Item for

Fragmented Packets.

Disabling ICSA Notification Item for

Multi cast Packets.

Adding IP/MAC binding rule for %s

MAC address "

Deleting IP/MAC binding rule for %s

MAC "

./src/firewall/linux/user/firewalld.c:60:#u ndef ADP_DEBUG

./src/firewall/linux/user/firewalld.c:62:#d efine ADP_DEBUG printf

Restarting traffic meter with %d mins,

%d hours, "

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

Enabling Remote SNMP

Disabling Remote SNMP

Enabling Remote SNMP

Disabling DOS Attacks

Enabling DOS Attacks

Enabling DOS Attacks

Restarting Firewall [%d]:[%d] For %s restartStatus = %d for LogicalIfName

= %s

Deleting Lan Group %s

Adding Lan Group %s

Deleting lan host %s from group %s

Adding lan host %s from group %s

Disabling Firewall Rule for IGMP

Protocol

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

265

Unified Services Router

User Manual

Updating traffic meter with %d mins,

%d hours, "

Deleting traffic meter.

Disabling block traffic for traffic meter.

Enabling traffic meter.

Adding lan group %s.

Deleting lan group %s.

Renaming lan group from %s to %s.

Deleting host %s from %s group.

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

Enabling Firewall Rule for IGMP

Protocol

Deleting IP/MAC Bind Rule for MAC address %s and IP "

Adding IP/MAC Bind Rule for MAC address %s and IP

Deleting Protocol Bind Rule for

Service %s

Deleting Protocol Bind Rule for

Service %s

Deleting Protocol Bind Rule for

Service %s

Adding Protocol Bind Rule for Service

%s

DEBUG %s Session Settings

Adding host %s to %s group.

Enabling Keyword blocking for %s keyword.

Disabling keyword Blocking for %s keyword .

Deleting trusted domain with keyword

%s.

Adding %s keyword to trusted domain.

DEBUG Restarting IPv6 Firewall Rules...

Deleting Port Trigger Rule for

DEBUG %d:%d:%d:%d:%d

Deleting Port Trigger Rule for

DEBUG

DEBUG

%d:%d:%d:%d:%d

Enabling Port Trigger Rule for

%d:%d:%d:%d:%d

DEBUG

Disabling Port Trigger Rule for

%d:%d:%d:%d:%d

Enabling Management Access from

Internet on port %d

Enabling remote access management for IP address range"

Enabling remote access management to only this PC.

Disabling Management Access from

Internet on port %d

Disabling remote access management for IP address range"

Disabling remote access management only to this PC.

MAC Filtering %sabled for BLOCK and

PERMIT REST.

MAC Filtering %sabled for PERMIT and

BLOCK REST.

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

Enabling Port Trigger Rule for

%d:%d:%d:%d:%d

Disabling Port Trigger Rule for

%d:%d:%d:%d:%d

Adding Port Trigger Rule for

%d:%d:%d:%d:%d

Enabling Content Filter

Disabling Content Filter

Enabling Content Filter

Setting NAT mode for pLogicalIfName

= %s

Enabling DROP for INPUT

Enabling Content Filtering. DEBUG Enabling DROP for FORWARD

Disabling Content Filtering.

Deleting rule, port triggering for protocol

TCP.

Deleting rule, port triggering for protocol

UDP.

Deleting rule, port triggering for protocol

TCP.

Deleting rule, port triggering for protocol

UDP.

Enabling rule, port triggering for protocol TCP.

Enabling rule, port triggering for protocol UDP.

Enabling rule, port triggering for protocol TCP.

Enabling rule, port triggering for protocol UDP.

DEBUG Enabling NAT based Firewall Rules

DEBUG

Setting transparent mode for pLogicalIfName \

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

Enabling Accept for INPUT

Enabling Accept for FORWARD

Setting Routing mode for pLogicalIfName \

Enabling DROP for INPUT

Enabling DROP for FORWARD

Disabling NAT based Firewall Rules

Enabling Firewall Rules for URL

Filtering & "

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

266

Unified Services Router

User Manual

Enabling DNS proxy.

Restarting DNS proxy. checking DNS proxy for Secure zone.

DEBUG Adding Firewall Rule for RIP Protocol DEBUG

DEBUG

Restarting Schedule Based Firewall

Rules DEBUG

DEBUG

DEBUG enabling IPS checks between %s and

%s zones. disabling IPS checks between %s and

%s zones.

DEBUG

DEBUG

DEBUG Stopping IPS...%s DEBUG checking DNS proxy for Public zone.

Enabling Block traffic from %s zone.

Configuring firewall session settings for

"

Disabling DMZ

Disabling WAN-DMZ rules .

Enabling WAN DMZ rules .

Restarting DMZ rule having %s address with %s address.

Enabling LAN DHCP relay.

DEBUG IPS started.

DEBUG Route already exists

DEBUG

Route addition failed: Network

Unreachable

DEBUG

DEBUG

DEBUG

DEBUG Route addition failed: Network is down DEBUG

DEBUG Route addition failed

DEBUG Failed to add rule in iptables

DEBUG

DEBUG

OneToOneNat configured successfully DEBUG Failed to delete rule from iptables fwLBSpillOverConfigure: Something

OneToOneNat configuration failed DEBUG

Deleting scheduled IPv6 rules. DEBUG going wrong here fwLBSpillOverConfigure: unable to get interfaceName delete from FirewallRules6 where

ScheduleName = '%s'.

Update FirewallRules6 where

ScheduleName = '%s' to New "

Dns proxy Restart failed deleting interface to ifgroup failed adding interface to ifgroup failed

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG fwLBSpillOverConfigure: Could not set

PREROUTING rules fwLBSpillOverConfigure: Could not set

POSTROUTING rules fwLBSpillOverConfigure: Something going wrong Here fwL2TPGenericRules.c: unable to open the database file " fwL2TPGenericRules.c: inet_aton failed deleting interface pVirtIface %s from ifgroup %d" adding interface pVirtIface %s to ifgroup %d failed

Deleting IP address %s.

Adding new IP address %s.

Updating old IP address %s to new IP address %s.

Restarting Firewall For %s Address

Update from %s:%s

Disabling Firewall Rule for MSS packet marking

Enabling Firewall Rule for MSS packet marking

Enabling packet marking rule for %s

IDLE timer

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG fwPPTPGenericRules.c: unable to open the database file " fwPPTPGenericRules.c: inet_aton failed

DNS proxy firewall rule add failed for

%s deleting interface %s from ifgroup %d failed adding interface %s to ifgroup %d failed nimfBridgeTblHandler: unable to get interfaceName nimfBridgeTblHandler: \ nimfBridgeTblHandler: unable to get \

Failed to %s traffic from %s to %s to

IPS.

Failed to %s traffic from %s to %s to

IPS.

DEBUG

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

Deleted firewall rule %s for service %s with action %s

%s firewall rule %s for service %s with action %s

Added firewall rule %s for service %s with action %s

DEBUG

DEBUG failed to start IPS service.

Timeout in waiting for IPS service to start.

ERROR

ERROR

267

Unified Services Router

User Manual

Deleting inbound(WAN-LAN) firewall rule.

Deleting inbound(WAN-DMZ) firewall rule.

RIPng disabled.

RIPng enabled.

Disable IPv6 firewall rule.

Enable IPv6 firewall rule.

Deleting IGMP proxy rule.

Enable IGMP proxy rule.

DEBUG

Usage:%s <DBFile> <opType>

<tblName> <rowId> " xlr8NatConfig: illegal invocation of

(%s) DEBUG

DEBUG Illegal invocation of [%s] xlr8NatMgmtTblHandler: failed query:

DEBUG %s

DEBUG

DEBUG

DEBUG

DEBUG

Could not open file: %s

Rip Error Command Too Long

No authentication for Ripv1

Invalid Rip Direction

Restarting IGMP rule. DEBUG Invalid Rip Version

Traffic meter enabled with no limit type. DEBUG Invalid Password for 1st Key

Traffic meter enabled for only download.

Traffic meter enabled for both

DEBUG Invalid Time for 1st Key

DEBUG Invalid Password for 2nd Key directions.

Deleted firewall rule %s for service %s with action %s

%s firewall rule %s for service %s with action %s

DEBUG

DEBUG

Invalid Time for 2nd Key

Invalid First KeyId

Added firewall rule %s for service %s with action %s DEBUG Invalid Second KeyId

Enabling Inter VLAN routing.

Updating inter VLAN routing status.

Deleting inter VLAN routing.

DEBUG Invalid Authentication Type

DEBUG ripDisable failed

DEBUG ripEnable failed

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

Facility: Local0 (Wireless)

Log Message

(node=%s) setting %s to val = %d

Custom wireless event: '%s'

Wireless event: cmd=0x%x len=%d

New Rogue AP

(%02x:%02x:%02x:%02x:%02x:%02x) detected

WPS session in progress, ignoring enrolle assoc request

Severity

DEBUG

DEBUG

DEBUG

DEBUG

Log Message

sqlite3QueryResGet failed sqlite3QueryResGet failed

VAP(%s) set beacon interval failed

VAP(%s) set DTIM interval failed

Severity

ERROR

ERROR

ERROR

ERROR

DEBUG VAP(%s) set RTS Threshold failed

VAP(%s) set Fragmentation

DEBUG Threshold failed

ERROR ran query %s

DBUpdate event: Table: %s opCode:%d rowId:%d

%sing VAPs using profile %s

%sing VAP %s ran query %s

%sing VAP instance %s

VAP(%s) set Short Preamble failed

ERROR

DEBUG VAP(%s) set Protection Mode failed

DEBUG VAP(%s) set Tx Power failed

DEBUG WDS Profile %s not found

DEBUG Failed to initalize WPS on %s

ERROR

ERROR

ERROR

ERROR

DEBUG failed to get profile %s ERROR

DEBUG could not initialize MGMT framework ERROR

VAP(%s) set Short Retry failed

VAP(%s) set Long Retry failed

DEBUG

DEBUG could not initialize MGMT framework dot11VapBssidUpdt SQL error: %s

ERROR

ERROR

Decrypting context with key %s DEBUG sqlite3QueryResGet failed.Query:%s ERROR

KDOT11_GET_PARAM(IEEE80211_

Unknown IAPP command %d received. DEBUG IOC_CHANNEL) failed ERROR

268

Unified Services Router

User Manual unexpected reply from %d cmd=%d ! unexpected reply from %d cmd=%d !

Recvied DOT11_EAPOL_KEYMSG shutting down AP:%s

APCtx Found

APCtx Not-Found node not found *:*:*:%x:%x:%x error installing unicast key for %s cmd =%d i_type =%d i_val=%d join event for new node %s wpa/rsn IE id %d/%d not supported wpa IE id %d not supported leave event for node %s

NodeFree request for node : %s installing key to index %d iReq.i_val : %d pIfName : %s iReq.i_val : %d setting mode: %d

Global counter wrapped, regenerating...

Got

PNAC_EVENT_PREAUTH_SUCCESS event for : %s event for non-existent node %s

PNAC_EVENT_EAPOL_START event received

PNAC_EVENT_EAPOL_LOGOFF event received

PNAC_EVENT_REAUTH event received

PNAC_EVENT_AUTH_SUCCESS event received

PNAC_EVENT_PORT_STATUS_CHAN

GED event received

DEBUG UDP failed, received Length is %d

DEBUG umiIoctl(UMI_COMP_KDOT11, umiIoctl(UMI_COMP_UDOT11,%d,%

DEBUG d) \ umiIoctl(UMI_COMP_KDOT11,%d,%

DEBUG d) \

DEBUG No IAPP Node found for req id %d

DEBUG

DEBUG

DEBUG umiIoctl(UMI_COMP_UDOT11,%d,% d) \ umiIoctl(UMI_COMP_KDOT11,%d,% d) \ umiIoctl(UMI_COMP_UDOT11,%d,% d) failed unsupported event %d from PNAC event for non-existent node %s. Create new node.

Add new node to DOT11 Node list

Update dot11STA database

Add PMKSA to the list eapolRecvAuthKeyMsg: received key message node not found eapolRecvKeyMsg: replay counter not incremented

DEBUG

Failed to get the channel setting for

%s ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

DEBUG profile %s not found ERROR

DEBUG sqlite3QueryResGet failed.Query:%s ERROR

Interface name and policy must be

DEBUG specified

Interface name and policy must be

ERROR

DEBUG specified ERROR

DEBUG invalid ACL type %d ERROR

DEBUG interface name not specified

DEBUG interface name not specified

DEBUG Invalid interface - %s specified

DEBUG buffer length not specified

ERROR

ERROR

ERROR

ERROR

DEBUG Invalid length(%d) specified

DEBUG failed created iappdLock

DEBUG failed to create cipher contexts.

DEBUG unable to register to UMI

DEBUG iappSockInit() failed

DEBUG

DEBUG

DEBUG iappInit got error, unregistering it with

UMI umiIoctl(UMI_COMP_UDOT11,%d,% d) failed umiIoctl(UMI_COMP_KDOT11,%d,% d) failed

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

DEBUG UDP socket is not created

DEBUG UDP send failed

DEBUG

IAPP: socket (SOCK_STREAM) failed.

DEBUG IAPP: TCP connect failed to %s.

DEBUG cmd %d not supported.sender=%d umiIoctl(UMI_COMP_KDOT11,%d,%

DEBUG d) failed

IAPP-CACHE-NOTIFY-REQUEST

DEBUG send to

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

269

Unified Services Router

User Manual eapolRecvKeyMsg: replay counter is not same processing pairwise key message 2

RSN IE matching: OK processing pairwise key message 4 processing group key message 2 processing key request message from client

WPA version %2x %2x not supported

(%s) group cipher %2x doesn't match

(%s)Pairwise cipher %s not supported

(%s) authentication method %d not supported

%s:Auth method=%s pairwise cipher=%s IE size=%d

WPA version %2x %2x not supported

Unable to obtain IE of type %d

PTK state changed from %s to %s using PMKSA from cache

PTK GK state changed from %s to %s

GK state changed from %s to %s

Sending PTK Msg1

Sending PTK Msg3

Sending GTK Msg1 sending EAPOL pdu to PNAC... creating pnac authenticator with values

%d %d - %s

Profile %s does not exist

IAPP initialized.

Encrypting context key=%s for could not find access point context for

%s join event for existing node %s failed to send

PNAC_FORCE_AUTHORIZED " failed to send PNAC_AUTHORIZED " failed to send

PNAC_VAR_KEY_AVAILABLE (TRUE)

" failed to send

PNAC_VAR_KEY_TX_EN (TRUE) " failed to send

PNAC_VAR_KEY_TX_EN (FALSE) " failed to send

PNAC_FORCE_AUTHORIZED " failed to send PNAC_AUTHORIZED " mic verification: OK

DEBUG

DEBUG BSSID value passed is NULL

DEBUG reserved requestId is passed

DEBUG interface name is NULL

DEBUG

DEBUG opening receive UDP socket failed enabling broadcast for UDP socket

DEBUG

DEBUG failed opening receive TCP socket for new

AP failed

DEBUG

DEBUG

DEBUG

./src/dot11/iapp/iappLib.c:1784:

ADP_ERROR(

./src/dot11/iapp/iappLib.c:1794:

ADP_ERROR(

./src/dot11/iapp/iappLib.c:1803:

ADP_ERROR(

DEBUG failed created dot11dLock.

DEBUG failed initialize profile library.

DEBUG failed to create cipher contexts.

DEBUG unable to register to UMI

DEBUG could not create MIB tree

DEBUG unable to register to PNAC

Max registration attempts by DOT11

DEBUG to PNAC exceeded

DEBUG Creation of EAP WPS Profile Failed umiIoctl(UMI_COMP_IAPP,%d )

DEBUG

DEBUG failed

DOT11_RX_EAPOL_KEYMSG: unknown ifname %s

DEBUG

DEBUG

DEBUG

DEBUG inteface name passed is NULL unable to allocate memory for

DEBUG cmd %d not supported.sender=%d inteface name passed is NULL

BSSID passed is NULL

DOT11_CTX

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

DEBUG unable to install wme mapping on %s ERROR

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

./src/dot11/iapp/iappLib.c:1314:

ADP_ERROR (

IP address value passed is NULL unable to get %s mac address

Failed to set %s SSID

Failed to set SSID broadcast status

Failed to set PreAuth mode

DEBUG unable to install key

KDOT11_SET_PARAM:IEEE80211_I

OC_AUTHMODE failed

KDOT11_SET_PARAM:IEEE80211_I

OC_PRIVACY failed

DEBUG wpaInit failed

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

270

Unified Services Router

User Manual pnacIfConfig: Invalid supplicant"

Failed to process user request

DEBUG dot11InstallProfile: unable to get interface index

DEBUG adpHmacInit(%s) failed

Failed to process user request - %s(%d) DEBUG interface %s not found pnacIfConfigUmiIoctl: umiIoctl failed pnacIfConfigUmiIoctl: usrPnac returned

%d pnacIfConfigUmiIoctl: usrPnac returned

%d pnacIfConfigUmiIoctl: usrPnac returned

%d pnacKernNotifier: invalid PAE configuration "

From pnacEapDemoAuthRecv: unsupported response "

From pnacEapDemoAuthRecv: invalid codes received

From pnacRadXlateDemoRecv: received unknown "

From pnacRadXlateDemoRecv: invalid codes received

Error from pnacRadXlateDemoRecv: malloc failed

From pnacRadXlateRadPktHandle: received a non-supported"

Only md5 authentication scheme currently supported. "

Message from authenticator: from pnacPDUXmit: bufsize = %d, pktType = %d," pnacPDUXmit: sending eap packet. code = %d, " pnacRecvRtn: no corresponding pnac port pae found

DEBUG AP not found on %s

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG error creating PNAC port for node %s ERROR

DEBUG

DEBUG

DEBUG keyLen > PNAC_KEY_MAX_SIZE

Invalid profile name passed

Creation of WPS EAP Profile failed unsupported command %d device %s not found unsupported command %d dot11NodeAlloc failed

Getting WPA IE failed for %s

Getting WPS IE failed for %s

Failed initialize authenticator for node

%s

Failed to get the system up time while adding node %s dot11NodeAlloc failed

Invalid arguments. umiIoctl(UMI_COMP_IAPP,%d) failed

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR sending unicast key sending broadcast key from pnacAuthPAEDisconnected: calling pnacTxCannedFail from pnacAuthPAEForceUnauth: calling pnacTxCannedFail state changed from %s to %s

PNAC user comp id not set. dropping event %d sending event %d to %d requesting keys informantion from %d pnacUmiPortPaeParamSet: error in getting port pae pnacUmiPortPaeParamSet: invalid param - %d pnacRecvASInfoMessage: Skey of length %d set pnacRecvASInfoMessage: reAuthPeriod set to: %d

DEBUG Invalid IE. umiIoctl(UMI_COMP_KDOT11_VAP,

DEBUG %d ) failed umiIoctl(UMI_COMP_KDOT11,%d

DEBUG

DEBUG

,%d) failed

KDOT11_SET_PARAM:IEEE80211_I

OC_WME_CWMIN failed

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

KDOT11_SET_PARAM:IEEE80211_I

OC_WME_CWMAX failed

KDOT11_SET_PARAM:IEEE80211_I

OC_WME_AIFS failed

KDOT11_SET_PARAM:80211_IOC_

WME_TXOPLIMIT failed

KDOT11_SET_PARAM:IEEE80211_I

OC_WME_ACM failed

KDOT11_SET_PARAM:IEEE80211_I

OC_WME failed

DEBUG

DEBUG

DEBUG invalid group cipher %d

KDOT11_SET_PARAM:IEEE80211_I

OC_MCASTCIPHER failed

KDOT11_SET_PARAM:IEEE80211_I

OC_MCASTKEYLEN failed

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

271

Unified Services Router

User Manual pnacRecvASInfoMessage: suppTimeout set to: %d

PORT SUCCESSFULLY DESTROYED creating physical port for %s pnacAuthInit: using defualt pnacAuthParams pnacSuppInit: using defualt pnacSuppParams

Error from pnacCombinedStMachTriggerFunc: "

Error from pnacCombinedStMachTriggerFunc: "

Error from pnacCombinedStMachTriggerFunc: "

Error from pnacCombinedStMachTriggerFunc: "

Error from pnacCombinedStMachTriggerFunc: "

Error from pnacCombinedStMachTriggerFunc: "

Error from pnacCombinedStMachTriggerFunc: "

Error from pnacCombinedStMachTriggerFunc: "

Error from pnacCombinedStMachTriggerFunc: " received a pdu on %s pnacRecvMapi: protoType: %04x pPhyPort->authToASSendRtn:%p port not found from pnacRecvMapi: pkt body len = %d, pktType = %d from pnacPDUProcess: received

PNAC_EAP_PACKET from pnacPDUProcess: received " from pnacPDUProcess: received " from pnacPDUProcess: received

PNAC_EAPOL_KEY_PACKET doing pnacTxCannedFail doing pnacTxCannedSuccess

DEBUG dot11Malloc failed

DEBUG dot11Malloc failed

DEBUG eapolRecvKeyMsg: unknown descType =%d

DEBUG eapolRecvKeyMsg: invalid descriptor version

DEBUG from pnacPDUProcess: currentId = %d DEBUG from pnacPDUProcess: code = %d,

DEBUG identifier = %d, " from pnacPDUProcess: setting rxResp true from pnacPDUProcess: code = %d, identifier = %d, "

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG eapolRecvKeyMsg: incorrect descriptor version eapolRecvKeyMsg: Ack must not be set eapolRecvKeyMsg: MIC bit must be set wpaAuthRecvPTKMsg2: unexpected packet received wpaAuthRecvPTKMsg2: mic check failed wpaAuthRecvPTKMsg2: rsn ie mismatch wpaAuthRecvPTKMsg4: unexpected packet received wpaAuthRecvPTKMsg4: keyDataLength not zero wpaAuthRecvPTKMsg4: mic check failed wpaAuthRecvGTKMsg2: unexpected packet received doing pnacTxReqId doing pnacTxReq

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

KDOT11_SET_PARAM:IEEE80211_I

OC_UCASTCIPHERS failed

KDOT11_SET_PARAM:IEEE80211_I

OC_KEYMGTALGS failed

KDOT11_SET_PARAM:IEEE80211_I

OC_WPA failed unknow cipher type = %d umiIoctl(UMI_COMP_IAPP,%d) failed invalid media value=%d invalid mediaOpt value=%d invalid mode value=%d dot11PnacIfCreate failed wpaPRF failed

DEBUG Error generating global key counter

DEBUG wpaCalcMic: unsupported key descriptor version

DEBUG

DEBUG integrity failed. need to stop all stations " couldn't find AP context for %s interface

DEBUG secureBit not set in GTK Msg2 wpaAuthRecvGTKMsg2:

DEBUG keyDataLength not zero

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

272

Unified Services Router

User Manual doing pnacTxStart DEBUG wpaAuthRecvGTKMsg2: mic check failed doing pnacTxLogoff doing pnacTxRspId: 1st cond

DEBUG

DEBUG wpaAuthRecvKeyReq: unexpected packet received wpaAuthRecvKeyReq: keyDataLength not zero doing pnacTxRspId: entering 2nd cond DEBUG from pnacTxRspId: code = %d, identifier

= %d, length = %d, " wpaAuthRecvKeyReq: mic check failed

DEBUG invalid OUI %x %x %x doing pnacTxRspId: 2nd cond DEBUG (%s) invalid OUI %x %x %x doing pnacTxRspAuth: 1st cond doing pnacTxRspAuth: 2nd cond

message for unknown port PAE from pnacACToSuppRecvRtn: calling pnacEapPktRecord from pnacEapPktRecord: code = %d, identifier = %d, " from pnacEapPktRecord: received success pkt from pnacEapPktRecord: received failure pkt from pnacEapPktRecord: received request pkt unknown EAP-code %d

Authenticator[%d]:

Auth PAE state = %s

Auth Reauth state = %s

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

[%s:%d] Cipher in WPA IE : %x

(%s) invalid OUI %x %x %x short WPA IE (length = %d) received

PTK state machine in unknown state.

dot11InstallKeys failed group state machine entered into

WPA_AUTH_GTK_INIT dot11Malloc failed dot11Malloc failed

DEBUG dot11Malloc failed

DEBUG aesWrap failed

DEBUG unknown key descriptor version %d

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

Back auth state = %s

Supplicant[%d]:

Supp Pae state = %s from pnacBackAuthFail: calling pnacTxCannedFail

%s returned ERROR pnacUmiIoctlHandler: cmd: %s(%d)

DEBUG dot11Malloc failed

DEBUG could not initialize AES128ECB

DEBUG could not initialize AES-128-ECB

DEBUG MD5 initialization failed

DEBUG

DEBUG PNAC framework initialization failed ERROR

DEBUG

RC4 framework initialization failed

ERROR: option value not specified

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

DEBUG ERROR: -u can be used only with -s ERROR %s not configured for 802.1x could not process PDU received from the wire pnacPDUForward: failed to foward the received PDU

Creating PHY port with AUTH backend :

%s SendRtn: %p RecvRtn:%p pnacUmiAuthConfig: %s not configured for 802.1x pnacSuppRegisterUserInfo: not a valid

AC

DEBUG

DEBUG

DEBUG

ERROR: user-name not specified failed to enable debug

[%s]: failed to convert string to MAC "

ERROR

ERROR

ERROR

ERROR

ERROR pnacIfConfig: autoAuth Enabled pnacSendRtn: no pnac port pae found for " sending portStatus: %s[%d] to dot11

DEBUG failed to initialize UMI pnacPhyPortParamSet:invalid

DEBUG arguments pnacPhyPortParamSet:Failed to

DEBUG create socket

Error from pnacPhyPortParamSet:%s-device

DEBUG

DEBUG invalid

Error from pnacPhyPortParamSet:%s-Getting

MAC address "

ERROR

ERROR

ERROR

273

Unified Services Router

User Manual pnacRecvASInfoMessage: Rkey of length %d set DEBUG

ASSendRtn: %p ASToAuthRecv: %p adpRand failed:unable to generate random unicast key using group key as unicast key

Integrity check failed more than once in last 60 secs.

MIC failed twice in last 60 secs, taking countermeasures

DEBUG

WARN

WARN

WARN

WARN

Failed to set dot11 port status

PTK state machine in NO_STATE.

PTK state machine in NO_STATE!!

PMKSA refcount not 1

IV verification failednknown subtype> pnacIfConfig: overwriting previous interface " pnacIfConfig: overwriting previous " pnacIfConfig: overwriting previous username" pnacIfConfig: overwriting previous password"

%s: Failed to set port status

%s: Failed to notify event to dot11 pnacLibDeinit: Failed to destroy the phyPort:%s pnacPortPaeDeconfig:kpnacPortPaeDe config failed pnacPortPaeDeconfig:kpnacPortPaeDe config failed pnacBackAuthSuccess: failed to notify the destination " could not initialize MGMT framework umiInit failed iappInit failed could not initialize IAPP MGMT. dot11Malloc failed pnacPhyPortParamSet:Failed to add

802.1X multicast " pnacIsInterfaceUp: failed to create a raw socket pnacIsInterfaceUp: failed to get interface flags failed to allocate buffer

ERROR

ERROR

ERROR

ERROR

WARN

WARN

WARN

WARN

WARN

WARN

WARN

WARN

WARN

WARN

WARN

WARN

WARN

WARN

WARN

ERROR

ERROR

ERROR

ERROR

ERROR

UMI initialization failed ERROR

UMI initialization failed

Error from pnacEapDemoAuthLibInit: malloc failed

Error from pnacEapDemoAuthRecv: received null EAP pkt

Error from pnacEapDemoAuthRecv: send "

Error from pnacRadXlateASAdd: cannot open socket

Error from pnacRadXlateDemoRecv: received null EAP pkt

From pnacRadXlateDemoRecv: send

"

Error from pnacRadXlateDemoRecv:

RADIUS "

Error from pnacRadXlateDemoRecv:

RADIUS "

Error from pnacRadXlateRadIdRespSend: send to failed

Error from pnacRadXlateRadNonIdRespSend: send to failed

Error from pnacRadXlateRadRecvProc: recvfrom failed

From pnacRadXlateRadPktIntegrityChk: no corresponding "

Error from pnacRadXlateRadPktIntegrityChk: no message "

Error from pnacRadXlateRadPktIntegrityChk: "

From pnacRadXlateRadChalPktHandle: no encapsulated eap "

Error from pnacRadXlateRadChalPktHandle: malloc for eap "

Error from pnacEapDemoSuppUserInfoRegister: invalid "

Error from pnacEapDemoSuppRecv: received null EAP pkt

Error from pnacEapDemoSuppRecv: send ptr to pnac supplicant"

From pnacEapDemoSuppRecv: user info not entered yet

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

274

Unified Services Router

User Manual buffer length not specified

Invalid length(%d) specified

Failed to get information about authorized AP list.

Recd IE data for non-existent AP %s

Recd IE data for wrong AP %s

ERROR

ERROR

ERROR

Error from pnacEapDemoSuppRecv: couldn't "

MDString: adpDigestInit for md5 failed

ERROR

ERROR

ERROR pnacUmiInit: UMI initialization failed ERROR could not start PNAC task

ERROR invalid aruments

Received Invalid IE data from WSC

Recd IE data for non-existent AP %s

Recd WSC Start command without interface name

Recd WSC start for non-existent AP %s

Recd WSC start for wrong AP %s

Unable to send

WSC_WLAN_CMD_PORT to WSC

ERROR pnacIfNameToIndex failed

ERROR pnacPhyPortParamSet: device invalid

%s%d

ERROR pnacPhyPortParamSet: EIOCGADDR ioctl failed

ERROR

ERROR pnacPhyPortParamSet: multicast addr add ioctl failed pnacPhyPortParamUnset: multicast addr del ioctl failed

Failed to get the ap context for %s

WPS can only be applied to

WPA/WPA2 security profiles wpsEnable: running wsccmd failed

ERROR pnacPDUXmit: Invalid arguments pnacPDUXmit: failed to get

ERROR

ERROR

M_BLK_ID from pnacIsInterfaceUp: device

%s%d invalid

ERROR pnacRecvRtn: dropping received packet as port is"

Failed to get the ap context for %s

WPS conf. under non WPA/WPA2 security setting

Failed to reset the Beacon Frame IE in the driver

Failed to reset the Beacon Frame IE in the driver

WPS method cannot be NULL

PIN value length should be a multiple of

4 !!

Failed to initiate PIN based association,

PIN = %s

Failed to initiate PBC based enrolle association

Invalid association mode. (Allowed modes : PIN/PBC) wpsEnable: running wsccmd failed

Failed to send QUIT command to WSC from DOT11

Failed to clear off the WPS process missing profile name

A profile exists with the same name

ERROR pnacSendRtn: Invalid arguments pnacSendRtn: no physical port

ERROR corresponding to" pnacSendRtn: dropping packet as

ERROR

ERROR port" pnacAuthBuildRC4KeyDesc: adpEncryptInit(RC4) failed

ERROR

ERROR pnacAuthBuildRC4KeyDesc: adpCipherContextCtrl" pnacDot11UserSet: incorrect buffer length

ERROR PNAC user component id not set. pnacKeyInfoGet:failed to allocate

ERROR

ERROR

ERROR

ERROR buffer

PNAC user comp id not set. dropping

EAPOL key pkt pnacUmiPortPaeParamSet: invalid buffer received

Error from pnacRecvASInfoMessage:

"

ERROR pnacRecvASInfoMessage: " pnacRecvASInfoMessage: Bad info

ERROR length

ERROR Error from pnacLibInit: malloc failed

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

Error in allocating memory for profile missing profile name missing profile name

Profile name and interface name must be specified

Profile %s does not exist

ERROR could not create phy ports lock

ERROR could not create nodes ports lock

ERROR port exists for iface - %s

ERROR

ERROR pnacPhyPortCreate failed kpnacPhyPortCreate failed

ERROR

ERROR

ERROR

ERROR

ERROR

275

Unified Services Router

User Manual

Could not set profile %s on the interface

%s missing profile name

Profile %s does not exist

Profile %s does not exist

SSID should not be longer than %d

Profile %s does not exist

Profile %s does not exist

Profile %s does not exist

Profile %s does not exist

Profile %s does not exist

Profile %s does not exist

SSID not set. SSID is needed to generate password hash

Password string too big dot11Malloc failed

ERROR invalid argument

ERROR pnacAuthConfig: maxAuth limit reached

ERROR pnacAuthConfig: malloc failed

Error from pnacAuthConfig: pAsArg

ERROR cannot be NULL

Error from pnacAuthConfig: receive

ERROR routine hook "

ERROR pnacAuthConfig: pnacAuthInit failed

ERROR kpnacPortPaeConfig failed

ERROR Invalid arguments

ERROR

ERROR

ERROR

Error from pnacSuppConfig: malloc failed

Error from pnacSuppConfig: receive routine hook "

Error from pnacSuppConfig: pnacSuppInit failed

ERROR kpnacPortPaeConfig failed

ERROR pnacAuthDeconfig failed: pPortPae

NULL

ERROR

ERROR

Error from pnacPhyPortDestroy: port not configured pnacPhyPortDestroy: Failed to deconfigure port Profile %s does not exist

Hex string should only have %d hex chars dot11Malloc failed

Profile %s does not exist invalid key index %d. key index should be 0-3. wepKey length incorrect

Profile %s does not exist

Invalid Cipher type %d

Profile supports WEP stas,Group cipher must be WEP

Profile %s does not exist

Profile %s does not exist

Profile %s does not exist invalid pairwise cipher type %d

Cipher %s is already in the list.

Profile %s does not exist

Invalid Cipher type %d

Cipher %s not found in the list.

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR pnacPhyPortParamUnset FAILED

Error from pnacPhyPortCreate:

ERROR

ERROR malloc failed

Error from pnacPhyPortCreate: pnacPhyPortParamSet"

ERROR

ERROR

ERROR

ERROR

ERROR error from pnacPhyPortCreate: malloc failed

Error from pnacAuthInit: pnacPortTimersInit failed

Error from pnacAuthInit: pnacAuthPAEInit failed

Error from pnacAuthInit: pnacAuthKeyTxInit failed

Error from pnacAuthInit: pnacReauthTimerInit failed

ERROR

ERROR

ERROR

Error from pnacAuthInit: pnacBackAuthInit failed

Error from pnacAuthInit: pnacCtrlDirInit failed

Error from pnacAuthInit: pnacKeyRecvInit failed

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR Error from pnacSuppInit: malloc failed ERROR

Error from pnacSuppInit:

ERROR ERROR

ERROR pnacPortTimersInit failed

Error from pnacSuppInit: pnacKeyRecvInit failed ERROR

ERROR

ERROR

Error from pnacSuppInit: pnacSuppKeyTxInit failed

Error from pnacSuppInit: pnacSuppPAEInit failed

ERROR

ERROR

276

Unified Services Router

User Manual

Profile %s does not exist

Profile %s does not exist

Auth method %s is already in the list

Profile %s does not exist

Auth method %s not found in the list.

Profile %s does not exist

Profile %s does not exist

Profile %s does not exist invalid type value %d. supported values are 1,2,3,4

Profile %s does not exist invalid type value %d. supported values are 1,2,3,4

Profile %s does not exist invalid type value %d. supported values are 1,2,3,4

Profile %s does not exist invalid type value %d. supported values are 1,2,3,4

ERROR

ERROR

Error from pnacRecvRtn: invalid arguments

Error from pnacRecvMapi: unsupported PDU received

ERROR

ERROR

ERROR suppToACSendRtn returned not OK! ERROR

Error from pnacBasicPktCreate:

ERROR malloc failed

Error from pnacEAPPktCreate: basic

ERROR

ERROR

ERROR pkt create failed

Error from pnacTxCannedFail: eap pkt create failed

ERROR

ERROR

ERROR

Error from pnacTxCannedSuccess: eap pkt create failed ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

Error from pnacTxReqId: eap pkt create failed

Error from pnacTxReq: eap pkt create failed

Error from pnacSendRespToServer: malloc failed

Error from pnacSendRespToServer: no AS configured

Error from pnacTxStart: basic pkt create failed

Error from pnacTxStart: basic pkt create failed

Error from pnacTxRspId: eap pkt create failed

Error from pnacTxRspAuth: eap pkt create failed

Error from pnacEapPktRecord: EAP packet too"

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR Profile %s does not exist invalid type value %d. supported values are 1,2,3,4

Profile %s does not exist

ERROR: incomplete DB update information. old values result does not contain 2 rows

ERROR Error from pnacEapPktRecord: "

ERROR from pnacBackAuthTimeout: calling pnacTxCannedFail

ERROR hmac_md5: adpHmacContextCreate failed sqlite3QueryResGet failed

Error in executing DB update handler sqlite3QueryResGet failed

ERROR: incomplete DB update information. old values result does not contain 2 rows

ERROR hmac_md5:adpHmacInit failed pnacUmiIoctlHandler: invalid cmd:

ERROR

ERROR

%d pnacEapRadAuthSend: Invalid arguments

ERROR pnacEapRadAuthSend: failed to allocate inbuffer

ERROR pnacXmit : umiIoctl failed[%d]

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR sqlite3QueryResGet failed

Error in executing DB update handler sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s

ERROR pnacPDUForward: Invalid input pnacPDUForward: error in getting

ERROR

ERROR port pae information pnacPDUForward: error allocating memory

ERROR

ERROR

ERROR pnacUmiIfMacAddrChange: %s not configured for 802.1x pnacUmiIfMacAddrChange: could not process PDU received" pnacUmiPhyPortConfig: Invalid config data

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

277

Unified Services Router

User Manual sqlite3QueryResGet failed.Query:%s ERROR pnacUmiPhyPortConfig: Invalid backend name specified startStopVap failed to stop %s ERROR

Invalid SQLITE operation code - %d ERROR

./src/dot11/mgmt/dot11Mgmt.c:1177:

ADP_ERROR ( only delete event expected on

ERROR dot11RogueAP. sqlite3QueryResGet failed unhandled database operation %d pnacUmiPhyPortConfig: could not create PNAC physical" pnacUmiAuthConfig: Invalid config data pnacUmiAuthConfig: Invalid backend name specified

ERROR unable to create new EAP context. unable to apply %s profile on the EAP

ERROR

ERROR context. pnacUmiAuthConfig: could not configure PNAC PAE " sqlite3QueryResGet failed failed to configure WPS on %s sqlite3QueryResGet failed sqlite3QueryResGet failed sqlite3QueryResGet failed sqlite3QueryResGet failed sqlite3QueryResGet failed

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR pnacUmiSuppConfig: Invalid config data pnacUmiSuppConfig: Invalid backend name specified pnacUmiSuppConfig: %s not configured for 802.1x pnacUmiSuppConfig: could not

PNAC port Access" pnacUmiSuppConfig: Failed to register user information pnacPortByMacDeconfig: port not found pnacPortByMacDeconfig: port not found

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR pnacUmiIfDown: Invalid config data ERROR no VAP rows returned. expected one multiple VAP rows returned. expected one sqlite3QueryResGet failed invalid query result. ncols=%d nrows=%d

%s:VAP(%s) create failed sqlite3QueryResGet failed invalid query result. ncols=%d nrows=%d

ERROR pnacUmiIfDown: Invalid config data ERROR

ERROR

Error from pnacPortDeconfig: port not configured ERROR

ERROR pnacUmiIfDown: could not deconfigure port ERROR

ERROR

ERROR

ERROR pnacUmiPhyPortDestroy: Invalid config data pnacUmiPhyPortDestroy: Invalid config data pnacUmiPhyPortDestroy: Failed to destroy the port

ERROR

ERROR

ERROR

Invalid config data ERROR

Facility: Kernel

Log Message

DNAT: multiple ranges no longer supported

DNAT: Target size %u wrong for %u ranges,

DNAT: wrong table %s, tablename

DNAT: hook mask 0x%x bad, hook_mask

%s%d: resetting MPPC/MPPE compressor,

Severity Log Message

DEBUG %s: %s%s:%d -> %s:%d %s,

DEBUG %s: %s%s:%d %s,

%s: Failed to add WDS MAC: %s,

DEBUG dev->name,

%s: Device already has WDS mac

DEBUG

DEBUG address attached,

%s: Added WDS MAC: %s, dev-

>name,

Severity

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

278

Unified Services Router

User Manual

%s%d: wrong offset value: %d,

%s%d: wrong length of match value:

%d,

%s%d: too big offset value: %d,

%s%d: cannot decode offset value,

%s%d: wrong length code: 0x%X,

%s%d: short packet (len=%d),

__FUNCTION__,

%s%d: bad sequence number: %d, expected: %d,

%s%d: bad sequence number: %d, expected: %d,

PPPIOCDETACH file->f_count=%d,

PPP: outbound frame not passed

PPP: VJ decompression error

PPP: inbound frame not passed

PPP: reconstructed packet

PPP: no memory for

missed pkts %u..%u,

%s%d: resetting MPPC/MPPE compressor,

%s%d: wrong offset value: %d,

%s%d: wrong length of match value:

%d,

%s%d: too big offset value: %d,

%s%d: cannot decode offset value,

%s%d: wrong length code: 0x%X,

%s%d: short packet (len=%d),

__FUNCTION__,

%s%d: bad sequence number: %d, expected: %d,

%s%d: bad sequence number: %d, expected: %d,

PPPIOCDETACH file->f_count=%d,

PPP: outbound frame not passed

PPP: VJ decompression error

PPP: inbound frame not passed

PPP: reconstructed packet

PPP: no memory for

missed pkts %u..%u,

%s: INC_USE_COUNT, now %d,

__FUNCTION__, mod_use_count \

%s: DEC_USE_COUNT, now %d,

__FUNCTION__, mod_use_count \

PPPOL2TP %s: _fmt,

DEBUG

DEBUG

%s: WDS MAC address %s is not known by this interface,

[madwifi] %s() : Not enough space.,

__FUNCTION__

DEBUG Returning to chan %d, ieeeChan

DEBUG WEP

DEBUG AES

DEBUG AES_CCM

DEBUG CKIP

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG TKIP DEBUG

DEBUG

%s: cannot map channel to mode; freq %u flags 0x%x,

DEBUG %s: %s, vap->iv_dev->name, buf

DEBUG %s: [%s] %s, vap->iv_dev->name,

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

%s: [%s] %s, vap->iv_dev->name, ether_sprintf(mac), buf

[%s:%s] discard %s frame, %s, vap-

>iv_dev->name,

[%s:%s] discard frame, %s, vap-

>iv_dev->name,

[%s:%s] discard %s information element, %s,

[%s:%s] discard information element,

%s,

[%s:%s] discard %s frame, %s, vap-

>iv_dev->name,

[%s:%s] discard frame, %s, vap-

>iv_dev->name,

DEBUG ifmedia_add: null ifm

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG Adding entry for DEBUG

DEBUG ifmedia_set: no match for 0x%x/0x%x, DEBUG

DEBUG DEBUG ifmedia_set: target

DEBUG ifmedia_set: setting to

DEBUG ifmedia_ioctl: no media found for

0x%x,

DEBUG ifmedia_ioctl: switching %s to , dev-

>name

DEBUG ifmedia_match: multiple match for

DEBUG <unknown type>

DEBUG desc->ifmt_string

DEBUG mode %s, desc->ifmt_string

DEBUG <unknown subtype>

DEBUG %s, desc->ifmt_string

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG %s%s, seen_option++ ? , : ,

DEBUG %s%s, seen_option++ ? , : ,

DEBUG %s, seen_option ? > :

DEBUG

DEBUG

DEBUG

279

Unified Services Router

User Manual

PPPOL2TP: --> %s, __FUNCTION__) DEBUG %s: %s, dev->name, buf

PPPOL2TP: <-- %s, __FUNCTION__) DEBUG

%s: no memory for sysctl table!,

__func__

%s: recv: , tunnel->name

%s: xmit:, session->name

%s: xmit:, session->name

DEBUG

DEBUG

DEBUG

%s: no memory for VAP name!,

__func__

%s: failed to register sysctls!, vap-

>iv_dev->name

%s: no memory for new proc entry

(%s)!, __func__,

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

%s: module use_count is %d,

__FUNCTION__, mod_use_count

PPPOL2TP %s: _fmt,

PPPOL2TP: --> %s, __FUNCTION__) DEBUG %02x, ((u_int8_t *)p)[i]

PPPOL2TP: <-- %s, __FUNCTION__) DEBUG first difference at byte %u, i

%s: recv: , tunnel->name

DEBUG %s: 0x%p len %u, tag, p, len

DEBUG %03d:, i

%s: xmit:, session->name

%s: xmit:, session->name

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG %s: , t->name

FAIL: ieee80211_crypto_newkey

DEBUG failed

DEBUG

DEBUG

DEBUG FAIL: ieee80211_crypto_setkey failed DEBUG

PPPOL2TP %s: _fmt, DEBUG FAIL: unable to allocate skbuff

PPPOL2TP: --> %s, __FUNCTION__) DEBUG FAIL: wep decap failed

PPPOL2TP: <-- %s, __FUNCTION__) DEBUG FAIL: decap botch; length mismatch

%s: recv: , tunnel->name DEBUG

FAIL: decap botch; data does not compare

%s: xmit:, session->name

%s: xmit:, session->name

IRQ 31 is triggered

DEBUG

DEBUG FAIL: wep encap failed

DEBUG FAIL: encap data length mismatch

DEBUG

DEBUG

DEBUG

DEBUG FAIL: encrypt data does not compare DEBUG

[%s:%d] , __func__, __LINE__\

\t[R%s %#0x %#0x 0x%08x%08x],

(status == ERROR ? # : ), page, addr,

(uint32_t)(*pValue >> 32),

(uint32_t)(*pValue & 0xffffffff)

\t[W%s %#0x %#0x 0x%08x%08x],

(status == ERROR ? # : ), page, addr,

(uint32_t)(value >> 32),

(uint32_t)(value & 0xffffffff)

%s: mac_add

%02X:%02X:%02X:%02X:%02X:%02X

, dev->name, addr[0], addr[1], addr[2], addr[3], addr[4], addr[5]

%s: mac_del

%02X:%02X:%02X:%02X:%02X:%02X

, dev->name, addr[0], addr[1], addr[2], addr[3], addr[4], addr[5]

%s: mac_kick

%02X:%02X:%02X:%02X:%02X:%02X

, dev->name, addr[0], addr[1], addr[2], addr[3], addr[4], addr[5]

%s: mac_undefined

%02X:%02X:%02X:%02X:%02X:%02X

, dev->name, addr[0], addr[1], addr[2], addr[3], addr[4], addr[5]

%s: addr_add

%02X:%02X:%02X:%02X:%02X:%02X

, dev->name, addr[0], addr[1], addr[2], addr[3], addr[4], addr[5]

DEBUG PASS

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

%u of %u 802.11i WEP test vectors passed, pass, total

%s: 0x%p len %u, tag, p, len

%03d:, i

%02x, ((u_int8_t *)p)[i] first difference at byte %u, i

%s: , t->name

FAIL: ieee80211_crypto_newkey failed

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

280

Unified Services Router

User Manual

%s: addr_del

%02X:%02X:%02X:%02X:%02X:%02X

, dev->name, addr[0], addr[1], addr[2], addr[3], addr[4], addr[5]

%s: mac_undefined

%02X:%02X:%02X:%02X:%02X:%02X

, dev->name, addr[0], addr[1], addr[2], addr[3], addr[4], addr[5]

%s: set_float %d;%d,

IRQ 32 is triggered ip_finish_output2: No header cache and no neighbour! a guy asks for address mask. Who is it? icmp v4 hw csum failure)

DEBUG FAIL: ieee80211_crypto_setkey failed DEBUG

DEBUG FAIL: unable to allocate skbuff

DEBUG FAIL: ccmp encap failed

DEBUG FAIL: encap data length mismatch

DEBUG

DEBUG

DEBUG

DEBUG FAIL: encrypt data does not compare DEBUG

DEBUG

DEBUG

DEBUG FAIL: ccmp decap failed

DEBUG FAIL: decap botch; length mismatch

DEBUG

FAIL: decap botch; data does not compare

DEBUG PASS

DEBUG

%u of %u 802.11i AES-CCMP test vectors passed, pass, total

DEBUG

DEBUG

DEBUG expire>> %u %d %d %d, expire, expire++ %u %d %d %d, expire, rt_cache @%02x: %u.%u.%u.%u, hash, rt_bind_peer(0) @%p,

NET_CALLER(iph) ip_rt_advice: redirect to ip_rt_bug: %u.%u.%u.%u ->

%u.%u.%u.%u, %s, udp cork app bug 2) udp cork app bug 3) udp v4 hw csum failure.)

UDP: short packet: From

%u.%u.%u.%u:%u %d/%d to

%u.%u.%u.%u:%u,

UDP: bad checksum. From

%d.%d.%d.%d:%d to

%d.%d.%d.%d:%d ulen %d,

%s: lookup policy [list] found=%s,

%s: called: [output START],

__FUNCTION__

%s: flow dst=%s, __FUNCTION__,

XFRMSTRADDR(fl->fl4_dst, family)

%s: flow src=%s, __FUNCTION__,

XFRMSTRADDR(fl->fl4_src, family)

%s: flow dst=%s, __FUNCTION__,

XFRMSTRADDR(fl->fl6_dst, family)

%s: flow src=%s, __FUNCTION__,

XFRMSTRADDR(fl->fl6_src, family) a guy asks for address mask. Who is it? icmp v4 hw csum failure) expire>> %u %d %d %d, expire, expire++ %u %d %d %d, expire, rt_cache @%02x: %u.%u.%u.%u, hash, rt_bind_peer(0) @%p,

NET_CALLER(iph)

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

%s: 0x%p len %u, tag, p, len

%03d:, i

%02x, ((u_int8_t *)p)[i] first difference at byte %u, i ieee80211_crypto_newkey failed ieee80211_crypto_setkey failed unable to allocate skbuff tkip enmic failed enmic botch; length mismatch enmic botch tkip encap failed encrypt phase1 botch encrypt data length mismatch encrypt data does not compare tkip decap failed decrypt phase1 botch decrypt data does not compare decap botch; length mismatch decap botch; data does not compare tkip demic failed

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

281

Unified Services Router

User Manual ip_rt_advice: redirect to ip_rt_bug: %u.%u.%u.%u ->

%u.%u.%u.%u, %s,

UDP: short packet: From

%u.%u.%u.%u:%u %d/%d to

%u.%u.%u.%u:%u,

UDP: bad checksum. From

%d.%d.%d.%d:%d to

%d.%d.%d.%d:%d ulen %d, a guy asks for address mask. Who is it? fib_add_ifaddr: bug: prim == NULL fib_del_ifaddr: bug: prim == NULL expire>> %u %d %d %d, expire, expire++ %u %d %d %d, expire, rt_cache @%02x: %u.%u.%u.%u, hash, rt_bind_peer(0) @%p, ip_rt_advice: redirect to ip_rt_bug: %u.%u.%u.%u ->

%u.%u.%u.%u, %s,

%s: lookup policy [list] found=%s,

%s: called: [output START],

__FUNCTION__

%s: flow dst=%s, __FUNCTION__,

XFRMSTRADDR(fl->fl4_dst, family)

%s: flow src=%s, __FUNCTION__,

XFRMSTRADDR(fl->fl4_src, family)

%s: flow dst=%s, __FUNCTION__,

XFRMSTRADDR(fl->fl6_dst, family)

%s: flow src=%s, __FUNCTION__,

XFRMSTRADDR(fl->fl6_src, family) a guy asks for address mask. Who is it? icmp v4 hw csum failure) expire>> %u %d %d %d, expire, expire++ %u %d %d %d, expire, rt_cache @%02x: %u.%u.%u.%u, hash, rt_bind_peer(0) @%p,

NET_CALLER(iph) ip_rt_advice: redirect to ip_rt_bug: %u.%u.%u.%u ->

%u.%u.%u.%u, %s,

UDP: short packet: From

%u.%u.%u.%u:%u %d/%d to

%u.%u.%u.%u:%u,

UDP: bad checksum. From

%d.%d.%d.%d:%d to

%d.%d.%d.%d:%d ulen %d,

REJECT: ECHOREPLY no longer supported.

DEBUG

DEBUG

802.11i TKIP test vectors passed

%s, buf

DEBUG

Atheros HAL assertion failure: %s: line %u: %s,

DEBUG ath_hal: logging to %s %s, ath_hal_logfile,

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG ath_hal: logging disabled

DEBUG %s%s, sep, ath_hal_buildopts[i]

DEBUG ath_pci: No devices found, driver not installed.

DEBUG _fmt, __VA_ARGS__

DEBUG

%s: Warning, using only %u entries in

%u key cache,

DEBUG

DEBUG

%s: TX99 support enabled, dev-

>name

%s:grppoll Buf allocation failed

,__func__

DEBUG %s: %s: unable to start recv logic,

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG %s: %s: unable to start recv logic,

DEBUG %s: no skbuff, __func__

DEBUG

%s: hardware error; resetting, dev-

>name

DEBUG

DEBUG

DEBUG

%s: rx FIFO overrun; resetting, dev-

>name

%s: unable to reset hardware: '%s'

(HAL status %u)

%s: unable to start recv logic, dev-

>name

DEBUG

%s: %s: unable to reset hardware:

'%s' (HAL status %u),

DEBUG %s: %s: unable to start recv logic,

DEBUG ath_mgtstart: discard, no xmit buf

%s: [%02u] %-7s , tag, ix, ciphers[hk-

DEBUG >kv_type]

DEBUG %02x, hk->kv_val[i]

DEBUG mac %s, ether_sprintf(mac)

DEBUG %s , sc->sc_splitmic ? mic : rxmic

DEBUG %02x, hk->kv_mic[i]

DEBUG txmic

DEBUG %02x, hk->kv_txmic[i]

DEBUG

DEBUG

%s: unable to update h/w beacon queue parameters,

%s: stuck beacon; resetting (bmiss count %u),

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

282

Unified Services Router

User Manual ipt_rpc: only valid for PRE_ROUTING,

FORWARD, POST_ROUTING,

LOCAL_IN and/or LOCAL_OUT targets. ip_nat_init: can't setup rules.

DEBUG move data from NORMAL to XR

DEBUG moved %d buffers from NORMAL to

XR, index

DEBUG

DEBUG ip_nat_init: can't register in hook. ip_nat_init: can't register out hook. ip_nat_init: can't register adjust in hook. ip_nat_init: can't register adjust out hook. ip_nat_init: can't register local out hook. ip_nat_init: can't register local in hook. ipt_hook: happy cracking. ip_conntrack: can't register pre-routing defrag hook. ip_conntrack: can't register local_out defrag hook. ip_conntrack: can't register pre-routing hook. ip_conntrack: can't register local out hook.

DEBUG move buffers from XR to NORMAL moved %d buffers from XR to

DEBUG NORMAL, count

%s:%d %s, __FILE__, __LINE__,

DEBUG

DEBUG

DEBUG

__func__

%s:%d %s, __FILE__, __LINE__,

__func__

%s: no buffer (%s), dev->name,

__func__

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

%s: no skbuff (%s), dev->name,

__func__

%s: HAL qnum %u out of range, max

%u!, grppoll_start: grppoll Buf allocation failed

%s: HAL qnum %u out of range, max

%u!,

%s: AC %u out of range, max %u!,

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG %s: unable to update hardware queue DEBUG

DEBUG

%s: bogus frame type 0x%x (%s), dev->name, DEBUG ip_conntrack: can't register local in helper hook. ip_conntrack: can't register postrouting helper hook. ip_conntrack: can't register postrouting hook. ip_conntrack: can't register local in hook.

DEBUG

DEBUG

DEBUG ath_stoprecv: rx queue 0x%x, link %p,

%s: %s: unable to reset channel %u

(%u MHz)

%s: %s: unable to restart recv logic,

DEBUG

DEBUG

DEBUG ip_conntrack: can't register to sysctl. ip_conntrack_rtsp v

IP_NF_RTSP_VERSION loading ip_conntrack_rtsp: max_outstanding must be a positive integer ip_conntrack_rtsp: setup_timeout must be a positive integer

DEBUG

DEBUG

DEBUG

DEBUG

%s: unable to allocate channel table, dev->name

%s: unable to allocate channel table, dev->name

%s: unable to collect channel list from

HAL;

R (%p %llx) %08x %08x %08x %08x

%08x %08x %c,

DEBUG

DEBUG

DEBUG

DEBUG ip_conntrack_rtsp: ERROR registering port %d, ports[i] ip_nat_rtsp v IP_NF_RTSP_VERSION loading

%s: Sorry! Cannot find this match option., __FILE__ ipt_time loading ipt_time unloaded ip_conntrack_irc: max_dcc_channels must be a positive integer ip_conntrack_irc: ERROR registering port %d,

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

T (%p %llx) %08x %08x %08x %08x

%08x %08x %08x %08x %c,

%s: no memory for sysctl table!,

__func__

%s: no memory for device name storage!, __func__

%s: failed to register sysctls!, sc-

>sc_dev->name

%s: mac %d.%d phy %d.%d, dev-

>name,

5 GHz radio %d.%d 2 GHz radio

%d.%d,

radio %d.%d, ah-

>ah_analog5GhzRev >> 4,

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

283

Unified Services Router

User Manual ip_nat_h323: ip_nat_mangle_tcp_packet ip_nat_h323: ip_nat_mangle_udp_packet

DEBUG

radio %d.%d, ah-

>ah_analog5GhzRev >> 4, ip_nat_h323: out of expectations ip_nat_h323: out of RTP ports ip_nat_h323: out of TCP ports ip_nat_q931: out of TCP ports

DEBUG %s: Use hw queue %u for %s traffic,

%s: Use hw queue %u for CAB traffic,

DEBUG dev->name,

%s: Use hw queue %u for beacons,

DEBUG

DEBUG dev->name,

Could not find Board Configuration

Data

Could not find Radio Configuration

DEBUG

DEBUG data ath_ahb: No devices found, driver not installed. ip_nat_ras: out of TCP ports ip_nat_q931: out of TCP ports DEBUG _fmt, __VA_ARGS__ ip_conntrack_core: Frag of proto %u., DEBUG _fmt, __VA_ARGS__ xlr8NatIpFinishOutput: Err.. skb2 ==

Broadcast packet! DEBUG NULL !

Should bcast: %u.%u.%u.%u-

>%u.%u.%u.%u (sk=%p, ptype=%u), ip_conntrack version %s (%u buckets,

%d max)

DEBUG

DEBUG xlr8NatSoftCtxEnqueue: Calling xlr8NatIpFinishOutput () .., status xlr8NatSoftCtxEnqueue: xlr8NatIpFinishOutput () returned

[%d], status

DEBUG icmpExceptionHandler: Exception! ERROR registering port %d, netfilter PSD loaded - (c) astaro AG

%s , WAN

DEBUG fragExceptionHandler: Exception! netfilter PSD unloaded - (c) astaro AG DEBUG algExceptionHandler: Exception!

%s , SELF DEBUG dnsExceptionHandler: Exception!

%s , LAN DEBUG IPsecExceptionHandler: Exception!

DEBUG

ESP Packet Src:%x Dest:%x

Sport:%d dport:%d secure:%d spi:%d isr:%p,

TRUNCATED

SRC=%u.%u.%u.%u

DST=%u.%u.%u.%u ,

LEN=%u TOS=0x%02X

PREC=0x%02X TTL=%u ID=%u ,

FRAG:%u , ntohs(ih->frag_off) &

IP_OFFSET

TRUNCATED

PROTO=TCP

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG xlr8NatConntrackPreHook: We found the valid context, xlr8NatConntrackPreHook: Not a secured packet. xlr8NatConntrackPreHook: isr=[%p], pIsr xlr8NatConntrackPreHook: secure=[%d], secure

Context found for ESP

%p,pFlowEntry->post.pIsr[0] xlr8NatConntrackPreHook: New connection.

INCOMPLETE [%u bytes] ,

SPT=%u DPT=%u ,

SEQ=%u ACK=%u ,

DEBUG

DEBUG xlr8NatConntrackPostHook: postSecure=[%d] postIsr=[%p %p],

DEBUG proto %d spi %d <-------> proto %d spi

%d,pPktInfo->proto,pPktInfo->spi,

DEBUG IPSEC_INF Clock skew detected

IPSEC_ERR [%s:%d]: Max (%d) No of SA Limit reached, WINDOW=%u , ntohs(th->window)

RES=0x%02x ,

(u8)(ntohl(tcp_flag_word(th) &

TCP_RESERVED_BITS) >> 22)

URGP=%u , ntohs(th->urg_ptr)

DEBUG

IPSEC_ERR [%s:%d]: Max (%d) No of SA Limit reached,

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG IPSEC_ERR [%s:%d]: time(secs): %u DEBUG

284

Unified Services Router

User Manual

TRUNCATED

%02X, op[i]

PROTO=UDP

INCOMPLETE [%u bytes] ,

SPT=%u DPT=%u LEN=%u ,

SPT=%u DPT=%u LEN=%u ,

PROTO=ICMP

INCOMPLETE [%u bytes] ,

TYPE=%u CODE=%u , ich->type, ich-

>code

INCOMPLETE [%u bytes] ,

ID=%u SEQ=%u ,

PARAMETER=%u ,

GATEWAY=%u.%u.%u.%u ,

MTU=%u , ntohs(ich->un.frag.mtu)

PROTO=AH

INCOMPLETE [%u bytes] ,

SPI=0x%x , ntohl(ah->spi)

PROTO=ESP

INCOMPLETE [%u bytes] ,

SPI=0x%x , ntohl(eh->spi)

PROTO=%u , ih->protocol

UID=%u , skb->sk->sk_socket->file-

>f_uid

<%d>%sIN=%s OUT=%s , loginfo-

>u.log.level, level_string

%sIN=%s OUT=%s ,

%s , prefix == NULL ? loginfo->prefix : prefix

IN=

OUT=

PHYSIN=%s , physindev->name

PHYSOUT=%s , physoutdev->name

MAC=

%02x%c, *p,

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

ERROR: Failed to add entry to IPsec sa table

ERROR: Failed to add entry to IPsec sa table

ERROR: Failed to add entry to IPsec sa table

ERROR: Failed to add entry to IPsec sa table

ERROR: Failed to add entry to IPsec sa table

ERROR: Failed to add entry to IPsec sa table DEBUG

DEBUG unknown oid '%s', varName

DEBUG could not find oid pointer for '%s', varName

DEBUG unRegistering IPsecMib .....

ERROR: Failed to add entry to IPsec

DEBUG sa table

ERROR: Failed to add entry to IPsec

DEBUG

DEBUG sa table

ERROR: Failed to add entry to IPsec sa table

DEBUG

DEBUG

DEBUG

ERROR: Failed to add entry to IPsec sa table

ERROR: Failed to add entry to IPsec sa table

ERROR: Failed to add entry to IPsec sa table

DEBUG unknown oid '%s', varName

DEBUG could not find oid pointer for '%s', varName

DEBUG unRegistering IPsecMib .....

DEBUG

. %u.%u.%u.%u, NIPQUAD(trt-

>rt_dst)

DEBUG %02x, *p

. %u.%u.%u.%u, NIPQUAD(trt-

DEBUG >rt_dst)

DEBUG %02x, *p

DEBUG

. %u.%u.%u.%u, NIPQUAD(trt-

>rt_dst)

DEBUG %02x, *p

. %u.%u.%u.%u, NIPQUAD(trt-

DEBUG >rt_dst)

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG %02x, *p

unable to register vIPsec kernel comp

DEBUG to UMI

DEBUG unregistering VIPSECK from UMI ....

DEBUG

DEBUG

DEBUG

DEBUG in vIPsecKIoctlHandler cmd - %d, cmd DEBUG

DEBUG

%s: Error. DST Refcount value less than 1 (%d), DEBUG

DEBUG

for %s DEVICE refcnt: %d ,pDst-

>dev->name, DEBUG

DEBUG

%s: Got Null m:%p *m:%p sa:%p

*sa:%p,__func__,ppBufMgr, DEBUG

285

Unified Services Router

User Manual

NAT: no longer support implicit source local NAT

NAT: packet src %u.%u.%u.%u -> dst

%u.%u.%u.%u,

SNAT: multiple ranges no longer supported format,##args) version offset_before=%d, offset_after=%d, correction_pos=%u, x->offset_before, x->offset_after, x->correction_pos ip_ct_h323: ip_ct_h323: incomplete TPKT

(fragmented?) ip_ct_h245: decoding error: %s, ip_ct_h245: packet dropped ip_ct_q931: decoding error: %s, ip_ct_q931: packet dropped ip_ct_ras: decoding error: %s, ip_ct_ras: packet dropped

ERROR registering port %d,

ERROR registering port %d, ipt_connlimit [%d]: src=%u.%u.%u.%u:%d dst=%u.%u.%u.%u:%d %s, ipt_connlimit [%d]: src=%u.%u.%u.%u:%d dst=%u.%u.%u.%u:%d new, ipt_connlimit: Oops: invalid ct state ? ipt_connlimit: Hmm, kmalloc failed :-( ipt_connlimit: src=%u.%u.%u.%u mask=%u.%u.%u.%u

_lvl PPPOL2TP: _fmt, ##args

%02X, ptr[length]

%02X, ((unsigned char *) m-

>msg_iov[i].iov_base)[j]

%02X, skb->data[i]

_lvl PPPOL2TP: _fmt, ##args

%02X, ptr[length]

%02X, ((unsigned char *) m-

>msg_iov[i].iov_base)[j]

DEBUG

DEBUG

DEBUG

%s Got Deleted SA:%p state:%d,__func__,pIPsecInfo,pIPsecI nfo->state

%s: %s: fmt, __FILE__,

__FUNCTION__ , ## args)

%s: %s: fmt, __FILE__,

__FUNCTION__ , ## args)

DEBUG ipt_TIME: format, ## args)

DEBUG

IPT_ACCOUNT_NAME : checkentry() wrong parameters (not equals existing table parameters).

DEBUG

INFO

INFO

INFO

INFO

DEBUG

DEBUG

DEBUG

DEBUG

IPT_ACCOUNT_NAME : checkentry() too big netmask.

IPT_ACCOUNT_NAME : checkentry() failed to allocate %zu for new table

%s., sizeof(struct t_ipt_account_table), info->name

IPT_ACCOUNT_NAME : checkentry() wrong network/netmask. account: Wrong netmask given by netmask parameter (%i). Valid is 32 to

0., netmask

IPT_ACCOUNT_NAME : checkentry() failed to create procfs entry. DEBUG

DEBUG

IPT_ACCOUNT_NAME : checkentry() failed to register match.

DEBUG failed to create procfs entry .

DEBUG

DEBUG

DEBUG

DEBUG

MPPE/MPPC encryption/compression module registered

MPPE/MPPC encryption/compression module unregistered

PPP generic driver version

PPP_VERSION

MPPE/MPPC encryption/compression module registered

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

DEBUG

DEBUG

DEBUG

MPPE/MPPC encryption/compression module unregistered

PPP generic driver version

PPP_VERSION

DEBUG PPPoL2TP kernel driver, %s,

DEBUG

DEBUG

PPPoL2TP kernel driver, %s,

PPPoL2TP kernel driver, %s,

DEBUG failed to create procfs entry .

DEBUG proc dir not created ..

DEBUG Initialzing Product Data modules

DEBUG De initializing by \

DEBUG kernel UMI module loaded

DEBUG kernel UMI module unloaded

Loading bridge module

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

286

Unified Services Router

User Manual

%02X, skb->data[i]

_lvl PPPOL2TP: _fmt, ##args

%02X, ptr[length]

%02X, ((unsigned char *) m-

>msg_iov[i].iov_base)[j]

DEBUG

DEBUG

DEBUG

Unloading bridge module unsupported command %d, cmd

Loading ifDev module

DEBUG Unloading ifDev module

ERROR#%d in alloc_chrdev_region,

DEBUG result %02X, skb->data[i]

KERN_EMERG THE value read is

%d,value*/

KERN_EMERG Factory Reset button is pressed

DEBUG ERROR#%d in cdev_add, result

DEBUG using bcm switch %s, bcmswitch

KERN_EMERG Returing error in INTR registration

KERN_EMERG Initialzing Factory defaults modules

Failed to allocate memory for pSipListNode

SIPALG: Memeory allocation failed for pSipNodeEntryTbl pkt-err %s, pktInfo.error

DEBUG

DEBUG

DEBUG privlegedID %d wanporttNo: %d, privlegedID,wanportNo

Loading mii

Unloading mii

DEBUG %s: Version 0.1

DEBUG %s: driver unloaded, dev_info

DEBUG wlan: %s backend registered, be-

>iab_name pkt-err %s, pktInfo.error pkt-err %s, pktInfo.error

%s Len=%d, msg, len

%02x , ((uint8_t *) ptr)[i]

End

CVM_MOD_EXP_BASE MISMATCH cmd=%x base=%x, cmd,

DEBUG wlan: %s backend unregistered, wlan: %s acl policy registered, iac-

DEBUG >iac_name wlan: %s acl policy unregistered, iac-

DEBUG >iac_name

DEBUG %s, tmpbuf op->sizeofptr = %ld, op->sizeofptr opcode cmd = %x, cmd modexp opcode received

Memory Allocation failed

DEBUG VLAN2

DEBUG

DEBUG

DEBUG

VLAN3

VLAN4 <%d %d>,

%s: %s, dev_info, version modexpcrt opcode received kmalloc failed kmalloc failed

DEBUG %s: driver unloaded, dev_info

DEBUG %s, buf

DEBUG %s: %s (, dev_info, ath_hal_version

DEBUG %s: driver unloaded, dev_info

DEBUG

%s: %s: mem=0x%lx, irq=%d hw_base=0x%p, kmalloc failed kmalloc failed kmalloc Failed kmalloc failed unknown cyrpto ioctl cmd received %x, cmd register_chrdev returned ZERO

DEBUG %s: %s, dev_info, version

DEBUG

DEBUG

%s: driver unloaded, dev_info

%s: %s: mem=0x%lx, irq=%d,

DEBUG %s: %s: mem=0x%lx, irq=%d,

DEBUG %s: %s, dev_info, version const char *descr, krb5_keyblock *k) { DEBUG %s: driver unloaded, dev_info

F password, &pdata DEBUG %s, buf

test key, key

pre-hashed key, key

DEBUG %s: %s (, dev_info, ath_hal_version

DEBUG %s: driver unloaded, dev_info const char *descr, krb5_keyblock *k) { DEBUG %s: driver unloaded, dev_info

AES 128-bit key, &key DEBUG %s: Version 2.0.0 const char *descr, krb5_keyblock *k) { DEBUG %s: driver unloaded, dev_info

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

287

Unified Services Router

User Manual

test key, key

pre-hashed key, key

DEBUG %s: driver unloaded, dev_info

DEBUG wlan: %s backend registered, be-

>iab_name const char *descr, krb5_keyblock *k) { DEBUG wlan: %s backend unregistered, wlan: %s acl policy registered, iac-

128-bit AES key,&dk DEBUG >iac_name wlan: %s acl policy unregistered, iac-

256-bit AES key, &dk DEBUG >iac_name

DEBUG %s: %s, dev_info, version WARNING: bwMonMultipathNxtHopSelect:: checking rates hop :%d dev:%s usableBwLimit = %d currBwShare = %d lastHopSelected =

%d weightedHopPrefer = %d ,

DEBUG

DEBUG

%s: driver unloaded, dev_info

%s: %s (, dev_info, ath_hal_version

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

1. selecting hop: %d lastHopSelected =

%d , selHop, lastHopSelected

4. hop :%d dev:%s usableBwLimit =

%d currBwShare = %d lastHopSelected = %d weightedHopPrefer = %d ,

2. selecting hop: %d lastHopSelected =

%d , selHop, lastHopSelected DEBUG %s: %s, dev_info, version INFO

3. selecting hop: %d lastHopSelected =

%d , selHop, lastHopSelected DEBUG %s: driver unloaded, dev_info INFO bwMonitor multipath selection enabled DEBUG ath_pci: switching rfkill capability %s, INFO bwMonitor multipath selection disabled DEBUG Unknown autocreate mode: %s, weightedHopPrefer set to %d

,weightedHopPrefer DEBUG %s: %s: mem=0x%lx, irq=%d, bwMonitor sysctl registration failed bwMonitor sysctl registered bwMonitor sysctl not registered

Unregistered bwMonitor sysctl

CONFIG_SYSCTL enabled ...

Initialized bandwidth monitor ...

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

%s: %s, dev_info, version

%s: driver unloaded, dev_info

%s: %s, dev_info, version

%s: unloaded, dev_info

%s: %s, dev_info, version

%s: unloaded, dev_info

%s: %s, dev_info, version

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO Removed bandwidth monitor ...

Oops.. AES_GCM_encrypt failed

(keylen:%u),key->cvm_keylen

Oops.. AES_GCM_decrypt failed

(keylen:%u),key->cvm_keylen

%s, msg

%02x%s, data[i],

DEBUG

DEBUG

%s: unloaded, dev_info failed to create procfs entry .

DEBUG ICMP: %u.%u.%u.%u:

INFO

INFO

INFO

INFO

Failed to set AES encrypt key

Failed to set AES encrypt key

DEBUG ICMP: %u.%u.%u.%u: Source

Wrong address mask %u.%u.%u.%u

DEBUG from

Redirect from %u.%u.%u.%u on %s

DEBUG about

INFO

INFO

AES %s Encrypt Test Duration:

%d:%d, hard ? Hard : Soft,

Failed to set AES encrypt key

Failed to set AES encrypt key

AES %s Decrypt Test Duration:

%d:%d, hard ? Hard : Soft,

DEBUG

DEBUG

IP: routing cache hash table of %u buckets, %ldKbytes, source route option %u.%u.%u.%u ->

%u.%u.%u.%u,

DEBUG ICMP: %u.%u.%u.%u:

INFO

INFO

INFO

INFO

Failed to set AES encrypt key

DEBUG

DEBUG

%s: driver unloaded, dev_info

%s: %s: mem=0x%lx, irq=%d,

DEBUG ICMP: %u.%u.%u.%u: Source

Wrong address mask %u.%u.%u.%u

DEBUG from

INFO

INFO

INFO

288

Unified Services Router

User Manual

Failed to set AES encrypt key

Failed to set AES encrypt key

Failed to set AES encrypt key

Failed to set DES encrypt key[%d], i

Failed to set DES decrypt key[%d], i

Failed to set DES encrypt key[%d], i

Failed to set DES decrypt key[%d], i

Failed to set DES encrypt key

Failed to set DES decrypt key

Failed to set DES encrypt key

Failed to set DES decrypt key

AES Software Test:

AES Software Test %s, aesSoftTest(0)

? Failed : Passed

AES Hardware Test:

AES Hardware Test %s, aesHardTest(0) ? Failed : Passed

DEBUG

DEBUG

DEBUG

DEBUG

Redirect from %u.%u.%u.%u on %s about

DEBUG

DEBUG

DEBUG

DEBUG

IP: routing cache hash table of %u buckets, %ldKbytes, source route option %u.%u.%u.%u ->

%u.%u.%u.%u,

Wrong address mask %u.%u.%u.%u from

Redirect from %u.%u.%u.%u on %s about

DEBUG source route option

DEBUG ICMP: %u.%u.%u.%u:

DEBUG ICMP: %u.%u.%u.%u: Source

Wrong address mask %u.%u.%u.%u

DEBUG from

Redirect from %u.%u.%u.%u on %s

DEBUG about

IP: routing cache hash table of %u buckets, %ldKbytes, source route option %u.%u.%u.%u ->

%u.%u.%u.%u,

IPsec: device unregistering: %s, dev-

>name

DEBUG IPsec: device down: %s, dev->name

DEBUG mark: only supports 32bit mark

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

INFO

3DES Software Test:

3DES Software Test %s, des3SoftTest(0) ? Failed : Passed

3DES Hardware Test:

3DES Hardware Test %s, des3HardTest(0) ? Failed : Passed

DES Software Test:

DES Software Test %s, desSoftTest(0)

? Failed : Passed

DEBUG ipt_time: invalid argument

DEBUG ipt_time: IPT_DAY didn't matched

DEBUG

./Logs_kernel.txt:45:KERN_WARNIN

G

DEBUG

DEBUG

DEBUG

DEBUG

./Logs_kernel.txt:59:KERN_WARNIN

G ipt_LOG: not logging via system console

%s: wrong options length: %u, fname, opt_len

%s: options rejected: o[0]=%02x, o[1]=%02x, DES Hardware Test:

DES Hardware Test %s, desHardTest(0) ? Failed : Passed

SHA Software Test:

SHA Software Test %s, shaSoftTest(0)

? Failed : Passed

SHA Hardware Test:

SHA Hardware Test %s, shaHardTest(0) ? Failed : Passed

DEBUG %s: wrong options length: %u,

DEBUG

DEBUG

DEBUG

DEBUG

%s: options rejected: o[0]=%02x, o[1]=%02x,

%s: don't know what to do: o[5]=%02x,

%s: wrong options length: %u, fname, opt_len

%s: options rejected: o[0]=%02x, o[1]=%02x,

MD5 Software Test:

MD5 Software Test %s, md5SoftTest(0) ? Failed : Passed

MD5 Hardware Test:

DEBUG

DEBUG

DEBUG

%s: wrong options length: %u,

%s: options rejected: o[0]=%02x, o[1]=%02x,

%s: don't know what to do: o[5]=%02x,

INFO

INFO

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

289

Unified Services Router

User Manual

MD5 Hardware Test %s, md5HardTest(0) ? Failed : Passed DEBUG

*** New port %d ***, ntohs(expinfo-

>natport)

AES Software Test: %d iterations, iter DEBUG ** skb len %d, dlen %d,(*pskb)->len,

AES Software Test Duration: %d:%d, DEBUG ********** Non linear skb

AES Hardware Test: %d iterations, iter DEBUG End of sdp %p, nexthdr

AES Hardware Test Duration: %d:%d, DEBUG %s: unknown pairwise cipher %d,

3DES Software Test: %d iterations, iter DEBUG %s: unknown group cipher %d,

3DES Software Test Duration: %d:%d, DEBUG

%s: unknown SIOCSIWAUTH flag

%d,

3DES Hardware Test: %d iterations, iter

3DES Hardware Test Duration:

%d:%d,

DEBUG

DEBUG

%s: unknown SIOCGIWAUTH flag

%d,

%s: unknown algorithm %d,

DES Software Test: %d iterations, iter DEBUG %s: key size %d is too large,

DES Software Test Duration: %d:%d, DEBUG try_module_get failed \

DES Hardware Test: %d iterations, iter DEBUG %s: request_irq failed, dev->name

DES Hardware Test Duration: %d:%d, DEBUG try_module_get failed

SHA Software Test: %d iterations, iter DEBUG try_module_get failed \

SHA Software Test Duration: %d:%d, DEBUG %s: unknown pairwise cipher %d,

SHA Hardware Test: %d iterations, iter DEBUG %s: unknown group cipher %d,

SHA Hardware Test Duration: %d:%d, DEBUG

%s: unknown SIOCSIWAUTH flag

%d,

MD5 Software Test: %d iterations, iter DEBUG

%s: unknown SIOCGIWAUTH flag

%d,

MD5 Software Test Duration: %d:%d, DEBUG %s: unknown algorithm %d,

MD5 Hardware Test: %d iterations, iter DEBUG %s: key size %d is too large,

MD5 Hardware Test Duration: %d:%d, DEBUG unable to load %s, scan_modnames[mode]

./pnac/src/pnac/linux/kernel/xcalibur.c:2

09:#define DEBUG_PRINTK printk DEBUG Failed to mkdir /proc/net/madwifi

DEBUG try_module_get failed bcmDeviceInit: registration failed bcmDeviceInit: pCdev Add failed

REG Size == 8 Bit

Value = %x ::: At Page = %x : Addr =

%x

REG Size == 16 Bit

Value = %x ::: At Page = %x : Addr =

%x

REG Size == 32 Bit

DEBUG %s: request_irq failed, dev->name too many virtual ap's (already got

DEBUG %d), sc->sc_nvaps

DEBUG %s: request_irq failed, dev->name

DEBUG rix %u (%u) bad ratekbps %u mode

%u,

DEBUG cix %u (%u) bad ratekbps %u mode

%u,

DEBUG %s: no rates for %s?,

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

290

Unified Services Router

User Manual

Value = %x ::: At Page = %x : Addr =

%x

REG Size == 64 Bit

DEBUG no rates yet! mode %u, sc-

>sc_curmode

DEBUG %u.%u.%u.%u sent an invalid ICMP

DEBUG dst cache overflow REG Size is not in 8/16/32/64

Written Value = %x ::: At Page = %x :

Addr = %x DEBUG Neighbour table overflow. bcm_ioctl :Unknown Ioctl Case : DEBUG host %u.%u.%u.%u/if%d ignores

=========Register Dump for Port

Number # %d=========,port

%s : Read Status=%s data=%#x,regName[j],

%s : Read Status=%s data=%#x,regName[j], powerDeviceInit: device registration failed

DEBUG

DEBUG

DEBUG

DEBUG martian destination %u.%u.%u.%u from martian source %u.%u.%u.%u from ll header:

%u.%u.%u.%u sent an invalid ICMP powerDeviceInit: adding device failed

%s: Error: Big jump in pn number.

TID=%d, from %x %x to %x %x.

%s: The MIC is corrupted. Drop this frame., __func__

%s: The MIC is OK. Still use this frame and update PN., __func__

ADDBA send failed: recipient is not a

11n node

DEBUG dst cache overflow

DEBUG Neighbour table overflow.

DEBUG host %u.%u.%u.%u/if%d ignores

DEBUG martian destination %u.%u.%u.%u from

DEBUG martian source %u.%u.%u.%u from

Cannot Set Rate: %x, value

Getting Rate Series: %x,vap-

>iv_fixed_rate.series

Getting Retry Series: %x,vap-

>iv_fixed_rate.retries

DEBUG

DEBUG ll header:

%u.%u.%u.%u sent an invalid ICMP

DEBUG dst cache overflow

IC Name: %s,ic->ic_dev->name usage: rtparams rt_idx <0|1> per

<0..100> probe_intval <0..100>

DEBUG Neighbour table overflow.

DEBUG host %u.%u.%u.%u/if%d ignores usage: acparams ac <0|3> RTS <0|1> aggr scaling <0..4> min mbps <0..250> DEBUG martian source %u.%u.%u.%u from usage: hbrparams ac <2> enable

<0|1> per_low <0..50>

%s(): ADDBA mode is AUTO,

__func__

DEBUG

DEBUG ll header: martian destination %u.%u.%u.%u from

DEBUG %u.%u.%u.%u sent an invalid ICMP %s(): Invalid TID value, __func__

%s(): ADDBA mode is AUTO,

__func__

%s(): Invalid TID value, __func__

DEBUG

DEBUG dst cache overflow

Neighbour table overflow.

%s(): Invalid TID value, __func__

Addba status IDLE

%s(): ADDBA mode is AUTO,

__func__

DEBUG host %u.%u.%u.%u/if%d ignores

DEBUG martian destination %u.%u.%u.%u from

DEBUG martian source %u.%u.%u.%u from

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

WARNIN

G

291

Unified Services Router

User Manual

%s(): Invalid TID value, __func__

Error in ADD- no node available

%s(): Channel capabilities do not match, chan flags 0x%x,

%s: cannot map channel to mode; freq

%u flags 0x%x, ic_get_currentCountry not initialized yet

Country ie is %c%c%c,

%s: wrong state transition from %d to

%d,

%s: wrong state transition from %d to

%d,

%s: wrong state transition from %d to

%d,

%s: wrong state transition from %d to

%d,

%s: wrong state transition from %d to

%d,

%s: wrong state transition from %d to

%d, ieee80211_deliver_l2uf: no buf available

%s: %s, vap->iv_dev->name, buf /*

NB: no */

%s: [%s] %s, vap->iv_dev->name,

%s: [%s] %s, vap->iv_dev->name, ether_sprintf(mac), buf

[%s:%s] discard %s frame, %s, vap-

>iv_dev->name,

[%s:%s] discard frame, %s, vap-

>iv_dev->name,

[%s:%s] discard %s information element, %s,

[%s:%s] discard information element,

%s,

[%s:%s] discard %s frame, %s, vap-

>iv_dev->name,

[%s:%s] discard frame, %s, vap-

>iv_dev->name,

HBR list dumpNode\tAddress\t\t\tState\tTrigger\t

Block

Nodes informationAddress\t\t\tBlock\t\tDroped

VI frames

%d\t

%2.2x:%2.2x:%2.2x:%2.2x:%2.2x:%2.

2x\t%s\t%s\t%s,

%2.2x:%2.2x:%2.2x:%2.2x:%2.2x:%2.

2x\t%s\t\t%d,

[%d]\tFunction\t%s, j, ni-

>node_trace[i].funcp

[%d]\tMacAddr\t%s, j,

[%d]\tDescp\t\t%s, j, ni-

>node_trace[i].descp

DEBUG ll header:

DEBUG Unable to create ip_set_list

DEBUG Unable to create ip_set_hash ip_conntrack_in: Frag of proto %u

DEBUG (hook=%u),

Unable to register netfilter socket

DEBUG option

DEBUG Unable to create ip_conntrack_hash

DEBUG

Unable to create ip_conntrack slab cache

DEBUG Unable to create ip_expect slab cache ERROR

DEBUG

DEBUG

Unable to create ip_set_iptreeb slab cache

Unable to create ip_set_iptreed slab cache

ERROR

ERROR

DEBUG

DEBUG

DEBUG

%s: cannot allocate space for

%scompressor, fname,

%s: cannot allocate space for MPPC history,

%s: cannot allocate space for MPPC history,

ERROR

ERROR

ERROR

DEBUG %s: cannot load ARC4 module, fname ERROR

DEBUG %s: cannot load SHA1 module, fname ERROR

%s: CryptoAPI SHA1 digest size too

DEBUG ERROR

DEBUG small, fname

%s: cannot allocate space for SHA1 digest, fname ERROR

DEBUG %s%d: trying to write outside history ERROR

DEBUG %s%d: trying to write outside history ERROR

DEBUG %s%d: trying to write outside history ERROR

%s%d: too big uncompressed packet:

DEBUG %d,

%s%d: encryption negotiated but not

ERROR

DEBUG an ERROR

DEBUG

DEBUG

%s%d: error - not an MPPC or MPPE frame

Kernel doesn't provide ARC4 and/or

SHA1 algorithms

DEBUG PPP: not interface or channel??

DEBUG PPP: no memory (VJ compressor)

DEBUG PPP: no memory (comp pkt)

WARNIN

G

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

DEBUG failed to register PPP device (%d), err ERROR

DEBUG PPP: no memory (VJ comp pkt) ERROR

ERROR

292

Unified Services Router

User Manual

[%d]\tValue\t\t%llu(0x%llx), j, ni-

>node_trace[i].value, ifmedia_add: null ifm

Adding entry for ifmedia_set: no match for 0x%x/0x%x, DEBUG ppp_decompress_frame: no memory ERROR ppp_mp_reconstruct bad seq %u < ifmedia_set: target DEBUG %u,

PPP: couldn't register device %s

ERROR ifmedia_set: setting to ifmedia_ioctl: switching %s to , dev-

>name

DEBUG

DEBUG

(%d), ppp: destroying ppp struct %p but dead=%d

ERROR

ERROR ifmedia_match: multiple match for

<unknown type> desc->ifmt_string

DEBUG ppp: compressor dropped pkt

DEBUG

DEBUG PPP: VJ uncompressed error

DEBUG ppp: destroying undead channel %p !, ERROR

DEBUG

PPP: removing module but units remain! ERROR

DEBUG

PPP: no memory (fragment)

PPP: failed to unregister PPP device

ERROR

ERROR

ERROR

ERROR

mode %s, desc->ifmt_string

<unknown subtype>

%s, desc->ifmt_string

%s%s, seen_option++ ? , : ,

%s%s, seen_option++ ? , : ,

%s, seen_option ? > :

%s: %s, dev->name, buf

%s: no memory for sysctl table!,

__func__

%s: failed to register sysctls!, vap-

>iv_dev->name

Atheros HAL assertion failure: %s: line

%u: %s, ath_hal: logging to %s %s, ath_hal_logfile, ath_hal: logging disabled

%s%s, sep, ath_hal_buildopts[i] ath_pci: No devices found, driver not installed.

DEBUG

DEBUG

DEBUG

%s: cannot allocate space for

%scompressor, fname,

%s: cannot allocate space for MPPC history,

%s: cannot allocate space for MPPC history,

ERROR

ERROR

ERROR

DEBUG %s: cannot load ARC4 module, fname ERROR

DEBUG %s: cannot load SHA1 module, fname ERROR

DEBUG

DEBUG

%s: CryptoAPI SHA1 digest size too small, fname

%s: cannot allocate space for SHA1 digest, fname

ERROR

ERROR

DEBUG

DEBUG

%s%d: trying to write outside history

%s%d: trying to write outside history

ERROR

ERROR

DEBUG %s%d: trying to write outside history ERROR

DEBUG

DEBUG

DEBUG

DEBUG

%s%d: too big uncompressed packet:

%d,

%s%d: encryption negotiated but not an

%s%d: error - not an MPPC or MPPE frame

Kernel doesn't provide ARC4 and/or

SHA1 algorithms

ERROR

ERROR

ERROR

ERROR

---:%d pri:%d qd:%u ad:%u sd:%u tot:%u amp:%d %02x:%02x:%02x,

SC Pushbutton Notify on %s::%s,dev-

>name,vap->iv_dev->name

Could not find Board Configuration

Data

Could not find Radio Configuration data

%s: No device, __func__ ath_ahb: No devices found, driver not installed.

PKTLOG_TAG %s:proc_dointvec failed, __FUNCTION__

PKTLOG_TAG %s:proc_dointvec failed, __FUNCTION__

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

PPP: not interface or channel??

PPP: no memory (VJ compressor) failed to register PPP device (%d), err

PPP: no memory (comp pkt) ppp: compressor dropped pkt

PPP: no memory (VJ comp pkt)

PPP: no memory (comp pkt)

PPP: no memory (fragment)

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

293

Unified Services Router

User Manual

%s: failed to register sysctls!, proc_name

PKTLOG_TAG %s: proc_mkdir failed,

__FUNCTION__

PKTLOG_TAG %s: pktlog_attach failed for %s,

PKTLOG_TAG %s:allocation failed for pl_info, __FUNCTION__

PKTLOG_TAG %s:allocation failed for pl_info, __FUNCTION__

PKTLOG_TAG %s: create_proc_entry failed for %s,

PKTLOG_TAG %s: sysctl register failed for %s,

PKTLOG_TAG %s: page fault out of range, __FUNCTION__

PKTLOG_TAG %s: page fault out of range, __FUNCTION__

PKTLOG_TAG %s: Log buffer unavailable, __FUNCTION__

PKTLOG_TAG

Logging should be disabled before changing bufer size

%s:allocation failed for pl_info,

__func__

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG JBD: corrupted journal superblock

DEBUG

DEBUG

PPP: VJ uncompressed error

(%d), ppp: destroying ppp struct %p but dead=%d ppp: destroying undead channel %p !,

PPP: removing module but units remain!

PPP: failed to unregister PPP device

JBD: bad block at offset %u,

JBD: bad block at offset %u,

JBD: Failed to read block at offset %u,

DEBUG JBD: error %d scanning journal, err

%s: Unable to allocate buffer, __func__ DEBUG JBD: IO error %d recovering block

%s:allocation failed for pl_info,

__func__ DEBUG ./Logs_kernel.txt:303:KERN_ERR

ERROR

DEBUG ppp_decompress_frame: no memory ERROR ppp_mp_reconstruct bad seq %u <

DEBUG %u,

PPP: couldn't register device %s

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

%s: Unable to allocate buffer, __func__ DEBUG ./Logs_kernel.txt:304:KERN_ERR

Atheros HAL assertion failure: %s: line

DEBUG JBD: recovery pass %d ended at %u: %s, ath_hal: logging to %s %s, ath_hal_logfile, DEBUG %s: %s:%d: BAD SESSION MAGIC \

ERROR

ERROR

ERROR ath_hal: logging disabled DEBUG %s: %s:%d: BAD TUNNEL MAGIC \ ERROR

%s%s, sep, ath_hal_buildopts[i] failed to allocate rx descriptors: %d, error

DEBUG

DEBUG msg->msg_namelen wrong, %d, msg-

>msg_namelen addr family wrong: %d, usin-

>sin_family

DEBUG udp addr=%x/%hu, usin-

>sin_addr.s_addr, usin->sin_port

DEBUG %s: %s:%d: BAD TUNNEL MAGIC

ERROR

ERROR

ERROR

ERROR ath_stoprecv: rx queue %p, link %p, no mpdu (%s), __func__

Reset rx chain mask. Do internal reset.

(%s), __func__

OS_CANCEL_TIMER failed!!

%s: unable to allocate channel table,

__func__

%s: unable to collect channel list from hal;

%s: cannot map channel to mode; freq

%u flags 0x%x,

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

%s: %s:%d: BAD TUNNEL MAGIC socki_lookup: socket file changed!

%s: %s:%d: BAD TUNNEL MAGIC

%s: %s:%d: BAD SESSION MAGIC \

%s: %s:%d: BAD TUNNEL MAGIC \

ERROR

ERROR

ERROR

ERROR

ERROR

%s: unable to reset channel %u

(%uMhz)

%s: unable to restart recv logic,

%s: start DFS WAIT period on channel

DEBUG

DEBUG

%d, __func__,sc->sc_curchan.channel DEBUG msg->msg_namelen wrong, %d, msg-

>msg_namelen addr family wrong: %d, usin-

>sin_family udp addr=%x/%hu, usin-

>sin_addr.s_addr, usin->sin_port

ERROR

ERROR

ERROR

294

Unified Services Router

User Manual

%s: cancel DFS WAIT period on channel %d, __func__, sc-

>sc_curchan.channel

Non-DFS channel, cancelling previous

DFS wait timer channel %d, sc-

>sc_curchan.channel

%s: unable to reset hardware; hal status %u

DEBUG

DEBUG

%s: %s:%d: BAD TUNNEL MAGIC

%s: %s:%d: BAD TUNNEL MAGIC

DEBUG socki_lookup: socket file changed!

%s: unable to start recv logic, __func__ DEBUG %s: %s:%d: BAD TUNNEL MAGIC

ERROR

ERROR

ERROR

ERROR

%s: unable to start recv logic, __func__ DEBUG %s: %s:%d: BAD SESSION MAGIC \ ERROR

%s: unable to reset hardware; hal status %u, DEBUG %s: %s:%d: BAD TUNNEL MAGIC \ ERROR hardware error; reseting DEBUG

DEBUG

DEBUG msg->msg_namelen wrong, %d, msg-

>msg_namelen addr family wrong: %d, usin-

>sin_family udp addr=%x/%hu, usin-

>sin_addr.s_addr, usin->sin_port

ERROR

ERROR

ERROR rx FIFO overrun; reseting

%s: During Wow Sleep and got

BMISS, __func__

AC\tRTS \tAggr Scaling\tMin

Rate(Kbps)\tHBR \tPER LOW

THRESHOLD

BE\t%s\t\t%d\t%6d\t\t%s\t%d,

BK\t%s\t\t%d\t%6d\t\t%s\t%d,

VI\t%s\t\t%d\t%6d\t\t%s\t%d,

VO\t%s\t\t%d\t%6d\t\t%s\t%d,

--%d,%p,%lu:0x%x 0x%x 0x%p 0x%x

0x%x 0x%x 0x%x, bb state: 0x%08x 0x%08x, bbstate(sc,

4ul), bbstate(sc, 5ul)

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

%s: %s:%d: BAD TUNNEL MAGIC

%s: %s:%d: BAD TUNNEL MAGIC socki_lookup: socket file changed!

%s: %s:%d: BAD TUNNEL MAGIC rebootHook: null function pointer

Bad ioctl command fResetMod: Failed to configure gpio pin

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

%08x %08x %08x %08x %08x %08x

%08x %08x%08x %08x %08x %08x, noise floor: (%d, %d) (%d, %d) (%d,

%d),

%p: %08x %08x %08x %08x %08x

%08x %08x %08x %08x %08x %08x

%08x,

--%d,%p,%lu:0x%x 0x%x 0x%p 0x%x

0x%x 0x%x 0x%x,

%08x %08x %08x %08x %08x %08x

%08x %08x%08x %08x %08x %08x,

DEBUG

DEBUG

DEBUG

DEBUG fResetMod: Failed to register interrupt handler registering char device failed unregistering char device failed proc entry delete failed

DEBUG proc entry initialization failed

%s: unable to allocate device object.,

__func__

%s: unable to attach hardware; HAL status %u,

DEBUG testCompHandler: received %s from

%d, (char *)pInBuf,

%s: HAL ABI msmatch;

%s: Warning, using only %u entries in

%u key cache,

DEBUG UMI proto registration failed %d,ret

DEBUG AF_UMI registration failed %d,ret

DEBUG umi initialization failed %d,ret unable to setup a beacon xmit queue! DEBUG kernel UMI registration failed! unable to setup CAB xmit queue! unable to setup xmit queue for BE traffic!

%s DFS attach failed, __func__

%s: Invalid interface id = %u,

__func__, if_id

DEBUG ./Logs_kernel.txt:447:KERN_ERR

DEBUG

DEBUG

DEBUG

ERROR msm not found properly %d, len %d, msm,

ModExp returned Error

ModExp returned Error

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

295

Unified Services Router

%s:grppoll Buf allocation failed

,__func__

%s: unable to start recv logic,

%s: Invalid interface id = %u,

__func__, if_id

%s: unable to allocate channel table,

__func__

%s: Tx Antenna Switch. Do internal reset., __func__

DEBUG

%s: 0x%p len %u, tag, p, (unsigned int)len

DEBUG %03d:, i

%02x, ((unsigned char *)p)[i]

Radar found on channel %d (%d MHz), DEBUG %03d:, i

End of DFS wait period DEBUG %02x, ((unsigned char *)p)[i]

%s error allocating beacon, __func__ failed to allocate UAPSD QoS NULL tx descriptors: %d, error failed to allocate UAPSD QoS NULL wbuf

%s: unable to allocate channel table,

__func__

%s: unable to update h/w beacon queue parameters,

ALREADY ACTIVATED

DEBUG

DEBUG mic check failed

%s: 0x%p len %u, tag, p, (unsigned

DEBUG int)len

DEBUG mic check failed

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

[%s] Wrong parameters, __func__

[%s] Wrong Key length, __func__

[%s] Wrong parameters, __func__

[%s] Wrong Key length, __func__

[%s] Wrong parameters, __func__

%s: missed %u consecutive beacons, DEBUG [%s] Wrong Key length, __func__

%s: busy times: rx_clear=%d, rx_frame=%d, tx_frame=%d, __func__, rx_clear, rx_frame, tx_frame

%s: unable to obtain busy times,

__func__

DEBUG

DEBUG

[%s] Wrong parameters, __func__

[%s] Wrong Key length, __func__

%s: beacon is officially stuck,

Busy environment detected

Inteference detected rx_clear=%d, rx_frame=%d, tx_frame=%d,

%s: resume beacon xmit after %u misses,

%s: stuck beacon; resetting (bmiss count %u),

DEBUG [%s]: Wrong parameters, __func__

DEBUG

DEBUG

DEBUG

[%s] Wrong Key Length %d,

__func__, des_key_len

[%s] Wrong parameters %d,

__func__, des_key_len

[%s] Wrong Key Length %d,

__func__, des_key_len

DEBUG

DEBUG

[%s] Wrong parameters, __func__

[%s] Wrong Key Length, __func__

DEBUG [%s] Wrong parameters, __func__ EMPTY QUEUE

SWRInfo: seqno %d isswRetry %d retryCnt %d,wh ? (*(u_int16_t *)&wh-

>i_seq[0]) >> 4 : 0, bf->bf_isswretry,bf-

>bf_swretries

Buffer #%08X --> Next#%08X

Prev#%08X Last#%08X,bf,

TAILQ_NEXT(bf,bf_list),

Stas#%08X flag#%08X

Node#%08X, bf->bf_status, bf-

>bf_flags, bf->bf_node

Descr #%08X --> Next#%08X

Data#%08X Ctl0#%08X Ctl1#%08X, bf->bf_daddr, ds->ds_link, ds-

>ds_data, ds->ds_ctl0, ds->ds_ctl1

Ctl2#%08X Ctl3#%08X

Sta0#%08X Sta1#%08X,ds->ds_hw[0], ds->ds_hw[1], lastds->ds_hw[2], lastds->ds_hw[3]

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

[%s] Wrong Key Length, __func__

[%s] Wrong parameters, __func__

[%s] Wrong parameters, __func__

[%s] Wrong parameters, __func__

[%s] Wrong parameters, __func__

User Manual

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

296

Unified Services Router

User Manual

Error entering wow mode

Wakingup due to wow signal

%s, wowStatus = 0x%x, __func__, wowStatus

DEBUG device name=%s not found, pReq-

>ifName

DEBUG unable to register KIFDEV to UMI

DEBUG

DEBUG

ERROR: %s: Timeout at page %#0x addr %#0x

ERROR: %s: Timeout at page %#0x addr %#0x

ERROR

ERROR

ERROR

Pattern added already

Error : All the %d pattern are in use.

Cannot add a new pattern ,

MAX_NUM_PATTERN

ERROR

Pattern added to entry %d ,i

Remove wake up pattern mask = %p pat = %p

,maskBytes,patternBytes mask = %x pat = %x

,(u_int32_t)maskBytes,

(u_int32_t)patternBytes

Pattern Removed from entry %d ,i

Error : Pattern not found

PPM STATE ILLEGAL %x %x, forcePpmStateCur, afp->forceState

FORCE_PPM %4d %6.6x %8.8x

%8.8x %8.8x %3.3x %4.4x, failed to allocate tx descriptors: %d, error failed to allocate beacon descripotrs:

%d, error failed to allocate UAPSD descripotrs:

%d, error hal qnum %u out of range, max %u!,

HAL AC %u out of range, max %zu!,

HAL AC %u out of range, max %zu!,

%s: unable to update hardware queue

%u!,

Multicast Q:

%p , buf buf flags - 0x%08x --------- , buf-

>bf_flags

DEBUG Invalid IOCTL %#08x, cmd

%s: unable to register device, dev-

DEBUG >name

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG

DEBUG ath_pci: 32-bit DMA not available ath_pci: cannot reserve PCI memory region

DEBUG ath_pci: cannot remap PCI memory region) ;

DEBUG ath_pci: no memory for device state

%s: unable to register device, dev-

DEBUG >name ath_dev_probe: no memory for device state

%s: no memory for device state,

__func__ kernel MIBCTL registration failed!

Bad ioctl command

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

DEBUG WpsMod: Failed to configure gpio pin ERROR

WpsMod: Failed to register interrupt

DEBUG handler ERROR

DEBUG registering char device failed ERROR

DEBUG unregistering char device failed ERROR

DEBUG

%s:%d - ERROR: non-NULL node pointer in %p, %p<%s>!

DEBUG

%s:%d - ERROR: non-NULL node pointer in %p, %p<%s>!

DEBUG can't alloc name %s, name

DEBUG

%s: unable to register device, dev-

>name

DEBUG failed to automatically load module:

%s; \

ERROR

ERROR

ERROR

ERROR

ERROR buf status - 0x%08x, buf->bf_status

# frames in aggr - %d, length of aggregate - %d, length of frame - %d, sequence number - %d, tidno - %d, isdata: %d isaggr: %d isampdu: %d ht:

%d isretried: %d isxretried: %d shpreamble: %d isbar: %d ispspoll: %d aggrburst: %d calcairtime: %d qosnulleosp: %d,

%p: 0x%08x 0x%08x 0x%08x 0x%08x

0x%08x 0x%08x 0x%08x 0x%08x

0x%08x 0x%08x,

DEBUG

Unable to load needed module: %s; no support for \

DEBUG Module \%s\ is not known, buf

DEBUG Error loading module \%s\, buf

ERROR

ERROR

ERROR

297

Unified Services Router

User Manual

0x%08x 0x%08x 0x%08x 0x%08x

0x%08x 0x%08x 0x%08x 0x%08x

0x%08x 0x%08x,

0x%08x 0x%08x 0x%08x 0x%08x, sc_txq[%d] : , i tid %p pause %d : , tid, tid->paused

%d: %p , j, tid->tx_buf[j]

DEBUG Module \%s\ failed to initialize, buf

DEBUG ath_pci: 32-bit DMA not available ath_pci: cannot reserve PCI memory

DEBUG

DEBUG region ath_pci: cannot remap PCI memory region) ;

DEBUG ath_pci: no memory for device state

DEBUG

%s: unable to attach hardware: '%s'

(HAL status %u),

DEBUG %s: HAL ABI mismatch;

ERROR

ERROR

ERROR

ERROR

ERROR

%p , buf axq_q:

%s: unable to reset hardware; hal status %u, __func__, status

****ASSERTION HIT****

MacAddr=%s,

TxBufIdx=%d, i

Tid=%d, tidno

AthBuf=%p, tid->tx_buf[i]

%s: unable to reset hardware; hal status %u,

%s: unable to reset hardware; hal status %u,

%s: unable to start recv logic,

_fmt, __VA_ARGS__ \ sample_pri=%d is a multiple of refpri=%d, sample_pri, refpri

===========ft-

>ft_numfilters=%u===========, ft-

>ft_numfilters filter[%d] filterID = %d rf_numpulses=%u; rf->rf_minpri=%u; rf->rf_maxpri=%u; rf->rf_threshold=%u; rf->rf_filterlen=%u; rf->rf_mindur=%u; rf->rf_maxdur=%u,j, rf->rf_pulseid,

NOL

WARNING!!! 10 minute CAC period as channel is a weather radar channel

%s disable detects, __func__

%s enable detects, __func__

%s disable FFT val=0x%x , __func__, val

%s enable FFT val=0x%x , __func__, val

%s debug level now = 0x%x ,

__func__, dfs_debug_level

RateTable:%d, maxvalidrate:%d, ratemax:%d, pRc-

>rateTableSize,k,pRc->rateMaxPhy

%s: txRate value of 0x%x is bad.,

__FUNCTION__, txRate

Valid Rate Table:-

DEBUG

DEBUG %s: recvd invalid skb

DEBUG unable to register KIFDEV to UMI

DEBUG

The system is going to factory defaults........!!!

DEBUG %s, msg

DEBUG %02x, *(data + i)

DEBUG Inside crypt_open in driver ######

ERROR

ERROR

DEBUG %s: failed to allocate descriptors: %d, ERROR

%s: unable to setup a beacon xmit

DEBUG queue!, ERROR

DEBUG %s: unable to setup CAB xmit queue!, ERROR

DEBUG

%s: unable to setup xmit queue for

%s traffic!, ERROR

DEBUG

%s: unable to register device, dev-

>name ERROR

DEBUG %s: autocreation of VAP failed: %d, ath_dev_probe: no memory for device

DEBUG state kdot11RogueAPEnable called with

DEBUG

DEBUG

NULL argument. kdot11RogueAPEnable: can not add more interfaces

DEBUG

DEBUG kdot11RogueAPGetState called with

NULL argument. kdot11RogueAPDisable called with

NULL argument.

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

CRITICAL

CRITICAL

CRITICAL

DEBUG Inside crypt_release in driver ###### CRITICAL

DEBUG

Inside crypt_init module in driver

@@@@@@@@ CRITICAL

DEBUG

%s: SKB does not exist.,

__FUNCTION__

Inside crypt_cleanup module in driver

@@@@@@@@

DEBUG SKB is null : %p ,skb

DEBUG DST is null : %p ,dst

ERROR

CRITICAL

CRITICAL

CRITICAL

CRITICAL

298

Unified Services Router

User Manual

Index:%d, value:%d, code:%x, rate:%d, flag:%x, i,

(int)validRateIndex[i],

RateTable:%d, maxvalidrate:%d, ratemax:%d, pRc-

>rateTableSize,k,pRc->rateMaxPhy

DEBUG

DEBUG

DEV is null %p %p ,dev,dst

Packet is Fragmented %d,pBufMgr-

>len

CRITICAL

CRITICAL

Can't allocate memory for ath_vap. DEBUG

Marked the packet proto:%d sip:%x dip:%x sport:%d dport:%d spi:%d,isr:%p:%p %p

SAV CHECK FAILED IN

DECRYPTION

CRITICAL

Unable to add an interface for ath_dev. DEBUG

%s: [%02u] %-7s , tag, ix, ciphers[hk-

>kv_type] DEBUG FAST PATH Breaks on BUF CHECK

CRITICAL

CRITICAL

%02x, hk->kv_val[i]

mac %02x-%02x-%02x-%02x-%02x-

%02x, mac[0], mac[1], mac[2], mac[3], mac[4], mac[5]

mac 00-00-00-00-00-00

%02x, hk->kv_mic[i]

txmic

%02x, hk->kv_txmic[i]

DEBUG FAST PATH Breaks on DST CHECK CRITICAL

FAST PATH Breaks on MTU %d %d

DEBUG

%d,bufMgrLen(pBufMgr),mtu,dst_mtu

(pDst->path) CRITICAL

DEBUG

FAST PATH Breaks on MAX PACKET

%d

%d,bufMgrLen(pBufMgr),IP_MAX_PA

CKET CRITICAL

DEBUG

DEBUG

DEBUG

DEBUG

SAV CHECK FAILED IN

ENCRYPTION

Match Found proto %d spi

%d,pPktInfo->proto,pFlowEntry-

>pre.spi

PRE: proto: %u srcip:%u.%u.%u.%u sport :%u dstip: %u.%u.%u.%u dport:

%u,

POST: proto: %u srcip:%u.%u.%u.%u sport :%u dstip: %u.%u.%u.%u dport:

%u,

CRITICAL

CRITICAL

CRITICAL

CRITICAL

Cannot support setting tx and rx keys individually bogus frame type 0x%x (%s),

ERROR: ieee80211_encap ret NULL

DEBUG Clearing the ISR %p,p

PROTO:%d %u.%u.%u.%u---

DEBUG >%u.%u.%u.%u,

ERROR: ath_amsdu_attach not called DEBUG ESP-DONE: %p %p,sav,m

%s: no memory for cwm attach,

DEBUG ESP-BAD: %p %p,sav,m __func__

%s: error - acw NULL. Possible attach failure, __func__ DEBUG Bug in ip_route_input_slow().

%s: unable to abort tx dma, __func__ DEBUG Bug in ip_route_input_slow().

CRITICAL

CRITICAL

CRITICAL

CRITICAL

CRITICAL

CRITICAL

%s: no memory for ff attach, __func__ DEBUG Bug in ip_route_input \

Failed to initiate PBC based enrolle association

KERN_EMERG Returing error in INTR registration

DEBUG

DEBUG

Bug in ip_route_input_slow().

AH: Assigning the secure flags for sav

:%p,sav

ESP: Assigning the secure flags for sav :%p skb:%p src:%x

KERN_EMERG Initialzing Wps module DEBUG dst:%x,sav,skb,ip->ip_src.s_addr,ip-

>ip_dst.s_addr

%s:%d %s, __FILE__, __LINE__,

__func__ DEBUG

%s Buffer %d mtu %d path mtu %d header %d trailer

%d,__func__,bufMgrLen(pBufMgr),mt u,dst_mtu(pDst->path),pDst-

>header_len,pDst->trailer_len

CRITICAL

CRITICAL

CRITICAL

CRITICAL

CRITICAL

299

Unified Services Router

Appendix E.

RJ-45 Pin-outs

Signal

RJ-45

Cable

Adapter

RJ-45 PIN DB-9 PIN

Signal

CTS

DTR

TxD

GND

GND

RxD

DSR

RTS

NC

NC

6

5

4

3

NC

NC

NC

NC

3

5

5

2

NC

NC

NC

NC

RxD

GND

GND

TxD

NC

NC

User Manual

300

Unified Services Router

User Manual

Appendix F.

New Wi Fi Frequency table ( New appendix section )

Country

Channel supported in20

Mhz

1)

2)

3)

4)

5)

6)

7)

8)

9)

10)

11)

Australia

Russia

Iceland

Singapore

Sweden

Taiwan

Finland

Slovenia

Ireland

United states

Latin

America

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48, 149,

153, 157, 161, 165

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48, 149,

153, 157, 161, 165

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11

56, 60, 64, 149, 153,

157, 161, 165

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11

36, 40, 44, 48, 149,

153, 157, 161, 165

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

64, 153, 161

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11

40, 48, 153,

161

5, 6, 7, 8, 9,

10, 11, 12, 13

Channel supported in 40

Mhz

Upper side band

Lower side band

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48, 153,

161

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48, 153,

161

5, 6, 7, 8, 9,

10, 11, 12, 13

1, 2, 3, 4, 5, 6,

7, 8, 9

36, 44, 149,

157

1, 2, 3, 4, 5, 6,

7, 8, 9

36, 44, 149,

157

1, 2, 3, 4, 5, 6,

7, 8, 9

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11

36,44

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7

60, 149, 157

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7

36, 44, 149,

157

1, 2, 3, 4, 5, 6,

7, 8, 9

301

Unified Services Router

23)

24)

25)

20)

21)

22)

16)

17)

18)

19)

12)

13)

14)

15)

Korea

Japan

Egypt

Denmark

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

Germany

Netherlands 2.4Ghz

5 Ghz

Norway 2.4Ghz

5 Ghz

Poland

Luxembour g

South

Africa

United

Kingdom

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

Ireland

France

Israel

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

User Manual

40, 48, 153,

161

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48, 153,

161

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48

5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48, 149,

153, 157, 161, 165

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48, 149,

153, 157, 161

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 44, 149,

157

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7, 8, 9

36, 44

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7, 8, 9

36, 44, 149,

157

1, 2, 3, 4, 5, 6,

7, 8, 9

36,44

1, 2, 3, 4, 5, 6,

7, 8, 9

302

Unified Services Router

26)

27)

28)

Brazil

Canada

China

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

2.4Ghz

5 Ghz

User Manual

36, 40, 44, 48, 52, 56,

60, 64

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11,12,13

36, 40, 44, 48, 149,

153, 157, 161, 165

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11

36, 40, 44, 48, 149,

153, 157, 161, 165

1, 2, 3, 4, 5, 6, 7, 8, 9,

10, 11, 12, 13

36, 40, 44, 48, 149,

153, 157, 161, 165

40, 48, 56, 64 36, 44, 52, 60

5, 6, 7, 8, 9, 1, 2, 3, 4, 5, 6,

10, 11,12,13 7,8,9

40, 48, 153,

161

5, 6, 7, 8, 9,

10, 11

36, 44, 149,

157

1, 2, 3, 4, 5, 6,

7

40, 48, 153,

161

5, 6, 7, 8, 9,

10, 11, 12, 13

40, 48, 153,

161

36, 44, 149,

157

1, 2, 3, 4, 5, 6,

7, 8, 9

36, 44, 149,

157

303

Unified Services Router

User Manual

Appendix G.

Product Statement

1. DSR-1000N

Federal Communications Commission (FCC) Compliance Notice: Radio Frequency Notice

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

Reorient or relocate the receiving antenna.

Increase the separation between the equipment and receiver.

Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

Consult the dealer or an experienced radio/TV technician for help.

FCC Radiation Exposure Statement

This equipment complies with FCC RF radiation exposure limits set forth for an uncontrolled environment.

This equipment should be installed and operated with a minimum distance of 20 centimeters between the radiator and your body.

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

1) This device may not cause harmful interference, and

2) This device must accept any interference received, including interference that may cause undesired operation.

This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter.

The antennas used for this transmitter must be installed to provide a spectrum distance of at least 20cm from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter.

This transmitter is restricted to indoor use in the 5150MHz to 5250MHz frequency range.

Non-modification Statement

Use only the integral antenna supplied by the manufacturer when operating this device. Unauthorized antennas, modifications, or attachments could damage the TI Navigator access point and violate FCC regulations. Any changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate this equipment.

Canadian Department of Communications Industry Canada (IC) Notice

This Class B digital apparatus complies with Canadian ICES-003 and RSS-210. Cet appareil numérique de la classe B est conforme à la norme NMB-003 et CNR-210 du Canada.

ndustry Canada Statement

This device complies with RSS-210 of the Industry Canada Rules. Operation is subject to the following two conditions:

1) This device may not cause harmful interference, and

2) This device must accept any interference received, including interference that may cause undesired operation.

IMPORTANT NOTE: Radiation Exposure Statement

This equipment complies with IC radiation exposure limits set forth for an uncontrolled environment. End users

304

Unified Services Router

User Manual must follow the specific operating instructions for satisfying RF exposure compliance. To maintain compliance with IC RF exposure compliance requirements, please follow operation instruction as documented in this manual.

This transmitter is restricted to indoor use in the 5150MHz to 5250MHz frequency range.

Europe

– EU Declaration of Conformity

This device complies with the essential requirements of the R&TTE Directive 1999/5/EC. The following test methods have been applied in order to prove presumption of conformity with the essential requirements of the R&TTE Directive 1999/5/EC:

- EN 60950-1: 2006+A11:2009

Safety of information technology equipment

- EN 300 328 V1.7.1 (2006-10)

Electromagnetic compatibility and Radio spectrum Matters (ERM); Wideband transmission systems; Data transmission equipment operating in the 2,4 GHz ISM band and using wide band modulation techniques;

Harmonized EN covering essential requirements under article 3.2 of the R&TTE Directive

- EN 301 893-1 V1.5.1 (2008-12)

Broadband Radio Access Networks (BRAN); 5 GHz high performance RLAN; Harmonized EN covering essential requirements of article 3.2 of the R&TTE Directive

- EN 301 489-17 V1.3.2 (2008-04) and EN 301 489-1 V1.8.1 (2008-04)

Electromagnetic compatibility and Radio spectrum Matters (ERM); Electro Magnetic Compatibility (EMC) standard for radio equipment and services; Part 17: Specific conditions for 2,4 GHz wideband transmission systems and 5 GHz high performance RLAN equipment

This device is a 2.4 GHz wideband transmission system (transceiver), intended for use in all EU member states and EFTA countries under the following conditions and/or with the following restrictions:

- In Italy the end-user should apply for a license at the national spectrum authorities in order to obtain authorization to use the device for setting up outdoor radio links and/or for supplying public access to telecommunications and/or network services.

- This device may not be used for setting up outdoor radio links in France and in some areas the RF output power may be limited to 10 mW EIRP in the frequency range of 2454

– 2483.5 MHz. For detailed information the enduser should contact the national spectrum authority in France.

This device is a 5 GHz wideband transmission system (transceiver), intended for use in all EU member states and EFTA countries under the following conditions and/or with the following restrictions:

- This device may only be used indoors in the frequency bands 5150

– 5250 MHz.

- In France and Luxembourg a limited implementation of the frequency bands 5150

– 5250 MHz and 5250 –

5350 MHz. In Luxermbourg it is not allowed to make use of the frequency band 5470

– 5725 MHz. End-users are encouraged to contact the national spectrum authorities in France and Luxembourg in order to obtain the latest information about any restrictions in the 5 GHz frequency band(s).

305

Unified Services Router

User Manual

Česky

[Czech]

[D-

Link Corporation] tímto prohlašuje, že tento [DSR-1000N] je ve shodě se základními požadavky a dalšími příslušnými ustanoveními směrnice 1999/5/ES.

Dansk

[Danish]

Undertegnede [D-Link Corporation] erklærer herved, at følgende udstyr [DSR-1000N] overholder de væsentlige krav og øvrige relevante krav i direktiv 1999/5/EF.

Deutsch

[German]

Hiermit erklärt [D-Link Corporation], dass sich das Gerät [DSR-1000N] in Übereinstimmung mit den grundlegenden Anforderungen und den übrigen einschlägigen Bestimmungen der

Richtlinie 1999/5/EG befindet.

Eesti

[Estonian]

Käesolevaga kinnitab [D-Link Corporation] seadme [DSR-1000N] vastavust direktiivi

1999/5/EÜ põhinõuetele ja nimetatud direktiivist tulenevatele teistele asjakohastele sätetele.

English

Hereby, [D-Link Corporation], declares that this [DSR-1000N] is in compliance with the essential requirements and other relevant provisions of Directive 1999/5/EC.

Español

[Spanish]

Por medio de la presente [D-Link Corporation] declara que el [DSR-1000N] cumple con los requisitos esenciales y cualesquiera otras disposiciones aplicables o exigibles de la

Directiva 1999/5/CE.

Ελληνική

[Greek]

ΜΕ ΤΗΝ ΠΑΡΟΥΣΑ [D-Link Corporation] ΔΗΛΩΝΕΙ ΟΤΙ [DSR-1000N] ΣΥΜΜΟΡΦΩΝΕΤΑΙ

ΠΡΟΣ ΤΙΣ ΟΥΣΙΩΔΕΙΣ ΑΠΑΙΤΗΣΕΙΣ ΚΑΙ ΤΙΣ ΛΟΙΠΕΣ ΣΧΕΤΙΚΕΣ ΔΙΑΤΑΞΕΙΣ ΤΗΣ

ΟΔΗΓΙΑΣ 1999/5/ΕΚ.

Français

[French]

Par la présente [D-Link Corporation] déclare que l'appareil [DSR-1000N] est conforme aux exigences essentielles et aux autres dispositions pertinentes de la directive 1999/5/CE.

Italiano

[Italian]

Con la presente [D-Link Corporation] dichiara che questo [DSR-1000N] è conforme ai requisiti essenziali ed alle altre disposizioni pertinenti stabilite dalla direttiva 1999/5/CE.

Latviski

[Latvian]

Ar šo [D-Link Corporation] deklarē, ka [DSR-1000N] atbilst Direktīvas 1999/5/EK būtiskajām prasībām un citiem ar to saistītajiem noteikumiem.

Lietuvių

[Lithuanian]

Šiuo [D-Link Corporation] deklaruoja, kad šis [DSR-1000N] atitinka esminius reikalavimus ir kitas 1999/5/EB Direktyvos nuostatas.

Nederlands

[Dutch]

Hierbij verklaart [D-Link Corporation] dat het toestel [DSR-1000N] in overeenstemming is met de essentiële eisen en de andere relevante bepalingen van richtlijn 1999/5/EG.

Malti

[Maltese]

Hawnhekk, [D-Link Corporation], jiddikjara li dan [DSR-1000N] jikkonforma malħtiġijiet essenzjali u ma provvedimenti oħrajn relevanti li hemm fid-Dirrettiva 1999/5/EC.

Magyar

[Hungarian]

Alulírott, [D-Link Corporation] nyilatkozom, hogy a [DSR-1000N] megfelel a vonatkozó alapvetõ követelményeknek és az 1999/5/EC irányelv egyéb elõírásainak.

Polski

[Polish]

Niniejszym [D-Link Corporation] oświadcza, że [DSR-1000N] jest zgodny z zasadniczymi wymogami oraz pozostałymi stosownymi postanowieniami Dyrektywy 1999/5/EC.

306

Unified Services Router

User Manual

Português

[Portuguese]

[D-Link Corporation] declara que este [DSR-1000N]está conforme com os requisitos essenciais e outras disposições da Directiva 1999/5/CE.

Slovensko

[Slovenian]

[D-Link Corporation] izjavlja, da je ta [DSR-1000N] v skladu z bistvenimi zahtevami in ostalimi relevantnimi določili direktive 1999/5/ES.

Slovensky

[Slovak]

[D-Link Corporation] týmto vyhlasuje, že [DSR-1000N] spĺňa základné požiadavky a všetky príslušné ustanovenia Smernice 1999/5/ES.

Suomi

[Finnish]

[D-Link Corporation] vakuuttaa täten että [DSR-1000N] tyyppinen laite on direktiivin

1999/5/EY oleellisten vaatimusten ja sitä koskevien direktiivin muiden ehtojen mukainen.

Svenska

[Swedish]

Härmed intygar [D-Link Corporation] att denna [DSR-1000N] står I överensstämmelse med de väsentliga egenskapskrav och övriga relevanta bestämmelser som framgår av direktiv

1999/5/EG.

307

Unified Services Router

User Manual

2.DSR-500N

Federal Communications Commission (FCC) Compliance Notice: Radio Frequency Notice

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

Reorient or relocate the receiving antenna.

Increase the separation between the equipment and receiver.

Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

Consult the dealer or an experienced radio/TV technician for help.

FCC Radiation Exposure Statement

This equipment complies with FCC RF radiation exposure limits set forth for an uncontrolled environment.

This equipment should be installed and operated with a minimum distance of 20 centimeters between the radiator and your body.

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

1) This device may not cause harmful interference, and

2) This device must accept any interference received, including interference that may cause undesired operation.

This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter.

The antennas used for this transmitter must be installed to provide a spectrum distance of at least 20cm from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter.

This transmitter is restricted to indoor use in the 5150MHz to 5250MHz frequency range.

Non-modification Statement

Use only the integral antenna supplied by the manufacturer when operating this device. Unauthorized antennas, modifications, or attachments could damage the TI Navigator access point and violate FCC regulations. Any changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate this equipment.

Canadian Department of Communications Industry Canada (IC) Notice

This Class B digital apparatus complies with Canadian ICES-003 and RSS-210. Cet appareil numérique de la classe B est conforme à la norme NMB-003 et CNR-210 du Canada.

Industry Canada Statement

This device complies with RSS-210 of the Industry Canada Rules. Operation is subject to the following two conditions:

1) This device may not cause harmful interference, and

2) This device must accept any interference received, including interference that may cause undesired operation.

IMPORTANT NOTE: Radiation Exposure Statement

This equipment complies with IC radiation exposure limits set forth for an uncontrolled environment.

End users must follow the specific operating instructions for satisfying RF exposure compliance.

To maintain compliance with IC RF exposure compliance requirements, please follow operation instruction as documented in this manual.

308

Unified Services Router

User Manual

Europe

– EU Declaration of Conformity

This device complies with the essential requirements of the R&TTE Directive 1999/5/EC. The following test methods have been applied in order to prove presumption of conformity with the essential requirements of the R&TTE Directive 1999/5/EC:

- EN 60950-1: 2006+A11:2009

Safety of information technology equipment

- EN 300 328 V1.7.1 (2006-10)

Electromagnetic compatibility and Radio spectrum Matters (ERM); Wideband transmission systems; Data transmission equipment operating in the 2,4 GHz ISM band and using wide band modulation techniques;

Harmonized EN covering essential requirements under article 3.2 of the R&TTE Directive

- EN 301 489-17 V1.3.2 (2008-04) and EN 301 489-1 V1.8.1 (2008-04)

Electromagnetic compatibility and Radio spectrum Matters (ERM); Electro Magnetic Compatibility (EMC) standard for radio equipment and services; Part 17: Specific conditions for 2,4 GHz wideband transmission systems and 5 GHz high performance RLAN equipment

This device is a 2.4 GHz wideband transmission system (transceiver), intended for use in all EU member states and EFTA countries under the following conditions and/or with the following restrictions:

- In Italy the end-user should apply for a license at the national spectrum authorities in order to obtain authorization to use the device for setting up outdoor radio links and/or for supplying public access to telecommunications and/or network services.

- This device may not be used for setting up outdoor radio links in France and in some areas the RF output power may be limited to 10 mW EIRP in the frequency range of 2454

– 2483.5 MHz. For detailed information the enduser should contact the national spectrum authority in France.

309

Unified Services Router

User Manual

Česky

[Czech]

[D-Link Corporation

] tímto prohlašuje, že tento [DSR-500N] je ve shodě se základními požadavky a dalšími příslušnými ustanoveními směrnice 1999/5/ES.

Dansk

[Danish]

Undertegnede [D-Link Corporation] erklærer herved, at følgende udstyr [DSR-500N] overholder de væsentlige krav og øvrige relevante krav i direktiv 1999/5/EF.

Deutsch

[German]

Hiermit erklärt [D-Link Corporation], dass sich das Gerät [DSR-500N] in Übereinstimmung mit den grundlegenden Anforderungen und den übrigen einschlägigen Bestimmungen der

Richtlinie 1999/5/EG befindet.

Eesti

[Estonian]

Käesolevaga kinnitab [D-Link Corporation] seadme [DSR-500N] vastavust direktiivi

1999/5/EÜ põhinõuetele ja nimetatud direktiivist tulenevatele teistele asjakohastele sätetele.

English

Hereby, [D-Link Corporation], declares that this [DSR-500N] is in compliance with the essential requirements and other relevant provisions of Directive 1999/5/EC.

Español

[Spanish]

Por medio de la presente [D-Link Corporation] declara que el [DSR-500N] cumple con los requisitos esenciales y cualesquiera otras disposiciones aplicables o exigibles de la

Directiva 1999/5/CE.

Ελληνική

[Greek]

ΜΕ ΤΗΝ ΠΑΡΟΥΣΑ [D-Link Corporation] ΔΗΛΩΝΕΙ ΟΤΙ [DSR-500N] ΣΥΜΜΟΡΦΩΝΕΤΑΙ

ΠΡΟΣ ΤΙΣ ΟΥΣΙΩΔΕΙΣ ΑΠΑΙΤΗΣΕΙΣ ΚΑΙ ΤΙΣ ΛΟΙΠΕΣ ΣΧΕΤΙΚΕΣ ΔΙΑΤΑΞΕΙΣ ΤΗΣ

ΟΔΗΓΙΑΣ 1999/5/ΕΚ.

Français

[French]

Par la présente [D-Link Corporation] déclare que l'appareil [DSR-500N] est conforme aux exigences essentielles et aux autres dispositions pertinentes de la directive 1999/5/CE.

Italiano

[Italian]

Con la presente [D-Link Corporation] dichiara che questo [DSR-500N] è conforme ai requisiti essenziali ed alle altre disposizioni pertinenti stabilite dalla direttiva 1999/5/CE.

Latviski

[Latvian]

Ar šo [D-Link Corporation] deklarē, ka [DSR-500N] atbilst Direktīvas 1999/5/EK būtiskajām prasībām un citiem ar to saistītajiem noteikumiem.

Lietuvių

[Lithuanian]

Šiuo [D-Link Corporation] deklaruoja, kad šis [DSR-500N] atitinka esminius reikalavimus ir kitas 1999/5/EB Direktyvos nuostatas.

Nederlands

[Dutch]

Hierbij verklaart [D-Link Corporation] dat het toestel [DSR-500N] in overeenstemming is met de essentiële eisen en de andere relevante bepalingen van richtlijn 1999/5/EG.

Malti

[Maltese]

Hawnhekk, [D-Link Corporation], jiddikjara li dan [DSR-500N] jikkonforma malħtiġijiet essenzjali u ma provvedimenti oħrajn relevanti li hemm fid-Dirrettiva 1999/5/EC.

Magyar

[Hungarian]

Alulírott, [D-Link Corporation] nyilatkozom, hogy a [DSR-500N] megfelel a vonatkozó alapvetõ követelményeknek és az 1999/5/EC irányelv egyéb elõírásainak.

Polski

[Polish]

Niniejszym [D-Link Corporation

] oświadcza, że [DSR-500N] jest zgodny z zasadniczymi wymogami oraz pozostałymi stosownymi postanowieniami Dyrektywy 1999/5/EC.

310

Unified Services Router

User Manual

Português

[Portuguese]

[D-Link Corporation] declara que este [DSR-500N]está conforme com os requisitos essenciais e outras disposições da Directiva 1999/5/CE.

Slovensko

[Slovenian]

[D-Link Corporation] izjavlja, da je ta [DSR-500N] v skladu z bistvenimi zahtevami in ostalimi relevantnimi določili direktive 1999/5/ES.

Slovensky

[Slovak]

[D-Link Corporation

] týmto vyhlasuje, že [DSR-500N] spĺňa základné požiadavky a všetky príslušné ustanovenia Smernice 1999/5/ES.

Suomi

[Finnish]

[D-Link Corporation] vakuuttaa täten että [DSR-500N] tyyppinen laite on direktiivin

1999/5/EY oleellisten vaatimusten ja sitä koskevien direktiivin muiden ehtojen mukainen.

Svenska

[Swedish]

Härmed intygar [D-Link Corporation] att denna [DSR-500N] står I överensstämmelse med de väsentliga egenskapskrav och övriga relevanta bestämmelser som framgår av direktiv 1999/5/EG.

311

Unified Services Router

User Manual

3.DSR-250N

Federal Communication Commission Interference Statement

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to

Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one of the following measures:

Reorient or relocate the receiving antenna.

Increase the separation between the equipment and receiver.

Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

Consult the dealer or an experienced radio/TV technician for help.

FCC Caution

:

Any changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate this equipment.

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1)

This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

RSS-GEN 7.1.4

:

User Manual for Transmitters with Detachable Antennas

The user manual of transmitter devices equipped with detachable antennas shall contain the following information in a conspicuous location:

This device has been designed to operate with the antennas listed below, and having a maximum gain of [1.8] dB. Antennas not included in this list or having a gain greater than [1.8] dB are strictly prohibited for use with this device. The required antenna impedance is [50] ohms.

RSS-GEN 7.1.5

To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more than that permitted for successful communication.

Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorisée aux deux conditions suivantes: (1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en comSpromettre le fonctionnement.

Is herewith confirmed to comply with the requirements set out in the Council Directive on the Approximation of the Laws of the Member States relating to Electromagnetic Compatibility (2004/108/EC), Low-voltage

Directive (2006/95/EC), the procedures given in European Council Directive 99/5/EC and 2004/104/EC.

The equipment was passed. The test was performed according to the following European standards:

EN 300 328 V.1.7.1

EN 301 489-1 V.1. 8.1 / EN 301 489-17 V.2.1.1

EN 62311

EN 60950-1

312

Unified Services Router

User Manual

Regulatory statement (R&TTE)

European standards dictate maximum radiated transmit power of 100mW EIRP and frequency range 2.400-

2.4835GHz; In France, the equipment must be restricted to the 2.4465-2.4835GHz frequency range and must be restricted to indoor use.

Operation of this device is subjected to the following National regulations and may be prohibited to use if certain restriction should be applied.

D=0.020m is the minimum safety distance between the EUT and human body when the E-Field strength is

61V/m.

NCC Warning Statement

Article 12

Without permission, any company, firm or user shall not alter the frequency, increase the power, or change the characteristics and functions of the original design of the certified lower power frequency electric machinery.

Article 14

The application of low power frequency electric machineries shall not affect the navigation safety nor interfere a legal communication, if an interference is found, the service will be suspended until improvement is made and the interference no longer exists.

313

Unified Services Router

User Manual

4. DSR-150N

Federal Communication Commission Interference Statement

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to

Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one of the following measures:

Reorient or relocate the receiving antenna.

Increase the separation between the equipment and receiver.

Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

Consult the dealer or an experienced radio/TV technician for help.

FCC Caution

:

Any changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate this equipment. This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

(1) This device may not cause harmful interference, and

(2) this device must accept any interference received, including interference that may cause undesired operation.

IMPORTANT NOTE:

FCC Radiation Exposure Statement

:

This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance 20cm between the radiator & your body.

This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter.

The availability of some specific channels and/or operational frequency bands are country dependent and are firmware programmed at the factory to match the intended destination. The firmware setting is not accessible by the end user.

Note

: The country code selection is for non-US model only and is not available to all US model. Per FCC regulation, all WiFi product marketed in US must fixed to US operation channels only..

Europe

– EU Declaration of Conformity

This device complies with the essential requirements of the R&TTE Directive 1999/5/EC. The following test methods have been applied in order to prove presumption of conformity with the essential requirements of the

R&TTE Directive 1999/5/EC:

EN 60950-1:

Safety of Information Technology Equipment

EN50385 : (2002-08)

Product standard to demonstrate the compliance of radio base stations and fixed terminal stations for wireless telecommunication systems with the basic restrictions or the reference levels related to human exposure to radio frequency electromagnetic fields (110MHz - 40 GHz) - General public

EN 300 328 V1.7.1: (2006-10)

Electromagnetic compatibility and Radio spectrum Matters (ERM); Wideband Transmission systems; Data transmission equipment operating in the 2,4 GHz ISM band and using spread spectrum modulation techniques; Harmonized EN covering essential requirements under article 3.2 of the R&TTE Directive

EN 301 489-1 V1.8.1: (2008-04)

314

Unified Services Router

User Manual

Electromagnetic compatibility and Radio Spectrum Matters (ERM); ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 1: Common technical requirements

EN 301 489-17 V2.1.1 (2009-05)

Electromagnetic compatibility and Radio spectrum Matters (ERM); ElectroMagnetic Compatibility (EMC) standard for radio equipment; Part 17: Specific conditions for Broadband Data Transmission Systems

This device is a 2.4 GHz wideband transmission system (transceiver), intended for use in all EU member states and EFTA countries, except in France and Italy where restrictive use applies.

In Italy the end-user should apply for a license at the national spectrum authorities in order to obtain authorization to use the device for setting up outdoor radio links and/or for supplying public access to telecommunications and/or network services.

This device may not be used for setting up outdoor radio links in France and in some areas the RF output power may be limited to 10 mW EIRP in the frequency range of 2454

– 2483.5 MHz. For detailed information the end-user should contact the national spectrum authority in France.

Česky

[Czech]

Dansk

[Danish]

Deutsch

[German]

Eesti

[Estonian]

English

Español

[Spanish]

Ελληνική

[Greek]

Français

[French]

Italiano

[Italian]

Latviski

[Latvian]

Lietuvių

[Lithuanian]

Nederlands

[Dutch]

Malti

[Maltese]

[Jméno výrobce] tímto prohlašuje, že tento [typ zařízení] je ve shodě se základními požadavky a dalšími příslušnými ustanoveními směrnice 1999/5/ES.

Undertegnede [fabrikantens navn] erklærer herved, at følgende udstyr [udstyrets typebetegnelse] overholder de væsentlige krav og øvrige relevante krav i direktiv

1999/5/EF.

Hiermit erklärt [Name des Herstellers], dass sich das Gerät [Gerätetyp] in

Übereinstimmung mit den grundlegenden Anforderungen und den übrigen einschlägigen

Bestimmungen der Richtlinie 1999/5/EG befindet.

Käesolevaga kinnitab [tootja nimi = name of manufacturer] seadme [seadme tüüp = type of equipment] vastavust direktiivi 1999/5/EÜ põhinõuetele ja nimetatud direktiivist tulenevatele teistele asjakohastele sätetele.

Hereby, [name of manufacturer], declares that this [type of equipment] is in compliance with the essential requirements and other relevant provisions of Directive 1999/5/EC.

Por medio de la presente [nombre del fabricante] declara que el [clase de equipo] cumple con los requisitos esenciales y cualesquiera otras disposiciones aplicables o exigibles de la Directiva 1999/5/CE.

ΜΕ ΤΗΝ ΠΑΡΟΥΣΑ [name of manufacturer] ΔΗΛΩΝΕΙ ΟΤΙ [type of equipment]

ΣΥΜΜΟΡΦΩΝΕΤΑΙ ΠΡΟΣ ΤΙΣ ΟΥΣΙΩΔΕΙΣ ΑΠΑΙΤΗΣΕΙΣ ΚΑΙ ΤΙΣ ΛΟΙΠΕΣ ΣΧΕΤΙΚΕΣ

ΔΙΑΤΑΞΕΙΣ ΤΗΣ ΟΔΗΓΙΑΣ 1999/5/ΕΚ.

Par la présente [nom du fabricant] déclare que l'appareil [type d'appareil] est conforme aux exigences essentielles et aux autres dispositions pertinentes de la directive 1999/5/CE.

Con la presente [nome del costruttore] dichiara che questo [tipo di apparecchio] è conforme ai requisiti essenziali ed alle altre disposizioni pertinenti stabilite dalla direttiva

1999/5/CE.

Ar šo [name of manufacturer / izgatavotāja nosaukums] deklarē, ka [type of equipment / iekārtas tips] atbilst Direktīvas 1999/5/EK būtiskajām prasībām un citiem ar to saistītajiem noteikumiem.

Šiuo [manufacturer name] deklaruoja, kad šis [equipment type] atitinka esminius reikalavimus ir kitas 1999/5/EB Direktyvos nuostatas.

Hierbij verklaart [naam van de fabrikant] dat het toestel [type van toestel] in overeenstemming is met de essentiële eisen en de andere relevante bepalingen van richtlijn 1999/5/EG.

Hawnhekk, [isem tal-manifattur], jiddikjara li dan [il-mudel tal-prodott] jikkonforma malħtiġijiet essenzjali u ma provvedimenti oħrajn relevanti li hemm fid-Dirrettiva 1999/5/EC.

315

Unified Services Router

User Manual

Magyar

[Hungarian]

Polski

[Polish]

Alulírott, [gyártó neve] nyilatkozom, hogy a [... típus] megfelel a vonatkozó alapvetõ követelményeknek és az 1999/5/EC irányelv egyéb elõírásainak.

Niniejszym [nazwa producenta] oświadcza, że [nazwa wyrobu] jest zgodny z zasadniczymi wymogami oraz pozostałymi stosownymi postanowieniami Dyrektywy 1999/5/EC.

Português

[Portuguese]

[Nome do fabricante] declara que este [tipo de equipamento] está conforme com os requisitos essenciais e outras disposições da Directiva 1999/5/CE.

Slovensko

[Slovenian]

Slovensky

[Slovak]

[Ime proizvajalca] izjavlja, da je ta [tip opreme] v skladu z bistvenimi zahtevami in ostalimi relevantnimi določili direktive 1999/5/ES.

[Meno výrobcu] týmto vyhlasuje, že [typ zariadenia] spĺňa základné požiadavky a všetky príslušné ustanovenia Smernice 1999/5/ES.

Suomi

[Finnish]

Svenska

[Swedish]

[Valmistaja = manufacturer] vakuuttaa täten että [type of equipment = laitteen tyyppimerkintä] tyyppinen laite on direktiivin 1999/5/EY oleellisten vaatimusten ja sitä koskevien direktiivin muiden ehtojen mukainen.

Härmed intygar [företag] att denna [utrustningstyp] står I överensstämmelse med de väsentliga egenskapskrav och övriga relevanta bestämmelser som framgår av direktiv

1999/5/EG.

Industry Canada statement

:

This device complies with RSS-210 of the Industry Canada Rules. Operation is subject to the following two conditions:

(1) This device may not cause harmful interference, and

(2) This device must accept any interference received, including interference that may cause undesired operation.

Ce dispositif est conforme à la norme CNR-210 d'Industrie Canada applicable aux appareils radio exempts de licence. Son fonctionnement est sujet aux deux conditions suivantes: (1) le dispositif ne doit pas produire de brouillage préjudiciable, et (2) ce dispositif doit accepter tout brouillage reçu, y compris un brouillage susceptible de provoquer un fonctionnement indésirable.

Radiation Exposure Statement

:

This equipment complies with IC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance 20cm between the radiator & your body.

Déclaration d'exposition aux radiations

:

Cet équipement est conforme aux limites d'exposition aux rayonnements IC établies pour un environnement non contrôlé. Cet équipement doit être installé et utilisé avec un minimum de 20 cm de distance entre la source de rayonnement et votre corps.

Wall-Mount Option

The Router has four wall-mount slots on its bottom panel.

Before you begin, make sure you have two screws that are size #4 - this indicates a diameter measurement of 0.112inches (2.845mm).

1. Determine where you want to mount the Router.

2. Drill two holes into the wall. Make sure adjacent holes are 2.36 inches (60mm) apart.

3. Insert a screw into each hole, and leave 0.2inches (5mm) of its head exposed.

4. Maneuver the Router so the wall-mount slots line up with the two screws.

5. Place the wall-mount slots over the screws and slide the Router down until the screws fit snugly into the wall-mount slots.

316

advertisement

Key Features

  • Multi WAN Support
  • Firewall and VPN
  • Wireless Access Point
  • VLAN Support
  • Traffic Management
  • Advanced Routing
  • Remote Management
  • Security Features

Frequently Answers and Questions

What is the purpose of the DSR series routers?
The DSR series routers are designed for small to medium businesses and organizations that need a reliable and secure network solution with advanced features such as VPN, firewall, and traffic management.
What is the difference between the DSR-150 and the DSR-500?
The DSR-150 is a entry-level router, while the DSR-500 is a more powerful router with more features and capacity. The DSR-500 supports more simultaneous connections and has higher performance specifications.
How do I configure the DSR router for wireless networking?
You can configure the DSR router for wireless networking by accessing the router's web interface. The user manual provides detailed instructions on how to set up a wireless network, including security settings.
What are the security features of the DSR router?
The DSR router includes a variety of security features, including a firewall, VPN, and intrusion prevention system (IPS). These features help to protect your network from unauthorized access and malicious attacks.

Related manuals

Download PDF

advertisement