ip access IPA219C 3G Picocellular basestation User Manual nano3GAP Installation Manual

ip.access ltd 3G Picocellular basestation nano3GAP Installation Manual

Installation manual

nano3GAP Installation Manual N3G_INST_300 2.0 ip.access Ltd Building 2020 Cambourne Business Park Cambourne Cambridgeshire CB23 6DW United Kingdom www.ipaccess.com
nano3GAP Installation Manual © ip.access Ltd Revision History Version Change Summary Date Author 0.1 First draft 29 Apr 09 ZN1 0.2 Updated from feedback 06 May 09 ZN1 0.3 Updated from further feedback 07 May 09 ZN1 0.4 Updated from review comments 08 May 09 ZN1 0.5 Added license texts, updated with minor comments 12 May 09 ZN1 0.6 Updated the instructions on deployment commissioning 05 Jun 09 ZN1 0.7 Updated with input from System Testing 24 Jul 09 ZN1 0.8 Updated from feedback from System Testing 27 Jul 09 ZN1 0.9 Added instructions to changing the IP configuration of the commissioning PC 27 Jul 09 ZN1 0.10 Implemented review comments 28 Jul 09 ZN1 0.11 Minor corrections before approval 29 Jul 09 ZN1 1.0 Released for N3G_1.1 29 Jul 09 ZN1 1.1 Added information on type approval and EMC standards Updated information on electrical ratings and PSUs 28 Aug 09 ZN1 1.2 Implemented review comments 28 Aug 09 ZN1 2.0 Released for N3G_1.1_UPGRADE 28 Aug 09 ZN1 Approved by e-mail. The information contained in this manual is commercially confidential and must not be disclosed to third parties without prior consent.
nano3GAP Installation Manual © ip.access Ltd Table of Contents 1 Introduction ..................................................................................................... 1 1.1 Installation Overview......................................................................................... 1 1.2 Related Information........................................................................................... 1 1.3 Terminology ...................................................................................................... 2 2 Installation Requirements .............................................................................. 3 2.1 nano3GAP Site Requirements.......................................................................... 3 2.1.1 nano3GAP-4 Site Requirements............................................................................ 3 2.2 Installation Tool Requirements ......................................................................... 6 2.3 Information Needed for Installation ................................................................... 7 2.3.1 Network Information ............................................................................................... 7 2.3.2 AP Configuration File ............................................................................................. 7 3 nano3GAP Hardware Installation .................................................................. 8 3.1 Warnings and Regulatory Information .............................................................. 8 3.2 Hardware Installation - nano3GAP-4 ................................................................ 8 3.2.1 Unpacking the nano3GAP-4 .................................................................................. 8 3.2.2 Mounting the nano3GAP-4..................................................................................... 8 4 Deployment Commissioning of the nano3GAP ......................................... 11 4.1 Configure the IP Settings of the Provisioning Laptop ..................................... 11 4.2 Configure the Connection to the AP ............................................................... 12 4.3 Set the IP Configuration of the AP .................................................................. 14 5 Configuration of the nano3GAP-4 from the OMC-R................................... 15 5.1 Start the OMC-R Client ................................................................................... 15 5.2 Download the Latest nano3GAP-4 Software Image ....................................... 17 5.3 Create an Attribute Configuration File for the AP............................................ 17 5.4 Download the Attribute Configuration to the AP ............................................. 18 5.5 Perform AP-specific Configuration.................................................................. 18 5.6 Bring the AP into Service ................................................................................ 18 6 Troubleshooting............................................................................................ 19 6.1 Internet Connection Problems ........................................................................ 19 6.2 LED Status Indicators ..................................................................................... 19 6.3 Factory Reset.................................................................................................. 20
nano3GAP Installation Manual © ip.access Ltd 7 nano3GAP and PSU Regulatory Information ............................................. 21 7.1 Warnings and Cautions................................................................................... 21 7.2 Regulatory Statements ................................................................................... 22 7.2.1 Type Approval and EMC Standards .................................................................... 22 7.2.2 Safety Standards.................................................................................................. 23 8 Appendices.................................................................................................... 24 8.1 Appendix A - Example AP Configuration File ................................................. 24 8.2 Appendix B - Licenses and Copyright Notices................................................ 25 8.2.1 asn1c.................................................................................................................... 25 8.2.2 bash...................................................................................................................... 25 8.2.3 BusyBox ............................................................................................................... 25 8.2.4 cramfs................................................................................................................... 25 8.2.5 dropbear ............................................................................................................... 26 8.2.6 glibc ...................................................................................................................... 26 8.2.7 gmp ...................................................................................................................... 26 8.2.8 ipkg....................................................................................................................... 26 8.2.9 iproute2 ................................................................................................................ 26 8.2.10 iptables ................................................................................................................. 26 8.2.11 libcurl .................................................................................................................... 26 8.2.12 libgcc .................................................................................................................... 27 8.2.13 libpcap .................................................................................................................. 27 8.2.14 libxml2 .................................................................................................................. 27 8.2.15 Linux Kernel ......................................................................................................... 27 8.2.16 mtd.utils ................................................................................................................ 27 8.2.17 ncurses................................................................................................................. 28 8.2.18 NTP daemon ........................................................................................................ 28 8.2.19 pcre ...................................................................................................................... 28 8.2.20 procps................................................................................................................... 30 8.2.21 SSL Stack............................................................................................................. 30 8.2.22 StrongSwan.......................................................................................................... 30 8.2.23 TCL....................................................................................................................... 30 8.2.24 tcpdump................................................................................................................ 31 8.2.25 thttpd .................................................................................................................... 31 8.2.26 U-Boot .................................................................................................................. 31 8.2.27 zlib ........................................................................................................................ 31 8.2.28 General Licenses ................................................................................................. 31
nano3GAP Installation Manual Introduction © ip.access Ltd Page 1 1 Introduction The ip.access nano3GAP-4 is an indoor pico-class base station. This document provides the reader with all the necessary information required to install the ip.access nano3GAP-4. The document provides step-by-step instructions for hardware installation, PSU Installation, and configuration steps required to bring the nano3GAP-4 into service. The AP can be configured with a static IP address or it can obtain its IP address dynamically via DHCP. The AP-AC connection can be configured to be secure (via IPSec) or unsecured. 1.1 Installation Overview The principal activities for installing and commissioning a nano3GAP are: 1) Install the nano3GAP hardware and power it up (installation engineer on site, section 3). 2) Commission the nano3GAP for connecting to an AC and OMC-R (installation engineer on site, section 4). 3) Configure the nano3GAP from the OMC-R to bring it to into service (OAM engineer remotely from the NOC, section 5). 1.2 Related Information [GST_100] nano3G System Overview Manual (N3G_GST_100) [GST_120] nano3G System Planning and Provisioning Manual (N3G_GST_120) [GST_300] nano3GAP Product Description (N3G_GST_300) [GST_400] nano3G OMC-R Product Description (N3G_GST_400) [INST_200] Nano3G AC Installation Manual (N3G_INST_200) [INST_400] nano3G OMC-R Installation Manual (N3G_INST_400) [OPM_300] nano3GAP Operations Manual (N3G_OPM_300) [OPM_410] nano3G OMC-R Client Operations Manual (N3G_OPM_410) [OPM_430] nano3G OAM File Server Operations Manual (N3G_OPM_430) [REF_105] nano3G System Glossary (N3G_REF_105) [REF_150] Iu+ Networking Reference Manual (N3G_REF_150) [21.905] Vocabulary for 3GPP Specifications, 3rd Generation Partnership Project
nano3GAP Installation Manual Introduction © ip.access Ltd Page 2 1.3 Terminology For standard nano3G System terminology, see [REF_105]. For additional standard GSM terminology, see [21.905].
nano3GAP Installation Manual Installation Requirements © ip.access Ltd Page 3 2 Installation Requirements 2.1 nano3GAP Site Requirements 2.1.1 nano3GAP-4 Site Requirements The nano3GAPs are installed in retail or small office environments. In summary, each AP will require: • One of: o A suitable mains power supply point within [1.5] metres of the intended AP site. o Power over Ethernet (where mains power is remote). • An Ethernet connection that provides an IP address (via static addressing or via DHCP) and a route to the public Internet. A DNS service is also required to resolve symbolic addresses. • Site for wall mounting or a stable free-standing position. • Cat5 cable. 2.1.1.1 Power Maximum expected power consumption: 13 Watts (Rated 9VDC 1450mA) The nano3GAP-4 supports the following power and Ethernet cabling options at a site: • Direct power from a power adapter • Power-over-Ethernet o from a POE switch o from a POE inserter
nano3GAP Installation Manual Installation Requirements © ip.access Ltd Page 4 The connections are shown in the figure below. nano3GAP-4 Ethernet and power connections The power adapter, as well as the POE inserter and splitter supplied by ip.access comply with LPS requirements in accordance with IEC/EN 60950-1. Power Adapter A suitable mains power supply point into which the power adapter for the AP can be plugged. This should be within [1.5] metres of the intended installation position of the AP. Only use the power adapter supplied by ip.access to power the AP: ip.access part number EPS1173R manufactured by Dee Van Enterprise Co Ltd. model DSA-20P-10 input 100-240V ~ 50/60Hz 0.7A output +9VDC 1.67A Power over Ethernet POE comprises of a power inserter and a splitter. The power inserter is positioned close to the Internet connection, while the splitter is positioned close to the AP. Only use the POE inserter supplied by ip.access: ip.access part number 109A manufactured by PPI Co Ltd model ILA1711112 input 100/230V ~ 60/50Hz 0.5/0.25A output 48VDC 0.38A
nano3GAP Installation Manual Installation Requirements © ip.access Ltd Page 5 POE inserter Only use the POE splitter supplied by ip.access: ip.access part number 222A manufactured by MIT model MIT-061-1209-IP input 48VDC 0.35A output 9VDC 1.33A POE splitter
nano3GAP Installation Manual Installation Requirements © ip.access Ltd Page 6 2.1.1.2 Physical The nano3GAP may be installed in the following ways: • free-standing on a flat stable surface (section 3.2.2.1) • attached to a wall or partition using the two screws which engage in keyhole slots in the rear surface of the AP (section 3.2.2.2) • attached to a POE splitter using the two screws which engage in keyhole slots in the rear surface of the AP; the POE splitter in turn attaches to a wall or partition using two screws (section 3.2.2.3) Attention should also be paid to ensuring free air circulation around the unit. The unit must be vertical. It is recommended that the AP is installed with its front surface facing the area requiring cellular coverage, unobscured by walls or partitions that may have significant RF attenuation. Height 176 mm (without stand) 193mm (with stand) Width 170 mm Depth 51 mm Dimensions and Weight Approximate Weight 0.42 Kg (AP only) Cooling Vents on the back at top and bottom Operating Temperature 0°C to 40°C Environmental Operating Humidity 10 to 70% non-condensing 2.1.1.3 IP Bandwidth Requirements At maximum capacity, a 4-Channel nano3GAP will require: • downlink: at least 5Mbps • uplink: 512kbps This will deliver up to 4 voice calls and HSDPA services up to 3.6Mbps. 2.2 Installation Tool Requirements • To mount the POE splitter or the AP onto the wall: o 2 self tapping pan head screws, size No. 6 (approx 3.5mm (0.14in) in diameter) o suitable drills, screwdriver, etc. • Provisioning laptop: o OS: Windows XP o web browser: Microsoft Internet Explorer 7
nano3GAP Installation Manual Installation Requirements © ip.access Ltd Page 7 o JavaScript enabled in the web browser 2.3 Information Needed for Installation 2.3.1 Network Information Installation Engineer: • subnet information: the installation laptop and the nano3GAP-4 to be configured must be on the same subnet • username and password for the AP web server • address of the security gateway • address of the serving 3G AC • ID of this AP on the serving 3G AC • CRL and NTP server addresses • DHCP or static IP • if IPSec is used: Traffic Selector information (IP address and subnet mask) NOC Engineer: • Username and password to the OMC-R • The valid URL to the latest AP software image on the OAM File Server • Configuration file to be used in the OMC-R Load Attributes Wizard (nano3GAP-4s hold the master copy of their own configuration and are not pre-provisioned via the OMC-R) • Configuration data for the AP: o MCC o MNC o LAC o SAI o SAC/LAC o UARFCN o Scrambling code o RNC ID o RAC 2.3.2 AP Configuration File Create a separate attributes file for each AP to commission (section 5.3).
nano3GAP Installation Manual nano3GAP Hardware Installation © ip.access Ltd Page 8 3 nano3GAP Hardware Installation This section documents the procedure used to install the nano3GAP-4 hardware and physical connections together with applying the base software configuration. 3.1 Warnings and Regulatory Information For all warnings and regulatory information, refer to section 7. 3.2 Hardware Installation - nano3GAP-4 3.2.1 Unpacking the nano3GAP-4 1) Unpack the nano3GAP-4, the stand and the POE splitter unit. Note: No screws are supplied to mount the AP or the splitter unit. 2) Check that the items have not been damaged in transit. Any damaged units should be returned to the supplier. 3.2.2 Mounting the nano3GAP-4 Note: The nano3GAP-4 should be installed in a position so that it is at least 2m away from the area where handsets are normally used. The nano3GAP-4 can be mounted in the following ways: • on a stand • directly onto the wall at or above head height • onto the splitter unit at or above head height The nano3GAP-4 has 2 holes at the back for the latter two mounting options:
nano3GAP Installation Manual nano3GAP Hardware Installation © ip.access Ltd Page 9 3.2.2.1 Mounting the nano3GAP-4 on a Stand 1) Plug the Ethernet cable and the power cable into the AP. 2) Slide the AP onto the stand. 3) Place the stand with the AP onto a stable flat surface. nano3GAP-4 mounted on a stand 3.2.2.2 Mounting the nano3GAP-4 directly onto the wall 1) Drill two holes 70mm (2.76in) apart vertically for the two screws. 2) Insert wall plugs (if required) and secure the screws leaving approximately 3mm (0.12in) clearance between the screw heads and the wall. 3) Plug the Ethernet cable and the power cable into the AP. 4) Slide the AP onto the 2 screws. nano3GAP-4 mounted directly on the wall
nano3GAP Installation Manual nano3GAP Hardware Installation © ip.access Ltd Page 10 3.2.2.3 Mounting the nano3GAP-4 onto the splitter unit on the wall 1) Secure the splitter unit to the wall using two screws. Ensure that the Ethernet socket is at the top. 2) Plug the Ethernet cable into the splitter unit. 3) Plug the Ethernet cable and the power cable coming from the splitter unit into the AP. 4) Mount the AP onto the 2 screws that are already fixed onto the splitter unit. nano3GAP-4 mounted on the POE splitter
nano3GAP Installation Manual Deployment Commissioning of the nano3GAP © ip.access Ltd Page 11 4 Deployment Commissioning of the nano3GAP Deployment commissioning is performed typically on site, with a provisioning laptop. The nano3GAP-4 must be in factory reset status for the commissioning. For instructions on performing a factory reset, see section 6.3. 4.1 Configure the IP Settings of the Provisioning Laptop 1) Open the control panel on the laptop. 2) Select Network Connections, select the relevant Local Area Connection, then right-click Properties. The following Dialog box appears:
nano3GAP Installation Manual Deployment Commissioning of the nano3GAP © ip.access Ltd Page 12 3) Select Internet Protocol (TCP/IP) and then click Properties. The following Dialog box appears: 4) Change the properties to Use the following IP address. 5) Set the IP Address to 192.168.0.2. 6) Set the Subnet Mask to 255.255.255.0. Note: The provisioning laptop and the AP must be in the same subnet. 7) Click OK and close the two dialog boxes. 4.2 Configure the Connection to the AP 8) Connect the AP to the Ethernet interface of the provisioning laptop via an Ethernet cable. 9) Apply power to the AP. 10) Start a web browser on the laptop. 11) Enter the pre-defined static IP address for the web server: 192.168.0.1. A login screen appears.
nano3GAP Installation Manual Deployment Commissioning of the nano3GAP © ip.access Ltd Page 13 12) Enter the commissioning username and the password (supplied separately). The default page (Connection Configuration) appears. 13) Edit the configuration information: It is recommended to leave the default NTP server address as default. Note: The CRL Server Base URL is embedded in the IPSec Gateway address in the current release. Therefore, this field will be left empty. 14) Save the configuration by clicking Apply Changes. 15) Start the AP in normal operation mode by clicking Complete Commissioning. 16) When the initial configuration is completed, power off the AP and disconnect it from the laptop. 17) Mount the AP at its intended location, see section 3.2.2. 18) Connect the AP to the operator network and apply power. The AP performs its normal, deployed mode start-up and connects to its host AC: During this procedure, the nano3GAP-4 obtains network time and day information from the NTP server and – if IPSec is in use – it establishes an IPSec tunnel to the Security Gateway. From this point on, the AP can be managed from the OMC-R. It is now ready for initial configuration by NOC engineers, see section 5.
nano3GAP Installation Manual Deployment Commissioning of the nano3GAP © ip.access Ltd Page 14 4.3 Set the IP Configuration of the AP 19) Click the IP Config link on the left of the screen. 20) Edit the parameters as needed and then click Apply. 21) Click the Connection Config link on the left of the screen and then click Complete Commissioning. 22) Read the warning and click OK to complete commissioning.
nano3GAP Installation Manual Configuration of the nano3GAP-4 from the OMC-R © ip.access Ltd Page 15 5 Configuration of the nano3GAP-4 from the OMC-R The nano3GAP-4 needs to be configured before it is brought into service. The NOC engineer must perform the configuration via the OMC-R Client. 5.1 Start the OMC-R Client The OMC-R Server provides a web page to start the OMC-R Client. 1) Start a web browser application. 2) Enter the URL for the OMC-R server’s web page as: http://<server-hostname>/omcr Where <server-hostname> is the fully qualified hostname of the OMC-R server. Note: This assumes that DNS is correctly configured on the management network: the OMC-R server can be found by using its host name from client computers on the same network. Note: If a redundant configuration is used, the IP address entered here is a virtual IP address that will ensure that the connection to the active OMC-R Server can be set up without further actions from the client. 3) Press the Enter key and the OMC-R web page will appear.
nano3GAP Installation Manual Configuration of the nano3GAP-4 from the OMC-R © ip.access Ltd Page 16 4) If it has not been installed on the client computer, click the link to download and install the Java runtime (JRE version 1.5) for Windows®. This will allow a Windows® client computer to run the OMC-R Client. Note: When installed on Windows®, the JRE may automatically update to version 1.6. The OMC-R Client will operate correctly with JRE 1.6. However, do not install any version later than 1.6 (or allow JRE to be automatically updated; for example, decline the update if prompted). The Java Control Panel may be used to disable automatic updates and/or disable usage of JRE versions later than 1.6. 5) The OMC-R Client is automatically installed when it is started. Click the link or icon for Start 3G OMC-R Client. If this is the first time the OMC-R Client has been started from this client computer, or if the client version on the OMC-R Server has been updated, the client application will download (which also installs the application). If a security warning appears about verification of the digital signature for the application, click the Run button. 6) The OMC-R Client will initialize and connect to the OMC-R Server. A login prompt will appear. The first time the client is used from a particular computer, the User name will be set to the log in ID used for the current session on the client computer. 7) Enter the username and password, then click OK. The user name will be remembered at the next login. 8) The OMC-R Client will initialize and connect to the OMC-R Server. The following screen appears:
nano3GAP Installation Manual Configuration of the nano3GAP-4 from the OMC-R © ip.access Ltd Page 17 9) Double-click through the tree (Management Views > Configuration Management) to navigate to the AP to configure. 5.2 Download the Latest nano3GAP-4 Software Image If the AP already has the latest software version, skip this section. The latest software image is downloaded to the AP from the OAM File Server. For instructions about how the software images are uploaded to the OAM File Server, see [OPM_430]. 10) Make sure that you have the URL to the latest software image file (SDP file) stored on the OAM File Server. 11) Select the AP in the OMC-R Client. 12) Right-click the AP, select Actions and then Perform Software Download. 13) In the Perform Software Download Actions window, enter the URL of the latest SDP file. 14) Select whether the image file should be downloaded only, or it should be swapped with the older image file, and whether the older image file should be removed from the standby folder on the AP. 15) Click Finish. The download in progress is indicated by the flashing network LED on the AP. 16) Monitor the 3G AP Admin Package of the AP object in the OMC-R Client. 17) When the standby software version is the version of the downloaded image, right-click the AP, select Action, and then select Swap Default Software. 18) Right-click the AP object again and then select Reinitialize. 19) Wait for the AP to be shown as connected to the OMC-R. 20) In the 3G AP Admin Package of the AP object, check that the Active Software Version is that of the new SDP. 5.3 Create an Attribute Configuration File for the AP The attributes to configure a nano3G-4 AP are stored in a text file. The file can be created and edited manually in any text editor. For a sample file, see section 8.1. To create the configuration file by using an existing one: 21) Log in to the OMC-R (see section 5.1). 22) Start the OMC-R Load Attributes Wizard: right-click on any existing AP object in the OMC-R Client and then select Save Attributes to File. 23) Save the file under a new name. 24) Edit the file in a text editor.
nano3GAP Installation Manual Configuration of the nano3GAP-4 from the OMC-R © ip.access Ltd Page 18 5.4 Download the Attribute Configuration to the AP 25) Ensure that the attribute configuration file is available on the configuration PC or at a location reachable from the configuration PC. For information on the AP configuration file, see section 8.1. 26) Log in to the OMC-R (see section 5.1). 27) Start the OMC-R Load Attributes Wizard: right-click on the AP object in the OMC-R Client and then select Load Attributes From File. 28) Browse to the configuration file and click Apply to load and apply the configuration settings. If any of the loaded values are inconsistent with the current state of the AP or if any of the values are illegal, the wizard displays a warning. 5.5 Perform AP-specific Configuration 29) Perform any AP-specific configurations. In particular, check and modify the attributes of the following packages as needed: o Network Listen Control Package Note: Ensure that the Neighbour List Population attribute is set to Static Only. Note: Ensure that the Scan Interval attribute in the package RF Scan Control is set so that the NWL scan does not disrupt the service. Scheduled NWL scans should be timed for low-usage time slots. NWL scans can be also disabled by setting the Scan Interval attribute to 0. In this case, the NWL scan can be run manually at any time, see the next step. o Cell Package o NAS Package o Location Package 30) Run a Network Listen scan: right-click the AP object, select Actions and then select Start Sequential NWL Scan. 31) Ensure that the oscillator frequency is correct: select Actions and then select Apply Frequency Correction. 5.6 Bring the AP into Service 32) Unlock the AP to bring it into service. The AP now has the latest software image and is ready for service.
nano3GAP Installation Manual Troubleshooting © ip.access Ltd Page 19 6 Troubleshooting 6.1 Internet Connection Problems If static IP addressing is disabled and DHCP is in use, the nano3GAP-4 expects to be automatically provided with an IP address by the broadband router every time it starts. Ensure that the DHCP service is enabled on the broadband router. 6.2 LED Status Indicators The following table shows the meaning of the state LED under normal and fault conditions. Off The nano3GAP-4 is not switched on. Green The nano3GAP-4 is powered up normally. Flashing green Self-test is running. Power Red There is a fault with the nano3GAP-4. Note: At power-up, this LED will light solid red by default. Off Unable to detect a network. This is usually because there is no network cable connected, or there is no network connection at the other end of the cable (for example, the router or broadband modem may have failed or may not be switched on). Green The 100Mbps connection is OK. Flashing green Indicates activity on the network at 100Mbps speed (that is, the nano3GAP-4 is sending and/or receiving data across the LAN). Amber The 10Mbps connection is OK. Flashing amber Indicates activity on the network at 10Mbps speed (that is, the nano3GAP-4 is sending and/or receiving data across the LAN). Network Note: This LED is driven by Ethernet hardware. Off The nano3GAP-4 is not provisioned, it has no IP address. This may be a temporary condition when you switch on the AP for the first time, or after you have performed a factory reset. Green The nano3GAP-4 is provisioned and unlocked. Flashing green (slow) The nano3GAP-4 is provisioned and locked. Service Flashing green (fast) Software download is in progress to the nano3GAP-4.
nano3GAP Installation Manual Troubleshooting © ip.access Ltd Page 20 6.3 Factory Reset Factory reset can help in case the AP does not connect. The AP configuration will need to be redone manually, see section 4.2. To perform factory reset, press the factory reset button and hold it for more than 10 seconds. When the button is initially pressed, the LED will blink fast (50ms on:50ms off) for 5 seconds, then it will start to blink slowly (200ms on: 200ms off). When the factory restore process has completed, the LED will extinguish and the AP will automatically reboot, take the fixed IP address and enable the web interface for configuration (see section 4).
nano3GAP Installation Manual nano3GAP and PSU Regulatory Information © ip.access Ltd Page 21 7 nano3GAP and PSU Regulatory Information This chapter provides the customer with safety and regulatory warnings, cautions and information for the ip.access Ltd range of products. 7.1 Warnings and Cautions Electrical Safety CAUTION The nano3GAP-4 is intended for dry indoor applications only. If evidence of condensation is present do not apply power to the nano3GAP-4. WARNING Do not immerse any part of the nano3GAP-4 or its power supply in water or any other liquid. Do not install or use the nano3GAP-4 or its power supply near open water. Do not spill liquids of any type on the nano3GAP-4 or its power supply. WARNING Do not use liquid, solvent or aerosol cleaning agents on or near the nano3GAP-4 or its power supply. CAUTION To avoid the risk of fire and/or electrical shock, do not push objects through openings into the nano3GAP-4 or its power supply (except when operating the Reset switch on the nano3GAP-4). CAUTION Do not disassemble the nano3GAP-4 or its power supply. CAUTION The nano3GAP-4 must only be powered using the ip.access power supply provided for use with the nano3GAP-4. CAUTION Before using the power supply, verify that the mains voltage is within the range specified by the voltage printed on the power supply. CAUTION The PSU supplied with the nano3GAP-4 must not be used for powering any other equipment. CAUTION To avoid the risk of fire and/or electrical shock, do not overload power outlets or extension cables. CAUTION When disconnecting the power supply from the mains, pull the plug. Pulling the cable may result in damage to the cable.
nano3GAP Installation Manual nano3GAP and PSU Regulatory Information © ip.access Ltd Page 22 Interference with Electronic Devices CAUTION If using a pacemaker, ensure you are using the device in accordance with its safety requirements with respect to RF devices. Consult your doctor if you have questions about RF signals and your pacemaker. CAUTION If using a hearing aid, RF devices may cause interference. CAUTION Unshielded electronic devices should not be used near the nano3GAP-4. Conversely, the nano3GAP-4 should not be installed adjacent to unshielded electrical or electronic devices (such as unshielded speakers). Other Warnings and Cautions WARNING Do not install the nano3GAP-4 in a position where the power supply cable or network cable may cause a tripping or choking hazard. WARNING Do not install the nano3GAP-4 or the power supply on an unstable surface. All caution must be observed to prevent the device from falling and causing injury to a person and/or damage to the device. WARNING The nano3GAP-4 should not be disposed of in household waste bins. Please follow local regulations for disposal of electronic devices. CAUTION Do not install the nano3GAP-4 in a position where the power supply cable or network cable may be damaged by walking on the cables. CAUTION Do not attempt to fit an external antenna or antenna cabling to the nano3GAP-4. 7.2 Regulatory Statements 7.2.1 Type Approval and EMC Standards • FCC CFR47 Parts 15B, 27 Note: Changes or modifications not expressly approved by the party responsible for compliance may void the user's authority to operate this equipment. Model nano3G 219C has FCC ID QGGIPA219C
nano3GAP Installation Manual nano3GAP and PSU Regulatory Information © ip.access Ltd Page 23 WARNING This is a class B product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures. Federal Communications Commission Note: 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 when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense. 7.2.2 Safety Standards • IEC 60950-1:2005 (2nd Edition) and EN 60950-1:2006 The power adapter, as well as the POE inserter and splitter supplied by ip.access comply with LPS requirements in accordance with IEC/EN 60950-1.
nano3GAP Installation Manual Appendices © ip.access Ltd Page 24 8 Appendices 8.1 Appendix A - Example AP Configuration File A configuration file with the object name and the objects instance (relative distinguished name) must be created for each AP to be commissioned. For instructions to use the configuration file, see section 5.3. The file has to conform to the following syntax: • all non-comment lines are of the form <name>=<value> • comment lines begin with the hash character (#) • attribute types are as follows: o integer tos=0 o enumeration t300=T300_4000_MSEC o array ascPersistenceScalingFactors=[6,6,6,6,6,6] o boolean soipHeartbeatEnabled=true o structure cellBroadcastMessage={50,GSM_DEFAULT,”oyster 3G”} o string “HMAC-SHA1” o set alarmFilter=() # Instance for the AP to be modified Object=apNano_001 ObjectInstance=ROOT#0;AC_CONNECTION#12007;RNS#0;AP_CONTROLLER# 0;AP_CONNECTION#31;AP#0 # Cell Package rncIdentity=139 # NAS Package mcc="159" mnc="12" sac=1 saiLac=1 # Network Listen Control Package lacRacCandidateList=({15912,(99)}) rfParamsCandidateList=({1062,437,1}) rssiScanBands=({BAND_NAME_UMTS_BAND_04_NO_SPOT,()}) # end of file Parameter Description Object ID of the AP
nano3GAP Installation Manual Appendices © ip.access Ltd Page 25 ObjectInstance Relative Distinguished Name rncIdentity ID of the AC Mcc Mobile Country Code Mnc Mobile Network Code Sac Service Access Code saiLac SAC Location Area Code lacRacCandidateList LAC and RAC list rfParamsCandidateList Radio Frequency parameter list rssiScanBands Scanning frequency bands for received signal strength indication 8.2 Appendix B - Licenses and Copyright Notices Portions of the AP are constructed from third-party software and open source code and ip.access ltd gratefully acknowledges the contributions that these libraries, technologies and components have made to the product. Each of these is supplied under the terms of a license agreement and these are either reproduced or referenced below in line with the stipulations of their authors. 8.2.1 asn1c asn1c by Lev Walkin (vlm@lionet.info) is covered by a BSD-type license: See the file "COPYING" in the source package 8.2.2 bash bash by GNU is covered by the GNU GPL Version 2, as reproduced in section 8.2.28.1. 8.2.3 BusyBox BusyBox by BusyBox.net is covered by the GNU GPL Version 2, as reproduced in section 8.2.28.1. 8.2.4 cramfs cramfs by SourceForge(cramfs) is covered by the GNU GPL Version 2, as reproduced in section 8.2.28.1.
nano3GAP Installation Manual Appendices © ip.access Ltd Page 26 8.2.5 dropbear dropbear by Matt Johnston (http://matt.ucc.asn.au/dropbear/dropbear.html) is covered by various MIT-type licenses. See the file "LICENSE" in the source package. 8.2.6 glibc glibc by Code Sourcery is covered by LGPL v2.1, as reproduced in section 8.2.28.2. 8.2.7 gmp gmp by GNU is covered by LGPL v2.1, as reproduced in section 8.2.28.2. 8.2.8 ipkg ipkg by Handhelds.org is covered by the GNU GPL Version 2, as reproduced in section 8.2.28.1. 8.2.9 iproute2 iproute2 by The Linux Foundation (osdl.org) is covered by the GNU GPL Version 2, as reproduced in section 8.2.28.1. 8.2.10 iptables iptables by Netfilrter is covered by GNU GPL Version 2, as reproduced in section 8.2.28.1. 8.2.11 libcurl libcurl by cURL is covered by an MIT-type license: COPYRIGHT AND PERMISSION NOTICE Copyright (c) 1996 - 2009, Daniel Stenberg, <daniel@haxx.se>. All rights reserved. Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder.
nano3GAP Installation Manual Appendices © ip.access Ltd Page 27 8.2.12 libgcc libgcc by Code Sourcery is covered by GPL v2 with “run-time exception”: See the gcc/libgcc2.c header in the source package. 8.2.13 libpcap libpcap by tcpdump.org is covered by an BSD-type license. See the file "LICENSE" in the source package. 8.2.14 libxml2 libxml by xmlsoft.org is covered by the MIT license: The MIT License Copyright (c) <year> <copyright holders> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 8.2.15 Linux Kernel The Linux Kernel by kernel.org is covered by the GNU GPL Version 2, as reproduced in section 8.2.28.1. 8.2.16 mtd.utils mtd.utils by MTD (http://www.linux-mtd.infradead.org/index.html) is covered by the GNU GPL Version 2, as reproduced in section 8.2.28.1.
nano3GAP Installation Manual Appendices © ip.access Ltd Page 28 8.2.17 ncurses ncurses by GNU is covered by an MIT-type license. See the header of the file "curses.h.in" in the source package. 8.2.18 NTP daemon NTP daemon by NTP.org is covered by the NTP.org license. Copyright (c) University of Delaware 1992-2009 Permission to use, copy, modify, and distribute this software and its documentation for any purpose with or without fee is hereby granted, provided that the above copyright notice appears in all copies and that both the copyright notice and this permission notice appear in supporting documentation, and that the name University of Delaware not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. The University of Delaware makes no representations about the suitability this software for any purpose. It is provided "as is" without express or implied warranty. 8.2.19 pcre pcre by pcre.org is covered by a BSD-type license. PCRE LICENCE ------------ PCRE is a library of functions to support regular expressions whose syntaxand semantics are as close as possible to those of the Perl 5 language. Release 7 of PCRE is distributed under the terms of the "BSD" licence, asspecified below. The documentation for PCRE, supplied in the "doc" directory, is distributed under the same terms as the software itself. The basic library functions are written in C and are freestanding. Also included in the distribution is a set of C++ wrapper functions. THE BASIC LIBRARY FUNCTIONS --------------------------- Written by: Philip Hazel Email local part: ph10 Email domain: cam.ac.uk University of Cambridge Computing Service, Cambridge, England. Copyright (c) 1997-2009 University of Cambridge All rights reserved.
nano3GAP Installation Manual Appendices © ip.access Ltd Page 29 THE C++ WRAPPER FUNCTIONS ------------------------- Contributed by: Google Inc. Copyright (c) 2007-2008, Google Inc. All rights reserved. THE "BSD" LICENCE ----------------- Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the University of Cambridge nor the name of Google Inc. nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. End
nano3GAP Installation Manual Appendices © ip.access Ltd Page 30 8.2.20 procps procps by SourceForge(procps) is covered by the GPL v2 and LGPL v2 licenses as reproduced in section 8.2.28.1 and in section 8.2.28.2, respectively. 8.2.21 SSL Stack SSL Stack by openssl.org is covered by the OpenSSL license, as reproduced in section 8.2.28.3. 8.2.22 StrongSwan StrongSwan by StrongSwan.org is covered mainly by GNU GPL Version 2.as reproduced in section 8.2.28.1. Some code is covered by the OpenSSL license (see section 8.2.28.3), and some under a BSD-type license. StrongSwan license Except for the DES library, MD2 and MD5 code, the PKCS#11 headers, and the FIPS_canister code this software is under the GNU Public License, see the file COPYING. See the file CREDITS for details on origins of more of the code. The DES library is under a BSD style license, see src/libcrypto/libdes/COPYRIGHT. Note that this software has a advertising clause in it. The MD2 implementation is from RSA Data Security Inc., so this package must include the following phrase: "RSA Data Security, Inc. MD2 Message Digest Algorithm" It is not under the GPL; see details in src/pluto/md2.c. The MD5 implementation is from RSA Data Security Inc., so this package must include the following phrase: "derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm". It is not under the GPL; see details in src/pluto/md5.c The PKCS#11 header files in src/pluto/rsaref/ are from RSA Security Inc., so they must include the following phrase: "RSA Security Inc. PKCS#11 Cryptographic Token Interface (Cryptoki)". The headers are not under the GPL; see details in src/pluto/rsaref/pkcs11.h. In addition to the terms set out under the GPL, permission is granted to link the software against the libdes, MD2, and MD5 libraries just mentioned. 8.2.23 TCL TCL by SoundForge(tcl) is covered by a BSD-type license: This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation, and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files. The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any purpose, provided that existing copyright notices
nano3GAP Installation Manual Appendices © ip.access Ltd Page 31 are retained in all copies and that this notice is included verbatim in any distributions. No written agreement, license, or royalty fee is required for any of the authorized uses. Modifications to this software may be copyrighted by their authors and need not follow the licensing terms described here, provided that the new terms are clearly indicated on the first page of each file where they apply. IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. GOVERNMENT USE: If you are acquiring this software on behalf of the U.S. government, the Government shall have only "Restricted Rights" in the software and related documentation as defined in the Federal Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you are acquiring the software on behalf of the Department of Defense, the software shall be classified as "Commercial Computer Software" and the Government shall have only "Restricted Rights" as defined in Clause 252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the authors grant the U.S. Government and others acting in its behalf permission to use and distribute the software in accordance with the terms specified in this license. 8.2.24 tcpdump tcpdump by tcpdump.org is covered by a BSD-type license. See the file "LICENSE" in the source package. 8.2.25 thttpd thttpd by ACME Laboratories is covered by a BSD-type license. See the header of the file "thttpd.c" in the source package. 8.2.26 U-Boot U-Boot by DENX is covered by GNU GPL Version 2, as reproduced in section 8.2.28.1. 8.2.27 zlib zlib by zlib.net is covered by the zlip license:. 8.2.28 General Licenses The licenses reproduced here are referenced by more than one product, as in the preceding sections.
nano3GAP Installation Manual Appendices © ip.access Ltd Page 32 8.2.28.1 GNU GPL Version 2 GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
nano3GAP Installation Manual Appendices © ip.access Ltd Page 33 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
nano3GAP Installation Manual Appendices © ip.access Ltd Page 34 In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any
nano3GAP Installation Manual Appendices © ip.access Ltd Page 35 further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
nano3GAP Installation Manual Appendices © ip.access Ltd Page 36 LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS 8.2.28.2 GNU LGPL v2.1 GNU Lesser General Public License Version 2.1, February 1999 Copyright (C) 1991, 1999 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. [This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.] Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This license, the Lesser General Public License, applies to some specially designated software packages--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below. When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive
nano3GAP Installation Manual Appendices © ip.access Ltd Page 37 source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things. To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it. For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights. We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library. To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others. Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license. Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs. When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library. We call this license the "Lesser" General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances. For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License.
nano3GAP Installation Manual Appendices © ip.access Ltd Page 38 In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system. Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library. The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run. TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you". A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables. The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".) "Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does. 1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
nano3GAP Installation Manual Appendices © ip.access Ltd Page 39 2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) The modified work must itself be a software library. b) You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change. c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License. d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful. (For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library. In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices. Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy. This option is useful when you wish to copy part of the code of the Library into a program that is not a library.
nano3GAP Installation Manual Appendices © ip.access Ltd Page 40 4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange. If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code. 5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables. When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law. If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.) Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself. 6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things: a) Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the
nano3GAP Installation Manual Appendices © ip.access Ltd Page 41 Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.) b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with. c) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution. d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place. e) Verify that the user has already received a copy of these materials or that you have already sent this user a copy. For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute. 7. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above. b) Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work. 8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under
nano3GAP Installation Manual Appendices © ip.access Ltd Page 42 this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 9. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it. 10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License. 11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
nano3GAP Installation Manual Appendices © ip.access Ltd Page 43 13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation. 14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Libraries If you develop a new library, and you want it to be of the greatest possible use to the public, we recommend making it free software that everyone can redistribute and change.
nano3GAP Installation Manual Appendices © ip.access Ltd Page 44 You can do so by permitting redistribution under these terms (or, alternatively, under the terms of the ordinary General Public License). To apply these terms, attach the following notices to the library. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the library's name and an idea of what it does.> Copyright (C) <year> <name of author> This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Also add information on how to contact you by electronic and paper mail. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a library for tweaking knobs) written by James Random Hacker. signature of Ty Coon, 1 April 1990 Ty Coon, President of Vice That's all there is to it! 8.2.28.3 OpenSSL License LICENSE ISSUES The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org. OpenSSL License Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
nano3GAP Installation Manual Appendices © ip.access Ltd Page 45 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)" 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org. * 5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project. * 6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)" THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ==================================================================== This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com). Original SSLeay License Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) All rights reserved. This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was written so as to conform with Netscapes SSL. This library is free for commercial and non-commercial use as long as the following conditions are aheared to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
nano3GAP Installation Manual Appendices © ip.access Ltd Page 46 Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: "This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)" The word 'cryptographic' can be left out if the rouines from the library being used are not cryptographic related :-). 4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)" THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The licence and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence.]

Navigation menu