all | frequencies |
|
|
exhibits | applications |
---|---|---|---|---|---|
manuals |
app s | submitted / available | |||||||
---|---|---|---|---|---|---|---|---|
1 |
|
User manual 1 of 2 | Users Manual | 4.15 MiB | ||||
1 |
|
User manual 2 of 2 | Users Manual | 2.08 MiB | ||||
1 | Cover Letter(s) | |||||||
1 | Cover Letter(s) | |||||||
1 | Attestation Statements | |||||||
1 | External Photos | |||||||
1 | Internal Photos | |||||||
1 | ID Label/Location Info | |||||||
1 | Cover Letter(s) | |||||||
1 | Cover Letter(s) | |||||||
1 | Test Report | |||||||
1 | Test Setup Photos |
1 | User manual 1 of 2 | Users Manual | 4.15 MiB |
User Manual Unified Services Router D-Link Corporation Copyright 2011. http://www.dlink.com Unified Services Router User Manual User Manual DSR-250N / DSR-500 / 500N / 1000 / 1000N Unified Services Router Version 1.03 Copyright 2011 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 in 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 PROFIT, 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 DAMAGES. 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 ..................................................................................................................... 10 1.1 1.2 About this User Manual ..................................................................................... 11 Typographical Conventions ............................................................................... 11 Chapter 2. Configuring Your Network: LAN Setup ......................................................................... 13 2.1 LAN Configuration .............................................................................................. 13 2.1.1 LAN Configuration in an IPv6 Network ............................................................. 16 2.1.2 Configuring IPv6 Router Advertisements ......................................................... 18 2.2 VLAN Configuration ........................................................................................... 21 2.2.1 Associating VLANs to ports ............................................................................... 22 2.3 Configurable Port: DMZ Setup .......................................................................... 24 Universal Plug and Play (UPnP) ....................................................................... 25 2.4 2.5 Captive Portal ..................................................................................................... 27 Chapter 3. Connecting to the Internet: WAN Setup ....................................................................... 28 3.1 Internet Setup Wizard ........................................................................................ 28 3.2 WAN Configuration ............................................................................................ 29 3.2.1 WAN Port IP address......................................................................................... 30 3.2.2 WAN DNS Servers............................................................................................. 30 3.2.3 DHCP WAN ........................................................................................................ 30 3.2.4 PPPoE ................................................................................................................ 31 3.2.5 Russia L2TP and PPTP WAN ........................................................................... 34 3.2.6 WAN Configuration in an IPv6 Network ........................................................... 35 3.2.7 Checking WAN Status ....................................................................................... 37 Bandwidth Controls ............................................................................................ 39 3.3 Features with Multiple WAN Links .................................................................... 41 3.4 3.4.1 Auto Failover ...................................................................................................... 41 3.4.2 Load Balancing .................................................................................................. 42 3.4.3 Protocol Bindings ............................................................................................... 43 3.5 Routing Configuration ........................................................................................ 44 3.5.1 Routing Mode ..................................................................................................... 44 3.5.2 Dynamic Routing (RIP) ...................................................................................... 46 3.5.3 Static Routing ..................................................................................................... 47 3.6 Configurable Port - WAN Option ....................................................................... 49 3.7 WAN Port Settings ............................................................................................. 51 Chapter 4. Wireless Access Point Setup ........................................................................................ 53 4.1 Wireless Settings Wizard .................................................................................. 53 4.1.1 Wireless Network Setup Wizard ....................................................................... 54 4.1.2 Add Wireless Device with WPS ........................................................................ 54 4.1.3 Manual Wireless Network Setup ....................................................................... 55 4.2 Wireless Profiles ................................................................................................ 55 4.2.1 WEP Security ..................................................................................................... 56 4.2.2 WPA or WPA2 with PSK ................................................................................... 57 4.2.3 RADIUS Authentication ..................................................................................... 58 4.3 Creating and Using Access Points ................................................................... 59 4.3.1 Primary benefits of Virtual APs: ........................................................................ 61 2 Unified Services Router User Manual Tuning Radio Specific Settings ......................................................................... 62 4.4 4.5 Advanced Wireless Settings ............................................................................. 63 4.6 Wi-Fi Protected Setup (WPS) ........................................................................... 63 Chapter 5. Securing the Private Network ........................................................................................ 65 Firewall Rules ..................................................................................................... 65 5.1 Defining Rule Schedules ................................................................................... 66 5.2 5.3 Configuring Firewall Rules ................................................................................ 67 5.3.1 Firewall Rule Configuration Examples ............................................................. 72 Security on Custom Services ............................................................................ 76 5.4 ALG support ....................................................................................................... 77 5.5 VPN Passthrough for Firewall ........................................................................... 78 5.6 5.7 Application Rules ............................................................................................... 79 5.8 Web Content Filtering ........................................................................................ 80 5.8.1 Content Filtering ................................................................................................. 80 5.8.2 Approved URLs .................................................................................................. 81 5.8.3 Blocked Keywords ............................................................................................. 82 IP/MAC Binding .................................................................................................. 83 5.9 5.10 Intrusion Prevention (IPS) ................................................................................. 84 5.11 Protecting from Internet Attacks........................................................................ 85 Chapter 6. IPsec / PPTP / L2TP VPN ............................................................................................. 87 VPN Wizard ........................................................................................................ 88 6.1 6.2 Configuring IPsec Policies................................................................................. 91 6.2.1 Extended Authentication (XAUTH) ................................................................... 94 Internet over IPSec tunnel ................................................................................. 94 6.2.2 Configuring VPN clients..................................................................................... 95 6.3 6.4 PPTP / L2TP Tunnels ........................................................................................ 95 6.4.1 PPTP Tunnel Support ........................................................................................ 95 6.4.2 L2TP Tunnel Support......................................................................................... 96 Chapter 7. SSL VPN ......................................................................................................................... 97 7.1 Users, Groups, and Domains ............................................................................ 98 7.1.1 User Types and Passwords ............................................................................ 100 7.2 Using SSL VPN Policies .................................................................................. 102 7.2.1 Using Network Resources ............................................................................... 105 Application Port Forwarding ............................................................................ 106 7.3 7.4 SSL VPN Client Configuration ........................................................................ 108 7.5 User Portal ........................................................................................................ 110 7.5.1 Creating Portal Layouts ................................................................................... 111 Chapter 8. Advanced Configuration Tools .................................................................................... 113 USB Device Setup ........................................................................................... 113 Authentication Certificates............................................................................... 114 Advanced Switch Configuration ...................................................................... 116 8.1 8.2 8.3 Chapter 9. Administration & Management .................................................................................... 118 3 Unified Services Router User Manual 9.1 Configuration Access Control.......................................................................... 118 9.1.1 Remote Management ...................................................................................... 118 9.1.2 CLI Access ....................................................................................................... 119 SNMP Configuration ........................................................................................ 119 9.2 9.3 Configuring Time Zone and NTP .................................................................... 121 9.4 Log Configuration ............................................................................................. 122 9.4.1 Defining What to Log ....................................................................................... 122 9.4.2 Sending Logs to E-mail or Syslog................................................................... 126 9.4.3 Event Log Viewer in GUI ................................................................................. 128 9.5 Backing up and Restoring Configuration Settings ......................................... 129 Upgrading Router Firmware ............................................................................ 130 9.6 Dynamic DNS Setup ........................................................................................ 131 9.7 9.8 Using Diagnostic Tools .................................................................................... 132 9.8.1 Ping ................................................................................................................... 133 9.8.2 Trace Route ...................................................................................................... 133 9.8.3 DNS Lookup ..................................................................................................... 134 9.8.4 Router Options ................................................................................................. 134 Chapter 10. Router Status and Statistics ........................................................................................ 135 10.1 System Overview ............................................................................................. 135 10.1.1 Device Status ................................................................................................... 135 10.1.2 Resource Utilization ......................................................................................... 137 10.2 Traffic Statistics ................................................................................................ 140 10.2.1 Wired Port Statistics ........................................................................................ 140 10.2.2 Wireless Statistics ............................................................................................ 141 10.3 Active Connections .......................................................................................... 142 10.3.1 Sessions through the Router........................................................................... 142 10.3.2 Wireless Clients ............................................................................................... 144 10.3.3 LAN Clients....................................................................................................... 144 10.3.4 Active VPN Tunnels ......................................................................................... 145 Chapter 11. Trouble Shooting .......................................................................................................... 147 11.1 Internet connection .......................................................................................... 147 11.2 Date and time ................................................................................................... 149 11.3 Pinging to Test LAN Connectivity ................................................................... 149 11.3.1 Testing the LAN path from your PC to your router ........................................ 149 11.3.2 Testing the LAN path from your PC to a remote device ............................... 150 11.4 Restoring factory-default configuration settings ............................................ 151 Chapter 12. Credits ........................................................................................................................... 153 Appendix A. Glossary ........................................................................................................................ 154 Appendix B. Factory Default Settings .............................................................................................. 157 Appendix C. Standard Services Available for Port Forwarding & Firewall Configuration ............. 158 Appendix D. Log Output Reference.................................................................................................. 159 Appendix E. RJ-45 Pin-outs .............................................................................................................. 213 4 Unified Services Router User Manual Appendix F. Product Statement ....................................................................................................... 214 5 Unified Services Router User Manual List of Figures Figure 1: Setup page for LAN TCP/IP settings .................................................................................. 15 Figure 2: IPv6 LAN and DHCPv6 configuration ................................................................................. 17 Figure 3: Configuring the Router Advertisement Daemon ................................................................ 20 Figure 4: IPv6 Advertisement Prefix settings ..................................................................................... 21 Figure 5: Adding VLAN memberships to the LAN ............................................................................. 22 Figure 6: Port VLAN list ....................................................................................................................... 23 Figure 7: Configuring VLAN membership for a port .......................................................................... 24 Figure 8: DMZ configuration ................................................................................................................ 25 Figure 9: UPnP Configuration ............................................................................................................. 26 Figure 10: Active Runtime sessions ................................................................................................... 27 Figure 11: Internet Connection Setup Wizard .................................................................................... 28 Figure 12: Manual WAN configuration ............................................................................................... 31 Figure 13: PPPoE configuration for standard ISPs ........................................................................... 32 Figure 14: WAN configuration for Japanese Multiple PPPoE (part 1) ............................................. 33 Figure 15: WAN configuration for Multiple PPPoE (part 2) ............................................................... 34 Figure 16: Russia L2TP ISP configuration ......................................................................................... 35 Figure 17: IPv6 WAN Setup page ....................................................................................................... 37 Figure 18: Connection Status information for both WAN ports......................................................... 38 Figure 19: List of Configured Bandwidth Profiles .............................................................................. 39 Figure 20: Bandwidth Profile Configuration page .............................................................................. 40 Figure 21: Traffic Selector Configuration ........................................................................................... 41 Figure 22: Load Balancing is available when multiple WAN ports are configured and Protocol Bindings have been defined .............................................................................................. 43 Figure 23: Protocol binding setup to associate a service and/or LAN source to a WAN and/or destination network ............................................................................................................ 44 Figure 24: Routing Mode is used to configure traffic routing between WAN and LAN, as well as Dynamic routing (RIP) ........................................................................................................ 46 Figure 25: Static route configuration fields ......................................................................................... 49 Figure 26: WAN2 configuration for 3G internet (part 1) .................................................................... 50 Figure 27: WAN2 configuration for 3G internet (part 2) .................................................................... 51 Figure 28: Physical WAN port settings ............................................................................................... 52 Figure 29: Wireless Network Setup Wizards ..................................................................................... 54 Figure 30: List of Available Profiles shows the options available to secure the wireless link......... 56 Figure 31: Profile configuration to set network security .................................................................... 57 Figure 32: RADIUS server (External Authentication) configuration ................................................. 59 6 Unified Services Router User Manual Figure 33: Virtual AP configuration ..................................................................................................... 60 Figure 34: List of configured access points (Virtual APs) shows one enabled access point on the radio, broadcasting its SSID .............................................................................................. 61 Figure 35: Radio card configuration options ...................................................................................... 62 Figure 36: Advanced Wireless communication settings.................................................................... 63 Figure 37: WPS configuration for an AP with WPA/WPA2 profile .................................................... 64 Figure 38: List of Available Firewall Rules ......................................................................................... 66 Figure 39: List of Available Schedules to bind to a firewall rule ....................................................... 67 Figure 40: 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) ...................................... 70 Figure 41: The firewall rule configuration page allows you to define the To/From zone, service, action, schedules, and specify source/destination IP addresses as needed. ............... 71 Figure 42: Schedule configuration for the above example. ............................................................. 75 Figure 43: List of user defined services.............................................................................................. 77 Figure 44: Available ALG support on the router. .............................................................................. 78 Figure 45: Passthrough options for VPN tunnels .............................................................................. 79 Figure 46: List of Available Application Rules showing 4 unique rules ............................................ 80 Figure 47: Content Filtering used to block access to proxy servers and prevent ActiveX controls from being downloaded...................................................................................................... 81 Figure 48: Two trusted domains added to the Approved URLs List................................................. 82 Figure 49: Two keywords added to the block list ............................................................................... 83 DSR. If there is an IP/MAC Binding violation, the violating packet will be dropped and logs will be captured ........................................................................................................... 84 Figure 51: Intrusion Prevention features on the router ...................................................................... 85 Figure 52: Protecting the router and LAN from internet attacks ....................................................... 86 Figure 53: Example of Gateway-to-Gateway IPsec VPN tunnel using two DSR routers connected to the Internet...................................................................................................................... 87 Figure 54: Example of three IPsec client connections to the internal network through the DSR IPsec gateway .................................................................................................................... 88 Figure 55: VPN Wizard launch screen ............................................................................................... 89 Figure 56: IPsec policy configuration .................................................................................................. 92 Figure 57: IPsec policy configuration continued (Auto policy via IKE) ............................................. 93 Figure 58: IPsec policy configuration continued (Auto / Manual Phase 2) ...................................... 94 Figure 59: PPTP tunnel configuration PPTP Server ...................................................................... 96 Figure 60: L2TP tunnel configuration L2TP Server ........................................................................ 96 Figure 61: Example of clientless SSL VPN connections to the DSR ............................................... 98 Figure 62: Available Users with login status and associated Group/Domain .................................. 99 Figure 63: User configuration options............................................................................................... 102 7 Unified Services Router User Manual Figure 64: List of SSL VPN polices (Global filter) ............................................................................ 103 Figure 65: SSL VPN policy configuration ......................................................................................... 104 Figure 66: List of configured resources, which are available to assign to SSL VPN policies ....... 106 Figure 67: List of Available Applications for SSL Port Forwarding ................................................. 108 Figure 68: SSL VPN client adapter and access configuration ........................................................ 109 Figure 69: Configured client routes only apply in split tunnel mode ............................................... 110 Figure 70: List of configured SSL VPN portals. The configured portal can then be associated with an authentication domain ................................................................................................. 111 Figure 71: SSL VPN Portal configuration ......................................................................................... 112 Figure 72: USB Device Detection ..................................................................................................... 114 Figure 73: Certificate summary for IPsec and HTTPS management ............................................. 116 Figure 74: Advanced Switch Settings ............................................................................................... 117 Figure 75: User Login policy configuration ....................................................................................... 118 Figure 76: Remote Management from the WAN ............................................................................. 119 Figure 77: SNMP Users, Traps, and Access Control ...................................................................... 120 Figure 78: SNMP system information for this router ....................................................................... 121 Figure 79: Date, Time, and NTP server setup ................................................................................. 122 Figure 80: Facility settings for Logging ............................................................................................. 124 Figure 81: Log configuration options for traffic through router........................................................ 126 Figure 82: E-mail configuration as a Remote Logging option ......................................................... 127 Figure 83: Syslog server configuration for Remote Logging (continued)....................................... 128 Figure 84: VPN logs displayed in GUI event viewer ........................................................................ 129 Figure 85: Restoring configuration from a saved file will result in the current configuration being overwritten and a reboot .................................................................................................. 130 Figure 86: Firmware version information and upgrade option ........................................................ 131 Figure 87: Dynamic DNS configuration ............................................................................................ 132 Figure 88: Router diagnostics tools available in the GUI ................................................................ 133 Figure 89: Sample traceroute output ................................................................................................ 134 Figure 90: Device Status display ...................................................................................................... 136 Figure 91: Device Status display (continued) .................................................................................. 137 Figure 92: Resource Utilization statistics ......................................................................................... 138 Figure 93: Resource Utilization data (continued) ............................................................................ 139 Figure 94: Resource Utilization data (continued) ............................................................................ 140 Figure 95: Physical port statistics ..................................................................................................... 141 Figure 96: AP specific statistics ........................................................................................................ 142 Figure 97: List of current Active Firewall Sessions .......................................................................... 143 8 Unified Services Router User Manual Figure 98: List of connected 802.11 clients per AP ......................................................................... 144 Figure 99: List of LAN hosts .............................................................................................................. 145 Figure 100: List of current Active VPN Sessions ............................................................................. 146 9 Unified Services Router User Manual Chapter 1. Introduction D-Link Unified 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) tunnels, 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 Unified 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 performance resulting in high availability. The second WAN port can be configured as a DMZ port allowing you to isolate servers from your LAN. DSR-250N has a single WAN interface, and thus it 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, allowing for operation on either the 2.4 GHz or 5 GHz radio bands. Multiple In Multiple Out (MIMO) technology allows the DSR-500N and DSR-
DSR-250N and DSR-500N supports 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-250N, DSR-
500, DSR-500N, DSR-1000 and DSR-1000N are capable of simultaneously managing 5, 10, 20 Secure Sockets Layer (SSL) VPN tunnels respectively, 10 Unified Services Router User Manual 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 branch office connectivity through encrypted virtual links. The DSR-250N, DSR-500(N) and DSR-1000(N) support 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 WiFi 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 Unified 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 Unified Services Router. o Model numbers DSR-500/500N/1000/1000N GUI Menu Path/GUI Navigation Monitoring > Router Status Important note 11 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. interface (GUI) for management by using any web browser, such as Microsoft Internet Explorer or Mozilla Firefox:
graphical user Go to http://192.168.10.1 management login screen. Default login credentials for the management GUI:
Username: admin Password: admin If bar of the browser to access the router IP address in the navigation
. 2.1 LAN Configuration Setup > Network Settings > LAN Configuration 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 WLAN clients. The PCs in the LAN are assigned 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, DHCP relay can be used to forward DHCP lease information from another LAN 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 for LAN and
. eful for wireless disabled all DHCP clients receive the DNS IP addresses of the ISP. Unified Services Router User Manual 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). 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 accessing the router via changed IP address. before Subnet mask (factory default: 255.255.255.0). 2. In the DHCP section, select the DHCP mode:
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.10.100. These address. You may wish to save part of the subnet range for devices with statically assigned IP addresses in the LAN. Primary and Secondary DNS servers: If configured domain name system
(DNS) servers are available on the LAN enter their IP addresses here. WINS Server (optional): Enter the IP address for the WINS server or, if present in your network, the Windows NetBios server. 14 Unified Services Router User Manual Lease Time: Enter the time, in hours, for which IP addresses are leased to clients. Enable DNS Proxy: To enable the router to act as a proxy for all DNS 3. Click Save Settings to apply all changes. Figure 1: Setup page for LAN TCP/IP settings 15 Unified Services Router User Manual 2.1.1 LAN Configuration in an IPv6 Network Advanced > IPv6 > IPv6 LAN > IPv6 LAN Config In IPv6 mode, the LAN DHCP server is enabled 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 IPv6 configuration options. Advanced > IPv6 > IP mode to enable LAN Settings The default IPv6 LAN address for the router is 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 bits long. All hosts in the network have common initial bits for their IPv6 address;
fec0::1. You can change this 128 bit 64 length field. 16 Unified Services Router User Manual Figure 2: IPv6 LAN and DHCPv6 configuration 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 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. The following settings are used to configure the DHCPv6 server:
17 Unified Services Router User Manual 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 details from the ISP directly. By selecting Use DNS proxy, this router acts as a proxy for all DNS requests and communicates servers (a WAN configuration parameter). Primary and Secondary DNS servers: If there are 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 IP addresses you can automate the process of informing other networking equipment on the LAN of DHCP information specific for the assigned prefix. Using a delegation prefix 2.1.2 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 supporting 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. 18 Unified Services Router User Manual RADVD Advanced > IPv6 > IPv6 LAN > 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 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:
these flags. Chose Managed to use the administered /stateful 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 autoconfigured by the router. The default is 1500. Router Lifetime:
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 the host and this router. 19 Unified Services Router User Manual Figure 3: Configuring the Router Advertisement Daemon Advertisement Prefixes Advanced > IPv6 > IPv6 LAN > 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. 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. 20 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. Figure 4: IPv6 Advertisement Prefix settings 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 subnetwork defined by VLAN identifiers. LAN ports can be assigned unique VLAN IDs so that traffic to and from that physical port 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 disabled 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. Setup > VLAN Settings > Available VLAN 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 untagged frames received on the interface. By enabling Inter VLAN Routing, you 21 Unified Services Router User Manual 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. Figure 5: Adding VLAN memberships to the LAN 2.2.1 Associating VLANs to ports In order to tag all traffic through a specific LAN port with a VLAN ID, you can associate a VLAN to a physical port. Setup > VLAN Settings > 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 General, 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. 22 Unified Services Router User Manual Figure 6: Port VLAN list 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 the selected VLAN membership IDs 23 Unified Services Router User Manual Figure 7: Configuring VLAN membership for a port 2.3 Configurable Port: DMZ Setup DSR-250N does not have a configurable port there is no DMZ support. 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 subnetwork that is open to the public but behind the firewall. The DMZ adds an additional layer of security to the LAN, as specific services/ports that 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 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. Setup > DMZ Setup > DMZ Setup Configuration 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. 24 Unified Services Router User Manual Figure 8: DMZ configuration DMZ in the Setup > Internet Settings > Configurable Port page. 2.4 Universal Plug and Play (UPnP) Advanced > Advanced Network > 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. 25 Unified Services Router User Manual 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. Figure 9: UPnP Configuration UPnP Port map Table The UPnP Port map Table 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) 26 Unified Services Router User Manual 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 DSR-250N does not have support for the Captive Portal feature. 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 sc enario 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 prompt for a username /
password. The login credentials are compared against the RunTimeAuth users in user database prior to granting HTTP access. Captive Portal is available for LAN users only and not for DMZ hosts. Status > Active RunTime Sessions The Active Runtime internet sessions through below table. These users are present in the local or external user database and have had their login credentials approved for internet access. A allows the DSR admin to selectively drop an authenticated user. Figure 10: Active Runtime sessions 27 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. Figure 11: Internet Connection Setup Wizard 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 confirms the settings by establishing a link with the ISP. Once connected, you can move on and configure other features in this router. 28 Unified Services Router User Manual 3G Internet access with a USB modem is supported on the secondary WAN port
(WAN2). The Internet Connection Setup Wizard assists with the primary WAN port
(WAN1) configuration only. 3.2 WAN Configuration Setup > Internet Settings > WAN1 Setup 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:
PPPoE Profile Name. This menu lists configured PPPoE profiles, particularly useful when configuring multiple PPPoE connections (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. such case, user has to take care of routing manually by configuting the routing from Static Routing page. In 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 disconnecting in the Idle Time field. 29 Unified Services Router User Manual 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-
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 dynamically at each login. If static, enter your IP address, IPv4 subnet mask, and the 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 its latter, enter addresses for the primary and secondary DNS servers. To avoid connectivity problems, ensure that you enter the addresses correctly. 3.2.3 DHCP WAN For DHCP client connections, you can choose the MAC address of the router to register with the ISP. address if the ISP is registered with that LAN host. 30 Unified Services Router User Manual Figure 12: Manual WAN configuration 3.2.4 PPPoE Setup > Internet Settings The PPPoE ISP settings are defined on the WAN Configuration page. There are two types of PPPoE PPPoE and Japan Multiple PPPoE. supported by the DSR: the standard username/password 31 Unified Services Router User Manual Figure 13: PPPoE configuration for standard ISPs password credentials to login and authenticate the DSR with the ISP. The ISP GUI will prompt you for authentication, service, and connection settings in order to establish the PPPoE link. 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 traffic and the Secondary PPPoE connection carries ISP specific (i.e. control) traffic between the DSR and the ISP. Japanese 32 Unified Services Router User Manual Figure 14: WAN configuration for Japanese Multiple 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 The DSR acts as a DNS proxy for LAN users
(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. 33 Unified Services Router User Manual 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 15: WAN configuration for Multiple PPPoE (part 2) 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 34 Unified Services Router User Manual Figure 16: Russia L2TP ISP configuration 3.2.6 WAN Configuration in an IPv6 Network Setup > IPv6 > IPv6 WAN1 Config 35 Unified Services Router User Manual 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 connect to for accessing the internet. The primary and secondary DNS servers on the used for resolving internet addresses, and these are provided along with the static IP address and prefix length from the ISP. 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 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. For stateless DHCP 36 Unified Services Router User Manual Figure 17: IPv6 WAN Setup page 3.2.7 Checking WAN Status Setup > Internet Settings > WAN Status The status and summary of configured settings for both WAN1 and WAN2 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 IP or Static IP 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 37 Unified Services Router User Manual Figure 18: Connection Status information for both WAN ports 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. 38 Unified Services Router 3.3 Bandwidth Controls User Manual Advanced > Advanced Network > Traffic Management > Bandwidth Profiles 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 (like guests or HTTP service) do bandwidth-priority-allocation purposes. Bandwidth profiles configuration consists of enabling the bandwidth control feature from the GUI and adding a profile which defines the control 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 regulation.
-savings or Figure 19: List of Configured Bandwidth Profiles 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 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. 39 Unified Services Router User Manual 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. Figure 20: Bandwidth Profile Configuration page Advanced > Advanced Network > Traffic Management > 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 Custom Services page. To have the profile apply to all services, select ANY. Advanced > Firewall Settings >
Traffic Selector Match Type: this defines the parameter to 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. 40 Unified Services Router User Manual Figure 21: Traffic Selector Configuration 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. Setup > Internet Settings > 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 disconnected 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 link goes down for any reason. Both WAN ports (primary and secondary) must be configured to connect to the respective IS 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 both WAN1 and WAN2 can be configured as the primary internet link. The 41 Unified Services Router User Manual Auto-Rollover using WAN port-WAN1: WAN1 is the primary internet link. Auto-Rollover using WAN port-WAN2: WAN2 is the primary internet link. 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 are 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 connectivity 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. 3.4.2 Load Balancing 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. Spill Over : If Spill Over method is selected, WAN1 acts as a dedicated link till a threshold is reached. After this, WAN2 will be used for new connections. You can configure spill-over mode by using folloing options:
Load Tolerance: It is the percentage of bandwidth after which the router switches to seconday WAN. Max Bandwidth: This sets the maximum bandwidth tolerable by the primary WAN. If the link bandwidth goes above the load tolerance value of max bandwidth, the router will spill-over 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 everytime a new connection is established the bandwidth increases. After a certain number of connections say bandwidth reached 70% of 1Kbps, the new connections will be spilled-over to secondary WAN. The maximum value of load tolerance is 80 and the least is 20. Protocol Bindings : Refer Section 3.4.3 for details 42 Unified Services Router User Manual 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 22: Load Balancing is available when multiple WAN ports are configured and Protocol Bindings have been defined 3.4.3 Protocol Bindings Advanced > Routing > Protocol Bindings Protocol bindings are required 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 43 Unified Services Router User Manual addresses 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 23: Protocol binding setup to associate a service and/or LAN source to a WAN and/or destination network 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 Setup > Internet Settings > Routing Mode 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. 44 Unified Services Router User Manual 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. Transparent routing between the LAN and WAN does not perform NAT. 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) are supported in transparent mode assuming the LAN and WAN are configured to be in the same broadcast domain. users on the LAN and DMZ to access internal servers (eg. an internal FTP server) using their externally-
at allows internal network to reach LAN servers by their external name. 45 Unified Services Router User Manual Figure 24: Routing Mode is used to configure traffic routing between WAN and LAN, as well as Dynamic routing (RIP) 3.5.2 Dynamic Routing (RIP) DSR-250N does not support RIP. 46 Unified Services Router User Manual 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 from 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 Advanced > Routing > Static Routing 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 47 Unified Services Router User Manual router and other devices to account for 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 enabled. 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, DMZ or LAN), through which this route is accessible. Gateway: IP address of the gateway through which the destination 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. 48 Unified Services Router User Manual Figure 25: Static route configuration fields 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 enabled. Setup > Internet Settings > WAN2 Setup WAN2 configuration is identical to the WAN1 configuration with one significant exception: configuration for the 3G USB modem is available only on WAN2. 3G WAN support is available on the dual WAN products: DSR-1000 and DSR-
1000N. 49 Unified Services Router User Manual Figure 26: WAN2 configuration for 3G internet (part 1) Cellular 3G internet access is available on WAN2 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 (
Status) and Enable the WAN2 link to establish the 3G connection. Setup > Internet Settings > WAN 50 Unified Services Router User Manual Figure 27: WAN2 configuration for 3G internet (part 2) 3.7 WAN Port Settings Advanced > Advanced Network > WAN Port Setup 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 information 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. 51 Unified Services Router User Manual The default MAC address is defined during the manufacturing process for the interfaces, and can uniquely identify this router. You can customize each W MAC address as needed, either by letting the WAN port assume the current LAN Figure 28: Physical WAN port settings 52 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. The content in this section is applicable to the DSR-500N and DSR-1000N products. Up to four unique wireless networks can be created 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 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-
network on your LAN and allow supported 802.11 clients to connect to the configured Access Point. 53 Unified Services Router User Manual Figure 29: Wireless Network Setup Wizards 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 either 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 pre-shared key for WPA or WPA2 type security. Supported clients that have been given this PSK can associate with this AP. The default (auto-assigned) 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:
54 Unified Services Router User Manual 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. 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 Points page. The manual options allow you to create new APs or modify the parameters of APs created by the Wizard. Setup> Wireless Settings> Access 4.2 Wireless Profiles Setup > Wireless Settings > Profiles The profile allows you to assign the security type, encryption and authentication to use when connecting the AP to a wireless security. This mode is insecure as it allows any compatible wireless clients to connect 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 profile. By choosing to broadcast the SSID, availability. The AP offers all advanced 802.11 security modes, including WEP, WPA, WPA2 and WPA+WPA2 options. The security of the Access point is configured by the Wireless Security Type section:
Open 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 55 Unified Services Router User Manual 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. 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 30: List of Available Profiles shows the options available to secure the wireless 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 generated from an easy-to-remember 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 a alphanumeric phrase and click Generate Key to generate 4 unique WEP keys with length determined by the encryption key 56 Unified Services Router User Manual 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. Figure 31: Profile configuration to set network security 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. 57 Unified Services Router User Manual 4.2.3 RADIUS Authentication Setup > Wireless Settings > RADIUS Settings Enterprise Mode 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. 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. 58 Unified Services Router User Manual Figure 32: RADIUS server (External Authentication) configuration 4.3 Creating and Using Access Points Setup > Wireless Settings > 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. points (VAPs). Each virtual AP that has a unique SSIDs appears as an independent access point to clients. configured in a way to optimize security and throughput for a group of clients as radio to be Wireless Settings > Access Points dropdown menu is used to select one of the configured profiles. page. After setting the AP name, the profile Setup >
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. 59 Unified Services Router User Manual Figure 33: Virtual AP configuration A valuable power saving feature is 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 access point automatically. Once the AP settings are configured, you must enable the AP on the radio on the Setup > Wireless Settings > Access Points page. The status field changes to 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. 60 Unified Services Router User Manual Figure 34: List of configured access points (Virtual APs) shows one enabled access point on the radio, broadcasting its 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 connected client will give the detailed send and receive traffic statistics for the wireless link between this AP and the client. 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 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. remember, Optimize security: you may wish to support 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 61 Unified Services Router User Manual 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 Setup > Wireless Settings > Radio Settings The Radio Settings page lets you configure the channels and power levels available 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. Figure 35: Radio card configuration options 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. 62 Unified Services Router 4.5 Advanced Wireless Settings Advanced > Wireless Settings > Advanced Wireless 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. User Manual Figure 36: Advanced Wireless communication settings 4.6 Wi-Fi Protected Setup (WPS) Advanced > Wireless Settings > 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. setup options available for WPS:
Personal Identification Number (PIN):
The wireless device that supports WPS There are two may have an alphanumeric PIN, if so add the PIN in this field. The router will 63 Unified Services Router User Manual below the 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 wireless 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. Figure 37: WPS configuration for an AP with WPA/WPA2 profile 64 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 (examples: 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
(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 Advanced > Firewall Settings > 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. address known depends on how the WAN ports are configured; for this router you Unified Services Router User Manual 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. You can change this default behavior in the Settings > Default Outbound Policy allow always, you can to block hosts on the LAN from accessing internet services by creating an outbound firewall rule for each service. page. When the default outbound policy is Firewall Figure 38: List of Available Firewall Rules 5.2 Defining Rule Schedules Tools > 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. 66 Unified Services Router User Manual Figure 39: List of Available Schedules to bind to a firewall rule 5.3 Configuring Firewall Rules Advanced > Firewall Settings > 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 Edit configuration page. To add a new rule, click 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:
67 Unified Services Router User Manual 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 by 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) Log: traffic that is filtered by this rule can be logged; this requires configuring 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. 68 Unified Services Router User Manual 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). 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 next 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. 69 Unified Services Router User Manual Figure 40: 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) 70 Unified Services Router User Manual Figure 41: The firewall rule configuration page allows you to define the To/From zone, service, action, schedules, and specify source/destination IP addresses as needed. 71 Unified Services Router User Manual 5.3.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 Value Insecure (WAN1/WAN2) Public (DMZ) HTTP ALLOW always Send to Local Server (DNAT IP) 192.168.5.2 (web server IP address) Destination Users Log Any Never Example 2: Allow videoconferencing from range of outside IP addresses 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) Secure (LAN) CU-SEEME:UDP ALLOW always 192.168.10.11 Address Range 132.177.88.2 134.177.88.254 Yes (enabled) 72 Unified Services Router User Manual 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 Value Parameter From HTTP Action Service To Zone From Zone Public (DMZ) Single Address ALLOW always Destination Users Insecure (WAN1/WAN2) Send to Local Server (DNAT IP) 192.168.12.222 ( web server local IP address) E x a m p l e 4
B l o Log c 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:
WAN Users 10.1.0.52 Never Any To setup a schedule that affects traffic on weekends only, navigate to Security: Schedule, and morning all day Saturday & Sunday 73 Unified Services Router User Manual In the Scheduled days box, check that you want the schedule to be active for In the scheduled time o this will apply the schedule between 12 am to 11:59 pm of the selected day. Click apply now s Sunday from the rest of the week. isolates all day Saturday and 74 Unified Services Router User Manual Figure 42: Schedule configuration for the above example. 2. Since we are trying to block HTTP requests, it is a service with To Zone: Insecure
(WAN1/WAN2) that is to be blocked according to schedule
. 75 Unified Services Router User Manual 3. S 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 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. 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 7. We d will add this firewall rule to the list of firewall rules. 8. The last step is to enable this firewall rule. Select list to make sure the firewall rule is active 5.4 Security on Custom Services clicking apply Advanced > Firewall Settings > 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. 76 Unified Services Router User Manual Figure 43: List of user defined services. 5.5 ALG support Advanced > Firewall Settings > 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 firewall. 77 Unified Services Router User Manual Figure 44: Available ALG support on the router. 5.6 VPN Passthrough for Firewall Advanced > Firewall Settings > VPN Passthrough 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. 78 Unified Services Router User Manual Figure 45: Passthrough options for VPN tunnels 5.7 Application Rules Advanced > Application Rules > Application Rules Application rules are also referred to as port 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 receive 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 outbound 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. 79 Unified Services Router User Manual Figure 46: List of Available Application Rules showing 4 unique rules 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.8 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. 5.8.1 Content Filtering Advanced > Website Filter > Content 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. 80 Unified Services Router User Manual Figure 47: Content Filtering used to block access to proxy servers and prevent ActiveX controls from being downloaded 5.8.2 Approved URLs Advanced > Website Filter > Approved URLs The Approved URLs is an acceptance list for all URL domain names. Domains added to this list are allowed in any form. m the LAN:
www.yahoo.com , yahoo.co.uk, etc. 81 Unified Services Router User Manual Figure 48: Two trusted domains added to the Approved URLs List 5.8.3 Blocked Keywords Advanced > Website Filter > Blocked Keywords 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. ite content that contains 82 Unified Services Router User Manual Figure 49: Two keywords added to the block list 5.9 IP/MAC Binding Advanced > IP/MAC Binding 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 address bound to it. 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 address having the same IP address) the packets will be dropped and can be logged for diagnosis. 83 Unified Services Router User Manual Figure 50: The following example binds a 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 5.10 Intrusion Prevention (IPS) Advanced > Advanced Network > IPS 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. 84 Unified Services Router User Manual Figure 51: Intrusion Prevention features on the router 5.11 Protecting from Internet Attacks Advanced > Advanced Network > 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 attacks, 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. 85 Unified Services Router User Manual Figure 52: Protecting the router and LAN from internet attacks 86 Unified Services Router User Manual Chapter 6. IPsec / PPTP / L2TP VPN 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 initiates a VPN tunnel as the IP address of the remote PC client is not known in advance. The gateway 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 initiates a VPN tunnel as the IP address of the remote NAT router is not known in advance. The gateway WAN port acts as responder. PPTP server for LAN / WAN PPTP client connections. L2TP server for LAN / WAN L2TP client connections. Figure 53: Example of Gateway-to-Gateway IPsec VPN tunnel using two DSR routers connected to the Internet 87 Unified Services Router User Manual Figure 54: Example of three IPsec client connections to the internal network through the DSR IPsec gateway 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 can modify it as required. 88 Unified Services Router User Manual Figure 55: VPN Wizard launch screen 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 Determine the local gateway for this tunnel; if there is more than 1 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:
static IP address 89 Unified Services Router User Manual Local WAN IP address / FQDN: This field can be left blank if you are not using a configuration. 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 a 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 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) Encryption Algorithm Authentication Algorithm 3DES SHA-1 Authentication Method Pre-shared Key PFS Key-Group Life Time (Phase 1) Life Time (Phase 2) NETBIOS 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. 90 User Manual Unified Services Router 6.2 Configuring IPsec Policies Setup > VPN Settings > IPsec > IPsec Policies An IPsec policy is between this router and another gateway or this router and a 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 local and remote private networks that can communicate over the tunnel. 91 Unified Services Router User Manual Figure 56: IPsec policy configuration 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 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 required 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 92 Unified Services Router User Manual Figure 57: IPsec policy configuration continued (Auto policy via IKE) 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 establish 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 on primary WAN will rollover to the seconday WAN incase of a link failure on a primary WAN. This feature can be used only if your WAN is configured in Auto-Rolleover mode. 93 Unified Services Router User Manual Figure 58: IPsec policy configuration continued (Auto / Manual Phase 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 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. PAP, the router 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. 94 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 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 populate 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 Setup > VPN Settings > PPTP > PPTP 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 ro by the PPTP server (the tunnel endpoint), PPTP clients have access to the network managed by the router. Once authenticated 95 Unified Services Router User Manual Figure 59: PPTP tunnel configuration PPTP Server 6.4.2 L2TP Tunnel Support Setup > VPN Settings > L2TP > L2TP 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 by the L2TP server (the tunnel endpoint), L2TP clients have access to the network managed by the router. Once authenticated Figure 60: L2TP tunnel configuration L2TP Server 96 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 pre-
installed 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 remot 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 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 accesses 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 61: Example of clientless SSL VPN connections to the DSR 7.1 Users, Groups, and Domains Advanced > Users > Users Authentication of the users (IPsec, SSL VPN, or GUI) is done by the router using either a local database on the router or external authentication servers (i.e. LDAP or RADIUS). The remote user must specify the user, group and domain when logging in to the router. One or more users are members of a Group. One or more Groups belong to an authentication Domain. The user settings contain the following:
User Name: This is unique identifier of the user. Us administrator, guest, XAUTH user, L2TP user, PPTP user, Local User. The SSL VPN User or administrator user should be selected. Select Group: A group is chosen from a list of configured groups. Password: The password associated with the user name. Confirm Password: The same password as above is required to mitigate against typing errors. 98 Unified Services Router User Manual Idle Timeout: The session timeout for the user. Once the user is configured, the DSR will display a list of all configured users. Figure 62: Available Users with login status and associated Group/Domain Advanced > Users > Domains The Domain determines the authentication method (local user database, external server) to be us determines the portal layout presented to the remote SSL user. Since the portal layout assigns access to SSL VPN tunnel and/or SSL VPN Port Forwarding features, the domain is essential in defining the authentication and features exposed to SSL users. The following information is used to configure a domain:
As well the Domain Domain Name: The unique identifier of the domain. Authentication Type: The authentication type can be one of the following:
Local User Database, Radius-PAP, Radius-CHAP, Radius-MSCHAP, Radius-
MSCHAPv2, NT Domain, Active Directory, and LDAP. Authentication Server: If the SSL VPN connection will use an authentication method other than the Local User Database (such as a RADIUS server), then the sever access details are needed. If there are multiple authentication servers, user can enter the details for upto three authentication servers. 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). 99 Unified Services Router User Manual Timeout: The timeout period for reaching the authentication server. Retries: The number of retries to authenticate with the authentication server after which the DSR stops trying to reach the server. Workgroup: This is required is for NT domain authentication. If there are multiple workgroups, user can enter the details for upto two workgroups. LDAP Base DN: This is the base domain name for the LDAP authentication server. If there are multiple LDAP authentication servers, user can enter the details for upto two 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 upto two authentication domains. Once the domain is configured, the DSR will display a list of all configured domains. Advanced > Users > Groups Groups are used to assign access policies to a set of SSL users within a domain. Groups are domain subsets that can be seen as types of SSL users; some groups require access to all available network resources and some can be provided access to a select few. With groups, a very secure hierarchy of SSL VPN remote access can be created for all types of users with minimal number of policies to configure. To configure a group in the DSR, enter the following information:
Name: This is a unique identifier for a group name. Domain: This is the authenticating domain the group is attached to. Idle timeout: This is the log in timeout period for users of this group. Once the group is defined the DSR will display a list of all configured groups. You must create a Domain first, and then a new Group can be created and assigned to the Domain. The last step is to add specific SSL VPN users to an already-
configured Group. 7.1.1 User Types and Passwords Advanced > Users > Users User level policies can be specified by browser, IP address of the host, and whether following user types are assigned to a user that reaches the GUI login screen from the LAN or WAN:
The Administrator:
-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. 100 Unified Services Router User Manual Guest (read only): The guest user gains read only access to the GUI to observe and review configuration settings. The guest does not have SSL VPN access. SSL VPN 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. XAuth User:
RADIUS or other Enterprise server. It is not part of the local user database. L2TP User: These are L2TP VPN tunnel LAN users that can establish a tunnel with the L2TP server on the WAN. PPTP User: These are PPTP VPN tunnel LAN users that can establish a tunnel with the PPTP server on the WAN. Local User:
Once the user type is determined, you can define/modify the password and idle login 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. 101 Unified Services Router User Manual Figure 63: User configuration options 7.2 Using SSL VPN Policies Setup > VPN Settings > SSL VPN Server > SSL VPN Policies 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. 102 Unified Services Router User Manual Figure 64: List of SSL VPN polices (Global filter) 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 appropriate 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) Once defined, the policy goes into effect immediately. 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. 103 Unified Services Router User Manual Figure 65: SSL VPN policy configuration 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. 104 Unified Services Router User Manual 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 Permission: The assigned resources defined by this policy can be explicitly permitted or denied. 7.2.1 Using Network Resources Setup > VPN Settings > SSL VPN Server > 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). 105 Unified Services Router User Manual Figure 66: List of configured resources, which are available to assign to SSL VPN 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 accessible to remote users. Allowing access to a LAN server requires entering the local server IP 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 Port Number 20 21 22 23 25 80 110 123 1494 3389 VNC (virtual network computing) 5900 or 5800 106 Unified Services Router User Manual 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 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 the local server which is hosting 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 name 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 forwarding 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. 107 Unified Services Router User Manual Figure 67: List of Available Applications for SSL Port Forwarding 7.4 SSL VPN Client Configuration Setup > VPN Settings > SSL VPN Client > SSL VPN Client 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 the 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. Th being accessed through the SSL VPN tunnel. 108 Unified Services Router User Manual Figure 68: SSL VPN client adapter and access configuration 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 router. 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. 109 Unified Services Router User Manual Setup > VPN Settings > SSL VPN Client > Configured 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 LA
(typically this router) is needed to forward private traffic through the VPN Firewall to the remote SSL VPN client. When split tunnel mode is enabled, the user is required to to configure routes for VPN tunnel clients:
Destination network: The network address of the LAN or the subnet perspective is set here. Subnet mask: The subnet information of the destination network is set here. Figure 69: Configured client routes only apply in split tunnel mode 7.5 User Portal Setup > VPN Settings > SSL VPN Client > SSL VPN Client Portal 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 domain determines the authentication method and portal layout screen presented to the remote user. 110 Unified Services Router User Manual Figure 70: List of configured SSL VPN portals. The configured portal can then be associated with an authentication domain 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. The default portal LAN IP address is bin/userPortal/portal. link is clicked on the SSL VPN menu of the router GUI. https://192.168.10.1/scgi-
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 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 to login. This field is optional. 111 Unified Services Router User Manual 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 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. It is Once the portal settings are configured, the newly configured portal is added to the list of portal layouts. Figure 71: SSL VPN Portal configuration 112 Unified Services Router User Manual Chapter 8. Advanced Configuration Tools 8.1 USB Device Setup Setup > USB Settings The DSR Unified 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 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 DSR 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, follow below given steps:
Click 'Start' on the desktop. 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. 113 Unified Services Router User Manual Figure 72: USB Device Detection 8.2 Authentication Certificates Advanced > 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 network VPN solutions. 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 invalid 114 Unified Services Router User Manual A self certificate is a certificate issued by a CA identifying your device (or self-
t 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. you 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 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 passing it along to the CA for signing. Once signed, the C 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 ty. 115 Unified Services Router User Manual Figure 73: Certificate summary for IPsec and HTTPS management 8.3 Advanced Switch Configuration The DSR allows you to adjust the power consumption of the hardware based on your for your LAN switch are Power function of on the number of connected ports. The overall current draw when a single consumption by the LAN switch is dependent 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. 116 Unified Services Router User Manual Figure 74: Advanced Switch Settings 117 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 HTTP, or over SSL). Administrator interface. The user type is set in the Guest user can be configured to access the router GUI from the LAN or the Internet
(WAN) by enabling the corresponding Login Policy. Advanced > Users > Users page. The Admin or Figure 75: User Login policy configuration 9.1.1 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. 118 Unified Services Router User Manual Figure 76: Remote Management from the WAN 9.1.2 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. console prompt and login with administrator user credentials. 9.2 SNMP Configuration Tools > Admin > SNMP SNMP is an additional management 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 manager can 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. o view or update configuration 119 Unified Services Router User Manual Figure 77: SNMP Users, Traps, and Access Control Tools > Admin > 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 identify the router for SysLog logging. 120 Unified Services Router User Manual Figure 78: SNMP system information for this router 9.3 Configuring Time Zone and NTP Tools > Date and Time You can configure your time zone, whether or not to adjust for Daylight 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 internet, the most accurate mechanism to set the router time is to enable NTP server communication. If the router has access to the 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 accurate logging. Please follow the steps below to configure the NTP server:
1. Select 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. 121 Unified Services Router User Manual Figure 79: Date, Time, and NTP server setup 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 settings and the ways you can access these logs. 9.4.1 Defining What to Log Tools > Log Settings > Logs Facility 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. 122 Unified Services Router User Manual 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 facitlity corresponds to IPS (Intrusion Prevension 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 severity 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:
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 123 Unified Services Router User Manual Figure 80: Facility settings for Logging The display for logging can be customized based on where the logs are sent, either the Event Log viewer in the GUI (the Event Log viewer is in the 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. Status > Logs Tools > Log Settings > Logs Configuration 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. 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 Ou monitor traffic that is passed through the firewall. 124 Unified Services Router User Manual 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 Ou 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 set 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. 125 Unified Services Router User Manual Figure 81: Log configuration options for traffic through router 9.4.2 Sending Logs to E-mail or Syslog Tools > Log Settings > Remote Logging 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 Once you enable the option to e-mail logs, enter the e-
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 addresses can be configured as log recipients. In order to establish a connection with the configured SMTP port and server, define 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
Up to three e-
126 Unified Services Router User Manual 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 82: E-mail configuration as a Remote Logging option 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 than 127 Unified Services Router User Manual 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. This router supports up to 8 concurrent Syslog servers. Each can be configured to receive different log facility messages of varying severity. To enable a Syslog server select the checkbox next to an empty Syslog 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) Syslog server once you save this configuration Figure 83: Syslog server configuration for Remote Logging (continued) 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 Configuration pages, the corresponding log message will be displayed in this window with a timestamp. or Tools > Log Settings > Logs It is very important to have accurate system time (manually set or from a NTP server) in order to understand log messages. Status > Logs > 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. 128 Unified Services Router User Manual Figure 84: VPN logs displayed in GUI event viewer 9.5 Backing up and Restoring Configuration Settings Tools > System You can back up 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. custom configuration settings to restore them to a 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. 129 Unified Services Router User Manual 2. To restore your saved settings from a backup file, click Browse then locate the file on the host. settings. After the restore, the router reboots automatically with the restored settings. 3. 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 85: Restoring configuration from a saved file will result in the current configuration being overwritten and a reboot 9.6 Upgrading Router Firmware Tools > Firmware 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 Device Info > Device Status page will reflect the new firmware version. Status >
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 process. 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 low-level process of restoring the flash firmware (not through the web GUI). 130 Unified Services Router User Manual Figure 86: Firmware version information and upgrade option 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. 9.7 Dynamic DNS Setup Tools > Dynamic DNS 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 DynDNS.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 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. 131 Unified Services Router User Manual Figure 87: Dynamic DNS configuration 9.8 Using Diagnostic Tools Tools > System Check The router has built in tools to allow an administrator to evaluate the communication status and overall network health. 132 Unified Services Router User Manual Figure 88: Router diagnostics tools available in the GUI 9.8.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.8.2 Trace Route This utility will display all the routers present between the destination IP address destination will be displayed. 133 Unified Services Router User Manual Figure 89: Sample traceroute output 9.8.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 This feature assumes there is internet access available on the WAN link(s). 9.8.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. 134 Unified Services Router User Manual Chapter 10. Router Status and Statistics 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 10.1.1 Device Status Status > Device Info > Device Status 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. 135 Unified Services Router User Manual Figure 90: Device Status display 136 Unified Services Router User Manual Figure 91: Device Status display (continued) 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. 137 Unified Services Router User Manual Figure 92: Resource Utilization statistics 138 Unified Services Router User Manual Figure 93: Resource Utilization data (continued) 139 Unified Services Router User Manual Figure 94: Resource Utilization data (continued) 10.2 Traffic Statistics 10.2.1 Wired Port Statistics Status > Traffic Monitor > 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. 140 Unified Services Router User Manual Figure 95: Physical port statistics 10.2.2 Wireless Statistics Status > Traffic Monitor > 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 through the VAP. The clients connected to a particular AP can be viewed by using the Status Button on the list of APs in the Setup > Wireless > Access Points are shown for that individual AP, as compared to the summary stats for each 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. page. Traffic statistics 141 Unified Services Router User Manual Figure 96: AP specific statistics 10.3 Active Connections 10.3.1 Sessions through the Router Status > Active Sessions This table lists the active internet sessions through the state, local and remote IP addresses are shown. The 142 Unified Services Router User Manual Figure 97: List of current Active Firewall Sessions 143 Unified Services Router User Manual 10.3.2 Wireless Clients Status > 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 used by the wireless link, as well as the time connected to the corresponding AP. 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 98: List of connected 802.11 clients per AP 10.3.3 LAN Clients Status > LAN Clients The LAN clients to the router are identified by an ARP scan through the LAN switch. The NetBios name (if available), IP address and MAC address of discovered LAN hosts are displayed. 144 Unified Services Router User Manual Figure 99: List of LAN hosts 10.3.4 Active VPN Tunnels Status > Active VPNs associations. Here, the active IPsec SAs (security associations) are listed along with the traffic details and tunnel state. The traffic is a cumulative measure of transmitted/received packets since the tunnel was established. IPsec security the Connect button of the corresponding policy. The Active IPsec SAs table displays a list of active IPsec SAs. Table fields are as follows. IPsec Field Description Policy Name IKE or VPN policy associated with this SA. Endpoint Tx (KB) IP address of the remote VPN gateway or client. Kilobytes of data transmitted over this SA. Tx (Packets) Number of IP packets transmitted over this SA. State Status of the SA for IKE policies: Not Connected or IPsec SA Established. 145 Unified Services Router User Manual Figure 100: List of current Active VPN Sessions 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. Field Description User Name The SSL VPN user that has an active tunnel or port forwarding session to this router. IP Address IP address of the remote VPN client. Local PPP Interface The interface (WAN1 or WAN2) through which the session is active. Peer PPP Interface IP The assigned IP address of the virtual network adapter. Connect Status Status of the SSL connection between this router and the remote VPN client: Not Connected or Connected. 146 Unified Services Router User Manual Chapter 11. Trouble Shooting 11.1 Internet connection Symptom:
your LAN. Recommended action:
1. Check the Ethernet connection between the PC and the router.
-configuration interface from a PC on 2. 3. 4. address is on the same subnet as the router. If you are using the 0.2 to 192.168.10.254. 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. know what it is, reset the router 0.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 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. 147 Unified Services Router User Manual Symptom: Router cannot access the Internet. 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. 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 there 6. If yes, inform your ISP that you have bought a new network device, and ask them to use 7. Alternatively, select Network Configuration > WAN Settings > Ethernet ISP Settings and configure your 148
1 | User manual 2 of 2 | Users Manual | 2.08 MiB |
Unified Services Router User Manual Symptom: Router can obtain an IP address, but PC is unable to load Internet pages. 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 t ime 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 ver y ea sy 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 PCs Windows toolbar, select Start > Run. 2. Type ping <IP_address> where <IP_address> is the routers IP address. Example: ping 192.168.10.1. 3. Click OK. 149 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 page 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 PCs 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 ISPs 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 PCs Network C ontrol Panel.) 150 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 t he 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 factor y-default configuration settings, do either of the following:
1. Do you know the account password and IP address?
If yes, select Administration > Settings Backup & Upgrade and click default. If no, do the following:
On the rear panel of the router, press and hold the Reset button about 10 seconds, until the test LED lights and then blinks. 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: password DHCP server on LAN: enabled WAN port configuration: Get configuration via DHCP 151 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 User Manual Appendix A. Glossary ARP CHAP DDNS DHCP DNS FQDN FTP HTTP IKE IPsec Address Resolution Protocol. Broadcast protocol for mapping IP addresses to MAC addresses. Challenge-Handshake Authentication Protocol. Protocol for authenticating users to an ISP. 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). ISAKMP Internet Key Exchange Security Protocol. Protocol for establishing security associations and cryptographic keys on the Internet. ISP Internet service provider. MAC Address Media-access-control address. Unique physical-address identifier attached to a network adapter. MTU NAT 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 LANs gateway router. NetBIOS Microsoft Windows protocol for file sharing, printer sharing, messaging, authentication, and name resolution. NTP PAP 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. 154 Unified Services Router User Manual PPPoE PPTP RADIUS RSA TCP UDP VPN WINS XAUTH 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. 155 Appendix B. Factory Default Settings Featur e Description User login URL Device login User name (case sensitive) Login password (case sensitive) Default Setting http://192.168.10.1 admin admin WAN MAC address Use default address Internet Connection WAN MTU size Local area network
(LAN) Port speed IP address IPv4 subnet mask RIP direction RIP version RIP authentication DHCP server DHCP starting IP address DHCP ending IP address Time zone Time zone adjusted for Daylight Saving Time SNMP Remote management 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 Inbound communications from the Internet Disabled (except traffic on port 80, the HTTP port) Firewall Outbound communications to the Internet Enabled (all) Source MAC filtering Stealth mode Disabled Enabled Unified Services Router User Manual Appendix C. Standard Services Available for Port Forwarding
& Firewall Configuration 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 ANY AIM BGP BOOTP_CLIENT ICMP-TYPE-8 ICMP-TYPE-9 ICMP-TYPE-10 ICMP-TYPE-11 BOOTP_SERVER ICMP-TYPE-13 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 ICQ IMAP2 IMAP3 IRC NEWS NFS NNTP PING POP3 PPTP RCMD REAL-AUDIO REXEC 158 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 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 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 nimfAdvOptSetWrap: NIMF table is %s nimfAdvOptSetWrap:WAN_MODE TRIGGER nimfAdvOptSetWrap: MTU: %d nimfAdvOptSetWrap: MacAddress: %s nimfAdvOptSetWrap: old Mtu Flag: %d Log Message BridgeConfig: too few arguments to command %s BridgeConfig: too few arguments to command %s sqlite3QueryResGet failed.Query:%s ddnsDisable failed sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s ddnsDisable failed failed to call ddns enable ddnsDisable failed Severity ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR sqlite3QueryResGet failed.Query:%s Error in executing DB update handler ERROR ERROR ERROR sqlite3QueryResGet failed.Query:%s ERROR Illegal invocation of ddnsView (%s) ERROR sqlite3QueryResGet failed.Query:%s ERROR sqlite3QueryResGet failed.Query:%s ddns: SQL error: %s ERROR Illegal operation interface got deleted ERROR ERROR sqlite3QueryResGet failed.Query:%s ERROR sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s ERROR Severity DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG ddnsDisable failed ddns: SQL error: %s DEBUG Failed to call ddns enable DEBUG ddns: SQL error: %s ERROR ERROR ERROR ERROR DEBUG sqlite3QueryResGet failed.Query:%s ERROR DEBUG Failed to call ddns enable DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG ddns: SQL error: %s ddnsDisable failed ddns: SQL error: %s sqlite3QueryResGet failed.Query:%s Failed to call ddns enable ddns: SQL error: %s ddnsDisable failed ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR 159 Unified Services Router User Manual DEBUG DEBUG DEBUG DEBUG nimfAdvOptSetWrap: user has changed MTU option nimfAdvOptSetWrap: MTU: %d nimfAdvOptSetWrap: old MTU size: %d nimfAdvOptSetWrap: old Port Speed Option: %d nimfAdvOptSetWrap: old Mac Address Option: %d nimfAdvOptSetWrap: MacAddress: %s Setting LED [%d]:[%d] For %s l2tpEnable: command string: %s nimfAdvOptSetWrap: handling reboot scenario DEBUG nimfAdvOptSetWrap: INDICATOR = %d DEBUG nimfAdvOptSetWrap: UpdateFlag: %d DEBUG nimfAdvOptSetWrap: returning with status: %s nimfGetUpdateMacFlag: MacTable Flag is: %d DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG ddns: SQL error: %s sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s ddnsDisable failed ddns: SQL error: %s sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s ddnsDisable failed failed to call ddns enable ddns: SQL error: %s ddnsDisable failed ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR sqlite3QueryResGet failed.Query:%s ERROR nimfMacGet: Mac Option changed nimfMacGet: Update Flag: %d nimfMacGet: MacAddress: %s nimfMacGet: MacAddress: %s nimfMacGet: MacAddress: %s nimfMacGet: MacAddress: %s nimfMacGet: MacAddress: %s nimfMacGet:Mac option Not changed \
nimfMacGet: MacAddress: %s nimfMacGet: MacAddress: %s nimfMacGet: MacAddress: %s nimfMacGet: returning with status: %s Now in enableing LanBridge function sucessfully executed the command %s Now in disableing LanBridge function sucessfully executed the command %s configPortTblHandler:Now we are in Sqlite Update "
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 failed query %s
%s:DBUpdate event: Table: %s opCode:%d rowId:%d Error in executing DB update handler Failed to open the resolv.conf file. Exiting./n Could not write to the resolv.conf file. Exiting. Error opening the lanUptime File Error Opening the lanUptime File. failed to open %s failed to open %s failed to query networkInterface table failed to query networkInterface table sqlite3QueryResGet failed.Query:%s failed to enable IPv6 forwarding failed to set capabilities on the "
failed to enable IPv6 forwarding failed to set capabilities on the "
failed to disable IPv6 forwarding failed to set capabilities on the "
failed to open %s DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR DEBUG Could not create ISATAP Tunnel DEBUG Could not destroy ISATAP Tunnel ERROR DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG Could not configure ISATAP Tunnel Could not de-configure ISATAP Tunnel nimfStatusUpdate: updating NimfStatus failed nimfStatusUpdate: updating NimfStatus failed nimfLinkStatusGet: determinig link's status failed nimfLinkStatusGet: opening status file failed ERROR ERROR ERROR ERROR ERROR ERROR 160 Unified Services Router User Manual
%s:DBUpdate event: Table: %s opCode:%d rowId:%d
%s:%d SIP ENABLE: %s sipTblHandler:failed to update ifStatic sipTblHandler:failed to update Configport DEBUG %s: Failed to commit "
DEBUG DEBUG DEBUG %s: SQL error: %s Failed to commit ifStatusDBUpdate: Failed to begin "
%s:%d SIP DISABLE: %s
%s:%d SIP SET CONF: %s DEBUG DEBUG DEBUG DEBUG %s: unable to kill dhclient 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 nimfNetIfaceTblHandler: unable to get LedPinId nimfNetIfaceTblHandler: unable to get LedPinId nimfNetIfaceTblHandler: unable to get LedPinId 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 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 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 nimfAdvOptSetWrap: interface advanced options applied DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG 161 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 pSshdEnable: %s Unified Services Router User Manual 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 Apn: %s 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 DEBUG DEBUG DEBUG DEBUG DEBUG nimfGetUpdateMacFlag: unable to get Flag from MacTable nimfMacGet: Updating MAC address failed sqlite3QueryResGet failed.Query:%s error executing the command %s error executing the command %s error executing the command %s disableLan function is failed to disable ConfigPort"
sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s Unable to Disable configurable port from configPortTblHandler has failed sqlite3QueryResGet failed.Query:%s Error in executing DB update handler sqlite3QueryResGet failed Failed to execute switchConfig for port\
Failed to execute switchConfig for port enable Failed to execute ifconfig for port enable Failed to execute ethtool for\
Failed to execute switchConfig for port disable Failed to execute ifconfig for port disable sqlite3QueryResGet failed sqlite3_mprintf failed sqlite3QueryResGet failed Failed to execute switchConfig for port mirroring Usage:%s <DB Name> <Entry Name> <logFile> <subject>
sqlite3QueryResGet failed Could not get all the required variables to email the Logs. runSmtpClient failed getaddrinfo returned %s file not found sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s No memory to allocate Failed to Open SSHD Configuration File Ipaddress should be provided with accessoption 1 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 162 Unified Services Router User Manual GetDnsFromIsp: %s IdleTimeOutFlag: %s IdleTimeOutValue: %d AuthMetho: %d executing %s ... %s removing %s from bridge%d... %s adding %s to bridge%d... %s DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG stopping bridge... restarting bridge... Could not configure 6to4 Tunnel Interface Could not de-configure 6to4 Tunnel Interface failed to restart 6to4 tunnel interfaces BridgeConfig: too few arguments to DEBUG command %s BridgeConfig: unsupported command %d DEBUG DEBUG DEBUG DEBUG BridgeConfig returned error=%d sqlite3QueryResGet failed Error in executing DB update handler sqlite3QueryResGet failed Failed to remove vlan Interface for vlanId
sqlite3QueryResGet failed Invalid oidp passed Invalid oidp passed Failed to get oid from the tree threegEnable: Input to wrapper %s threegEnable: spawning command %s 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
%s: SQL get query: %s
%s: sqlite3QueryResGet failed
%s: no result found DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG Subnetaddress should be provided with accessoption 2 Failed to restart sshd unable to open the "
sqlite3QueryResGet failed.Query:%s Error in executing DB update handler Error in executing DB update handler unknown vlan state Failed to execute vlanConfig binary for vlanId %d sqlite3_mprintf failed Access port can be present only in single vlan Failed to execute vlanConfig binary for vlanId %d unknown vlan state Failed to execute vlanConfig binary for port number %d Failed to clear vlan for oldPVID %d Failed to execute vlanConfig binary for port number %d Failed to clear vlan for %d Failed to set vlan entry for vlan %d Failed to set vlan entries, while enabling \
sqlite3QueryResGet failed Failed to execute vlanConfig binary for port number %d Failed to execute vlanConfig binary for vlanId %d Failed to enable vlan Failed to disable vlan Failed to set vlanPort table entries, while \
Failed to enable vlan unknown vlan state 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 in executing DB update handler ERROR unknown vlan state ERROR Failed to execute vlanConfig binary for vlanId %d ERROR sqlite3_mprintf failed Access port can be present only in single vlan Failed to execute vlanConfig binary for vlanId %d unknown vlan state Failed to execute vlanConfig binary for port number %d Failed to clear vlan for oldPVID %d Failed to execute vlanConfig binary for port number %d ERROR ERROR ERROR ERROR ERROR ERROR ERROR 163 Unified Services Router User Manual
%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 pppoeMgmtTblHandler:
IdleTimeOutValue: %d pppoeMgmtTblHandler: UserName: %s pppoeMgmtTblHandler: Password: %s pppoeMgmtTblHandler: DNS specified:
%s pppoeMgmtTblHandler: Service: %s pppoeMgmtTblHandler: StaticIp: %s 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 Failed to clear vlan for %d Failed to set vlan entry for vlan %d Failed to set vlan entries, while enabling \
Failed to execute vlanConfig binary for port number %d Failed to execute vlanConfig binary for vlanId %d Failed to enable vlan Failed to disable vlan Failed to set vlanPort table entries, while \
Failed to enable vlan unknown vlan state threegMgmtInit: unable to open the database file %s threegConnEnable: failed to get the WanMode threegEnable:spawning failed threegDisable: unable to kill ppp daemon threegMgmtHandler: Query: %s threegMgmtHandler: error in executing database update Error in executing DB update handler are we getting invoked twice ??
could not open %s to append could not write nameserver %s to %s could not write nameserver %s to %s could not open %s to truncate dnsResolverConfigMgmtInit: unable to open the "
resolverConfigDBUpateHandler:
sqlite3QueryResGet "
could not configure DNS resolver dnsResolverConfigure: could not write nameserver:%s,"
unboundMgmt: unable to open the "
ioctl call Failed-could not update active user Details sqlite3QueryResGet failed.Query:%s Can't kill xl2tpd DEBUG xl2tpd restart failed DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG failed to get field value failed to get field value sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s unboundMgmt: unable to open the "
writing options.xl2tpd failed 164 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 Unified Services Router User Manual 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 pptpMgmtTblHandler: UserName: %s pptpMgmtTblHandler: Password: %s pptpMgmtTblHandler: dynamic MyIp configured pptpMgmtTblHandler: MyIp: %s pptpMgmtTblHandler: ServerIp: %s pptpMgmtTblHandler: StaticIp: %s pptpMgmtTblHandler: NetMask: %s pptpMgmtTblHandler:
MppeEncryptSupport: %s pptpMgmtTblHandler: SplitTunnel: %s pptpEnable: ppp dial string: %s pptpEnable: spawning command %s 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. DHCPv6 Client stopped successfully. DEBUG DHCPv6 Client Restart successful l2tpMgmtTblHandler: MtuFlag: %d l2tpMgmtTblHandler: Mtu: %d l2tpMgmtTblHandler: IspName: %s DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG xl2tpdStop failed writing xl2tpd.conf failed writing options.xl2tpd failed xl2tpdStop failed xl2tpdStart failed sqlite3QueryResGet failed.Query:%s writing Chap-secrets/Pap-Secrets failed DEBUG xl2tpdStop failed DEBUG xl2tpdStart failed DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG sqlite3QueryResGet failed.Query:%s writing Chap-secrets/Pap-Secrets failed xl2tpdStop failed xl2tpdStart failed sqlite3QueryResGet failed.Query:%s writing Chap-secrets/Pap-Secrets failed Error in executing DB update handler unboundMgmt: unable to open the "
Can't kill pptpd pptpd restart failed Can't kill pptpd failed to get field value failed to get field value unboundMgmt: unable to open the "
DEBUG writing options.pptpd failed DEBUG pptpdStop failed DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG writing pptpd.conf failed writing options.pptpd failed pptpdStop failed pptpdStart failed writing Chap-secrets/Pap-Secrets failed Error in executing DB update handler 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 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 165 Unified Services Router User Manual l2tpMgmtTblHandler: UserName: %s l2tpMgmtTblHandler: Password: %s DEBUG DEBUG l2tpMgmtTblHandler: AccountName: %s DEBUG l2tpMgmtTblHandler: DomainName: %s l2tpMgmtTblHandler: Secret: not specified l2tpMgmtTblHandler: Secret: %s l2tpMgmtTblHandler: dynamic MyIp configured l2tpMgmtTblHandler: MyIp: %s l2tpMgmtTblHandler: ServerIp: %s 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 RADVD started successfully RADVD stopped successfully DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG empty update. nRows=%d nCols=%d WARN Wan is not up or in load balencing mode WARN threegMgmtHandler: no row found. nRows = %d nCols = %d pppoeMgmtDBUpdateHandler: empty update. dhcpcEnable: dhclient already running on: %s WARN WARN WARN dhcpcDisable: deleted dhclient.leases l2tpMgmtInit: unable to open the database file %s l2tpEnable: unable to resolve address:
%s l2tpEnable: inet_aton failed WARN ERROR ERROR ERROR 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 pptpEnable: inet_aton failed pptpEnable: inet_aton failed pptpEnable:spawning failed pptpDisable: unable to kill ppp daemon pptpMgmtTblHandler: unable to get current MTU Option pptpMgmtTblHandler: unable to get the Mtu pptpMgmtTblHandler:
dbRecordValueGet failed for %s "
pptpMgmtTblHandler: pptp enable failed pptpMgmtTblHandler: pptp disable failed pptpMgmtDBUpdateHandler:
sqlite3QueryResGet "
pptpMgmtDBUpdateHandler: error in executing "
Illegal invocation of dhcpConfig (%s) dhcpLibInit: unable to open the database file %s sqlite3QueryResGet failed.Query:%s dhcpcMgmtInit: unable to open the database file %s dhcpcReleaseLease: unable to release lease dhcpcEnable: unable to kill dhclient dhcpcEnable: enabling dhcpc failed on: %s dhcpcDisable: unable to kill dhclient dhcpcDisable: delete failed for dhclient.leases dhcpcDisable: failed to reset the ip dhcpcMgmtTblHandler: unable to get current Mtu Option dhcpcMgmtTblHandler: unable to get the Mtu 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 166 Unified Services Router User Manual The Enable Command is %s l2tpEnable:Executing the Command failed l2tpDisable: command string: %s l2tpDisable: unable to stop l2tp session l2tpMgmtTblHandler: unable to get current MTU option l2tpMgmtTblHandler: unable to get the Mtu l2tpMgmtTblHandler: dbRecordValueGet failed for %s "
l2tpMgmtTblHandler: l2tpEnable failed ERROR ERROR l2tpMgmtTblHandler: disabling l2tp failed ERROR l2tpMgmtDBUpdateHandler:
sqlite3QueryResGet "
l2tpMgmtDBUpdateHandler: error in executing Illegal invocation of tcpdumpConfig (%s) ERROR ERROR ERROR Failed to start tcpdump Failed to stop tcpdump Invalid tcpdumpEnable value Facility: System (VPN) ERROR ERROR ERROR Severity Log Message DEBUG
%d command not supported by eapAuth DEBUG pCtx NULL. Current cert subject name= %s DEBUG X509_STORE_CTX_get_ex_data failed. DEBUG Cannot get cipher, no session est. DEBUG
%s:
SSL_ERROR_WANT_X509_LOOKUP err code = (%d) in %s BIO_write: Error Decrypting: BIO reset failed Encrypting BIO reset: ERROR 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 DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG ERROR ERROR ERROR ERROR ERROR dhcpcMgmtTblHandler: dhclient enable failed dhcpcMgmtTblHandler: dhcpc release failed dhcpcMgmtTblHandler: dhcpc disable failed dhcpcMgmtDBUpdateHandler: failed query: %s dhcpcMgmtDBUpdateHandler: error in executing "
ERROR DHCPv6 Client start failed. ERROR ERROR ERROR ERROR ERROR ERROR DHCPv6 Client stop failed. ERROR failed to create/open DHCPv6 client " ERROR failed to write DHCPv6 client configuration file ERROR failed to restart DHCPv6 Client failed to create/open DHCPv6 Server
Restoring old configuration.. DHCPv6 Server configuration update failed DHCPv6 Server Restart failed sqlite3QueryResGet failed.Query:%s ERROR ERROR ERROR ERROR ERROR ERROR DEBUG Wrong identity size: ERROR Log Message PEAP key derive: ERROR PEAP context is NULL: ERROR Constructing P2 response: ERROR innerEapRecv is NULL: ERROR Decrypting TLS data: ERROR Wrong size for extensions packet:
ERROR innerEapRecv is NULL: ERROR. Inner EAP processing: ERROR TLS handshake: ERROR. Sending P1 response: ERROR Unexpected tlsGlueContinue return value. 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 TLS encrypting response: ERROR Severity ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR 167 Unified Services Router User Manual Created EAP/PEAP context: OK 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. 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. Authenticator response check: Error Authenticator response check: Failed MS-CHAP2 Response AVP size = %u Created EAP/MS-CHAP2 context: OK. pCtx NULL. Deleted EAP/MS-CHAPv2 context: OK Not authenticated yet. Authenticator response invalid EAP-MS-CHAPv2 password changed. 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 Setting message in fragment buffer:
ERROR Allocating TLS read buffer is NULL:
ERROR Setting last fragment: ERROR Getting message: ERROR Processing PEAP message: ERROR Setting fragment: ERROR Creating receive buffer: ERROR Setting first fragment: ERROR Sending P1 response: ERROR NULL request (or response) PDU or NULL context: ERROR Expecting start packet, got something else: ERROR Protocol version mismatch: ERROR Processing PEAP message (from frag): ERROR Processing PEAP message: ERROR Processing PEAP message: ERROR Indicated length not valid: ERROR Did not get Acknowledged result:
ERROR Cannot understand AVP value:
ERROR eapExtResp is NULL: ERROR eapWscCtxCreate:
EAPAUTH_MALLOC failed. eapWscProcess: umiIoctl req to WSC failed, status = %d eapWscCheck: Invalid frame eapWscBuildReq: Invalid state %d eapWscProcessWscResp: Invalid data recd pData = %p, dataLen"
Data received for invalid context, dropping it eapWscProcessWscResp: Build Request failed eapWscProcessWscResp: Invalid state %d eapWscProcessWscResp: Message processing failed 0x%X eapWscProcessWscData: Invalid notification recd %d unable to initialize MD5 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 DEBUG DEBUG ERROR DEBUG MDString: adpDigestInit for md5 failed ERROR DEBUG ERROR ERROR DEBUG ERROR DEBUG ERROR DEBUG DEBUG ERROR ERROR DEBUG EAPAUTH_MALLOC failed. EAPAUTH_MALLOC failed. NULL context created: Error NULL context received: Error Authenticator ident invalid. Success request message invalid:
168 Unified Services Router User Manual DEBUG DEBUG DEBUG rcvd. opCode %d. pCtx NULL. TLS message len changed in the fragment, ignoring. no data to send while fragment ack DEBUG received. DEBUG TLS handshake successful. DEBUG Created EAP/TTLS context: OK Deleted EAP/TTLS context: OK DEBUG No more fragments in message. ERROR DEBUG Upper EAP sent us: method state = %d;
decision = %d P2: sending fragment. DEBUG DEBUG 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) Got start Got first fragment (n). Got fragment (n). Got last fragment Got unfragmented message. Got frag ack. Rcvd. AVP Code-%u: flags-0x%x: len-
%u: vendorId-%u: "
MOD EAP: method state from upper =
%d; decision = %d 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. Error Plugin context is NULL Deriving implicit challenge: Error Generating NT response: Error ERROR ERROR ERROR ERROR NULL in/out buffer: Error Incorrect vendor id. ERROR Allocating memory for outBuff: ERROR ERROR ERROR AVP code not recognized EAPAUTH_MALLOC failed. ERROR Converting password to unicode: Error ERROR Generating password hash: Error. ERROR Generating password hash hash:
Error. Generating master key: Error. Generating first 16 bytes of session key: Error.n Generating second 16 bytes of session key: Error.n ERROR ERROR ERROR ERROR Converting password to unicode: Error ERROR Constructing failure response: ERROR ERROR Error checking authenticator response. ERROR Error generating NT response. ERROR Username string more than 256 ASCII characters: ERROR Invalid Value-Size. Invalid MS-Length. Got (%d), expected
(%d) Error constructing response. Got type (%d), expecting (%d) Cannot handle message; opCode =
%d ERROR ERROR ERROR ERROR ERROR ERROR DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG EAPAUTH_MALLOC failed. DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG tlsGlueCtxCreate failed. client certificate must be set in the profile. received tls message length too big. total frags len > initial total tls length. total frags len > initial total tls length. total data rcvd(%d) doesnt match the initial "
couldnt write %d data to TLS buffer. invalid flags %s passed to eapTlsBuildResp. EAPAUTH_MALLOC failed. tlsGlueCtxCreate failed. Context NULL: ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR 169 Unified Services Router User Manual 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. 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
\tmsLen = %d
\tvalSize = %d Frag Buffer bytes left = (%d) Stripped username=(%s) digestLen = %d. ClearText =
CipherText =
digestLen = %d. digestLen1 = %d. digestLen2 = %d. DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG Setting profile to glue layer: ERROR. _eapCtxCreate failed.
%d authentication not enabled in the system. Initializing inner non-EAP auth plugin:
ERROR TTLS key derive: ERROR TTLS context from EAP plugin is NULL: ERROR Allocating memory for TTLS Phase 2 payload: ERROR TLS Encrypting response: ERROR Allocating TLS read buffer is NULL:
ERROR Inner authentication (id: %d) unhandled innerEapRecv is NULL: ERROR. Decrypting TLS data: ERROR DEBUG DEBUG Processing Phase 2 method: Error DEBUG Writing message to BIO: ERROR. DEBUG TLS handshake: ERROR. Unexpected tlsGlueContinue return value. NULL request (or response) PDU or NULL context Protocol version mismatch: ERROR Creating receive buffer: ERROR Setting first fragment: ERROR Setting fragment: ERROR Setting last fragment: ERROR Getting message: ERROR Processing TTLS message: ERROR Processing TTLS message: ERROR Processing TTLS message: ERROR Decapsulating AVP: ERROR Processing EAP receive: Error AVP code not EAP: Error Encapsulating AVP: ERROR profile %s doesnt exist. profile %s is in use. profile %s already exists. EAPAUTH_MALLOC failed User not found. EAP-MD5 not enabled in system configuration. EAP-MSCHAPV2 not enabled in system configuration. EAP-TLS not enabled in system configuration. EAP-TTLS not enabled in system configuration. DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG 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 ERROR ERROR 170 Unified Services Router User Manual 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"
DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG X590_ERROR : Failed to create File '%s' DEBUG 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 "
SSL_CTX_use_certificate_file (cert, PEM) failed. SSL_CTX_use_PrivateKey_file failed. private key does not match public key SSL_CTX_load_verify_locations failed SSL_new failed. Both SSL_VERIFY_PEER and SSL_VERIFY_NONE set: Error EAPAUTH_MALLOC failed. 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. 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"
invalid innerAuth %d. profile %s doesnt exist. Re-assembling fragments incorrect size Error creating cipher context. Error initializing cipher context. Error creating digest context. Error initializing digest context. Error initializing DES in Klite Error initializing MD4 in Klite DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR Error initializing RC4 in Klite ERROR ERROR Error initializing SHA in Klite Error cleaning cipher context. ERROR Error destroying cipher context. ERROR ERROR ERROR ERROR ERROR Error cleaning digest context. Error destroying digest context. Error stripping domain name. Error cleaning digest context. Error cleaning digest context. Challenge not present in failure packet. ERROR ERROR Wrong challenge length. EAPAUTH_MALLOC failed. eapTimerCreate failed. eapCtxDelete:pCtx == NULL eapRole != EAP_ROLE_PEER or EAP_ROLE_AUTHENTICATOR ERROR ERROR ERROR ERROR Incorrect password change version value. Error generating password hash. Error generating password hash. Error encrypting password hash with block 171 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 Unified Services Router User Manual 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. 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 Process operation failed state machine is in invalid state. Packet length mismatch %d, %d eapAuthTypeToType: Invalid eapAuthType %d eapTypeToAuthType: Invalid eapType
%d 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 pCtx is NULL: ERROR tlsGlueCtxCreate failed eapVars is NULL Context NULL: ERROR Initializing inner EAP auth: ERROR pCtx is NULL: ERROR Memory Allocation Failed Facility: System (Admin) ERROR Could not initialize des-ecb ERROR Error cleaning cipher context. ERROR ERROR ERROR ERROR ERROR ERROR Error cleaning cipher context. Error cleaning digest context. Error cleaning digest context. adpDigestInit for SHA1 failed. X509_ERROR : .Query:%s X509_ERROR : Invalid Certificate for the "
ERROR ERROR ERROR Memory allocation failed invalid x509 certificate Couldn't get the x509 cert hash FileName too lengthy Couldn't execute command ERROR ERROR ERROR Memory allocation failed ERROR Memory allocation failed ERROR invalid certificate data ERROR ERROR ERROR Memory allocation failed
.Query:%s
.Query:%s X509_ERROR : Failed to validate the certficate "
ERROR ERROR Memory allocation failed ERROR
.Query:%s ERROR Invalid Sign Key Length : %d ERROR Invalid Hash Alg : %d ERROR Invalid Sign Alg : %d No Memory Available Certificate Request Failed File Open Failed File is Empty ERROR ERROR ERROR ERROR ERROR Memory Allocation Failed ERROR ERROR ERROR File Open Failed File is Empty Error in executing DB update handler 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 Log Message Usage:%s <DBFile>
Severity DEBUG Log Message unable to register to UMI Severity ERROR 172 Unified Services Router User Manual 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)"
DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG adpCmdExec exited with return code=%d DEBUG
%s op=%d row=%d sqlite3_mprintf failed 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)"
DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG email logs: No logging events enabled DEBUG
%s Mail sent and the Database is reset. Disabled syslog server DEBUG DEBUG DEBUG Event logs are full, sending logs to email DEBUG Email logs sending failed Packing attribute: %s Server found: %s, secret: %s Packed Auth. Reqest: code:%d, id:%d, len:%d Sending Packet to %x:%d .... Receiving Reply Packet.... Verified Reply Packet Integrity DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG Generated Reply Attribute-Value pairs DEBUG Verified Message-Authenticator Unloaded RADIUS Dictionary Adding Dictionary Attribute %s Adding Dictionary Value %s Loaded Dictionary %s DEBUG DEBUG DEBUG DEBUG DEBUG sqlite3QueryResGet failed radSendtoServer: socket: %s radSendtoServer: bind() Failed: %s:
%s radRecvfromServer: recvfrom() Failed:
%s 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 radPairNew: unknown attribute %d radPairGen: Attribute(%d) has invalid length radPairValue: unknown attribute type
%d radPairValueLen: unknown attribute type %d radPairLocate: Attribute(%d) has invalid length radPairUnpackDefault: Unknown-
Attribute[%d]:
radConfigure: can't open %s: %s radConfigure: %s: line %d: bogus format: %s radConfAssert: No AuthServer Specified radConfAssert: No Default Timeout Specified radConfAssert: No Default Retry Count Specified radExtractMppeKey: Invalid MS-
MPPE-Key Length 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 radGetHostIP: couldn't get hostname radGetHostIP: couldn't get host IP address radius dictionary loading failed Failed to set default timeout value 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 173 Unified Services Router User Manual Adding Dictionary Attribute '%s'
Adding Dictionary Value %s DEBUG DEBUG DEBUG Receiving attribute: %s DEBUG Processing attribute: %s DEBUG Processing attribute: %s DEBUG Processing attribute: %s DEBUG Processing attribute: %s DEBUG radConfGet: "
DEBUG Added Server %s:%d with "
DEBUG Added Server %s:%d with "
DEBUG Default Timeout Set to %d DEBUG Default Retry Count Set to %d DEBUG
%s - %s : %d Deleting Server %s:%d with "
DEBUG Adding RowId:%d to Server %s:%d with " DEBUG DEBUG rowIds: %d - %d DEBUG Deleting Server %s:%d with "
RADIUS Deconfigured DEBUG Found Option %s on line %d of file %s DEBUG 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 Releasing Packet with cookie:%p DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG Received EAP-Identity from Pnac: %s DEBUG Filling User-Name: %s DEBUG Filling State:
DEBUG Filling EAP-Message:
DEBUG Filling Service-Type: %d DEBUG Filling Framed-MTU: %d DEBUG Received Access-Challenge from Server DEBUG DEBUG Sending Reply EAP Packet to Pnac DEBUG Error sending packet to Pnac RADIUS Authentication Failed; "
DEBUG DEBUG RADIUS Authentication Successful; "
DEBUG Got Packet with cookie:%p Next DNS Retry after 1 min DEBUG DEBUG Next Synchronization after"
ERROR ERROR ERROR Failed to set default retries value ERROR: incomplete DB update information. old values result does not contain 2 ERROR rows ERROR sqlite3QueryResGet failed ERROR empty update. nRows=%d nCols=%d ERROR Error in executing DB update handler ERROR sqlite3QueryResGet failed ERROR Invalid SQLITE operation code - %d ERROR sqlite3QueryResGet failed ERROR empty result. nRows=%d nCols=%d ERROR sqlite3QueryResGet failed empty result. nRows=%d nCols=%d ERROR RADIUS Accounting Exchange Failed ERROR Unable to set debug for radAcct. ERROR Unable to set debug level for radAcct. ERROR ERROR ERROR: option value not specified ERROR ERROR: option value not specified Unable to initialize radius ERROR 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 radEapRecvTask: "
failed to initialize UMI umiRegister failed. errno=%d Invalid arguments to ioctl handler radEapSendRtn: Invalid Arguments radEapSendRtn: failed to allocate ERROR buffer ERROR umiIoctl failed failed to initialize EAP message queue ERROR ERROR Unable to set debug for radEap. ERROR Unable to set debug level for radEap. ERROR: option value not specified ERROR ERROR ERROR: option value not specified ERROR could not initialize MGMT framework ERROR Unable to initialize radius Unable to set debug for radEap. ERROR ERROR Unable to set debug level for radEap. ERROR ERROR: option value not specified Unable to initialize radius ERROR ERROR Invalid username or password ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR 174 Unified Services Router User Manual Next Synchronization after"
Next Synchronization after %d \
Primary is not available, "
Secondary is not available, "
DEBUG DEBUG DEBUG DEBUG Invalid value for use default servers, "
DEBUG No server is configured, "
DEBUG Backing off for %d seconds DEBUG Requesting time from %s DEBUG Synchronized time with %s DEBUG Received KOD packet from %s DEBUG No suitable server found %s DEBUG Received Invalid Length packet from %s DEBUG Received Invalid Version packet from %s DEBUG Received Invalid Mode packet from %s DEBUG Request Timed out from %s Looking Up %s 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 pNtpControl-
>ServerNames[SECONDARY_SERVER]
: %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 ERROR Unable to set debug for radAuth. Unable to set debug level for radAuth. ERROR ERROR ERROR: option value not specified Unable to initialize radius ERROR Invalid username, challenge or ERROR response Unable to set debug for radAuth. ERROR Unable to set debug level for radAuth. ERROR ERROR: option value not specified ERROR ERROR Unable to initialize radius ERROR Invalid username or password ERROR usage : %s <DB fileName>
ntpd : umi initialization failed ERROR ERROR ntpd : ntpInit failed ntpd : ntpMgmtInit failed ERROR There was an error while getting the timeZoneChangeScript."
ERROR unexpected reply from %d cmd=%d !
ERROR cmd %d not supported. caller %d ERROR default reached ERROR Unable to initialize ntpControl ERROR ntpMgmt : Couldn't open database %s ERROR ERROR : incomplete DB update information empty update. nRows=%d nCols=%d Error in executing DB update handler ERROR ERROR ERROR DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG requestNtpTime: Invalid addr ERROR DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG ERROR ERROR ERROR ERROR ERROR failed to take lock for compId: %d failed to convert ioctl args to buffer for"
request timeout dst(%d) <-- src(%d) failed to take lock for compId: %d umiIoctlArgsToBuf: failed to allocate memory umiRecvFrom: could not allocate ERROR memory adpMalloc failed ERROR context with ID: %d already registered ERROR Failed to allocate memory for creating UMI context Failed to create recvSem for UMI context Failed to create mutex locks for UMI context Failed to create mutex recvQLock for UMI context Invalid arguments to umiIoctl could not find the destination context ERROR ERROR ERROR ERROR ERROR ERROR 175 Unified Services Router User Manual DEBUG memPartAlloc for %d size failed DEBUG memPartAlloc for %d size failed timeout after semTake srcId=%d(%s) <-- destId=%d(%s) cmd=%d Un-registerting component with Id %d failed to send ioctl request: dst(%d) <---
src(%d) processed a reply dst(%d) <-- src(%d) request with no result option dst(%d) <--
src(%d) cmd = %s cmdstring is %s %s:%d Calling printerConfig binary ... Calling unmount for USB ... Calling mount for USB ... usbdevice is %d %s:%d 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. "
%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 DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG USB: failed to commit transaction: %s DEBUG 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 snmpd.conf not found
[SNMP_DEBUG] : Fwrite Successful
[SNMP_DEBUG] : Fwrite failed radPairGen: received unknown attribute
%d of length %d radPairGen: %s has unknown type radPairLocate: unknown attribute %ld of length %d radPairLocate: %s has unknown type Illegal invocation of cpuMemUsage (%s) DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG WARN WARN WARN WARN ERROR No Handler registered for this UMI context Couldn't find component with ID
(%d),"
id=%d handler=%x Received NULL buffer in umiBufToIoctlArgs() usbMgmtInit: unable to open the database file %s call to printConfig failed Failed to Disable Network Storage"
Some error occurred while removing device Some error occurred while removing device Sqlite update failed Failed to enable printer properly Failed to mount device on system Failed to enable network storage device"
Failed to mount device on system Sqlite update failed USB1 Touch failed USB2 Touch failed Sqlite update failed Failed query: %s Failed to execute usb database update handler Usage:%s <DBFile> <opType>
<tblName> <rowId>
Illegal invocation of snmpConfig (%s) Invalid Community Access Type Invalid User Access Type Invalid Security Level Invalid Authentication Algorithm Invalid Privacy Algorithm Invalid Argument Failed to allocate memory for engineID
[SNMP_DEBUG]: Failed to get host address
[SNMP_DEBUG] : FOPEN failed sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s Invalid Security Level Invalid Authentication Algorithm 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 176 Unified Services Router User Manual cpuMemUsageDBUpdateHandler: SQL error: %s 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 no component id matching %s umiIoctl (%s, UMI_CMD_DB_UPDATE(%d)) failed. sqlite3_mprintf failed sqlite3_mprintf failed no component id matching %s umiIoctl (%s, UMI_CMD_IFDEV_EVENT(%d)) failed. klogctl(9) failed malloc failed for %d bytes klogctl(4) failed emailLogs: Invalid Number of Arguments!! Exiting. sqlite3QueryResGet failed Could not execute the smtpClient. Error while cleaning the database.Exiting. %s Facility: System (Firewall) Log Message Enabling rule for protocol binding. Disabling rule for protocol binding. Enabling Remote SNMP on WAN. Disabling Remote SNMP on WAN ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR Invalid Privacy Algorithm Failed to Get Host Address Invalid version snmp v3 Trap Configuration Failed sqlite3QueryResGet failed query:%s sqlite3QueryResGet failed.Query:%s Failed to Open Snmp Configuration File Failed to write access control entries Failed to write snmpv3 users entries Failed to write snmp trap entries Failed to write system entries. Error in executing DB update handler ERROR Failed to restart snmp ERROR %s failed with status ERROR ERROR %s: Unable to open file: %s ERROR ERROR RADVD start failed RADVD stop failed failed to create/open RADVD configuration file %s ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR Restoring old configuration.. failed to write/update RADVD configuration file upnpDisableFunc failed upnpEnableFunc failed sqlite3QueryResGet failed.Query:%s Error in executing DB update handler unable to open the DB file %s umiInit failed unable to register to UMI short DB update event request!
short ifDev event request!
sqlite3_mprintf failed
%s failed. status=%d 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 Severity DEBUG DEBUG DEBUG DEBUG Log Message Disable all NAT rules. Enable all NAT rules. Enabling NAT URL filter rules. Restarting all NAT rules. Severity DEBUG DEBUG DEBUG DEBUG 177 Unified Services Router User Manual wan traffic counters are restared DEBUG DEBUG Traffic limit has been reached Traffic meter monthly limit has been changed to %d. DEBUG Enabling traffic meter for only dowload. DEBUG Enabling traffic meter for both directions. DEBUG DEBUG Enabling traffic meter with no limit. Email alert in traffic meter disabled. DEBUG Email alert in traffic meter enabled. DEBUG Traffic Meter:Monthly limit %d MB has been "
Traffic Metering: Adding rule to drop all traffic Traffic Metering: %sabling Email traffic Disabling attack checks for IPv6 rules. DEBUG DEBUG DEBUG DEBUG Enabling attack checks for IPv6 rules. 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 DEBUG Disabling attack check for TCP Flood. DEBUG Disabling attack check for UDP Flood. DEBUG Disabling attack check for IPsec. Disabling attack check for PPTP. Disabling attack check for L2TP. DEBUG DEBUG DEBUG Disabling attack check for UDP Flood. DEBUG Disabling attack check for IPsec. Disabling attack check for PPTP. Disabling attack check for L2TP. 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. Enabling attack check for UDP Flood. Enabling attack check for IPsec. Enabling attack check for PPTP. DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG Deleting schedule based firewall rules. DEBUG Deleting schedule based firewall rules from DB. Update schedule based firewall rules in DB. Restart schedule based firewall rules. inter vlan routing enabled inter vlan routing disabled Disabling Content Filter for %d Enabling Content Filter for %d
./src/firewall/linux/user/firewalld.c:59:#u ndef ADP_DEBUG2
./src/firewall/linux/user/firewalld.c:61:#d efine ADP_DEBUG2 printf Enabling Source MAC Filtering Disabling Source MAC Filtering Adding MAC Filter Policy for Block &
Permit Rest Adding MAC Filter Policy for Permit &
Block Rest DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG Restarting Source MAC Address Policy DEBUG 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 Deleting MAC Filter Policy for Address
%s Adding MAC Filter Policy for Address
%s Disabling Firewall Rules for DMZ host Enabling Firewall Rules for DMZ host Disabling Firewall Rules for Spill Over Load Balancing Disabling Firewall Rules for Load Balancing Enabling Firewall Rules for Load Balancing Enabling Firewall Rules for Spill Over Load Balancing 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 Deleting BlockSites Keyword \
Enabling BlockSites Keyword \
Disabling BlockSites Keyword \
DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG 178 Unified Services Router User Manual Enabling attack check for L2TP. Enabling attack check for UDP Flood. Enabling attack check for IPsec. Enabling attack check for PPTP. 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:#un def ADP_DEBUG
./src/firewall/linux/user/firewalld.c:62:#def ine ADP_DEBUG printf Restarting traffic meter with %d mins,
%d hours, "
Updating traffic meter with %d mins, %d hours, "
Deleting traffic meter. DEBUG DEBUG DEBUG DEBUG DEBUG Updating BlockSites Keyword from \
Inserting BlockSites Keyword \
Deleting Trusted Domain \
Adding Trusted Domain \
Restarting Schedule Based Firewall Rules DEBUG Enabling Remote SNMP DEBUG Disabling Remote SNMP DEBUG Enabling Remote SNMP DEBUG Disabling DOS Attacks DEBUG Enabling DOS Attacks DEBUG Enabling DOS Attacks DEBUG DEBUG Restarting Firewall [%d]:[%d] For %s restartStatus = %d for LogicalIfName =
%s DEBUG Deleting Lan Group %s DEBUG Adding Lan Group %s DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG Deleting lan host %s from group %s DEBUG DEBUG DEBUG DEBUG DEBUG Adding lan host %s from group %s Disabling Firewall Rule for IGMP Protocol 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 DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG Disabling block traffic for traffic meter. DEBUG Enabling traffic meter. Adding lan group %s. Deleting lan group %s. DEBUG DEBUG DEBUG Renaming lan group from %s to %s. Deleting host %s from %s group. 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. Enabling Management Access from DEBUG DEBUG %s Session Settings DEBUG Restarting IPv6 Firewall Rules... Deleting Port Trigger Rule for
%d:%d:%d:%d:%d Deleting Port Trigger Rule for
%d:%d:%d:%d:%d Enabling Port Trigger Rule for
%d:%d:%d:%d:%d Disabling Port Trigger Rule for
%d:%d:%d:%d:%d Enabling Port Trigger Rule for DEBUG DEBUG DEBUG DEBUG DEBUG 179 Unified Services Router User Manual 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. Enabling Content Filtering. 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. Enabling DNS proxy. Restarting DNS proxy. checking DNS proxy for Secure zone. DEBUG DEBUG checking DNS proxy for Public zone. Enabling Block traffic from %s zone. DEBUG Configuring firewall session settings for " DEBUG DEBUG Disabling DMZ Disabling WAN-DMZ rules . Enabling WAN DMZ rules . Restarting DMZ rule having %s address with %s address. Enabling LAN DHCP relay. OneToOneNat configured successfully OneToOneNat configuration failed Deleting scheduled IPv6 rules. delete from FirewallRules6 where ScheduleName = '%s'. DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG
%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 DEBUG DEBUG DEBUG Enabling Content Filter DEBUG Disabling Content Filter DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG Enabling Content Filter Setting NAT mode for pLogicalIfName
= %s Enabling DROP for INPUT Enabling DROP for FORWARD Enabling NAT based Firewall Rules Setting transparent mode for pLogicalIfName \
DEBUG Enabling Accept for INPUT DEBUG DEBUG Enabling Accept for FORWARD Setting Routing mode for pLogicalIfName \
DEBUG Enabling DROP for INPUT DEBUG Enabling DROP for FORWARD DEBUG DEBUG DEBUG DEBUG Disabling NAT based Firewall Rules Enabling Firewall Rules for URL Filtering & "
Adding Firewall Rule for RIP Protocol Restarting Schedule Based Firewall Rules enabling IPS checks between %s and
%s zones. disabling IPS checks between %s and
%s zones. Stopping IPS...%s IPS started. Route already exists Route addition failed: Network Unreachable Route addition failed: Network is down Route addition failed Failed to add rule in iptables Failed to delete rule from iptables fwLBSpillOverConfigure: Something going wrong here fwLBSpillOverConfigure: unable to get interfaceName fwLBSpillOverConfigure: Could not set PREROUTING rules 180 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 ERROR ERROR ERROR Unified Services Router User Manual Update FirewallRules6 where ScheduleName = '%s' to New "
Dns proxy Restart failed deleting interface to ifgroup failed adding interface to ifgroup 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 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 Deleting inbound(WAN-LAN) firewall rule. Deleting inbound(WAN-DMZ) firewall rule. RIPng disabled. DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG RIPng enabled. DEBUG Disable IPv6 firewall rule. DEBUG Enable IPv6 firewall rule. DEBUG Deleting IGMP proxy rule. DEBUG Enable IGMP proxy rule. DEBUG Restarting IGMP rule. Traffic meter enabled with no limit type. DEBUG Traffic meter enabled for only download. DEBUG Traffic meter enabled for both directions. DEBUG 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 Enabling Inter VLAN routing. Updating inter VLAN routing status. Deleting inter VLAN routing. DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG 181 DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG ERROR ERROR fwLBSpillOverConfigure: Could not set POSTROUTING rules fwLBSpillOverConfigure: Something going wrong Here fwL2TPGenericRules.c: unable to open the database file "
ERROR fwL2TPGenericRules.c: inet_aton failed ERROR 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 ERROR ERROR ERROR ERROR ERROR ERROR DEBUG 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. failed to start IPS service. Timeout in waiting for IPS service to start. Usage:%s <DBFile> <opType>
<tblName> <rowId> "
ERROR ERROR ERROR ERROR ERROR ERROR ERROR xlr8NatConfig: illegal invocation of (%s) ERROR Illegal invocation of [%s]
ERROR xlr8NatMgmtTblHandler: failed query:
%s Could not open file: %s Rip Error Command Too Long No authentication for Ripv1 Invalid Rip Direction Invalid Rip Version Invalid Password for 1st Key Invalid Time for 1st Key Invalid Password for 2nd Key ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR Invalid Time for 2nd Key Invalid First KeyId Invalid Second KeyId Invalid Authentication Type ripDisable failed ripEnable failed ERROR ERROR ERROR ERROR ERROR ERROR Unified Services Router User Manual 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 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 VAP(%s) set Short Retry failed VAP(%s) set Long Retry failed Decrypting context with key %s Unknown IAPP command %d received. 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 Severity DEBUG DEBUG DEBUG Log Message sqlite3QueryResGet failed sqlite3QueryResGet failed VAP(%s) set beacon interval failed DEBUG VAP(%s) set DTIM interval failed DEBUG DEBUG VAP(%s) set RTS Threshold failed VAP(%s) set Fragmentation Threshold failed Severity ERROR ERROR ERROR ERROR ERROR ERROR VAP(%s) set Protection Mode failed VAP(%s) set Tx Power failed DEBUG DEBUG DEBUG WDS Profile %s not found DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR Failed to initalize WPS on %s failed to get profile %s could not initialize MGMT framework could not initialize MGMT framework dot11VapBssidUpdt SQL error: %s sqlite3QueryResGet failed.Query:%s KDOT11_GET_PARAM(IEEE80211_I OC_CHANNEL) failed ERROR Failed to get the channel setting for %s ERROR ERROR sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s ERROR ERROR profile %s not found sqlite3QueryResGet failed.Query:%s ERROR Interface name and policy must be specified Interface name and policy must be specified invalid ACL type %d interface name not specified interface name not specified Invalid interface - %s specified buffer length not specified Invalid length(%d) specified failed created iappdLock failed to create cipher contexts. unable to register to UMI iappSockInit() failed 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 ERROR ERROR ERROR ERROR ERROR ERROR ERROR DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG Global counter wrapped, re-generating... DEBUG 182 Unified Services Router User Manual DEBUG DEBUG 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 DEBUG PNAC_EVENT_REAUTH event received DEBUG PNAC_EVENT_AUTH_SUCCESS event received PNAC_EVENT_PORT_STATUS_CHAN GED event received DEBUG DEBUG DEBUG 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 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 DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG WPA version %2x %2x not supported DEBUG
(%s) group cipher %2x doesn't match DEBUG
(%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 DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG UDP failed, received Length is %d umiIoctl(UMI_COMP_KDOT11, umiIoctl(UMI_COMP_UDOT11,%d,%d
umiIoctl(UMI_COMP_KDOT11,%d,%d
No IAPP Node found for req id %d umiIoctl(UMI_COMP_UDOT11,%d,%d
umiIoctl(UMI_COMP_KDOT11,%d,%d
umiIoctl(UMI_COMP_UDOT11,%d,%d
) failed ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR UDP socket is not created UDP send failed ERROR IAPP: socket (SOCK_STREAM) failed. ERROR ERROR IAPP: TCP connect failed to %s. cmd %d not supported.sender=%d umiIoctl(UMI_COMP_KDOT11,%d,%d
) failed IAPP-CACHE-NOTIFY-REQUEST send to
./src/dot11/iapp/iappLib.c:1314:
ADP_ERROR (
BSSID value passed is NULL reserved requestId is passed interface name is NULL IP address value passed is NULL ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR opening receive UDP socket failed enabling broadcast for UDP socket failed opening receive TCP socket for new AP failed
./src/dot11/iapp/iappLib.c:1784:
ADP_ERROR(
./src/dot11/iapp/iappLib.c:1794:
ADP_ERROR(
./src/dot11/iapp/iappLib.c:1803:
ADP_ERROR(
failed created dot11dLock. failed initialize profile library. failed to create cipher contexts. unable to register to UMI could not create MIB tree unable to register to PNAC Max registration attempts by DOT11 to ERROR PNAC exceeded Creation of EAP WPS Profile Failed ERROR umiIoctl(UMI_COMP_IAPP,%d ) failed ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR 183 Unified Services Router User Manual DEBUG DEBUG DEBUG DEBUG DEBUG 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) " DEBUG failed to send PNAC_VAR_KEY_TX_EN
(TRUE) "
failed to send PNAC_VAR_KEY_TX_EN
(FALSE) "
failed to send PNAC_FORCE_AUTHORIZED "
DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG failed to send PNAC_AUTHORIZED "
mic verification: OK pnacIfConfig: Invalid supplicant"
Failed to process user request Failed to process user request - %s(%d) 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, "
DOT11_RX_EAPOL_KEYMSG:
unknown ifname %s cmd %d not supported.sender=%d inteface name passed is NULL BSSID passed is NULL inteface name passed is NULL unable to allocate memory for DOT11_CTX unable to install wme mapping on %s unable to get %s mac address Failed to set %s SSID ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR Failed to set SSID broadcast status ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR Failed to set PreAuth mode unable to install key KDOT11_SET_PARAM:IEEE80211_I OC_AUTHMODE failed KDOT11_SET_PARAM:IEEE80211_I OC_PRIVACY failed wpaInit failed dot11InstallProfile: unable to get interface index adpHmacInit(%s) failed interface %s not found AP not found on %s DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG keyLen > PNAC_KEY_MAX_SIZE DEBUG Invalid profile name passed DEBUG Creation of WPS EAP Profile failed ERROR DEBUG unsupported command %d DEBUG device %s not found DEBUG unsupported command %d DEBUG dot11NodeAlloc failed DEBUG Getting WPA IE failed for %s DEBUG DEBUG DEBUG DEBUG Getting WPS IE failed for %s Failed initialize authenticator for node
%s Failed to get the system up time while adding node %s error creating PNAC port for node %s DEBUG dot11NodeAlloc failed DEBUG Invalid arguments. ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR 184 Unified Services Router User Manual pnacRecvRtn: no corresponding pnac port pae found 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 pnacRecvASInfoMessage: suppTimeout set to: %d DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG PORT SUCCESSFULLY DESTROYED DEBUG 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 umiIoctl(UMI_COMP_IAPP,%d) failed Invalid IE. umiIoctl(UMI_COMP_KDOT11_VAP,
%d ) failed umiIoctl(UMI_COMP_KDOT11,%d
,%d) failed KDOT11_SET_PARAM:IEEE80211_I OC_WME_CWMIN failed 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 invalid group cipher %d KDOT11_SET_PARAM:IEEE80211_I OC_MCASTCIPHER failed KDOT11_SET_PARAM:IEEE80211_I OC_MCASTKEYLEN failed KDOT11_SET_PARAM:IEEE80211_I OC_UCASTCIPHERS failed KDOT11_SET_PARAM:IEEE80211_I OC_KEYMGTALGS failed KDOT11_SET_PARAM:IEEE80211_I OC_WPA failed ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR DEBUG DEBUG unknow cipher type = %d DEBUG umiIoctl(UMI_COMP_IAPP,%d) failed ERROR DEBUG invalid media value=%d DEBUG invalid mediaOpt value=%d DEBUG invalid mode value=%d DEBUG dot11PnacIfCreate failed DEBUG wpaPRF failed DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG Error generating global key counter wpaCalcMic: unsupported key descriptor version integrity failed. need to stop all stations
couldn't find AP context for %s interface dot11Malloc failed dot11Malloc failed eapolRecvKeyMsg: unknown descType =%d ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR 185 Unified Services Router User Manual from pnacRecvMapi: pkt body len = %d, pktType = %d from pnacPDUProcess: received PNAC_EAP_PACKET from pnacPDUProcess: currentId = %d from pnacPDUProcess: code = %d, identifier = %d, "
from pnacPDUProcess: setting rxResp true from pnacPDUProcess: code = %d, identifier = %d, "
from pnacPDUProcess: received "
from pnacPDUProcess: received "
from pnacPDUProcess: received PNAC_EAPOL_KEY_PACKET doing pnacTxCannedFail doing pnacTxCannedSuccess doing pnacTxReqId doing pnacTxReq doing pnacTxStart doing pnacTxLogoff doing pnacTxRspId: 1st cond doing pnacTxRspId: entering 2nd cond from pnacTxRspId: code = %d, identifier
= %d, length = %d, "
doing pnacTxRspId: 2nd cond 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 Back auth state = %s Supplicant[%d]:
Supp Pae state = %s DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG eapolRecvKeyMsg: invalid descriptor version 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 secureBit not set in GTK Msg2 wpaAuthRecvGTKMsg2:
keyDataLength not zero wpaAuthRecvGTKMsg2: mic check failed wpaAuthRecvKeyReq: unexpected packet received wpaAuthRecvKeyReq: keyDataLength not zero wpaAuthRecvKeyReq: mic check failed invalid OUI %x %x %x
(%s) invalid OUI %x %x %x
[%s:%d] Cipher in WPA IE : %x
(%s) invalid OUI %x %x %x short WPA IE (length = %d) received ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR DEBUG PTK state machine in unknown state. ERROR DEBUG DEBUG dot11InstallKeys failed group state machine entered into WPA_AUTH_GTK_INIT DEBUG dot11Malloc failed DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG dot11Malloc failed dot11Malloc failed aesWrap failed unknown key descriptor version %d dot11Malloc failed could not initialize AES128ECB could not initialize AES-128-ECB MD5 initialization failed ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR 186 Unified Services Router User Manual from pnacBackAuthFail: calling pnacTxCannedFail
%s returned ERROR pnacUmiIoctlHandler: cmd: %s(%d)
%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 pnacIfConfig: autoAuth Enabled pnacSendRtn: no pnac port pae found for
DEBUG DEBUG sending portStatus: %s[%d] to dot11 pnacRecvASInfoMessage: Rkey of length %d set 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 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 DEBUG DEBUG DEBUG DEBUG RC4 framework initialization failed PNAC framework initialization failed ERROR: option value not specified ERROR: -u can be used only with -s DEBUG ERROR: user-name not specified DEBUG failed to enable debug ERROR ERROR ERROR ERROR ERROR ERROR DEBUG
[%s]: failed to convert string to MAC "
ERROR WARN UMI initialization failed DEBUG DEBUG DEBUG DEBUG DEBUG WARN WARN WARN WARN WARN WARN WARN WARN WARN WARN WARN WARN WARN WARN WARN failed to initialize UMI pnacPhyPortParamSet:invalid arguments pnacPhyPortParamSet:Failed to create socket Error from pnacPhyPortParamSet:%s-
device invalid Error from pnacPhyPortParamSet:%s-
Getting MAC address "
pnacPhyPortParamSet:Failed to add 802.1X multicast "
pnacIsInterfaceUp: failed to create a raw socket pnacIsInterfaceUp: failed to get interface flags failed to allocate buffer 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 ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR From pnacRadXlateDemoRecv: send " ERROR 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 ERROR ERROR ERROR ERROR 187 Unified Services Router User Manual ERROR ERROR ERROR MDString: adpDigestInit for md5 failed ERROR phyPort:%s pnacPortPaeDeconfig:kpnacPortPaeDec onfig failed pnacPortPaeDeconfig:kpnacPortPaeDec onfig failed pnacBackAuthSuccess: failed to notify the destination "
WARN WARN WARN could not initialize MGMT framework ERROR Recd WSC start for non-existent AP %s ERROR umiInit failed iappInit failed could not initialize IAPP MGMT. dot11Malloc failed 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 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 wrong AP %s Unable to send WSC_WLAN_CMD_PORT to WSC Failed to get the ap context for %s WPS can only be applied to WPA/WPA2 security profiles wpsEnable: running wsccmd failed 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 ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR 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 from pnacEapDemoSuppRecv:
couldn't "
ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR pnacUmiInit: UMI initialization failed could not start PNAC task invalid aruments pnacIfNameToIndex failed pnacPhyPortParamSet: device invalid
%s%d pnacPhyPortParamSet: EIOCGADDR ioctl failed pnacPhyPortParamSet: multicast addr add ioctl failed pnacPhyPortParamUnset: multicast addr del ioctl failed ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR pnacPDUXmit: Invalid arguments ERROR pnacPDUXmit: failed to get M_BLK_ID ERROR from pnacIsInterfaceUp: device %s%d invalid pnacRecvRtn: dropping received packet as port is"
pnacSendRtn: Invalid arguments pnacSendRtn: no physical port corresponding to"
pnacSendRtn: dropping packet as port"
pnacAuthBuildRC4KeyDesc:
adpEncryptInit(RC4) failed pnacAuthBuildRC4KeyDesc:
adpCipherContextCtrl"
pnacDot11UserSet: incorrect buffer length ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR PNAC user component id not set. ERROR 188 Unified Services Router User Manual 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 in allocating memory for profile missing profile name missing profile name Profile name and interface name must be specified Profile %s does not exist 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 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 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 pnacKeyInfoGet:failed to allocate buffer PNAC user comp id not set. dropping EAPOL key pkt pnacUmiPortPaeParamSet: invalid buffer received ERROR ERROR ERROR Error from pnacRecvASInfoMessage: " ERROR pnacRecvASInfoMessage: "
ERROR pnacRecvASInfoMessage: Bad info length Error from pnacLibInit: malloc failed could not create phy ports lock could not create nodes ports lock port exists for iface - %s ERROR ERROR ERROR ERROR ERROR pnacPhyPortCreate failed kpnacPhyPortCreate failed invalid argument pnacAuthConfig: maxAuth limit reached pnacAuthConfig: malloc failed Error from pnacAuthConfig: pAsArg cannot be NULL Error from pnacAuthConfig: receive routine hook "
pnacAuthConfig: pnacAuthInit failed kpnacPortPaeConfig failed Invalid arguments Error from pnacSuppConfig: malloc failed Error from pnacSuppConfig: receive routine hook "
Error from pnacSuppConfig:
pnacSuppInit failed kpnacPortPaeConfig failed pnacAuthDeconfig failed: pPortPae NULL Error from pnacPhyPortDestroy: port not configured pnacPhyPortDestroy: Failed to deconfigure port pnacPhyPortParamUnset FAILED Error from pnacPhyPortCreate: malloc failed Error from pnacPhyPortCreate:
pnacPhyPortParamSet"
error from pnacPhyPortCreate: malloc failed Error from pnacAuthInit:
pnacPortTimersInit failed Error from pnacAuthInit:
pnacAuthPAEInit failed ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR 189 Unified Services Router User Manual 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. 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 Profile %s does not exist invalid type value %d. supported values are 1,2,3,4 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 Profile %s does not exist ERROR: incomplete DB update information. ERROR old values result does not contain 2 rows ERROR ERROR sqlite3QueryResGet failed ERROR Error from pnacAuthInit:
pnacAuthKeyTxInit failed Error from pnacAuthInit:
pnacReauthTimerInit failed Error from pnacAuthInit:
pnacBackAuthInit failed Error from pnacAuthInit: pnacCtrlDirInit failed Error from pnacAuthInit:
pnacKeyRecvInit failed Error from pnacSuppInit: malloc failed Error from pnacSuppInit:
pnacPortTimersInit failed Error from pnacSuppInit:
pnacKeyRecvInit failed Error from pnacSuppInit:
pnacSuppKeyTxInit failed Error from pnacSuppInit:
pnacSuppPAEInit failed Error from pnacRecvRtn: invalid arguments Error from pnacRecvMapi:
unsupported PDU received suppToACSendRtn returned not OK!
Error from pnacBasicPktCreate: malloc failed Error from pnacEAPPktCreate: basic pkt create failed Error from pnacTxCannedFail: eap pkt create failed Error from pnacTxCannedSuccess:
eap pkt create failed 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 from pnacEapPktRecord: "
from pnacBackAuthTimeout: calling pnacTxCannedFail hmac_md5: adpHmacContextCreate failed hmac_md5:adpHmacInit failed pnacUmiIoctlHandler: invalid cmd: %d 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 190 Unified Services Router User Manual Error in executing DB update handler ERROR sqlite3QueryResGet failed ERROR: incomplete DB update information. ERROR old values result does not contain 2 rows ERROR ERROR sqlite3QueryResGet failed ERROR Error in executing DB update handler ERROR sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s sqlite3QueryResGet failed.Query:%s startStopVap failed to stop %s ERROR ERROR ERROR ERROR ERROR Invalid SQLITE operation code - %d
./src/dot11/mgmt/dot11Mgmt.c:1177:
ADP_ERROR (
only delete event expected on dot11RogueAP. ERROR ERROR ERROR sqlite3QueryResGet failed unhandled database operation %d sqlite3QueryResGet failed failed to configure WPS on %s sqlite3QueryResGet failed sqlite3QueryResGet failed sqlite3QueryResGet failed sqlite3QueryResGet failed sqlite3QueryResGet failed no VAP rows returned. expected one multiple VAP rows returned. expected one sqlite3QueryResGet failed ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR invalid query result. ncols=%d nrows=%d ERROR
%s:VAP(%s) create failed sqlite3QueryResGet failed ERROR ERROR invalid query result. ncols=%d nrows=%d ERROR pnacEapRadAuthSend: Invalid arguments pnacEapRadAuthSend: failed to allocate inbuffer pnacXmit : umiIoctl failed[%d]
pnacPDUForward: Invalid input pnacPDUForward: error in getting port pae information pnacPDUForward: error allocating memory pnacUmiIfMacAddrChange: %s not configured for 802.1x pnacUmiIfMacAddrChange: could not process PDU received"
pnacUmiPhyPortConfig: Invalid config data pnacUmiPhyPortConfig: Invalid backend name specified pnacUmiPhyPortConfig: could not create PNAC physical"
pnacUmiAuthConfig: Invalid config data pnacUmiAuthConfig: Invalid backend name specified unable to create new EAP context. unable to apply %s profile on the EAP context. pnacUmiAuthConfig: could not configure PNAC PAE "
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 pnacUmiIfDown: Invalid config data pnacUmiIfDown: Invalid config data Error from pnacPortDeconfig: port not configured pnacUmiIfDown: could not de-
configure port pnacUmiPhyPortDestroy: Invalid config data pnacUmiPhyPortDestroy: Invalid config data pnacUmiPhyPortDestroy: Failed to destroy the port 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 191 Unified Services Router User Manual 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,
%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, Invalid config data ERROR Severity Log Message Severity DEBUG %s: %s%s:%d -> %s:%d %s, DEBUG %s: %s%s:%d %s, DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG
%s: Failed to add WDS MAC: %s, dev-
>name,
%s: Device already has WDS mac address attached,
%s: Added WDS MAC: %s, dev-
>name,
%s: WDS MAC address %s is not known by this interface,
[madwifi] %s() : Not enough space., __FUNCTION__ Returning to chan %d, ieeeChan WEP AES DEBUG AES_CCM DEBUG CKIP DEBUG TKIP
%s: cannot map channel to mode; freq
%u flags 0x%x, DEBUG DEBUG DEBUG DEBUG DEBUG %s: %s, vap->iv_dev->name, buf DEBUG %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, ifmedia_add: null ifm Adding entry for ifmedia_set: no match for 0x%x/0x%x, DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG ifmedia_set: target DEBUG ifmedia_set: setting to 192 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 Unified Services Router User Manual PPPOL2TP: <-- %s, __FUNCTION__) DEBUG
%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, PPPOL2TP: --> %s, __FUNCTION__)
%s: recv: , tunnel->name
%s: xmit:, session->name
%s: xmit:, session->name
%s: module use_count is %d, __FUNCTION__, mod_use_count PPPOL2TP %s: _fmt, PPPOL2TP: --> %s, __FUNCTION__) PPPOL2TP: <-- %s, __FUNCTION__)
%s: recv: , tunnel->name
%s: xmit:, session->name
%s: xmit:, session->name PPPOL2TP %s: _fmt, PPPOL2TP: --> %s, __FUNCTION__) PPPOL2TP: <-- %s, __FUNCTION__)
%s: recv: , tunnel->name
%s: xmit:, session->name
%s: xmit:, session->name IRQ 31 is triggered
[%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]
DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG ifmedia_ioctl: no media found for 0x%x, DEBUG ifmedia_ioctl: switching %s to , dev-
>name ifmedia_match: multiple match for
<unknown type>
desc->ifmt_string mode %s, desc->ifmt_string
<unknown subtype>
%s, desc->ifmt_string DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG %s%s, seen_option++ ? , : , DEBUG %s%s, seen_option++ ? , : , DEBUG %s, seen_option ? > :
DEBUG %s: %s, dev->name, buf
%s: no memory for sysctl table!, __func__
%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 DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG
%02x, ((u_int8_t *)p)[i]
first difference at byte %u, i DEBUG %s: 0x%p len %u, tag, p, len DEBUG %03d:, i DEBUG DEBUG DEBUG %s: , t->name DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG FAIL: ieee80211_crypto_newkey failed DEBUG DEBUG FAIL: ieee80211_crypto_setkey failed DEBUG FAIL: unable to allocate skbuff FAIL: wep decap failed DEBUG FAIL: decap botch; length mismatch DEBUG FAIL: decap botch; data does not compare FAIL: wep encap failed FAIL: encap data length mismatch FAIL: encrypt data does not compare PASS DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG
%u of %u 802.11i WEP test vectors passed, pass, total DEBUG DEBUG %s: 0x%p len %u, tag, p, len DEBUG DEBUG %03d:, i DEBUG 193 Unified Services Router User Manual DEBUG DEBUG
%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]
%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!
DEBUG a guy asks for address mask. Who is it? DEBUG DEBUG icmp v4 hw csum failure) DEBUG DEBUG DEBUG DEBUG DEBUG expire>> %u %d %d %d, expire, expire++ %u %d %d %d, expire, DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG rt_cache @%02x: %u.%u.%u.%u, hash, DEBUG 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) DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG
%02x, ((u_int8_t *)p)[i]
DEBUG first difference at byte %u, i DEBUG DEBUG %s: , t->name DEBUG FAIL: ieee80211_crypto_newkey failed DEBUG FAIL: ieee80211_crypto_setkey failed DEBUG FAIL: unable to allocate skbuff FAIL: ccmp encap failed FAIL: encap data length mismatch FAIL: encrypt data does not compare FAIL: ccmp decap failed FAIL: decap botch; length mismatch FAIL: decap botch; data does not compare PASS
%u of %u 802.11i AES-CCMP test vectors passed, pass, total DEBUG %s: 0x%p len %u, tag, p, len DEBUG %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 194 DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG Unified Services Router User Manual DEBUG
%s: flow dst=%s, __FUNCTION__, XFRMSTRADDR(fl->fl6_dst, family)
%s: flow src=%s, __FUNCTION__, XFRMSTRADDR(fl->fl6_src, family) DEBUG a guy asks for address mask. Who is it? DEBUG DEBUG icmp v4 hw csum failure) DEBUG expire>> %u %d %d %d, expire, expire++ %u %d %d %d, expire, DEBUG rt_cache @%02x: %u.%u.%u.%u, hash, DEBUG 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, DEBUG a guy asks for address mask. Who is it? DEBUG fib_add_ifaddr: bug: prim == NULL DEBUG DEBUG DEBUG fib_del_ifaddr: bug: prim == NULL expire>> %u %d %d %d, expire, DEBUG DEBUG 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 802.11i TKIP test vectors passed DEBUG %s, buf Atheros HAL assertion failure: %s: line
%u: %s, DEBUG ath_hal: logging to %s %s, ath_hal_logfile, ath_hal: logging disabled DEBUG %s%s, sep, ath_hal_buildopts[i]
ath_pci: No devices found, driver not installed. _fmt, __VA_ARGS__
%s: Warning, using only %u entries in
%u key cache, expire++ %u %d %d %d, expire, DEBUG rt_cache @%02x: %u.%u.%u.%u, hash, DEBUG %s: TX99 support enabled, dev->name DEBUG DEBUG
%s:grppoll Buf allocation failed
,__func__ DEBUG DEBUG DEBUG %s: %s: unable to start recv logic, DEBUG %s: %s: unable to start recv logic, DEBUG %s: no skbuff, __func__ 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? DEBUG %s: %s: unable to start recv logic, ath_mgtstart: discard, no xmit buf icmp v4 hw csum failure)
%s: [%02u] %-7s , tag, ix, ciphers[hk-
>kv_type]
%s: hardware error; resetting, dev-
>name
%s: rx FIFO overrun; resetting, dev-
>name
%s: unable to reset hardware: '%s'
(HAL status %u)
%s: unable to start recv logic, dev-
>name
%s: %s: unable to reset hardware: '%s'
(HAL status %u), DEBUG DEBUG DEBUG DEBUG DEBUG expire>> %u %d %d %d, expire, expire++ %u %d %d %d, expire, rt_cache @%02x: %u.%u.%u.%u, hash, DEBUG rt_bind_peer(0) @%p, NET_CALLER(iph) ip_rt_advice: redirect to DEBUG DEBUG %02x, hk->kv_val[i]
mac %s, ether_sprintf(mac) DEBUG DEBUG %02x, hk->kv_mic[i]
%s , sc->sc_splitmic ? mic : rxmic 195 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 Unified Services Router User Manual txmic DEBUG 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. ipt_rpc: only valid for PRE_ROUTING, FORWARD, POST_ROUTING, LOCAL_IN and/or LOCAL_OUT targets. DEBUG move data from NORMAL to XR
%s: unable to update h/w beacon queue parameters,
%s: stuck beacon; resetting (bmiss count %u), DEBUG %02x, hk->kv_txmic[i]
DEBUG DEBUG ip_nat_init: can't setup rules. ip_nat_init: can't register in hook. moved %d buffers from NORMAL to XR, index DEBUG DEBUG move buffers from XR to NORMAL ip_nat_init: can't register out hook. DEBUG ip_nat_init: can't register adjust in hook. DEBUG ip_nat_init: can't register adjust out hook. DEBUG ip_nat_init: can't register local out hook. DEBUG ip_nat_init: can't register local in hook. DEBUG 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. ip_conntrack: can't register local in helper hook. ip_conntrack: can't register postrouting helper hook. ip_conntrack: can't register post-routing hook. ip_conntrack: can't register local in hook. 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 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__ DEBUG %s: AC %u out of range, max %u!, DEBUG %s: unable to update hardware queue DEBUG moved %d buffers from XR to NORMAL, count
%s:%d %s, __FILE__, __LINE__, __func__
%s:%d %s, __FILE__, __LINE__, __func__
%s: no buffer (%s), dev->name, __func__
%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!, DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG
%s: bogus frame type 0x%x (%s), dev-
>name, ath_stoprecv: rx queue 0x%x, link %p,
%s: %s: unable to reset channel %u
(%u MHz) DEBUG DEBUG DEBUG DEBUG %s: %s: unable to restart recv logic,
%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, 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__ DEBUG DEBUG DEBUG DEBUG 196 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 Unified Services Router User Manual ipt_time loading ipt_time unloaded ip_conntrack_irc: max_dcc_channels must be a positive integer ip_conntrack_irc: ERROR registering port %d, ip_nat_h323:
ip_nat_mangle_tcp_packet ip_nat_h323:
ip_nat_mangle_udp_packet 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 ip_nat_ras: out of TCP ports ip_nat_q931: out of TCP ports ip_conntrack_core: Frag of proto %u., Broadcast packet!
Should bcast: %u.%u.%u.%u-
>%u.%u.%u.%u (sk=%p, ptype=%u), ip_conntrack version %s (%u buckets,
%d max) ERROR registering port %d, netfilter PSD loaded - (c) astaro AG netfilter PSD unloaded - (c) astaro AG
%s , SELF
%s , LAN
%s , WAN 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 INCOMPLETE [%u bytes] , SPT=%u DPT=%u , SEQ=%u ACK=%u , DEBUG DEBUG DEBUG DEBUG DEBUG
%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, radio %d.%d, ah->ah_analog5GhzRev
>> 4, DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG %s: Use hw queue %u for %s traffic,
%s: Use hw queue %u for CAB traffic, dev->name,
%s: Use hw queue %u for beacons, dev->name, Could not find Board Configuration Data Could not find Radio Configuration data ath_ahb: No devices found, driver not installed. _fmt, __VA_ARGS__ _fmt, __VA_ARGS__ xlr8NatIpFinishOutput: Err.. skb2 ==
NULL !
xlr8NatSoftCtxEnqueue: Calling xlr8NatIpFinishOutput () .., status xlr8NatSoftCtxEnqueue:
xlr8NatIpFinishOutput () returned [%d], status icmpExceptionHandler: Exception!
fragExceptionHandler: Exception!
algExceptionHandler: Exception!
dnsExceptionHandler: Exception!
IPsecExceptionHandler: Exception!
ESP Packet Src:%x Dest:%x Sport:%d dport:%d secure:%d spi:%d isr:%p, 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. xlr8NatConntrackPostHook:
postSecure=[%d] postIsr=[%p %p], proto %d spi %d <-------> proto %d spi
%d,pPktInfo->proto,pPktInfo->spi, IPSEC_INF Clock skew detected 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 DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG 197 Unified Services Router User Manual WINDOW=%u , ntohs(th->window) RES=0x%02x ,
(u8)(ntohl(tcp_flag_word(th) &
TCP_RESERVED_BITS) >> 22) URGP=%u , ntohs(th->urg_ptr) 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 DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG IPSEC_ERR [%s:%d]: Max (%d) No of SA Limit reached, DEBUG DEBUG IPSEC_ERR [%s:%d]: Max (%d) No of SA Limit reached, DEBUG IPSEC_ERR [%s:%d]: time(secs): %u 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 unknown oid '%s', varName could not find oid pointer for '%s', varName DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG unRegistering IPsecMib ..... 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 unknown oid '%s', varName could not find oid pointer for '%s', varName unRegistering IPsecMib ..... %u.%u.%u.%u, NIPQUAD(trt-
DEBUG
>rt_dst) DEBUG %02x, *p DEBUG DEBUG DEBUG DEBUG DEBUG 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 DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG IN=
OUT=
PHYSIN=%s , physindev->name DEBUG DEBUG DEBUG unable to register vIPsec kernel comp to UMI DEBUG unregistering VIPSECK from UMI .... DEBUG in vIPsecKIoctlHandler cmd - %d, cmd DEBUG 198 Unified Services Router User Manual PHYSOUT=%s , physoutdev->name DEBUG MAC=
%02x%c, *p, 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-
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
%s: Error. DST Refcount value less than 1 (%d), for %s DEVICE refcnt: %d ,pDst-
>dev->name,
%s: Got Null m:%p *m:%p sa:%p
*sa:%p,__func__,ppBufMgr,
%s Got Deleted SA:%p state:%d,__func__,pIPsecInfo,pIPsecIn fo->state
%s: %s: fmt, __FILE__, __FUNCTION__ , ## args)
%s: %s: fmt, __FILE__, __FUNCTION__ , ## args) ipt_TIME: format, ## args) IPT_ACCOUNT_NAME : checkentry() wrong parameters (not equals existing table parameters). 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. IPT_ACCOUNT_NAME : checkentry() failed to register match. failed to create procfs entry . MPPE/MPPC encryption/compression module registered MPPE/MPPC encryption/compression module unregistered PPP generic driver version PPP_VERSION MPPE/MPPC encryption/compression module registered MPPE/MPPC encryption/compression module unregistered PPP generic driver version PPP_VERSION PPPoL2TP kernel driver, %s, PPPoL2TP kernel driver, %s, PPPoL2TP kernel driver, %s, failed to create procfs entry . proc dir not created .. Initialzing Product Data modules DEBUG DEBUG DEBUG DEBUG INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO 199 Unified Services Router User Manual
>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]
%02X, skb->data[i]
_lvl PPPOL2TP: _fmt, ##args
%02X, ptr[length]
%02X, ((unsigned char *) m-
>msg_iov[i].iov_base)[j]
%02X, skb->data[i]
KERN_EMERG THE value read is
%d,value*/
KERN_EMERG Factory Reset button is pressed 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 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, op->sizeofptr = %ld, op->sizeofptr opcode cmd = %x, cmd modexp opcode received Memory Allocation failed modexpcrt opcode received kmalloc failed kmalloc failed kmalloc failed kmalloc failed kmalloc Failed kmalloc failed unknown cyrpto ioctl cmd received %x, cmd register_chrdev returned ZERO const char *descr, krb5_keyblock *k) {
F password, &pdata DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG De initializing by \
kernel UMI module loaded kernel UMI module unloaded Loading bridge module Unloading bridge module unsupported command %d, cmd Loading ifDev module Unloading ifDev module ERROR#%d in alloc_chrdev_region, result DEBUG ERROR#%d in cdev_add, result DEBUG DEBUG using bcm switch %s, bcmswitch privlegedID %d wanporttNo: %d, privlegedID,wanportNo DEBUG Loading mii DEBUG Unloading mii DEBUG %s: Version 0.1 DEBUG %s: driver unloaded, dev_info DEBUG DEBUG wlan: %s backend registered, be-
>iab_name wlan: %s backend unregistered, wlan: %s acl policy registered, iac-
>iac_name wlan: %s acl policy unregistered, iac-
DEBUG
>iac_name DEBUG %s, tmpbuf DEBUG VLAN2 VLAN3 VLAN4 <%d %d>, DEBUG DEBUG DEBUG DEBUG %s: %s, dev_info, version DEBUG %s: driver unloaded, dev_info DEBUG %s, buf DEBUG %s: %s (, dev_info, ath_hal_version DEBUG %s: driver unloaded, dev_info
%s: %s: mem=0x%lx, irq=%d hw_base=0x%p, DEBUG DEBUG %s: %s, dev_info, version DEBUG %s: driver unloaded, dev_info DEBUG %s: %s: mem=0x%lx, irq=%d, DEBUG %s: %s: mem=0x%lx, irq=%d, DEBUG %s: %s, dev_info, version DEBUG %s: driver unloaded, dev_info DEBUG %s, buf 200 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 Unified Services Router User Manual test key, key pre-hashed key, key const char *descr, krb5_keyblock *k) {
AES 128-bit key, &key const char *descr, krb5_keyblock *k) {
test key, key pre-hashed key, key const char *descr, krb5_keyblock *k) {
128-bit AES key,&dk 256-bit AES key, &dk WARNING:
bwMonMultipathNxtHopSelect::
checking rates hop :%d dev:%s usableBwLimit = %d currBwShare = %d lastHopSelected =
%d weightedHopPrefer = %d , 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 3. selecting hop: %d lastHopSelected =
%d , selHop, lastHopSelected bwMonitor multipath selection enabled bwMonitor multipath selection disabled weightedHopPrefer set to %d
,weightedHopPrefer bwMonitor sysctl registration failed bwMonitor sysctl registered bwMonitor sysctl not registered Unregistered bwMonitor sysctl CONFIG_SYSCTL enabled ... Initialized bandwidth monitor ... 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], Failed to set AES encrypt key Failed to set AES encrypt key AES %s Encrypt Test Duration: %d:%d, hard ? Hard : Soft, Failed to set AES encrypt key DEBUG %s: %s (, dev_info, ath_hal_version DEBUG %s: driver unloaded, dev_info DEBUG %s: driver unloaded, dev_info DEBUG %s: Version 2.0.0 DEBUG %s: driver unloaded, dev_info DEBUG %s: driver unloaded, dev_info DEBUG DEBUG DEBUG wlan: %s backend registered, be-
>iab_name wlan: %s backend unregistered, wlan: %s acl policy registered, iac-
>iac_name wlan: %s acl policy unregistered, iac-
>iac_name DEBUG DEBUG %s: %s, dev_info, version DEBUG %s: driver unloaded, dev_info INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO DEBUG %s: %s (, dev_info, ath_hal_version INFO DEBUG %s: driver unloaded, dev_info DEBUG %s: %s: mem=0x%lx, irq=%d, DEBUG %s: %s, dev_info, version DEBUG %s: driver unloaded, dev_info DEBUG DEBUG ath_pci: switching rfkill capability %s, Unknown autocreate mode: %s, DEBUG %s: %s: mem=0x%lx, irq=%d, DEBUG %s: %s, dev_info, version DEBUG %s: driver unloaded, dev_info DEBUG %s: %s, dev_info, version DEBUG %s: unloaded, dev_info DEBUG %s: %s, dev_info, version DEBUG %s: unloaded, dev_info DEBUG %s: %s, dev_info, version DEBUG %s: unloaded, dev_info DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG failed to create procfs entry . ICMP: %u.%u.%u.%u:
ICMP: %u.%u.%u.%u: Source Wrong address mask %u.%u.%u.%u from Redirect from %u.%u.%u.%u on %s about IP: routing cache hash table of %u buckets, %ldKbytes, source route option %u.%u.%u.%u ->
%u.%u.%u.%u, 201 INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO Unified Services Router User Manual Failed to set AES encrypt key AES %s Decrypt Test Duration: %d:%d, hard ? Hard : Soft, Failed to set AES encrypt key 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 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 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 ICMP: %u.%u.%u.%u:
DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG ICMP: %u.%u.%u.%u: Source Wrong address mask %u.%u.%u.%u from Redirect from %u.%u.%u.%u on %s about 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 source route option ICMP: %u.%u.%u.%u:
ICMP: %u.%u.%u.%u: Source Wrong address mask %u.%u.%u.%u from Redirect from %u.%u.%u.%u on %s 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 IPsec: device down: %s, dev->name DEBUG mark: only supports 32bit mark DEBUG ipt_time: invalid argument DEBUG ipt_time: IPT_DAY didn't matched DEBUG
./Logs_kernel.txt:45:KERN_WARNING DEBUG DEBUG DEBUG DEBUG
./Logs_kernel.txt:59:KERN_WARNING ipt_LOG: not logging via system console
%s: wrong options length: %u, fname, opt_len
%s: options rejected: o[0]=%02x, o[1]=%02x, DEBUG %s: wrong options length: %u, DEBUG
%s: options rejected: o[0]=%02x, o[1]=%02x, DEBUG DEBUG %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, DEBUG MD5 Software Test:
DEBUG %s: wrong options length: %u, 202 INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO 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 Unified Services Router User Manual MD5 Software Test %s, md5SoftTest(0)
? Failed : Passed DEBUG
%s: options rejected: o[0]=%02x, o[1]=%02x, MD5 Hardware Test:
MD5 Hardware Test %s, md5HardTest(0) ? Failed : Passed DEBUG %s: don't know what to do: o[5]=%02x, 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 DEBUG %s: unknown SIOCGIWAUTH flag %d, 3DES Hardware Test Duration: %d:%d, DEBUG %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 MD5 Hardware Test Duration: %d:%d,
./pnac/src/pnac/linux/kernel/xcalibur.c:2 09:#define DEBUG_PRINTK printk DEBUG %s: key size %d is too large, DEBUG unable to load %s, scan_modnames[mode]
DEBUG Failed to mkdir /proc/net/madwifi bcmDeviceInit: registration failed DEBUG try_module_get failed bcmDeviceInit: pCdev Add failed REG Size == 8 Bit Value = %x ::: At Page = %x : Addr =
%x REG Size == 16 Bit DEBUG %s: request_irq failed, dev->name DEBUG too many virtual ap's (already got %d), sc->sc_nvaps DEBUG %s: request_irq failed, dev->name rix %u (%u) bad ratekbps %u mode
%u, DEBUG 203 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 Unified Services Router User Manual Value = %x ::: At Page = %x : Addr =
%x DEBUG cix %u (%u) bad ratekbps %u mode
%u, REG Size == 32 Bit Value = %x ::: At Page = %x : Addr =
%x DEBUG %s: no rates for %s?, DEBUG no rates yet! mode %u, sc-
>sc_curmode REG Size == 64 Bit DEBUG %u.%u.%u.%u sent an invalid ICMP REG Size is not in 8/16/32/64 Written Value = %x ::: At Page = %x :
Addr = %x DEBUG dst cache overflow DEBUG Neighbour table overflow. bcm_ioctl :Unknown Ioctl Case : DEBUG
=========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 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 Cannot Set Rate: %x, value Getting Rate Series: %x,vap-
>iv_fixed_rate.series Getting Retry Series: %x,vap-
>iv_fixed_rate.retries IC Name: %s,ic->ic_dev->name usage: rtparams rt_idx <0|1> per
<0..100> probe_intval <0..100>
usage: acparams ac <0|3> RTS <0|1>
aggr scaling <0..4> min mbps <0..250>
usage: hbrparams ac <2> enable <0|1>
per_low <0..50>
host %u.%u.%u.%u/if%d ignores martian destination %u.%u.%u.%u from DEBUG martian source %u.%u.%u.%u from ll header:
DEBUG %u.%u.%u.%u sent an invalid ICMP DEBUG dst cache overflow DEBUG Neighbour table overflow. DEBUG DEBUG host %u.%u.%u.%u/if%d ignores martian destination %u.%u.%u.%u from DEBUG martian source %u.%u.%u.%u from DEBUG ll header:
DEBUG %u.%u.%u.%u sent an invalid ICMP DEBUG dst cache overflow DEBUG Neighbour table overflow. DEBUG host %u.%u.%u.%u/if%d ignores DEBUG martian source %u.%u.%u.%u from DEBUG ll header:
martian destination %u.%u.%u.%u from
%s(): ADDBA mode is AUTO, __func__ DEBUG
%s(): Invalid TID value, __func__ DEBUG %u.%u.%u.%u sent an invalid ICMP
%s(): ADDBA mode is AUTO, __func__ DEBUG dst cache overflow
%s(): Invalid TID value, __func__ DEBUG Neighbour table overflow.
%s(): Invalid TID value, __func__ Addba status IDLE host %u.%u.%u.%u/if%d ignores DEBUG DEBUG martian destination %u.%u.%u.%u 204 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 User Manual G WARNIN G WARNIN G ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR Unified Services Router from
%s(): ADDBA mode is AUTO, __func__ DEBUG martian source %u.%u.%u.%u from ll header:
Unable to create ip_set_list Unable to create ip_set_hash ip_conntrack_in: Frag of proto %u
(hook=%u), Unable to register netfilter socket option Unable to create ip_conntrack_hash Unable to create ip_conntrack slab cache Unable to create ip_expect slab cache Unable to create ip_set_iptreeb slab cache Unable to create ip_set_iptreed slab cache
%s: cannot allocate space for
%scompressor, fname,
%s: cannot allocate space for MPPC history,
%s: cannot allocate space for MPPC history, DEBUG %s: cannot load ARC4 module, fname DEBUG %s: cannot load SHA1 module, fname
%s: CryptoAPI SHA1 digest size too small, fname
%s: cannot allocate space for SHA1 digest, fname DEBUG %s%d: trying to write outside history DEBUG %s%d: trying to write outside history DEBUG %s%d: trying to write outside history
%s%d: too big uncompressed packet:
%d,
%s%d: encryption negotiated but not an DEBUG
%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, DEBUG DEBUG DEBUG DEBUG DEBUG ic_get_currentCountry not initialized yet DEBUG Country ie is %c%c%c, DEBUG
%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, DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG ieee80211_deliver_l2uf: no buf available DEBUG
%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.2 x\t%s\t%s\t%s,
%2.2x:%2.2x:%2.2x:%2.2x:%2.2x:%2.2 x\t%s\t\t%d,
[%d]\tFunction\t%s, j, ni-
>node_trace[i].funcp DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG
%s%d: error - not an MPPC or MPPE frame ERROR Kernel doesn't provide ARC4 and/or SHA1 algorithms PPP: not interface or channel??
PPP: no memory (VJ compressor) ERROR ERROR ERROR failed to register PPP device (%d), err ERROR 205 Unified Services Router
[%d]\tMacAddr\t%s, j,
[%d]\tDescp\t\t%s, j, ni-
>node_trace[i].descp
[%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, ifmedia_set: target ifmedia_set: setting to ifmedia_ioctl: switching %s to , dev-
>name ifmedia_match: multiple match for
<unknown type>
desc->ifmt_string 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 User Manual ERROR ERROR DEBUG PPP: no memory (VJ comp pkt) DEBUG PPP: no memory (comp pkt) DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG ERROR ERROR ERROR ERROR ppp: compressor dropped pkt PPP: no memory (fragment) PPP: VJ uncompressed error ppp_decompress_frame: no memory ppp_mp_reconstruct bad seq %u <
%u, ERROR PPP: couldn't register device %s (%d), ERROR 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
%s: cannot allocate space for
%scompressor, fname,
%s: cannot allocate space for MPPC history,
%s: cannot allocate space for MPPC history, ERROR ERROR ERROR ERROR ERROR ERROR DEBUG DEBUG %s: cannot load ARC4 module, fname DEBUG %s: cannot load SHA1 module, fname DEBUG DEBUG
%s: CryptoAPI SHA1 digest size too small, fname
%s: cannot allocate space for SHA1 digest, fname ERROR ERROR ERROR ERROR ERROR DEBUG %s%d: trying to write outside history ERROR DEBUG %s%d: trying to write outside history ERROR DEBUG DEBUG DEBUG %s%d: trying to write outside history
%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 DEBUG DEBUG DEBUG
%s%s, sep, ath_hal_buildopts[i]
ath_pci: No devices found, driver not installed.
---:%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 DEBUG Could not find Board Configuration Data DEBUG Could not find Radio Configuration data DEBUG
%s: No device, __func__ DEBUG ath_ahb: No devices found, driver not installed. PKTLOG_TAG %s:proc_dointvec failed, __FUNCTION__ DEBUG PKTLOG_TAG %s:proc_dointvec failed, 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) 206 ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR Unified Services Router User Manual DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG __FUNCTION__
%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 DEBUG changing bufer size
%s:allocation failed for pl_info, __func__ DEBUG
%s: Unable to allocate buffer, __func__ DEBUG
%s:allocation failed for pl_info, __func__ DEBUG
%s: Unable to allocate buffer, __func__ DEBUG Atheros HAL assertion failure: %s: line
%u: %s, ath_hal: logging to %s %s, ath_hal_logfile, ath_hal: logging disabled DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG
%s%s, sep, ath_hal_buildopts[i]
failed to allocate rx descriptors: %d, 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,
%s: unable to reset channel %u
(%uMhz)
%s: unable to restart recv logic,
%s: start DFS WAIT period on channel
%d, __func__,sc->sc_curchan.channel PPP: VJ uncompressed error ppp_decompress_frame: no memory ppp_mp_reconstruct bad seq %u <
%u, ERROR ERROR ERROR PPP: couldn't register device %s (%d), ERROR ppp: destroying ppp struct %p but dead=%d ERROR ppp: destroying undead channel %p !, PPP: removing module but units remain!
ERROR ERROR PPP: failed to unregister PPP device ERROR JBD: bad block at offset %u, JBD: corrupted journal superblock JBD: bad block at offset %u, JBD: Failed to read block at offset %u, JBD: error %d scanning journal, err JBD: IO error %d recovering block
./Logs_kernel.txt:303:KERN_ERR
./Logs_kernel.txt:304:KERN_ERR JBD: recovery pass %d ended at DEBUG DEBUG %s: %s:%d: BAD SESSION MAGIC \
DEBUG %s: %s:%d: BAD TUNNEL MAGIC \
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 DEBUG DEBUG %s: %s:%d: BAD TUNNEL MAGIC DEBUG DEBUG %s: %s:%d: BAD TUNNEL MAGIC DEBUG socki_lookup: socket file changed!
DEBUG %s: %s:%d: BAD TUNNEL MAGIC ERROR DEBUG %s: %s:%d: BAD SESSION MAGIC \
ERROR DEBUG DEBUG %s: %s:%d: BAD TUNNEL MAGIC \
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 DEBUG DEBUG ERROR ERROR ERROR ERROR 207 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 Unified Services Router User Manual DEBUG %s: %s:%d: BAD TUNNEL MAGIC
%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 socki_lookup: socket file changed!
%s: unable to start recv logic, __func__ DEBUG %s: %s:%d: BAD TUNNEL MAGIC
%s: unable to start recv logic, __func__ DEBUG %s: %s:%d: BAD SESSION MAGIC \
%s: unable to reset hardware; hal status
%u, DEBUG %s: %s:%d: BAD TUNNEL MAGIC DEBUG hardware error; reseting 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)
%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,
%s: unable to allocate device object., __func__
%s: unable to attach hardware; HAL status %u,
%s: HAL ABI msmatch;
%s: Warning, using only %u entries in
%u key cache, unable to setup a beacon xmit queue!
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
%s:grppoll Buf allocation failed DEBUG DEBUG %s: %s:%d: BAD TUNNEL MAGIC \
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 DEBUG DEBUG DEBUG %s: %s:%d: BAD TUNNEL MAGIC DEBUG %s: %s:%d: BAD TUNNEL MAGIC DEBUG socki_lookup: socket file changed!
DEBUG %s: %s:%d: BAD TUNNEL MAGIC DEBUG rebootHook: null function pointer DEBUG Bad ioctl command DEBUG DEBUG fResetMod: Failed to configure gpio pin ERROR fResetMod: Failed to register interrupt handler ERROR DEBUG registering char device failed ERROR DEBUG unregistering char device failed DEBUG proc entry delete failed DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG proc entry initialization failed testCompHandler: received %s from
%d, (char *)pInBuf, UMI proto registration failed %d,ret AF_UMI registration failed %d,ret umi initialization failed %d,ret kernel UMI registration failed!
./Logs_kernel.txt:447:KERN_ERR ERROR msm not found properly %d, len %d, msm, DEBUG DEBUG ModExp returned Error DEBUG ModExp returned Error DEBUG %s: 0x%p len %u, tag, p, (unsigned 208 ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR Unified Services Router
,__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__ Radar found on channel %d (%d MHz), End of DFS wait period
%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
%s: missed %u consecutive beacons,
%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__
%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), 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]
Error entering wow mode int)len DEBUG %03d:, i DEBUG
%02x, ((unsigned char *)p)[i]
%s: 0x%p len %u, tag, p, (unsigned int)len DEBUG mic check failed DEBUG DEBUG %03d:, i DEBUG DEBUG mic check failed
%02x, ((unsigned char *)p)[i]
DEBUG
[%s] Wrong parameters, __func__ DEBUG
[%s] Wrong Key length, __func__ DEBUG
[%s] Wrong parameters, __func__ DEBUG DEBUG DEBUG
[%s] Wrong Key length, __func__
[%s] Wrong parameters, __func__
[%s] Wrong Key length, __func__ DEBUG
[%s] Wrong parameters, __func__ DEBUG DEBUG DEBUG DEBUG DEBUG
[%s] Wrong Key length, __func__
[%s]: Wrong parameters, __func__
[%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
[%s] Wrong parameters, __func__ DEBUG DEBUG
[%s] Wrong Key Length, __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 DEBUG
[%s] Wrong Key Length, __func__ ERROR DEBUG
[%s] Wrong parameters, __func__ ERROR DEBUG
[%s] Wrong parameters, __func__ ERROR DEBUG
[%s] Wrong parameters, __func__ ERROR DEBUG DEBUG
[%s] Wrong parameters, __func__ device name=%s not found, pReq-
ERROR ERROR 209 Unified Services Router User Manual Wakingup due to wow signal
%s, wowStatus = 0x%x, __func__, wowStatus Pattern added already Error : All the %d pattern are in use. Cannot add a new pattern , MAX_NUM_PATTERN 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 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, 0x%08x 0x%08x 0x%08x 0x%08x 0x%08x 0x%08x 0x%08x 0x%08x DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG
>ifName unable to register KIFDEV to UMI ERROR: %s: Timeout at page %#0x addr %#0x ERROR: %s: Timeout at page %#0x addr %#0x Invalid IOCTL %#08x, cmd
%s: unable to register device, dev-
>name ath_pci: 32-bit DMA not available ath_pci: cannot reserve PCI memory region ath_pci: cannot remap PCI memory region) ;
ath_pci: no memory for device state
%s: unable to register device, dev-
>name ath_dev_probe: no memory for device state
%s: no memory for device state, __func__ DEBUG kernel MIBCTL registration failed!
DEBUG Bad ioctl command DEBUG DEBUG DEBUG DEBUG DEBUG WpsMod: Failed to configure gpio pin WpsMod: Failed to register interrupt handler registering char device failed unregistering char device failed
%s:%d - ERROR: non-NULL node pointer in %p, %p<%s>!
%s:%d - ERROR: non-NULL node pointer in %p, %p<%s>!
can't alloc name %s, name
%s: unable to register device, dev-
>name failed to automatically load module:
%s; \
DEBUG DEBUG DEBUG DEBUG ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR DEBUG Unable to load needed module: %s; no support for \
ERROR DEBUG Module \%s\ is not known, buf ERROR DEBUG Error loading module \%s\, buf ERROR DEBUG Module \%s\ failed to initialize, buf ERROR 210 Unified Services Router User Manual 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]
%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 DEBUG DEBUG ath_pci: 32-bit DMA not available ath_pci: cannot reserve PCI memory region ath_pci: cannot remap PCI memory region) ;
ath_pci: no memory for device state
%s: unable to attach hardware: '%s'
(HAL status %u), DEBUG DEBUG %s: HAL ABI mismatch;
DEBUG %s: failed to allocate descriptors: %d,
%s: unable to setup a beacon xmit queue!, DEBUG DEBUG %s: unable to setup CAB xmit queue!,
%s: unable to setup xmit queue for %s traffic!,
%s: unable to register device, dev-
>name DEBUG DEBUG %s: autocreation of VAP failed: %d, DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG ath_dev_probe: no memory for device state kdot11RogueAPEnable called with NULL argument. kdot11RogueAPEnable: can not add more interfaces kdot11RogueAPGetState called with NULL argument. kdot11RogueAPDisable called with NULL argument.
%s: SKB does not exist., __FUNCTION__ DEBUG %s: recvd invalid skb DEBUG unable to register KIFDEV to UMI The system is going to factory defaults........!!!
DEBUG DEBUG %s, msg DEBUG
%02x, *(data + i) ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR CRITICAL CRITICAL CRITICAL DEBUG Inside crypt_open in driver ######
CRITICAL DEBUG DEBUG Inside crypt_release in driver ######
Inside crypt_init module in driver
CRITICAL CRITICAL DEBUG DEBUG DEBUG Inside crypt_cleanup module in driver
SKB is null : %p ,skb DST is null : %p ,dst CRITICAL CRITICAL CRITICAL 211 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 Can't allocate memory for ath_vap. Unable to add an interface for ath_dev.
%s: [%02u] %-7s , tag, ix, ciphers[hk-
>kv_type]
%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]
Cannot support setting tx and rx keys individually bogus frame type 0x%x (%s), ERROR: ieee80211_encap ret NULL ERROR: ath_amsdu_attach not called
%s: no memory for cwm attach, __func__
%s: error - acw NULL. Possible attach failure, __func__
%s: unable to abort tx dma, __func__
%s: no memory for ff attach, __func__ Failed to initiate PBC based enrolle association KERN_EMERG Returing error in INTR registration KERN_EMERG Initialzing Wps module DEBUG
%s:%d %s, __FILE__, __LINE__, __func__ DEBUG DEBUG DEV is null %p %p ,dev,dst CRITICAL DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG DEBUG Packet is Fragmented %d,pBufMgr-
>len Marked the packet proto:%d sip:%x dip:%x sport:%d dport:%d spi:%d,isr:%p:%p %p SAV CHECK FAILED IN DECRYPTION FAST PATH Breaks on BUF CHECK FAST PATH Breaks on DST CHECK FAST PATH Breaks on MTU %d %d
%d,bufMgrLen(pBufMgr),mtu,dst_mtu(
pDst->path) FAST PATH Breaks on MAX PACKET
%d
%d,bufMgrLen(pBufMgr),IP_MAX_PA CKET 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, Clearing the ISR %p,p PROTO:%d %u.%u.%u.%u---
>%u.%u.%u.%u, ESP-DONE: %p %p,sav,m DEBUG ESP-BAD: %p %p,sav,m DEBUG DEBUG DEBUG DEBUG DEBUG Bug in ip_route_input_slow(). Bug in ip_route_input_slow(). Bug in ip_route_input \
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 dst:%x,sav,skb,ip->ip_src.s_addr,ip-
>ip_dst.s_addr
%s Buffer %d mtu %d path mtu %d header %d trailer
%d,__func__,bufMgrLen(pBufMgr),mtu
,dst_mtu(pDst->path),pDst-
>header_len,pDst->trailer_len 212 CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL Unified Services Router User Manual Appendix E. RJ-45 Pin-outs Signal RJ-45 Cable Adapter Signal RJ-45 PIN DB-9 PIN NC NC 6 5 4 3 NC NC NC NC 3 5 5 2 NC NC CTS DTR TxD GND GND RxD DSR RTS NC NC RxD GND GND TxD NC NC 213 Unified Services Router User Manual Appendix F. 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. Connect the equipment into an outlet on a circuit different from that to which the receiver is Increase the separation between the equipment and receiver. 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 numrique 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. 214 Unified Services Router User Manual 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. 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). 215 Unified Services Router User Manual esky
[Czech]
Dansk
[Danish]
Deutsch
[German]
[D-Link Corporation] tmto prohlauje, e tento [DSR-1000N] je ve shod se zkladnmi poadavky a dalmi pslunmi ustanovenmi smrnice 1999/5/ES. Undertegnede [D-Link Corporation] erklrer herved, at flgende udstyr [DSR-1000N]
overholder de vsentlige krav og vrige relevante krav i direktiv 1999/5/EF. Hiermit erklrt in bereinstimmung mit den grundlegenden Anforderungen und den brigen einschlgigen Bestimmungen der Richtlinie 1999/5/EG befindet.
[D-Link Corporation], dass sich das Gert
[DSR-1000N]
Eesti
[Estonian]
Kesolevaga kinnitab [D-Link Corporation] seadme [DSR-1000N] vastavust direktiivi 1999/5/E phinuetele ja nimetatud direktiivist tulenevatele teistele asjakohastele stetele. 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. Espaol
[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]
[DSR-1000N]
1999/5/.
[D-Link Corporation]
Franais
[French]
Par la prsente [D-Link Corporation] dclare que l'appareil [DSR-1000N] est conforme aux exigences essentielles et aux autres dispositions pertinentes de la directive 1999/5/CE. Italiano
[Italian]
Latviski
[Latvian]
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. Ar o [D-Link Corporation] deklar, ka [DSR-1000N] atbilst Direktvas 1999/5/EK btiskajm prasbm un citiem ar to saisttajiem noteikumiem. Lietuvi
[Lithuanian]
iuo [D-Link Corporation] deklaruoja, kad is [DSR-1000N] atitinka esminius reikalavimus ir kitas 1999/5/EB Direktyvos nuostatas. Nederlands
[Dutch]
Malti
[Maltese]
Magyar
[Hungarian]
Polski
[Polish]
Hierbij verklaart [D-Link Corporation] dat het toestel [DSR-1000N] in overeenstemming is met de essentile eisen en de andere relevante bepalingen van richtlijn 1999/5/EG. Hawnhekk, [D-Link Corporation], jiddikjara li dan [DSR-1000N] jikkonforma mal-tiijiet essenzjali u ma provvedimenti orajn relevanti li hemm fid-Dirrettiva 1999/5/EC. Alulrott, [D-Link Corporation] nyilatkozom, hogy a [DSR-1000N] megfelel a vonatkoz alapvet kvetelmnyeknek s az 1999/5/EC irnyelv egyb elrsainak. Niniejszym [D-Link Corporation] owiadcza, e [DSR-1000N] jest zgodny z zasadniczymi wymogami oraz pozostaymi stosownymi postanowieniami Dyrektywy 1999/5/EC. 216 Unified Services Router User Manual Portugus
[Portuguese]
Slovensko
[Slovenian]
Slovensky
[Slovak]
Suomi
[Finnish]
[D-Link Corporation] declara que este [DSR-1000N]est conforme com os requisitos essenciais e outras disposies da Directiva 1999/5/CE.
[D-Link Corporation] izjavlja, da je ta [DSR-1000N] v skladu z bistvenimi zahtevami in ostalimi relevantnimi doloili direktive 1999/5/ES.
[D-Link Corporation] tmto vyhlasuje, e [DSR-1000N] spa zkladn poiadavky a vetky prslun ustanovenia Smernice 1999/5/ES.
[D-Link Corporation] vakuuttaa tten ett [DSR-1000N] tyyppinen laite on direktiivin 1999/5/EY oleellisten vaatimusten ja sit koskevien direktiivin muiden ehtojen mukainen. Svenska
[Swedish]
Hrmed intygar [D-Link Corporation] att denna [DSR-1000N] str I verensstmmelse med de vsentliga egenskapskrav och vriga relevanta bestmmelser som framgr av direktiv 1999/5/EG. 217 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. Connect the equipment into an outlet on a circuit different from that to which the receiver is Increase the separation between the equipment and receiver. 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 numrique 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. 218 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. 219 Unified Services Router User Manual esky
[Czech]
Dansk
[Danish]
[D-Link Corporation] tmto prohlauje, e tento [DSR-500N] je ve shod se zkladnmi poadavky a dalmi pslunmi ustanovenmi smrnice 1999/5/ES. Undertegnede [D-Link Corporation] erklrer herved, at flgende udstyr [DSR-500N]
overholder de vsentlige krav og vrige relevante krav i direktiv 1999/5/EF. Deutsch
[German]
Hiermit erklrt [D-Link Corporation], dass sich das Gert [DSR-500N] in bereinstimmung mit den grundlegenden Anforderungen und den brigen einschlgigen Bestimmungen der Richtlinie 1999/5/EG befindet. Eesti
[Estonian]
Kesolevaga kinnitab [D-Link Corporation] seadme [DSR-500N] vastavust direktiivi 1999/5/E phinuetele ja nimetatud direktiivist tulenevatele teistele asjakohastele stetele. 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. Espaol
[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]
Franais
[French]
Italiano
[Italian]
Latviski
[Latvian]
[D-Link Corporation] [DSR-500N]
1999/5/. Par la prsente [D-Link Corporation] dclare que l'appareil [DSR-500N] est conforme aux exigences essentielles et aux autres dispositions pertinentes de la directive 1999/5/CE. 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. Ar o [D-Link Corporation] deklar, ka [DSR-500N] atbilst Direktvas 1999/5/EK btiskajm prasbm un citiem ar to saisttajiem noteikumiem. Lietuvi
[Lithuanian]
iuo [D-Link Corporation] deklaruoja, kad is [DSR-500N] atitinka esminius reikalavimus ir kitas 1999/5/EB Direktyvos nuostatas. Nederlands
[Dutch]
Malti
[Maltese]
Hierbij verklaart [D-Link Corporation] dat het toestel [DSR-500N] in overeenstemming is met de essentile eisen en de andere relevante bepalingen van richtlijn 1999/5/EG. Hawnhekk, [D-Link Corporation], jiddikjara li dan [DSR-500N] jikkonforma mal-tiijiet essenzjali u ma provvedimenti orajn relevanti li hemm fid-Dirrettiva 1999/5/EC. Magyar
[Hungarian]
Alulrott, [D-Link Corporation] nyilatkozom, hogy a [DSR-500N] megfelel a vonatkoz alapvet kvetelmnyeknek s az 1999/5/EC irnyelv egyb elrsainak. Polski
[Polish]
Niniejszym [D-Link Corporation] owiadcza, e [DSR-500N] jest zgodny z zasadniczymi wymogami oraz pozostaymi stosownymi postanowieniami Dyrektywy 1999/5/EC. 220 Unified Services Router User Manual Portugus
[Portuguese]
Slovensko
[Slovenian]
Slovensky
[Slovak]
Suomi
[Finnish]
[D-Link Corporation] declara que este [DSR-500N]est conforme com os requisitos essenciais e outras disposies da Directiva 1999/5/CE.
[D-Link Corporation] izjavlja, da je ta [DSR-500N] v skladu z bistvenimi zahtevami in ostalimi relevantnimi doloili direktive 1999/5/ES.
[D-Link Corporation] tmto vyhlasuje, e [DSR-500N] spa zkladn poiadavky a vetky prslun ustanovenia Smernice 1999/5/ES.
[D-Link Corporation] vakuuttaa tten ett [DSR-500N] tyyppinen laite on direktiivin 1999/5/EY oleellisten vaatimusten ja sit koskevien direktiivin muiden ehtojen mukainen. Svenska
[Swedish]
Hrmed intygar [D-Link Corporation] att denna [DSR-500N] str I verensstmmelse med de vsentliga egenskapskrav och vriga relevanta bestmmelser som framgr av direktiv 1999/5/EG. 221 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. Connect the equipment into an outlet on a circuit different from that to which the receiver is Increase the separation between the equipment and receiver. 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. connected. RSS-GEN 7.1.2:
Under Industry Canada regulations, this radio transmitter may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by Industry Canada. 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 necessary for successful communication. RSS-GEN 7.1.3 222 Unified Services Router User Manual 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 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. 223
frequency | equipment class | purpose | ||
---|---|---|---|---|
1 | 2011-06-26 | 2422 ~ 2452 | DTS - Digital Transmission System | Original Equipment |
app s | Applicant Information | |||||
---|---|---|---|---|---|---|
1 | Effective |
2011-06-26
|
||||
1 | Applicant's complete, legal business name |
D-Link Corporation
|
||||
1 | FCC Registration Number (FRN) |
0007371172
|
||||
1 | Physical Address |
17595 Mt. Herrmann
|
||||
1 |
Fountain Valley, 92708
|
|||||
1 |
United States
|
|||||
app s | TCB Information | |||||
1 | TCB Application Email Address |
c******@ccsemc.com
|
||||
1 | TCB Scope |
A4: UNII devices & low power transmitters using spread spectrum techniques
|
||||
app s | FCC ID | |||||
1 | Grantee Code |
KA2
|
||||
1 | Equipment Product Code |
SR250NA1
|
||||
app s | Person at the applicant's address to receive grant or for contact | |||||
1 | Name |
B******** A******
|
||||
1 | Title |
General Counsel
|
||||
1 | Telephone Number |
714-8********
|
||||
1 | Fax Number |
866-7********
|
||||
1 |
b******@dlink.com
|
|||||
app s | Technical Contact | |||||
n/a | ||||||
app s | Non Technical Contact | |||||
n/a | ||||||
app s | Confidentiality (long or short term) | |||||
1 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
1 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
1 | Is this application for software defined/cognitive radio authorization? | No | ||||
1 | Equipment Class | DTS - Digital Transmission System | ||||
1 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | Wireless N Service Router | ||||
1 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
1 | Modular Equipment Type | Does not apply | ||||
1 | Purpose / Application is for | Original Equipment | ||||
1 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | No | ||||
1 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
1 | Grant Comments | Power listed is the maximum combined conducted output power. Device is Router operating in a 2x2 Spatial Multiplexing MIMO configuration as described in this filing. End-users and responsible parties must be provided with operating and installation instructions to ensure RF exposure compliance. The antenna(s) used for this transmitter must be installed to provide a separation distance of at least 20 cm from all persons and must not be collocated or operating in conjunction with any other antenna or transmitter within a host device, except in accordance with FCC multi-transmitter product procedures. | ||||
1 | Is there an equipment authorization waiver associated with this application? | No | ||||
1 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
app s | Test Firm Name and Contact Information | |||||
1 | Firm Name |
Compliance Certification Services Inc.
|
||||
1 | Name |
K******** C******
|
||||
1 | Telephone Number |
886-3******** Extension:
|
||||
1 | Fax Number |
886-3********
|
||||
1 |
k******@ccsrf.com
|
|||||
Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
1 | 1 | 15C | 2412 | 2462 | 0.279 | ||||||||||||||||||||||||||||||||||||
1 | 2 | 15C | MO | 2412 | 2462 | 0.391 | |||||||||||||||||||||||||||||||||||
1 | 3 | 15C | MO | 2422 | 2452 | 0.354 |
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC